EP4584992A1 - Schicht 1 / schicht 2 basierte mobilitätsverbesserung - Google Patents

Schicht 1 / schicht 2 basierte mobilitätsverbesserung

Info

Publication number
EP4584992A1
EP4584992A1 EP23790462.8A EP23790462A EP4584992A1 EP 4584992 A1 EP4584992 A1 EP 4584992A1 EP 23790462 A EP23790462 A EP 23790462A EP 4584992 A1 EP4584992 A1 EP 4584992A1
Authority
EP
European Patent Office
Prior art keywords
base station
wireless device
message
mobility
cell
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
EP23790462.8A
Other languages
English (en)
French (fr)
Inventor
Jian Xu
Kyungmin Park
Esmael Hejazi Dinan
Sungduck Chun
Stanislav Filin
Peyman TALEBI FARD
Weihua Qiao
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 EP4584992A1 publication Critical patent/EP4584992A1/de
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists

Definitions

  • FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.
  • 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. 10A illustrates three carrier aggregation configurations with two component carriers.
  • FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.
  • FIG. 11A illustrates an example of an SS/PBCH block structure and location.
  • FIG. 11B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.
  • FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.
  • FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.
  • FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.
  • FIG. 14B illustrates an example of a COE-to-REG mapping for DOI transmission on a CORESET and PDCCH processing.
  • FIG. 15 illustrates an example of a wireless device in communication with a base station.
  • FIG. 16A, FIG. 16B, FIG. 160, and FIG. 16D illustrate example structures for uplink and downlink transmission.
  • FIG. 17A, and FIG. 17B are diagrams of an example multi connectivity as per an aspect of an embodiment of the present disclosure.
  • FIG. 18 is an example diagram of an aspect of an embodiment of the present disclosure.
  • FIG. 19 is an example diagram of an aspect of an embodiment of the present disclosure.
  • FIG. 21 is an example diagram of an aspect of an embodiment of the present disclosure.
  • FIG. 22 is an example diagram of an aspect of an embodiment of the present disclosure.
  • FIG. 24 is an example diagram of an aspect of an embodiment of the present disclosure.
  • Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies).
  • this disclosure may refer to a subset of the total wireless devices in a coverage area.
  • This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station.
  • the plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like.
  • There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.
  • a and B are sets and every element of A is an element of B, A is called a subset of B.
  • A is called a subset of B.
  • possible subsets of B ⁇ celH , cell2 ⁇ are: ⁇ celH ⁇ , ⁇ cell2 ⁇ , and ⁇ celH , cell2 ⁇ .
  • the phrase “based on” is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
  • 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 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.
  • the ON 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 ON 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.
  • wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable.
  • a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle road side unit (RSU), relay node, automobile, and/or any combination thereof.
  • the term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and/or wireless communication device.
  • the RAN 104 may include one or more base stations (not shown).
  • the term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and/or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and/or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and/or 5G standards), an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard), and/or any combination thereof.
  • a base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).
  • PBOH physical broadcast channel
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • PRACH physical random access channel
  • the physical layer Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer.
  • the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.
  • FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same/similar first four protocol layers as the example NR user plane protocol stack.
  • These four protocol layers include the PHYs 211 and 221 , the MAGs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224.
  • 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 RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and/or NAS message transfer.
  • RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.
  • 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.
  • An RRC state may be associated with a mobility management mechanism.
  • RRC idle 604 and RRC inactive 606 mobility is managed by the UE through cell reselection.
  • the purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network.
  • the mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network.
  • the mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).
  • RAI RAN area identifier
  • TAI tracking area and identified by a tracking area identifier
  • Tracking areas may be used to track the UE at the CN level.
  • the CN e.g., the CN 102 or the 5G-CN 152 may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the ON to allow the ON to update the UE’s location and provide the UE with a new the UE registration area.
  • RAN areas may be used to track the UE at the RAN level.
  • the UE may be assigned a RAN notification area.
  • a RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs.
  • a base station may belong to one or more RAN notification areas.
  • a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE’s RAN notification area.
  • a base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station.
  • An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and/or during a period of time that the UE stays in RRC inactive 606.
  • a gNB such as gNBs 160 in FIG. 1 B, may be split in two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU).
  • a gNB-CU may be coupled to one or more gNB-DUs using an F1 interface.
  • the gNB-CU may comprise the RRC, the PDCP, and the SDAP.
  • a gNB-DU may comprise the RLC, the MAC, and the PHY.
  • OFDM orthogonal frequency divisional multiplexing
  • FAM frequency divisional multiplexing
  • M-QAM M-quadrature amplitude modulation
  • M-PSK M-phase shift keying
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols
  • the IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers.
  • the output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers.
  • the F time-domain samples may form a single OFDM symbol.
  • an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency.
  • the F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block.
  • This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR).
  • DFT Discrete Fourier Transform
  • PAPR peak to average power ratio
  • Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.
  • FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.
  • An NR frame may be identified by a system frame number (SFN).
  • the SFN may repeat with a period of 1024 frames.
  • one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration.
  • a subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.
  • the duration of a slot may depend on the numerology used for the OFDM symbols of the slot.
  • a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range).
  • a numerology may be defined in terms of subcarrier spacing and cyclic prefix duration.
  • subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz
  • cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps.
  • NR defines numerologies with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 ps; 30 kHz/2.3 ps; 60 kHz/1.2 ps; 120 kHz/0.59 ps; and 240 kHz/0.29 ps.
  • a slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).
  • a numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe.
  • FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration).
  • a subframe in NR may be used as a numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled.
  • scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.
  • FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.
  • the slot includes resource elements (REs) and resource blocks (RBs).
  • An RE is the smallest physical resource in NR.
  • An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8.
  • An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8.
  • Such a limitation may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.
  • FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier.
  • multiple numerologies may be supported on the same carrier.
  • 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.
  • 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 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.
  • the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322.
  • the UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI.
  • the UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and/or the RAR comprises a MAC sub-PDU with the preamble identifier.
  • the UE may determine the response as an indication of an acknowledgement for an SI request.
  • FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE.
  • the configuration message 1330 may be analogous in some respects to the configuration message 1310 and/or the configuration message 1320.
  • the procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.
  • Msg A 1331 may be transmitted in an uplink transmission by the UE.
  • Msg A 1331 may comprise one or more transmissions of a preamble 1341 and/or one or more transmissions of a transport block 1342.
  • the UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and/or unlicensed spectrum.
  • the UE may determine, based on one or more factors, whether to initiate the two-step random access procedure.
  • the one or more factors may be: a radio access technology in use (e.g., LTE, NR, and/or the like); whether the UE has valid TA or not; a cell size; the UE’s RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and/or any other suitable factors.
  • the UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and/or an uplink transmit power for the preamble 1341 and/or the transport block 1342 included in the Msg A 1331.
  • the RACH parameters may indicate a modulation and coding schemes (MOS), a time-frequency resource, and/or a power control for the preamble 1341 and/or the transport block 1342.
  • a time-frequency resource for transmission of the preamble 1341 e.g., a PRACH
  • a time-frequency resource for transmission of the transport block 1342 e.g., a PUSCH
  • the RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and/or receiving Msg B 1332.
  • the transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and/or device information (e.g., an International Mobile Subscriber Identity (I MSI)).
  • the base station may transmit the Msg B 1332 as a response to the Msg A 1331.
  • the Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and/or an MCS); a UE identifier for contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).
  • RNTI e.g., a C-RNTI or a TC-RNTI
  • 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 (PDCOH).
  • the payload transmitted on the PDCCH may be referred to as downlink control information (DOI).
  • the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.
  • a base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors.
  • CRC cyclic redundancy check
  • the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits.
  • the identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).
  • RNTI radio network temporary identifier
  • DCIs may be used for different purposes.
  • a purpose may be indicated by the type of RNTI used to scramble the CRC parity bits.
  • a DCI having CRC parity bits scrambled with a paging RNTI may indicate paging information and/or a system information change notification.
  • the P-RNTI may be predefined as “FFFE” in hexadecimal.
  • a DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information.
  • SI-RNTI may be predefined as “FFFF” in hexadecimal.
  • RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and/or the like.
  • CS-RNTI Configured Scheduling RNTI
  • TPC-PUCCH-RNTI Transmit Power Control-PUSCH RNTI
  • TPC-SRS-RNTI Transmit Power Control-SRS RNTI
  • INT-RNTI Interruption RNTI
  • the base station may transmit the DCIs with one or more DCI formats.
  • DCI format 0_0 may be used for scheduling of PUSCH in a cell.
  • DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads).
  • DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0).
  • DCI format 1_0 may be used for scheduling of PDSCH in a cell.
  • DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads).
  • DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0).
  • DCI format 2_0 may be used for providing a slot format indication to a group of UEs.
  • DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and/or OFDM symbol where the UE may assume no transmission is intended to the UE.
  • DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH.
  • DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs.
  • DCI format(s) for new functions may be defined in future releases.
  • DCI formats may have different DCI sizes, or may share the same DCI size.
  • the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and/or QPSK modulation.
  • a base station may map the coded and modulated DCI on resource elements used and/or configured for a PDCCH. Based on a payload size of the DOI and/or a coverage of the base station, the base station may transmit the DOI via a PDCCH occupying a number of contiguous control channel elements (CCEs).
  • the number of the contiguous CCEs (referred to as aggregation level) may be 1 , 2, 4, 8, 16, and/or any other suitable number.
  • a CCE may comprise a number (e.g., 6) of resource-element groups (REGs).
  • REG may comprise a resource block in an OFDM symbol.
  • the mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).
  • FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.
  • the base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs).
  • a CORESET may comprise a timefrequency resource in which the UE tries to decode a DCI using one or more search spaces.
  • the base station may configure a CORESET in the time-frequency domain.
  • a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot.
  • the first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain.
  • a third CORESET 1403 occurs at a third symbol in the slot.
  • a fourth CORESET 1404 occurs at the seventh symbol in the slot.
  • CORESETs may have a different number of resource blocks in frequency domain.
  • 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 CCEs at a given aggregation level.
  • the configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and/or whether a search space set is a common search space set or a UE- specific search space set.
  • a set of CCEs in the common search space set may be predefined and known to the UE.
  • a set of CCEs in the UE-specific search space set may be configured based on the UE’s identity (e.g., C-RNTI).
  • the UE may determine a time-frequency resource for a CORESET based on RRC messages.
  • the UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and/or mapping parameters) for the CORESET based on configuration parameters of the CORESET.
  • the UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages.
  • the UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set.
  • the UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs.
  • Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DOI formats. Monitoring may comprise decoding a DOI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g. , number of CCEs, number of PDCCH candidates in common search spaces, and/or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats.
  • the decoding may be referred to as blind decoding.
  • the UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value).
  • the UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and/or the like).
  • the UE may transmit an SR indicating that uplink data is available for transmission to the base station.
  • the UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
  • HARQ-ACK HARQ acknowledgements
  • CSI report CSI report
  • SR SR
  • the UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.
  • PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits.
  • the UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is one or two.
  • PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits.
  • the UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK/SR bits is one or two.
  • PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits.
  • the UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more.
  • PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits.
  • the UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code.
  • PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.
  • the base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message.
  • the plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell.
  • a PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g. , pucch-Resourceid), and/or a number (e.g. a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set.
  • a PUCCH resource identifier e.g. , pucch-Resourceid
  • the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ- ACK, SR, and/or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to “1”.
  • a total bit length of the UCI information bits e.g., HARQ- ACK, SR, and/or CSI.
  • the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.
  • the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and/or SR) transmission.
  • the UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH.
  • a three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set.
  • the UE may transmit the UCI (HARQ- ACK, CSI and/or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.
  • FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure.
  • the wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1 B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and/or more than one base station, with the same or similar configuration as those shown in FIG. 15.
  • the base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506.
  • the communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink.
  • Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and/or some combination of the two duplexing techniques.
  • data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504.
  • the data may be provided to the processing system 1508 by, for example, a core network.
  • data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502.
  • the processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission.
  • Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.
  • Layer 3 may include an RRC layer as with respect to FIG. 2B.
  • the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504.
  • the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502.
  • the transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality.
  • Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.
  • the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and/or the like.
  • a reception processing system 1512 may receive the uplink transmission from the wireless device 1502.
  • a reception processing system 1522 may receive the downlink transmission from base station 1504.
  • the reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality.
  • Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.
  • the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, 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 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and/or the processing system 1518 to carry out one or more of the functionalities discussed in the present application.
  • the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and/or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.
  • the processing system 1508 and/or the processing system 1518 may comprise one or more controllers and/or one or more processors.
  • the one or more controllers and/or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, an on-board unit, or any combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the processing system 1508 and/or the processing system 1518 may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.
  • the processing system 1508 and/or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively.
  • the one or more peripherals 1516 and the one or more peripherals 1526 may include software and/or hardware that provide features and/or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and/or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and/or the like).
  • sensors e.g., an accelerometer, a gyroscope, a temperature sensor, a
  • the processing system 1508 and/or the processing system 1518 may receive user input data from and/or provide user output data to the one or more peripherals 1516 and/or the one or more peripherals 1526.
  • the processing system 1518 in the wireless device 1502 may receive power from a power source and/or may be configured to distribute the power to the other components in the wireless device 1502.
  • the power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof.
  • the processing system 1508 and/or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively.
  • the GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.
  • FIG. 16A illustrates an example structure for uplink transmission.
  • a baseband signal representing a physical uplink shared channel may perform one or more functions.
  • the one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP- OFDM signal for an antenna port; and/or the like.
  • SC-FDMA Single Carrier-Frequency Division Multiple Access
  • FIG. 16A illustrates an example structure for uplink transmission.
  • FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency.
  • the baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.
  • PRACH Physical Random Access Channel
  • FIG. 16C illustrates an example structure for downlink transmissions.
  • a baseband signal representing a physical downlink channel may perform one or more functions.
  • the one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complexvalued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued timedomain OFDM signal for an antenna port; and/or the like.
  • These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.
  • FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency.
  • the baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.
  • a wireless device may receive from a base station one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g. primary cell, secondary cell).
  • the wireless device may communicate with at least one base station (e.g. two or more base stations in dual-connectivity) via the plurality of cells.
  • the one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device.
  • the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc.
  • the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels.
  • a timer may begin running once it is started and continue running until it is stopped or until it expires.
  • a timer may be started if it is not running or restarted if it is running.
  • a timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value).
  • the duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching).
  • a timer may be used to measure a time period/window for a process.
  • a timer may be used to measure a time period/window for the procedure.
  • a random access response window timer may be used for measuring a window of time for receiving a random access response.
  • the time difference between two time stamps may be used.
  • a timer is restarted, a process for measurement of time window may be restarted.
  • Other example implementations may be provided to restart a measurement of a time window.
  • FIG. 17A and FIG. 17B show packet flows employing a multi connectivity (e.g. dual connectivity, multi connectivity, tight interworking, and/or the like).
  • FIG. 17A is an example diagram of a protocol structure of a wireless device 170 (e.g. UE) with GA and/or multi connectivity as per an aspect of an embodiment.
  • FIG. 17B is an example diagram of a protocol structure of multiple base stations with CA and/or multi connectivity as per an aspect of an embodiment.
  • the multiple base stations may comprise a master node, MN 1730 (e.g. a master node, a master base station, a master g N B, a master eNB, and/or the like) and a secondary node, SN 1750 (e.g. a secondary node, a secondary base station, a secondary gNB, a secondary eNB, and/or the like).
  • MN 1730 e.g. a master node, a master base station, a master g N B, a master eNB, and/or the like
  • SN 1750 e.g. a secondary node, a secondary base station, a secondary gNB,
  • the wireless device 170 When multi connectivity is configured for a wireless device 170 (e.g., via an RRC reconfiguration message), the wireless device 170, which may support multiple reception/transmission functions in an RRC connected state, may be configured to utilize radio resources provided by multiple schedulers of a multiple base stations. Multiple base stations may be inter-connected via a non-ideal or ideal backhaul (e.g. Xn interface, X2 interface, and/or the like).
  • a base station involved in multi connectivity for a certain wireless device may perform at least one of two different roles: a base station may either act as a master base station or as a secondary base station.
  • a wireless device In multi connectivity, a wireless device may be connected to one master base station and one or more secondary base stations.
  • a master base station may provide a master cell group (MCG) comprising a primary cell and/or one or more secondary cells for a wireless device (e.g. the wireless device 170).
  • MCG master cell group
  • a secondary base station e.g. the SN 1750
  • SCG secondary cell group
  • PSCell primary secondary cell
  • SCG secondary cell group
  • a radio protocol architecture that a bearer employs may depend on how a bearer is setup.
  • three different type of bearer setup options may be supported: an MCG bearer, an SCG bearer, and/or a split bearer.
  • a wireless device may receive/transmit packets of an MCG bearer via one or more cells of the MCG, and/or may receive/transmits packets of an SCG bearer via one or more cells of an SCG.
  • Multi-connectivity may also be described as having at least one bearer configured to use radio resources provided by the secondary base station. Multi-connectivity may or may not be configured/implemented in some of the example embodiments.
  • a wireless device may transmit and/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP 1710), a PDCP layer (e.g. NRPDCP 1711), an RLC layer (e.g. MN RLC 1714), and a MAC layer (e.g. MN MAC 1718); packets of a split bearer via an SDAP layer (e.g. SDAP 1710), a PDCP layer (e.g. NR PDCP 1712), one of a master or secondary RLC layer (e.g. MN RLC 1715, SN RLC 1716), and one of a master or secondary MAC layer (e.g.
  • SDAP layer e.g. SDAP 1710
  • a PDCP layer e.g. NRPDCP 1711
  • RLC layer e.g. MN RLC 1714
  • a MAC layer e.g. MN MAC 1718
  • MN MAC 1718, SN MAC 1719 MN MAC 1718, SN MAC 1719
  • packets of an SCG bearer via an SDAP layer e.g. SDAP 1710
  • a PDCP layer e.g. NR PDCP 1713
  • an RLC layer e.g. SN RLC 1717
  • a MAC layer e.g. MN MAC 1719
  • a master base station and/or a secondary base station may maintain RRM measurement configurations of a wireless device; a master base station may (e.g. based on received measurement reports, traffic conditions, and/or bearer types) may decide to request a secondary base station to provide additional resources (e.g.
  • An MN may decide to request a target SN to allocate resources for one or more specific PDU Sessions/QoS Flows, indicating QoS Flows characteristics (e.g., QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info, etc.).
  • QoS Flows characteristics e.g., QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info, etc.
  • QoS Flows characteristics e.g., QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info, etc.
  • QoS Flows characteristics e.g., QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info, etc.
  • An MN may indicate requested SCG configuration information, comprising UE capabilities and/or UE capability coordination results.
  • An MN may provide measurement results for an
  • an MN may provide Xn-U uplink (UL) tunnel (TNL) address information.
  • UL uplink
  • TNL tunnel
  • an MN may provide a list of available DRB IDs.
  • An S-NG-RAN node e.g., SN
  • An S-NG-RAN node may store this information and/or use it when establishing SN terminated bearers.
  • An SN may reject the request.
  • an MCG and/or an SCG resources may be requested of an amount that QoS for a respective QoS Flow is guaranteed by a sum of resources provided by the MCG and the SCG together, or more.
  • an MN decision may be reflected by QoS Flow parameters signaled to an SN, which may differ from QoS Flow parameters received via an NG interface.
  • an MN may request a direct establishment of an SCG and/or split bearers, e.g., without first having to establish MCG bearers. It may be allowed that QoS flows are mapped to SN terminated bearers (e.g., there is no QoS flow mapped to an MN terminated bearer).
  • an RRM entity of an SN may allocate respective radio resources and/or respective transport network resources (e.g., dependent on bearer type options).
  • an SN may trigger UE Random Access so that synchronization of an SN radio resource configuration is performed.
  • An SN may decide for a PSCell and/or other SCG SCells.
  • An SN may provide an SCG radio resource configuration to an MN within an SN RRC configuration message contained in an SN Addition Request Acknowledge message.
  • the SN may provide Xn-U TNL address information for a respective DRB, Xn-U UL TNL address information for SN terminated bearers, Xn-U DL TNL address information for MN terminated bearers, and/or the like.
  • an SN may provide NG-U DL TNL address information for a respective PDU Session and security algorithm. If SOG radio resources have been requested, an SCG radio resource configuration may be provided.
  • MN terminated bearers transmission of user plane data may take place.
  • data forwarding and/or an SN Status Transfer may take place.
  • an MN may allocate up to 4 separate Xn-U bearers and an SN may provide a logical channel ID for primary or split secondary path to the MN.
  • an SN may allocate up to 4 separate Xn-U bearers and/or an MN may provide a logical channel ID for primary or split secondary path to the SN via an additional MN-initiated SN modification procedure.
  • a UE may apply new configurations and/or reply to an MN with an MN RRC reconfiguration complete message, which may comprise an SN RRC response message for SN, if needed.
  • an MN RRC reconfiguration complete message which may comprise an SN RRC response message for SN, if needed.
  • the UE may perform a reconfiguration failure procedure.
  • An MN may inform an SN that a UE has completed a reconfiguration procedure successfully via an SN Reconfiguration Complete message, which may comprise an SN RRC response message, if received from the UE.
  • a UE may perform synchronization towards a PSCell configured by an SN.
  • the order that a UE sends an MN RRC reconfiguration complete message and/or performs a Random Access (RA) procedure towards a SCG may not be fixed.
  • a successful RA procedure towards an SCG may not be required for a successful completion of an RRC Connection Reconfiguration procedure.
  • an MN may send an SN Status Transfer.
  • the MN may take actions to reduce service interruption due to activation of MR-DC (Data forwarding). If applicable, an update of an UP path towards a 5GC may be performed via a PDU Session Path Update procedure.
  • a serving cell change may need to be performed.
  • Serving cell change may be triggered by layer 3 (L3) measurements and may be done via RRC signalling, which may be triggered via RRC reconfiguration with synchronization for change of PCell and PSCell, as well as release add for SCells when applicable.
  • L3 layer 3
  • RRC signalling which may be triggered via RRC reconfiguration with synchronization for change of PCell and PSCell, as well as release add for SCells when applicable.
  • the cases above may involve complete layer 2 (L2) and/or layer 1 (L1) resets, leading to longer latency, larger overhead and longer interruption time than beam switch mobility.
  • L1/L2 based mobility via L1/L2 signaling may reduce the latency, overhead and interruption time.
  • inter-cell beam level mobility may be used, in which the lower layer function entity (e.g., distribute unit (DU)) of base station may trigger beam managements by means of physical layer and MAC layer control signaling, and the wireless device may receive or transmit UE dedicated channels/sign als via a TRP associated with another cell without serving cell change.
  • the lower layer function entity e.g., distribute unit (DU)
  • DU distribute unit
  • L1/L2-based mobility may be a procedure in which a base station may receive L1 measurement reports from UEs, and relying on which the base station may change UEs’ serving cell(s) through on L1/L2 signaling.
  • the base station may prepare one or multiple candidate target cells and provide the candidate target cell configurations to the UE.
  • L1/L2 based mobility may refer to a handover that a wireless device triggers (e.g., perform and/or initiate) in response to receiving L1/L2 signaling.
  • the L1/L2 signaling may comprise at least one of layer 1 (e.g., Physical layer) signal (e.g., DOI and/or UCI) and/or a layer 2 (e.g., MAC layer) signal (e.g., MAC CE and/or MAC subheader).
  • the L1/L2 based mobility may comprise a procedure that the wireless device receives, from a network (e.g., a serving cell or a serving base station), at least two signals (e.g., at least two control signals/messages).
  • the at least two signals may comprise an L3 signaling (e.g., an RRC message and/or SIB) comprising configuration parameters of the L1/L2 based mobility.
  • the configuration parameters may be semi-statical ly pre-configured for the handover triggered by the L1/L2 signaling.
  • the at least two signals may comprise the L1/L2 signaling that triggers (e.g., performs and/or initiates) the L1/L2 based mobility.
  • a wireless device may receive, from a network (e.g., a serving cell, a service base station, a serving DU, and/or a serving CU), one or more messages (e.g., RRC message and/or SIB) comprising parameters used for the L1/L2 based mobility.
  • a network e.g., a serving cell, a service base station, a serving DU, and/or a serving CU
  • the wireless device may receive, via a source cell (e.g., current serving cell) of the network, the one or more messages.
  • the one or more messages may comprise one or more handover configurations (e.g., comprising parameters used for the L1/L2 based mobility).
  • each of the one or more handover configurations may be associated with a respective handover and/or be associated with a respective target cell.
  • a handover configuration (that is associated with a respective target cell) of the one or more handover configuration may comprise configuration parameters of L1/L2 based mobility to the respective target cell.
  • the configuration parameters comprise: an identifier of the respective target cell; and/or an indication indicating that the respect handover corresponding to the configuration parameters is triggered (or initiated) by the L1/L2 signaling.
  • the wireless device may monitor downlink transmission occasions (e.g., PDCCH and/or PDSCH) of the source cell.
  • the wireless device may receive the L1/L2 signaling via the downlink transmission occasions.
  • the L1/L2 signaling may comprise a DOI with a particular format that the wireless device detects/receives via the downlink transmission occasion (e.g., PDCCH).
  • the L1/L2 signaling may comprise an MAC CE that the wireless device receives, decodes, and/or parses from a PDSCH that is scheduled by a DCI (or a PDCCH) received via the downlink transmission occasions.
  • the L1/L2 signaling may comprise an indication indicating one of the one or more handover configurations that are received, configured, and/or indicated by the one or more messages (e.g., RRC message and/or SIB).
  • the indication indicating a first handover configuration of the one or more handover configurations.
  • the indication may comprise an identifier of the first handover configuration.
  • the indication may be a configuration ID of the first handover configuration.
  • the indication may comprise an identifier of a target cell respective to the first handover configuration.
  • the wireless device may perform and/or execute, in response to receiving the L1/L2 signaling, the handover (e.g., L1/L2 based mobility) to the target cell using configuration parameters of the first handover configuration.
  • a network may determine to perform (e.g., trigger and/or initiate) L1/L2 based mobility, e.g., after or in response to transmitting the one or more handover configurations to the wireless device.
  • the network may determine when to transmit, to the wireless device, the L1/L2 signaling to perform (e.g., trigger and/or initiate) L1/L2 based mobility, e.g., after or in response to transmitting the one or more handover configurations to the wireless device.
  • the wireless device may transmit, for the network to determine to perform the L1/L2 based mobility, a report comprising one or more measurements (e.g., L1 measurement and/or L3 measurement) of radio channel (s) over which the wireless device receives one or more reference signals from the network.
  • the network may determine to perform (e.g., trigger and/or initiate) L1/L2 based mobility based on the report comprising the one or more measurements.
  • the network may determine, based on the one or more measurements, which cell, among one or more cells configured for L1/L2 based mobility (e.g., as potential target cells for L1/L2 based mobility), is a target cell of the L1/L2 based mobility.
  • the network indicates the target cell using the indicator of the L1/L2 signaling to the wireless device to trigger (e.g., perform and/or initiate) the L1/L2 based mobility.
  • the network may determine, based on the one or more measurements, when to transmit, to the wireless device, the indication of the L1/L2 signaling to trigger (e.g., perform and/or initiate) the L1/L2 based mobility to the target cell.
  • the report may comprise L1 measurement.
  • the L1 measurement may refer to a measurement report generated by a layer 1 (physical layer) and/or transmitted via physical channel(s) (e.g., FIG. 5B).
  • the physical channel(s) may comprise a PUCCH and/or PUSCH.
  • the wireless device may transmit the L1 measurement via PUSCH by piggybacking the PUCCH (e.g., comprising the L1 measurement) onto the PUSCH.
  • the report may comprise L3 measurement.
  • the L3 measurement may refer to a measurement report generated by a layer 3 (RRC layer) and/or transmitted via logical channel(s) (e.g., FIG. 5B).
  • the logical channel(s) may comprise CCCH and/or DCCH.
  • the network may transmit one or more handover configurations for the L1/L2 based mobility for the L1 measurement.
  • the one or more messages (e.g., a handover configuration of the one or more handover configurations) may comprise one or more resource configurations (e.g., CSI-ResourceConfig IE) of one or more reference signals and/or one or more report configurations (e.g., CSI-ReportConfig IE).
  • the one or more resource configurations and/or the one or more report configurations are for the L1 measurement of the L1/L2 based mobility.
  • the one or more resource configurations may indicate the radio resource configuration parameters based on which the wireless device receives the one or more reference signals.
  • the one or more report configurations may indicate parameter(s) and/or value(s) to be contained in the report comprising L1 measurement.
  • Each of the one or more report configurations may be associated with at least one (e.g., downlink) reference signal indicated by the one or more resource configurations.
  • a first reporting configuration of the one or more report configurations may comprise an identifier of at least one reference signal indicated by the one or more resource configurations.
  • the wireless device may transmit a report comprising a measured quantity of the at least one reference signal, e.g., if the report is generated based on the first reporting configuration and/or if the first reporting configuration comprises the identifier of at least one reference signal.
  • BS2 may send/configure, to the wireless device, the candidate target cell list associated with L1/L2-based mobility and the L1/L2-based mobility configurations associated with the candidate target cell list via SRB3, which may be used by the wireless device to facilitate L1/L2-based inter-cell mobility/handover within the cell group (CG) of secondary base station (BS2), i.e., when lower layer (L1/L2) of BS2 indicates the wireless device to perform inter-cell mobility/handover within the cell group (CG) of secondary base station.
  • the inter-cell mobility/handover within the CG of BS2 may be realized with low latency, low overhead and low interruption time for the wireless device.
  • BS1 may provide one or more services to the wireless device. Later, BS1 may configure the wireless device and/or BS2 for dual connectivity as shown in FIG. 17B. Dual connectivity may enable the network to provide the service using radio resources of BS2. In an example, based on dual connectivity being configured, the service may be provided via radio resources of BS1 and radio resources of BS2 (e.g., a first portion of the service is provided by BS1 and a second portion is provided by BS2). In an example, based on dual connectivity being configured, the service may be provided via radio resources of BS2 (e.g., BS1 does not provide the service).
  • the mobility configurations may comprise configuration parameters used for L1 measurement of the L1/L2 based mobility.
  • the configuration parameters may comprise of one or more resource configurations (e.g., CSI-ResourceConfig IE) and/or of one or more report configurations (e.g., CSI-ReportConfig IE) that are used for the L1 measurement.
  • the one or more resource configurations e.g., CSI-ResourceConfig IE
  • one or more report configurations e.g., CSI-ReportConfig IE
  • BS2 may send, to BS1, one or more messages.
  • the one or more messages may be a secondary node (SN) configuration message, and/or a SN modification required message.
  • the one or more messages may be, for example, a single message. It may be understood that the message may have any suitable name.
  • the one or more messages may comprise at least one of an identifier (e.g., MeNB UE X2AP ID, SgNB UE X2AP ID) of the wireless device within eNB or gNB; an identifier (e.g., M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID) of the wireless device within master NG-RAN node or secondary NG-RAN node; and/or the like.
  • an identifier e.g., MeNB UE X2AP ID, SgNB UE X2AP ID
  • M-NG-RAN node UE XnAP ID e.g., M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID
  • the secondary node (SN) configuration may comprise at least one of: a field indicating to configure L1/L2-based mobility, via SRB3, in the second base station for the wireless device, the candidate target cell list associated with the L1/L2-based mobility for the wireless device, the mobility configurations associated with the candidate target cell list for the wireless device, as described above.
  • the candidate target cell list and the mobility configurations may be transmitted by BS2 to the wireless device via the SRB3 of BS2.
  • BS1 may take the candidate target cell list into account for its decisions on L1/L2-based mobility/handover and/or other mobility/handover.
  • BS2 may send to the wireless device, via the SRB3, one or more messages (e.g., RRC message and/or SIB) message comprising at lease one of: the candidate target cell list associated with L1/L2-based mobility via SRB3, the mobility configurations associated with the candidate target cell list for the wireless device, as described above.
  • messages e.g., RRC message and/or SIB
  • the wireless device may store the candidate target cell list associated with L1/L2-based mobility and the mobility configurations associated with the candidate target cell list for the wireless device, as described above, which were sent from BS1 (originally from BS2).
  • the wireless device may interpretate the inter-cell mobility/handover within the CG of BS2 may comprise one or more of handover scenarios, e.g., from a PSOell to another PSOell, from a PSOell to a SCell, from a SCell to a PSOell, from a SCell to another SCell.
  • the wireless device may send to BS2 one or more messages (e.g., RRC reconfiguration complete message). It may be for confirming to BS2 on the completion of the configurations (the candidate target cell list and the mobility configurations) above in the wireless device.
  • BS2 one or more messages (e.g., RRC reconfiguration complete message). It may be for confirming to BS2 on the completion of the configurations (the candidate target cell list and the mobility configurations) above in the wireless device.
  • the wireless device may start, perform, or initiate the L1 measurement according to the configurations (the candidate target cell list and the mobility configurations) received, in which the configuration parameters comprise of: one or more resource configurations (e.g., CSI-ResourceConfig IE); and/or of one or more report configurations (e.g., CSI-ReportConfig IE), e.g., after or in response to receiving the configuration parameters.
  • the wireless device determines (or measures) CQI, Rl, PMI, RSRP, RSRQ, and/or SINR of (or using) one or more reference signals (e.g., CSI-RSs, SSBs, PT-RSs) configured by the one or more resource configurations.
  • the wireless device may generate a report comprising the L1 measurement.
  • the wireless device may determine the contents and/or parameter value(s) contained in the report or the L1 measurement according to a report configuration, of the one or more report configurations, that triggers the transmission of the report.
  • the report may comprise one of more measurement results of: CQI, Rl, PMI, RSRP, RSRQ, and/or SINR of (or using) the one or more reference signals (e.g., CSI-RSs, SSBs, PT-RSs) configured by the one or more resource configurations.
  • the one or more reference signals e.g., CSI-RSs, SSBs, PT-RSs
  • the wireless device may transmit the report (e.g., lower layer measurement report) to BS2.
  • the lower layer functions (L1/L2) of BS2 may determine to perform L1/L2-based mobility (serving cell change), which may comprise one or more cell change/handover scenarios of, e.g., from a PSCell to another PSCell, from a PSCell to a SCell, from a SCell to a PSCell, from a SCell to another SCell.
  • the wireless device may receive, after or in response to transmitting the report, L1/L2 signaling that triggers (or initiates) the L1/L2 based mobility.
  • the L1/L2 signaling may (e.g., DCI and/or MAC CE), as described above.
  • the L1/L2 signaling may comprise an indication/command to notify the wireless device to perform serving cell change.
  • the L1/L2 signaling may comprise the determined target cell identifier.
  • the L1/L2 signaling may comprise one or more cell change/handover scenarios of, e.g., from a PSCell to another PSCell, from a PSCell to a SCell, from a Scell to a PSCell, from a Scell to another Scell.
  • the L1/L2 signaling may comprise the cell identifiers (e.g., PSCell identifier(s), SCell identifier(s)) corresponding to the one or more cell change/handover scenarios, e.g. , from a PSCell to another PSCell, from a PSCell to a SCell, from a SCell to a PSCell, from a SCell to another SCell.
  • the cell identifiers e.g., PSCell identifier(s), SCell identifier(s)
  • the wireless device may perform cell change based on the L1/L2 signaling received above.
  • the cell change may comprise at least one of: from a PSCell to another PSCell, from a PSCell to a SCell, from a SCell to a PSCell, from a SCell to another SCell.
  • the cell change may be to a cell associated with the target cell identifier.
  • the wireless device may send a message (e.g., RRC message and/or random access procedure) notifying/indicating a successful target/serving cell change to BS2.
  • the successful serving cell change may be from an old serving cell of the BS2 to the new target/serving cell.
  • the message may comprise of C-RANTI of the wireless device and/or the new target/serving cell identifier.
  • BS2 may transmit to BS1 one or more messages (e.g., a second SN configuration message) comprising a field indicating the successful L1/L2-based serving cell change.
  • the one or more messages may comprise the serving cell identifier of the new serving cell.
  • the new cell may be a PSCell and/or a SCell.
  • the one or more messages may be, for example, a single message. It may be understood that the message may have any suitable name.
  • the one or more messages may comprise at least one of an identifier (e.g., MeNB UE X2AP ID, SgNB UE X2AP ID) of the wireless device within eNB or gNB; an identifier (e.g., M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID) of the wireless device within master NG-RAN node or secondary NG-RAN node; and/or the like.
  • BS1 may know the cell change which happened in BS2 for the wireless device.
  • BS1 may know location of the wireless device, e.g., via the PSCell identifier.
  • FIG. 24 depicts an example embodiment of the present disclosure.
  • FIG. 24 illustrates two base stations (e.g., a master base station (BS1), a send/secondary base station (BS2)) and a wireless device (UE in FIG. 24).
  • BS1 master base station
  • BS2 send/secondary base station
  • UE wireless device
  • BS2 may receive one or more radio measurement reports (the details may be referred to the description above in FIG. 23) from the wireless device and/or passed from BS1 (e.g., BS1 may receive one or more radio measurement reports from the wireless device). Based on the radio measurement report, BS2 may determine to modify/revise L1/L2-based mobility via a signaling radio bearer 3 (SRB3) within the second base station (BS2) for the wireless device.
  • SRB3 signaling radio bearer 3
  • the L1/L2-based mobility via the SRB3 may comprise of handover for the wireless device within the cell group (CG) of secondary base station (BS2) based on a command from lower layer (L1/L2) of BS2.
  • BS2 may further determine to modify/revise the configurations, which were determined previously, for the wireless device.
  • the modified configurations for the wireless device may comprise at least one of: a field indicating to modify configurations of L1/L2-based mobility via SRB3 in the secondary base station for the wireless device, an updated/modified candidate target cell list associated with the L1/L2-based mobility via SRB3 for the wireless device, updated/modified mobility configurations associated with the updated/modified candidate target cell list for the wireless device, and/or the like.
  • the candidate target cell list and the mobility configurations may be transmitted by BS2 to the wireless device via the SRB3 of BS2.
  • the updated/modified candidate target cell list may be one or more cells from the CG of BS2. Since BS2 may provide the CG comprising a primary secondary cell (PSCell) and/or one or more secondary cells (SCells) for the wireless device, the inter-cell mobility/handover within the CG of BS2 may comprise one or more of handover scenarios, e.g., from a PSCell to another PSCell, from a PSCell to a SCell, from a SCell to a PSCell, from a SCell to another SCell.
  • the updated/modified candidate target cell list may be one or more cells comprising of: one or more candidate PScells, one or more SCells.
  • the updated/modified candidate target cell list may be one or more handover scenarios comprising of: from a PSCell to another PSCell, from a PSCell to a SCell, from a SCell to a PSCell, from a SCell to another SCell.
  • the updated/modified mobility configurations may comprise configuration parameters used for L1 measurement of the L1/L2 based mobility.
  • the configuration parameters may comprise of one or more resource configurations (e.g., CSI- ResourceConfig IE) and/or of one or more report configurations (e.g., CSI-ReportConfig IE) that are used for the L1 measurement.
  • the one or more resource configurations e.g., CSI-ResourceConfig IE
  • one or more report configurations e.g., CSI-ReportConfig IE
  • FIG. 25 depicts an example embodiment of the present disclosure.
  • FIG. 25 illustrates two base stations (e.g., a master base station (BS1), a send/secondary base station (BS2)) and a wireless device (UE in FIG. 25).
  • BS1 master base station
  • BS2 send/secondary base station
  • UE wireless device
  • the wireless device may release the candidate target cell list and/or the mobility configurations associated with L1/L2-based mobility via SRB3 for the wireless device in the secondary base station.
  • the wireless device may release the candidate target cell list and/or the mobility configurations associated with L1/L2-based mobility via SRB3 for the wireless device in the secondary base station.
  • the secondary node (SN) request message may comprise at least one of: a field indicating to configure layer 1 and/or layer 2 (L1/L2)-based mobility, via a signal radio bearer 1 (SRB1) and/or a SRB2, in the secondary base station for the wireless device; the one or more radio measurement reports received from the wireless device, and/or the like.
  • the L1/L2-based mobility may comprise of handover for the wireless device within the cell group (CG) of secondary base station (BS2) based on command from lower layer (L1/L2) of BS2.
  • the DU of BS2 may determine to generate configurations for the wireless device. The determination may be based on the received information, as described above, from the CU of BS2 (e.g., the UE context setup/modification message, and/or content thereof).
  • the configurations for the wireless device may comprise mobility configurations associated with the candidate target cell list for the wireless device.
  • the mobility configurations, associated with the candidate target cell list for the wireless device may comprise configuration parameters used for L1 measurement of the L1/L2 based mobility. The details about the mobility configurations may be referred to the description above in FIG. 23.
  • the CU of BS2 may send to the wireless device, via SRB3, one or more messages (e.g., RRC message and/or SIB) message comprising at least one of: the candidate target cell list associated with L1/L2-based mobility via SRB3, the mobility configurations associated with the candidate target cell list for the wireless device, as described above, which were received from the DU of BS2.
  • messages e.g., RRC message and/or SIB
  • FIG. 27 depicts an example embodiment of the present disclosure.
  • FIG. 27 illustrates two base stations (e.g., a master base station (BS1), a send/secondary base station (BS2)) and a wireless device (UE in FIG. 27).
  • the send/secondary base station (BS2) may comprise of: a central unit (CU) of the send/secondary base station, a source distributed unit 1 (DU1) of the send/secondary base station, a target distributed unit 2 (DU2) of the send/secondary base station.
  • CU central unit
  • DU1 source distributed unit 1
  • DU2 target distributed unit 2
  • the wireless device may start, perform, or initiate the L1 measurement according to the configurations (the candidate target cell list and the mobility configurations) received, in which the configuration parameters comprise of: one or more resource configurations (e.g., CSI-ResourceConfig IE); and/or of one or more report configurations (e.g., CSI-ReportConfig IE), e.g., after or in response to receiving the configuration parameters.
  • the wireless device determines (or measures) CQI, Rl, PMI, RSRP, RSRQ, and/or SINR of (or using) one or more reference signals (e.g., CSI-RSs, SSBs, PT-RSs) configured by the one or more resource configurations.
  • the wireless device may generate a report comprising the L1 measurement.
  • the wireless device may determine the contents and/or parameter value(s) contained in the report or the L1 measurement according to a report configuration, of the one or more report configurations, that triggers the transmission of the report.
  • the report may comprise one of more measurement results of: CQI, Rl, PMI, RSRP, RSRQ, and/or SINR of (or using) the one or more reference signals (e.g., CSI-RSs, SSBs, PT-RSs) configured by the one or more resource configurations.
  • the one or more reference signals e.g., CSI-RSs, SSBs, PT-RSs
  • the wireless device may transmit the report (e.g., lower layer measurement report) to the source DU1 of BS2.
  • the lower layer functions (L1/L2) the source DU1 of BS2 may determine to perform L1/L2-based mobility (serving cell change), which may comprise one or more cell change/handover scenarios of, e.g., from a PSCell to another PSCell, from a PSCell to a SCell, from a Scell to a PSCell, from a Scell to another Scell.
  • the wireless device may receive from the source DU1 of BS2, after or in response to transmitting the report, L1/L2 signaling that triggers (or initiates) the L1/L2 based mobility.
  • the L1/L2 signaling may (e.g., DCI and/or MAC CE), as described above.
  • the L1/L2 signaling may comprise an indication/command/field to notify the wireless device to perform serving cell change.
  • the L1/L2 signaling may comprise the determined target cell identifier.
  • the L1/L2 signaling may comprise one or more cell change/handover scenarios of, e.g., from a PSCell to another PSCell, from a PSCell to a SCell, from a Scell to a PSCell, from a Scell to another Scell.
  • the L1/L2 signaling may comprise the cell identifiers (e.g., PSCell identifier(s), SCell identifier(s)) corresponding to the one or more cell change/handover scenarios, e.g., from a PSCell to another PSCell, from a PSCell to a SCell, from a Scell to a PSCell, from a Scell to another Scell.
  • the wireless device may send to a message (e.g., RRC message and/or random access procedure) notifying/indicating a successful target/serving cell change to the target DU2 of BS2 and/or the source DU1 of BS2.
  • the successful serving cell change may be from an old serving cell of the source DU1 of BS2 to the new target/serving cell of the target DU2 of BS2.
  • the successful serving cell change may be from an old serving cell of the source DU1 of BS2 to the new target/serving cell of the source DU1 of BS2.
  • the message may comprise of C-RANTI of the wireless device and/or the the new target/serving cell identifier.
  • the one or more messages may comprise at least one of an identifier (e.g., MeNB UE X2AP ID, SgNB UE X2AP ID) of the wireless device within eNB or gNB; an identifier (e.g., M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID) of the wireless device within master NG-RAN node or secondary NG-RAN node; and/or the like.
  • BS1 may know the cell change which happened in BS2 for the wireless device.
  • BS1 may know location of the wireless device, e.g., via the PSCell identifier.
  • a first base station may communicate, with a wireless device, a packet flow associated with a service.
  • BS1 may receive from the wireless device, one or more measurement report.
  • BS1 may receive from a second/secondary base station (BS2), a message comprising at least of: a field indicating to configure L1/L2-based mobility, via SRB3, in the second base station for the wireless device, a candidate target cell list associated with the L1/L2-based mobility, via SRB3, for the wireless device, and/or the like.
  • BS1 may receive, from BS2, a message comprising at least of: a field indicating a successful L1/L2- based serving cell change, and the serving cell identifier of the new serving cell, and/or the like.
  • a second/secondary base station may communicate, with a wireless device, a packet flow associated with a service.
  • BS2 may receive, from the wireless device, one or more radio measurement reports.
  • BS2 may determine to configure L1/L2-based mobility, via a signal radio bearer 3 (SRB3), in the secondary base station for the wireless device.
  • SRB3 signal radio bearer 3
  • BS2 may further determine to generate at least of: a candidate target cell list associated with L1/L2-based mobility via SRB3, and mobility configurations associated with the candidate target cell list, via SRB3, and/or the like.
  • BS2 may send to the wireless device a message comprising at least of: a candidate target cell list associated with the L1/L2-based mobility via SRB3 for the wireless device, and the mobility configurations associated with the candidate target cell list for the wireless device, and/or the like.
  • BS2 may receive, from the wireless device, a message comprising a low layer measurement report.
  • BS2 may determine to perform an L1/L2-based serving cell change for the wireless device.
  • BS2 may send to, the wireless device, a message comprising at least of: an indication to notify the wireless device to perform serving cell change, and a serving cell identifier of the new serving cell, and/or the like.
  • BS2 may send, to BS1, a message comprising at least of: afield indicating a successful L1/L2-based serving cell change, and the serving cell identifier of the new serving cell, and/or the like.
  • a second base station may receive, from a wireless device, a radio resource control message comprising a radio measurement report.
  • the second base station may determine, based on the radio measurement report, for the wireless device, to perform layer 1 and/or layer 2 (L1/L2)-based mobility, via a signal radio bearer 3 (SRB3), in the second base station (e.g., secondary BS);
  • the second base station may generate a candidate target cell list associated with L1/L2-based mobility, and mobility configurations associated with the candidate target cell list, for the wireless device.
  • the second base station may send to a first base station (e.g., a master base station), based on the determining, a secondary node (SN) configuration message, comprising at least of: a field indicating to configure L1/L2-based mobility via SRB3 in the second base station for the wireless device; the candidate target cell list associated with L1/L2-based mobility; and/or the like.
  • a first base station e.g., a master base station
  • SN secondary node
  • the second base station may send, to the wireless device, a radio resource control (RRC) message via SRB3, comprising the candidate target cell list associated with L1/L2-based mobility; and the mobility configurations associated with the candidate target cell list.
  • RRC radio resource control
  • the second base station may receive, from the wireless device, a message comprising a low layer measurement report.
  • the second base station may determine, based on the low layer measurement report, an L1/L2-based serving cell change, for the wireless device.
  • the second base station may send, to the wireless device, a lower layer message, comprising at least of: a field indicating the L1/L2-based serving cell change; a serving cell identifier identifying a cell of the candidate cell list as a new serving cell of the wireless device; and/or the like.
  • the second base station may receive, from the wireless device, a message notifying/indicating a successful serving cell change from an old serving cell of the second base station to the new serving cell.
  • the second base station may send to the first base station, a second SN configuration message, comprising at least one of a field indicating the successful L1/L2-based serving cell change; the serving cell identifier of the serving cell; and/or the like.
  • a second base station e.g., a secondary BS
  • the second base station may send, to the wireless device, a radio resource control (RRC) message via SRB3, comprising at least one of: the candidate target cell list associated with L1/L2-based mobility; the mobility configurations associated with the candidate target cell list; and/or the like.
  • RRC radio resource control
  • the first base station may be a master base station of the wireless device.
  • the second base station may be a secondary base station of the wireless device.
  • the wireless device may store the candidate target cell list associated with L1/L2-based mobility; and the mobility configurations associated with the candidate target cell list, for the wireless device.
  • the wireless device may perform serving cell change to a cell associated with the serving cell identifier.
  • the second base station may send to the first base station, a message (e.g., SN modification required message) comprising at least one of: the updated/modified candidate target cell list associated with L1 /12- based mobility via SRB3 for the wireless device in the second base station; the updated/modified mobility configurations associated with the updated/modified candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station; an indication of modifying configurations of layer 1 and/or layer 2 (L1/L2)-based mobility via SRB3 in the secondary base station for the wireless device; and/or the like.
  • a message e.g., SN modification required message
  • the second base station may send, to the wireless device, a radio resource control (RRC) message (e.g., RRC reconfiguration), comprising at least of: an indication of modifying configurations of layer 1 and/or layer 2 (L1/L2)-based mobility via SRB3 in the secondary base station for the wireless device; the updated/modified candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station; the updated/modified mobility configurations associated with the updated/modified candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station; and/or the like.
  • RRC radio resource control
  • the wireless device may store the updated/modified candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station; and may store the updated/modified mobility configurations associated with the updated/modified candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station.
  • the wireless device may send to the second base station, a RRC message comprising a field indicating a successful L1/L2-based mobility modification via SRB3 in the second base station for the wireless device.
  • the second base station e.g., a secondary BS
  • the second base station may determine to release the candidate target cell list and/or the mobility configurations associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station (e.g., the secondary BS).
  • the second base station may send to the first base station, a message (e.g., SN modification required message) comprising at least one of: a field indicating to release L1/L2-based mobility via SRB3 for the wireless device in the second base station; the candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station; and/or the like.
  • a message e.g., SN modification required message
  • the second base station may send, to the wireless device, a radio resource control (RRC) message (e.g., RRC reconfiguration), comprising at least one of: a field indicating to release L1/L2-based mobility via SRB3 for the wireless device in the second base station; the candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station; and/or the like.
  • RRC radio resource control
  • the wireless device may release the mobility configurations associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station.
  • the wireless device may send to the second base station, a RRC message comprising a field indicating a successful L1/L2-based mobility releasing via SRB3 in the second base station for the wireless device.
  • the second base station may receive, from a wireless device, a radio resource control message comprising a radio measurement report.
  • the second base station e.g., a secondary BS
  • CU central unit
  • the CU of the second base station may determine, to configure L1/L2-based mobility in secondary BS via SRB3.
  • the CU of the second base station may generate a candidate target cell list associated with L1/L2-based mobility via SRB3 for the wireless device in the second base station.
  • the CU of the second base station may send to a distributed unit (DU) of the second base station, a message (e.g., UE context setup/modification message) comprising at least one of: a field indicating to configure L1/L2-based mobility via SRB3, for the wireless device; the candidate target cell list associated with L1/L2- based mobility via SRB3.
  • a message e.g., UE context setup/modification message
  • the CU of the second base station may receive from the DU of the second base station, a message (e.g., UE context setup/modification response message) comprising mobility configurations associated with the candidate target cell list, for the wireless device.
  • the sending by the second base station to the first base station, the second SN configuration message may comprise the sending, by the central unit (CU) of the second base station.
  • the sending by the second base station to the wireless device, the lower layer message may comprise the sending, by the central unit (CU) of the second base station.
  • the DU of the second base station may determine to generate mobility configurations to be configured via SRB3 associated with the candidate target cell list, for the wireless device.
  • the receiving, by the second base station (e.g., a secondary BS) from the wireless device, the message comprising the low layer measurement report may comprise the receiving by the source DU (DU1) of the second base station.
  • the source DU of the second base station may determine, based on the low layer measurement report, to perform an L1/L2-based serving cell change, for the wireless device.
  • the source DU of the second base station may send to the wireless device, a lower layer message, comprising at least one of: a field indicating the L1/L2-based serving cell change; a serving cell identifier identifying a cell of the candidate cell list as a new serving cell of the wireless device; and/or the like.
  • the source DU and/or a target DU (DU2) of the second base station may receive from the wireless device, a message notifying/indicating a successful serving cell change from an old serving cell of the second base station to the new serving cell.
  • the source DU and/or the target DU of the second base station may send to the OU of the second base station a message notifying/indicating a successful serving cell change from an old serving cell of the second base station to the new serving cell.
  • the wireless device may perform serving cell change to a cell associated with the serving cell identifier.
  • a wireless device may send, a radio measurement report, to a second base station (e.g., a secondary BS) of the wireless device.
  • the wireless device may receive, from the second base station, a radio resource control (RRC) message via a signaling radio bearer 3 (SRB3), comprising at least one of: a candidate target cell list associated with L1/L2-based mobility for the wireless device associated with a second base station (e.g., a secondary BS) of the wireless device; mobility configurations associated with the candidate target cell list, for the wireless device.
  • RRC radio resource control
  • SRB3 signaling radio bearer 3
  • the wireless device may store the candidate target cell list associated with L1/L2-based mobility for the wireless device associated with the second base station (e.g., a secondary BS) of the wireless device; and the mobility configurations associated with the candidate target cell list, for the wireless device.
  • the second base station e.g., a secondary BS
  • the wireless device may send, to the second base station, a message comprising a low layer measurement report.
  • the wireless device may receive, from the second base station, a lower layer message, comprising at least one of: a field indicating an L1/L2-based serving cell change; a serving cell identifier identifying a cell of the candidate cell list as a new serving cell of the wireless device.
  • the second base station may send to a first base station (e.g., a master base station), based on the determining, a secondary node (SN) configuration message, comprising a field indicating to configure L1 /12- based via SRB3 in the second base station for the wireless device, and the candidate target cell list associated with L1/L2-based mobility.
  • a secondary node (SN) configuration message comprising a field indicating to configure L1 /12- based via SRB3 in the second base station for the wireless device, and the candidate target cell list associated with L1/L2-based mobility.
  • the second base station may send to the first base station (e.g. , a master base station), a second SN configuration message, comprising a field indicating the successful L1/L2-based serving cell change, and the serving cell identifier of the serving cell.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP23790462.8A 2022-09-23 2023-09-22 Schicht 1 / schicht 2 basierte mobilitätsverbesserung Pending EP4584992A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263409631P 2022-09-23 2022-09-23
PCT/US2023/033469 WO2024064333A1 (en) 2022-09-23 2023-09-22 Layer 1 /layer 2 based mobility enhancement

Publications (1)

Publication Number Publication Date
EP4584992A1 true EP4584992A1 (de) 2025-07-16

Family

ID=88416975

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23790462.8A Pending EP4584992A1 (de) 2022-09-23 2023-09-22 Schicht 1 / schicht 2 basierte mobilitätsverbesserung

Country Status (3)

Country Link
US (1) US20250247750A1 (de)
EP (1) EP4584992A1 (de)
WO (1) WO2024064333A1 (de)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2025534386A (ja) * 2022-09-28 2025-10-15 コムキャスト ケーブル コミュニケーションズ， エルエルシー 一次セル切り替えのための遅延低減
US12587909B2 (en) * 2022-10-11 2026-03-24 Qualcomm Incorporated Reconfiguration for lower layer mobility
WO2025235675A1 (en) * 2024-05-08 2025-11-13 Google Llc Enabling subsequent inter-central unit lower-layer triggered mobility in dual connectivity

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12538193B2 (en) * 2020-07-13 2026-01-27 Qualcomm Incorporated Fast CA/DC reconfiguration in L1/L2 based inter-cell mobility
KR102639499B1 (ko) * 2020-07-24 2024-02-22 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 이동성 절차를 위한 방법 및 장치

Also Published As

Publication number Publication date
US20250247750A1 (en) 2025-07-31
WO2024064333A1 (en) 2024-03-28

Similar Documents

Publication Publication Date Title
US12035365B2 (en) Sharing channel occupancy ratio information
US20260039335A1 (en) Conditional Handover Configurations of Beams of a Cell
US20230239748A1 (en) Handover Procedures with Beam Management
EP4070600B1 (de) Sidelink-messverfahren
US12592763B2 (en) Beam failure measurements of overlapping reference signals
US20250220530A1 (en) Mobility Enhancement
US20240284274A1 (en) Configuration Information for Multi-Connectivity
US20240032146A1 (en) Cell Activation and Deactivation
US20250247750A1 (en) Mobility Enhancement
US20240179736A1 (en) Resources for Network Slice
US20250234259A1 (en) Identification of Candidate Cell Configuration
EP4458093A1 (de) Direktzugriffsinformationen auf der basis von netzwerk-slices
US20250227576A1 (en) Mobility Enhancement
US20240323807A1 (en) Slice Group Information
US20240235790A1 (en) Default Rules in Inter-Cell Multiple Transmission-and-Reception Points
EP4714184A2 (de) Direktzugriffsverfahren mit mobilität
EP4591617A1 (de) Informationsbericht auf der basis von mobilität niedriger schicht
WO2024072829A1 (en) Signaling between base stations for network energy saving
US12568416B2 (en) Configuration handling for subsequent layer 1 or layer 2 triggered mobility in dual connectivity
US20260129517A1 (en) Rate Control for Extended Reality in Dual Connectivity
US20240306217A1 (en) Random Access Resource Information Based on Network Slices
US20260040304A1 (en) Overlapping Transmissions in User Equipment Initiated Channel State Information Reporting
US20260019863A1 (en) Reporting of Redundant Protocol Data Units for Extended Reality
US20250351053A1 (en) Wireless Device Predictions
WO2025235575A1 (en) Configuration Handling for Layer 1 or Layer 2 Triggered Mobility in Dual Connectivity

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250407

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20250808

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)