WO2023132766A1 - Informations d'assistance pour spectre sans licence dans une architecture distribuée - Google Patents

Informations d'assistance pour spectre sans licence dans une architecture distribuée Download PDF

Info

Publication number
WO2023132766A1
WO2023132766A1 PCT/SE2022/051226 SE2022051226W WO2023132766A1 WO 2023132766 A1 WO2023132766 A1 WO 2023132766A1 SE 2022051226 W SE2022051226 W SE 2022051226W WO 2023132766 A1 WO2023132766 A1 WO 2023132766A1
Authority
WO
WIPO (PCT)
Prior art keywords
unlicensed spectrum
base station
assistance information
gnb
lbt
Prior art date
Application number
PCT/SE2022/051226
Other languages
English (en)
Inventor
Luca LUNARDI
Angelo Centonza
Pradeepa Ramachandra
Marco BELLESCHI
Johan Rune
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023132766A1 publication Critical patent/WO2023132766A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present disclosure relates to operation of a cellular communications system in unlicensed spectrum.
  • NG-RAN Next Generation RAN
  • 3GPP 3 rd Generation Partnership Project
  • TS Technical Specification
  • the New Generation Radio Access Network comprises a set of New Radio (NR) Base Stations (gNBs) connected to the Fifth Generation Core (5GC) through the Next Generation (NG) interface.
  • gNBs New Radio
  • the NG-RAN may also include a set of next generation evolved Node Bs (ng-eNBs).
  • An ng-eNB may include a ng-eNB Central Unit (ng-eNB-CU) and one or more ng-eNB Distributed Units (ng-eNB-DUs).
  • ng-eNB-CU and the ng-eNB-DU are connected via the W1 interface.
  • the general principle described in this section also applies to ng-eNB and W1 interface, if not explicitly specified otherwise.
  • the gNBs can be interconnected through the Xn interface.
  • the gNB may include a ‘gNB Central Unit (gNB-CU) and one or more gNB Distributed Units (gNB-DUs).
  • the gNB-CU and the gNB-DU are connected via the Fl interface.
  • One gNB-DU is connected to only one gNB-CU.
  • the NG, Xn, and Fl interfaces are logical interfaces.
  • the NG and Xn-C interfaces for a gNB including a gNB-CU and gNB-DUs terminate in the gNB-CU.
  • EUTRA Evolved Universal Terrestrial Radio Access
  • EN-DC Evolved Universal Terrestrial Radio Access
  • the Sl-U and X2-C interfaces for a gNB including a gNB-CU and gNB- DUs terminate in the gNB-CU.
  • the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5 th Generation Core (5GC) as a gNB.
  • 5GC 5 th Generation Core
  • a gNB may include a gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs.
  • the gNB-CU-CP is connected to the gNB-DU through the Fl-C interface.
  • the gNB-CU-UP is connected to the gNB-DU through the Fl-U interface.
  • the gNB-CU-UP is connected to the gNB-CU-CP through the El interface.
  • One gNB-DU is connected to only one gNB-CU-CP.
  • One gNB-CU-UP is connected to only one gNB-CU-CP.
  • One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP.
  • One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP.
  • NR-U NR in Unlicensed Spectrum
  • NR New Radio
  • MTC Machine Type Communication
  • URLLC Ultra-Low Latency Critical Communications
  • D2D side-link Device-to-Device
  • a slot comprises 14 Orthogonal Frequency Division Multiplexing (OFDM) symbols for the normal cyclic prefix configuration.
  • OFDM Orthogonal Frequency Division Multiplexing
  • NR supports many different subcarrier spacing configurations and, at a subcarrier spacing of 30 kilohertz (kHz), the OFDM symbol duration is ⁇ 33 microseconds (ps).
  • ps microseconds
  • a slot with 14 symbols for the same subcarrier-spacing (SCS) is 500ps long (including cyclic prefixes).
  • NR also supports flexible bandwidth configurations for different User Equipments (UEs) on the same serving cell.
  • UEs User Equipments
  • the bandwidth monitored by a UE and used for its control and data channels may be smaller than the carrier bandwidth.
  • One or multiple bandwidth part configurations for each component carrier can be semi-statically signaled to a UE, where a bandwidth part comprises a group of contiguous Physical Resource Blocks (PRBs). Reserved resources can be configured within the bandwidth part.
  • the bandwidth of a bandwidth part is equal to or smaller than the maximal bandwidth capability supported by a UE.
  • NR targets both licensed and unlicensed bands, and a work item named ‘NR-based Access to unlicensed Spectrum’ (NR-U) was started in January 2019. Allowing unlicensed networks, i.e., networks that operate in shared spectrum (or unlicensed spectrum) to effectively use the available spectrum is an attractive approach to increase system capacity. Although unlicensed spectrum does not match the qualities of the licensed regime, solutions that allow an efficient use of it as a complement to licensed deployments have the potential to bring great value to the 3GPP operators, and, ultimately, to the 3GPP industry as a whole. It is expected that some features in NR will need to be adapted to comply with the special characteristics of the unlicensed band as well as also different regulations. Subcarrier spacings of 15 kHz and 30 kHz are the most promising candidates for NR-U OFDM numerologies for frequencies below 6 Gigahertz (GHz).
  • GHz Gigahertz
  • LBT Listen- Before-talk
  • the sensing is done in a particular channel (corresponding to a defined carrier frequency) and over a predefined bandwidth. For example, in the 5 GHz band, the sensing is done over 20 Megahertz (MHz) channels.
  • Many devices are capable of transmitting (and receiving) data over a wide bandwidth including multiple sub-bands/channels, e.g., multiple LBT sub-bands where an LBT sub-band is a frequency part with bandwidth equal to LBT bandwidth.
  • a device is only allowed to transmit data on the sub-bands where the medium is sensed as free. Again, there are different variations of how the sensing should be done when multiple sub-bands are involved.
  • a device can operate over multiple sub-bands.
  • One way is that the transmitter/receiver bandwidth is changed depending on which sub-bands are sensed as free.
  • CC Carrier Component
  • the other way is that the device operates almost independent processing chains for each channel. Depending on how independent the processing chains are, this option can be referred to as either Carrier Aggregation (CA) or Dual Connectivity (DC).
  • CA Carrier Aggregation
  • DC Dual Connectivity
  • LBT is designed for unlicensed spectrum co-existence with other Radio Access Technologies (RATs).
  • RATs Radio Access Technologies
  • a radio device applies a Clear Channel Assessment (CCA) check (i.e., channel sensing) before any transmission.
  • CCA Clear Channel Assessment
  • the transmitter involves Energy Detection (ED) over a time period compared to a certain threshold (ED threshold) in order to determine if a channel is idle.
  • ED Energy Detection
  • LBT parameter settings may be set for devices in a network by a network node configuring the devices in the network.
  • the limits may be set as pre-defined rules or tables in specifications or regulatory requirements for operation in a certain region. Such limits are part of the European Telecommunications Standards Institute (ETSI) harmonized standard in Europe as well as the 3GPP specification for operation of LTE/NR-U in unlicensed spectrum.
  • ETSI European Telecommunications Standards Institute
  • Downlink channel access procedures are specified for an evolved Node B (eNB) operation Licensed-Assisted Access (LAA) Secondary Cell(s) (SCell(s)) on channel(s) and a gNB performing transmission(s) on channel(s) according to clause 4.1 of 3GPP TS 37.213 V16.7.0 (2021-9).
  • eNB evolved Node B
  • LAA Licensed-Assisted Access
  • SCell(s) Secondary Cell(s)
  • the eNB/gNB may transmit data after first sensing the channel to be idle during the sensing slot durations of a defer duration Td and after a counter N is zero, where N depends on the Contention Window for a given Channel Access Priority Class “p”, (CW P ), with CW P comprised between a minimum value CWmin, P and a maximum value CW ma x, P .
  • CW P Channel Access Priority Class
  • the eNB/gNB shall not transmit data on a channel for a Channel Occupancy Time (COT) that exceeds T m cot, P where the channel access procedures are performed based on a Channel Access Priority Class “p” associated with the eNB/gNB transmissions, as given in the table shown in Figure 3.
  • COT Channel Occupancy Time
  • P Channel Access Priority Class
  • Two modes of access operations are defined - Frame-Based Equipment (FBE) and Load-Based Equipment (LBE).
  • FBE mode the sensing period is simple, while the sensing scheme in LBE mode is more complex.
  • FBE mode and LBE mode are explained below.
  • FIG 4 illustrates an example of FBE procedure depicting 3GPP semi-static channel occupancy, which comes from ETSI harmonized standard EN 301 893 Section 4.2.7.3.1.
  • the gNB assigns Fixed Frame Periods (FFPs), senses the channel just before the FFP boundary, and if the channel is sensed to be free, it starts with a downlink transmission and/or allocates resources among different UEs in the FFP. This procedure can be repeated with a certain periodicity.
  • FFPs Fixed Frame Periods
  • downlink (DL) / uplink (UL) transmissions are only allowed within the COT, which is a subset of FFP resource, where the remaining Idle period is reserved so that other nodes also have the chance to sense and utilize the channel.
  • the channel is sensed at specific intervals just before the FFP boundary.
  • the FFP can be set to values between 1 and 10 milliseconds (ms) and can be changed after a minimum of 200 ms.
  • LBT category 4 The default LBT mechanism for LBE operation, LBT category 4, is similar to existing Wi-Fi operation, where a node can sense the channel at any time and start transmitting if the channel is free after a deferral and backoff period. For specific cases, e.g. shared COT, other LBT categories allowing a very short sensing period, are allowed.
  • Sensing is done typically for a random number of sensing intervals with this random number being a number within the range of 0 to CW, where CW represents a contention window size.
  • a backoff counter is initialized to this random number drawn within 0 and CW.
  • a device When a busy carrier is sensed to have become idle, a device must wait for a fixed period also known as a prioritization period, after which it can sense the carrier in units of the sensing interval. For each sensing interval within which the carrier is sensed to be idle, the backoff counter is decremented. When the backoff counter reaches zero, the device can transmit on the carrier. After transmission, if a collision is detected via the reception of a negative acknowledgement or by some other means, the contention window size, CW, is doubled.
  • MCOT Maximum Channel Occupancy Time
  • QoS Quality of Service
  • CWS Contention Window Sizes
  • MCOT MCOT
  • 3GPP TS 38.331 vl6.7.0 (2021-12) indicates that the LBT-FailureRecoveryConfig Information Element (IE) is specified to configure parameters used for detection of consistent uplink LBT failures when operating with shared spectrum channel access, as shown in the following excerpt:
  • IE LBT-FailureRecoveryConfig Information Element
  • LBT-FailureRecoveryConfig-rl6 is used to configure the parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321.
  • LBT-FailureRecoveryConfig-rl6 SEQUENCE ⁇ lbt-Failure!nstanceMaxCount-rl6 ENUMERATED ⁇ n4, n8, nl6, n32, n64, nl28 ⁇ , lbt-FailureDetectionTimer-rl6 ENUMERATED ⁇ mslO, ms20, ms40, ms80, msl60, ms320 ⁇ ,
  • BWP Bandwidth Part
  • 3GPP TS 38.321 vl6.7.0 (2021-12) clause 5.15.1 indicates that the BWP switching for a Serving Cell is used to activate an inactive BWP and deactivate an active BWP at a time.
  • the BWP switching can be controlled by the MAC entity upon detection of consistent LBT failure on SpCell.
  • the MAC entity may be configured by RRC with a consistent LBT failure recovery procedure. Consistent LBT failure is detected per UL BWP by counting LBT failure indications, for all UL transmissions, from the lower layers to the MAC entity.
  • a UE can switch the active UL BWP to an UL BWP on the same carrier in the Serving Cell, configured with Physical Random Access Channel (PRACH) occasion and for which consistent LBT failure has not been triggered.
  • PRACH Physical Random Access Channel
  • the UE then performs Random Access in the new UL BWP and, if it succeeds, the UE can continue to transmit UL data in the new UL BWP.
  • the UE will send a MAC Control Element (CE), from which the network can identify the Serving Cell for which consistent LBT failure has been triggered and not cancelled.
  • CE MAC Control Element
  • the NR user plane (NR-U) protocol layer uses services of the transport network layer in order to allow flow control of user data packets transferred from the node hosting NR Packet Data Convergence Protocol (PDCP) to the corresponding node.
  • PDCP Packet Data Convergence Protocol
  • the purpose of the Transfer of Downlink User Data procedure is to provide NR User Plane (NR-U) specific sequence number information at the transfer of user data carrying a DL NR PDCP Protocol Data Unit (PDU) from the node hosting the NR PDCP entity to the corresponding node.
  • NR-U NR User Plane
  • PDU Protocol Data Unit
  • 3GPP TS 38.425 vl6.3.0 (2021-4) clause 5.5.2.1 describes the DL USER DATA (PDU Type 0) frame format, which allows the detection of NR-U packets and may be associated with the transfer of a downlink NR PDCP PDU.
  • the Assistance Info. Report Polling Flag indicates that the node hosting the NR PDCP entity requests the corresponding node to send an ASSISTANCE INFORMATION DATA PDU, which is described in the following excerpt from 3GPP TS 38.425 vl6.3.0 (2021-4), section 5.5.3.40:
  • This parameter indicates that the node hosting the NR PDCP entity requests the corresponding node to send an ASSISTANCE INFORMATION DATA PDU.
  • the purpose of the Downlink Data Delivery Status procedure is to provide feedback from the corresponding node to the node hosting the NR PDCP entity to allow the node hosting the NR PDCP entity to control the downlink user data flow via the corresponding node for the respective data radio bearer.
  • the corresponding node may also transfer uplink user data for the concerned data radio bearer to the node hosting the NR PDCP entity together with a DL DATA DELIVERY STATUS frame within the same General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) PDU.
  • GPRS General Packet Radio Service
  • GTP-U General Packet Radio Service
  • the Downlink Data Delivery Status procedure is also used to provide feedback from the corresponding node to the node hosting the NR PDCP entity to allow the node hosting the NR PDCP entity to control the successful delivery of DL control data to the corresponding node.
  • 3GPP TS 38.425 vl6.3.0 (2021-4) clause 5.5.2.2 describes DL DATA DELIVERY STATUS (PDU Type 1) frame format. This frame is used to transfer feedback to allow the receiving node (i.e., the node that hosts the NR PDCP entity) to control the downlink user data flow via the sending node (i.e., the corresponding node).
  • the Successful DL DATA DELIVERY STATUS procedure is shown in Figure 5.4.2.1.1-1 of 3GPP TS 38.425, which is reproduced in Figure 6 of the present disclosure.
  • the Cause Value parameter indicates specific events reported by the corresponding node, the details of which are provided in the following excerpt from 3GPP TS 38.425 vl6.3.0 (2021-4) clause 5.5.3.23:
  • the purpose of the Transfer of Assistance Information procedure is to provide assistance information to the node hosting the NR PDCP entity. Such information may be taken into consideration by the node hosting the NR PDCP entity for UP management and optimization procedures.
  • 3GPP TS 38.425 vl6.3.0 (2021-4) clause 5.5.2.3 describes ASSISTANCE INFORMATION DATA (PDU Type 2) frame format. This frame allows the node hosting the NR PDCP entity to receive assistance information.
  • the Assistance Information Type field indicates the type of radio quality assistance information provided, if supported, by the corresponding node to the node hosting the NR PDCP entity. Details of Assistance Information Type field are provided in 3GPP TS 38.425 vl6.3.0 (2021-4) clause 5.5.3.38, as shown in the excerpt below. Figure 5.4.3.1-1 of 3GPP TS 38.425 vl6.3.0 (2021-4) is reproduced herein as Figure 7.
  • This field describes the type of radio quality assistance information provided, if supported, by the corresponding node to the node hosting the NR PDCP entity.
  • the DL Radio Quality Index is a numerical index expressing the radio quality of the data radio bearer or the RLC entity in DL, where the value 0 represents the lowest quality.
  • the UL Radio Quality Index is a numerical index expressing the radio quality of the data radio bearer or the RLC entity in UL, where the value 0 represents the lowest quality.
  • the averaging window for the Average CQI, Average HARQ Failure and Average HARQ Retransmission is set by means of configuration.
  • Power Headroom Report is PHR MAC control element reported by as defined in 3GPP TS 36.321 and 3GPP TS 38.321.
  • a method performed by a system including a base station central unit user plane part (CU-UP), a base station distributed unit (DU), and a base station central unit control plane part (CU-CP) comprises, at the base station DU, sending a set of unlicensed spectrum assistance information to either or both of the base station CU-UP and the base station CU-CP.
  • CU-UP base station central unit user plane part
  • DU base station distributed unit
  • CU-CP base station central unit control plane part
  • the method further comprises, at either or both of the base station CU-UP and the base station CU-CP, receiving the set of unlicensed spectrum assistance information from the base station DU and performing one or more actions related to unlicensed spectrum operation based on the set of unlicensed spectrum assistance information.
  • RAN optimization and UE reconfiguration can be provided based on unlicensed spectrum assistance information.
  • the set of unlicensed spectrum assistance information comprises: (a) average amount of consistent LBT failures over a period of time experienced by the base station DU for downlink transmissions in a certain serving cell, within a certain time interval; (b) an indication, for a serving cell controlled by the base station DU, that indicates an amount of UEs that have switched their active uplink bandwidth parts in which the UEs were last scheduled in the serving cell to another uplink bandwidth part on the serving cell due to the UEs experiencing consistent LBT failures in the serving cell, within a certain time interval; (c) an indication, for a serving cell controlled by the base station DU, that indicates a total or average number of times an uplink bandwidth part switch occurred in the serving cell from an uplink bandwidth part in which a UE was last scheduled to another uplink bandwidth part in the serving cell; (d) an indication, for a serving cell controlled by the base station DU, that indicates a total or average or minimum or maximum number of UEs that have deactivated the serving cell due to UEs
  • sending the set of unlicensed spectrum assistance information comprises sending the set of unlicensed spectrum assistance information to the base station CU- UP. In one embodiment, sending the set of unlicensed spectrum assistance information to the base station CU-UP comprises sending the set of unlicensed spectrum assistance information to the base station CU-UP via a downlink data delivery status frame or an assistance information data frame. In one embodiment, the method further comprises, at the base station CU-UP, sending the set of unlicensed spectrum assistance information to the base station CU-CP. In one embodiment, at the base station CU-UP, performing the one or more actions comprises determining, based on the set of unlicensed spectrum assistance information, first control information associated to unlicensed spectrum operation for regulating user plane data transmission and reception. In one embodiment, at the base station CU-UP, performing the one or more actions further comprises using the first control information to regulate sending and receiving of user plane data among dual connectivity cells associated to a UE.
  • performing the one or more actions further comprises sending the first control information to the base station CU-CP.
  • the method further comprises, at the base station CU-CP, receiving the first control information from the base station CU-UP and controlling UE configuration and operation based on the first control information.
  • the first control information comprises one or more flow control parameters that regulate sending of downlink user data towards the base station DU adapted based on the set of unlicensed spectrum assistance information, information about which transmission leg of a multi -connectivity configuration with a UE to use to deliver traffic to and from the UE, one or more indications to reduce downlink data due to consistent LBT failure, one or more indications to increase downlink data due to recovery from consistent LBT failure, one or more indications to switch traffic to a different transmission leg of a multiconnectivity configuration of a UE, an indication that triggers signaling to the base station DU to discard one or more downlink protocol data units (PDUs), an indication that triggers signaling to the base station DU of a polling flag for a PDU type that contains unlicensed spectrum assistance information, or a combination of any two or more thereof.
  • PDUs downlink protocol data units
  • performing the one or more actions comprises determining, based on the set of unlicensed spectrum assistance information, second control information associated to unlicensed spectrum operation for controlling configuration or operation of a UE. In one embodiment, at the base station CU-UP, performing the one or more actions comprises sending the second control information to the base station CU-CP. In one embodiment, the method further comprises, at the base station CU-CP, receiving the second control information from the base station CU-UP and controlling UE configuration and operation based on the second control information.
  • sending the set of unlicensed spectrum assistance information comprises sending the set of unlicensed spectrum assistance information to the base station CU- CP. In one embodiment, sending the set of unlicensed spectrum assistance information comprises sending the set of unlicensed spectrum assistance information to the base station CU- CP via a F1AP message.
  • the method further comprises, at the base station DU, receiving a first set of unlicensed spectrum assistance information from a UE, wherein the set of unlicensed spectrum assistance information sent from the base station DU to either or both of the base station CU-UP and the base station CU-CP is a second set of unlicensed spectrum assistance information that is dependent on the first set of unlicensed spectrum assistance information received from the UE.
  • the first set of unlicensed spectrum assistance information comprises: (i) LBT failure Medium Access Control (MAC) Control Elements (CEs) that indicate that the UE has experienced consistent LBT failures in one or more secondary cells and, based thereupon, deactivated the one or more secondary cells; (ii) a random access attempt in a special cell in an uplink bandwidth part that is different from an uplink bandwidth part in which the UE was last scheduled for uplink transmissions for the special cell; (iii) channel availability information; or (iv) a combination of any two or more of (i)-(iii).
  • MAC Medium Access Control
  • CEs Control Elements
  • the first set of unlicensed spectrum assistance information comprises uplink LBT statistics that indicate an amount of LBT failures the UE has experienced in a given serving cell, a ratio between the amount of LBT failures and an overall amount of LBT attempts in the given serving cell, an amount of time spent in a measurement period by the UE to perform an LBT procedure before an uplink transmission, or any combination of two or more thereof.
  • the method further comprises, at the base station DU, receiving a request for the unlicensed spectrum assistance information prior to sending the set of unlicensed spectrum assistance information to either or both of the base station CU-UP and the base station CU-CP.
  • the set of unlicensed spectrum assistance information is received, at the base station CU-CP, either directly from the base station DU or indirectly from the base station DU through one or more other network nodes, and the method further comprises, at the base station CU-CP, either: determining a UE configuration for a UE based on control information associated to unlicensed spectrum operation, the control information being dependent on the set of unlicensed spectrum assistance information or using the control information associated to unlicensed spectrum operation to reconfiguration one or more UEs and cells or sending the control information associated to unlicensed spectrum operation to one or more UEs or sending the control information associated to unlicensed spectrum operation to the base station CU-UP.
  • a method performed by a UE comprises sending unlicensed spectrum assistance information to a network node, wherein the unlicensed spectrum assistance information comprises: (a) one or more indications that consistent LBT failures occurred; (b) an average or maximum number of LBT failures over a period of time; (c) one or more indications that the UE switches uplink bandwidth parts in a special cell due to consistent LBT failures; (d) one or more indications that the UE deactivates one or more secondary cells due to consistent LBT failures; (e) an average, maximum, or minimum number of UE switches of an active uplink bandwidth part to another uplink bandwidth part due to consistent LBT failures; (f) one or more indications of detected LBT outage; (g) one or more ranges of lost user plane sequence numbers; (h) a highest successfully delivered Packet Data Convergence Protocol (PDCP) sequence number; (i) a highest transmitted PDCP sequence number; (PDCP) PDCP
  • the method further comprises receiving a reconfiguration that is based, at least in part, on the unlicensed spectrum assistance information and applying the reconfiguration.
  • a UE comprises a communication interface and processing circuitry associated with the communication interface.
  • the processing circuitry is configured to cause the UE to send unlicensed spectrum assistance information to a network node, wherein the unlicensed spectrum assistance information comprises: (a) one or more indications that consistent LBT failures occurred; (b) an average or maximum number of LBT failures over a period of time; (c) one or more indications that the UE switches uplink bandwidth parts in a special cell due to consistent LBT failures; (d) one or more indications that the UE deactivates one or more secondary cells due to consistent LBT failures; (e) an average, maximum, or minimum number of UE switches of an active uplink bandwidth part to another uplink bandwidth part due to consistent LBT failures; (f) one or more indications of detected LBT outage; (g) one or more ranges of lost user plane sequence numbers; (h) a highest successfully delivered PDCP sequence number; (i) a highest transmitted
  • Figure 2 illustrates the overall architecture for separation of New Radio (NR) base station (gNB) Central Unit (CU) Control Plane part (gNB-CU-CP) and gNB-CU User Plane part(gNB- CU-UP) as depicted in Figure 6.1.2-1 in 3GPP TS 38.401 vl6.8.0 (2021-12);
  • NR New Radio
  • gNB Base Station
  • CU Central Unit
  • Control Plane part gNB-CU-CP
  • gNB-CU-CP gNB-CU User Plane part
  • Figure 2 illustrates the overall architecture for separation of New Radio (NR) base station (gNB) Central Unit (CU) Control Plane part (gNB-CU-CP) and gNB-CU User Plane part(gNB- CU-UP) as depicted in Figure 6.1.2-1 in 3GPP TS 38.401 vl6.8.0 (2021-12);
  • FIG. 3 is a table that defines a maximum Channel Occupancy Time (COT) for different channel access priority classes
  • Figure 4 illustrates an example of a Frame-Based Equipment (FBE) procedure depicting 3 GPP semi-static channel occupancy
  • Figure 5 illustrates a transfer of downlink user data procedure defined in 3GPP TS 38.425 V16.3.0 (2021-4), clause 5.4.1;
  • Figure 6 illustrates the Successful DL DATA DELIVERY STATUS procedure from Figure 5.4.2.1.1-1 of 3GPP TS 38.425;
  • Figure 7 is a reproduction of Figure 5.4.3.1-1 of 3GPP TS 38.425 vl6.3.0 (2021-4);
  • Figure 8 Figure 9, Figure 10, Figure 11, Figure 12, and Figure 13 illustrate non-limiting examples of chains of transfer of unlicensed spectrum assistance information in accordance with embodiments of the present disclosure
  • Figure 14 illustrates a procedure for transfer and use of unlicensed spectrum assistance information in accordance with embodiments of the present disclosure
  • Figures 15A to 15K reproduce tables from an example implementation of an embodiment of the present disclosure represented as changes to 3GPP TS 38.473;
  • Figure 16 is a reproduction of Figure 8.3.5.2-1 from an example implementation of an embodiment of the present disclosure represented as changes to 3GPP TS 38.473;
  • Figures 17A to 17F reproduce tables from an example implementation of an embodiment of the present disclosure represented as changes to 3GPP TS 38.473;
  • Figure 18 shows an example of a communication system in accordance with some embodiments of the present disclosure.
  • FIG. 19 shows a User Equipment (UE) in accordance with some embodiments
  • Figure 20 shows a network node in accordance with some embodiments.
  • flow control of downlink user data does not take into account LBT failures in unlicensed spectrum, which can impact integrity performance (e.g., downlink throughput). Namely, flow control may reveal that the channel is performing well while the channel is available. When the channel is not available, flow control will reveal that there are no or few packets successfully transmitted to the UE. The latter may be misleading for a gNB Central Unit (gNB-CU), which hosts the Packet Data Convergence Protocol (PDCP) layer, because it might be interpreted as radio degradation of the channel, while it is due to LBT failure events.
  • gNB-CU which hosts the Packet Data Convergence Protocol (PDCP) layer
  • traffic management policies may not have sufficient information to properly configure/de-configure or activate/deactivate secondary carriers in carrier aggregation scenario, based on whether the UE experienced consistent LBT failures in those carriers.
  • traffic management policies may not have sufficient information to properly configure/de-configure or activate/deactivate secondary carriers in carrier aggregation scenario, based on whether the UE experienced consistent LBT failures in those carriers.
  • due to missing awareness of channel access failure due to failed LBT it is not possible to make effective decisions on how to schedule traffic between different legs of a multi -connectivity configuration (e.g., a dual connectivity configuration where scheduling happens between a master cell group and a secondary cell group).
  • the methods of the present disclosure allow consideration of indications of consistent LBT failures in Radio Access Network (RAN) optimization, particularly in relation to flow control, and potential reconfiguration of UEs making use of unlicensed spectrum.
  • RAN Radio Access Network
  • Embodiments of the present disclosure enable a flow control of downlink user data, which takes into account LBT failures, and reconfiguration of the UE according to unlicensed spectrum assistance information indicating consistent LBT failures.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • One of the advantages of the proposed solution is to enable improved downlink flow control of user data by taking into account the effect of consistent LBT failures on data delivery.
  • the latter includes decisions to switch traffic delivery to connection legs that are not affected by failed LBT events.
  • Traffic management decision e.g., configuration/deconfiguration or activation/deactivation of carriers for carrier aggregation usage
  • a “network node” can be a RAN node, a gNB, evolved Node B (eNB), en-gNB, next generation eNB (ng-eNB), gNB-CU, gNB-CU-CP, gNB-CU User Plane part (gNB-CU-UP), gNB-DU, eNB Central Unit (eNB-CU), eNB-CU Control Plane part (eNB- CU-CP), eNB-CU User Plane part (eNB-CU-UP), eNB Distributed Unit (eNB-DU), Integrated Access and Backhaul (IAB) node, lAB-donor-Distributed Unit (DU), lAB-donor-Central Unit (CU), lAB-donor-CU-Control Plane part (CP),
  • IAB Integrated Access and Backhaul
  • first set of unlicensed spectrum assistance information is referred to a set of unlicensed spectrum assistance information that the second network node (i.e., DU) receives from the UE.
  • second set of unlicensed spectrum assistance information is referred to a set of unlicensed spectrum assistance information that the first network node (i.e., gNB-CU-UP) or third network node (i.e., gNB-CU- CP) receives from the second network node.
  • the first network node is a gNB-CU-UP
  • the second network node is a gNB-DU
  • the third network node is a gNB-CU-CP
  • a first network node or a third network node receives, from a second network node, a second set of unlicensed spectrum assistance information comprising one of more of the following information:
  • an indication for a serving cell ‘controlled’ (the term ‘controlled’ here means that the serving cell is managed by the DU) by the gNB-DU indicating the amount of UEs that have switched the active uplink (UL) bandwidth part (BWP) in which the UE was last scheduled in such serving cell to another UL BWP on the same serving cell due to UEs experiencing consistent LBT failures in such serving cell, wherein the amount of UEs is calculated within a certain time interval.
  • the indication may also comprise indication that the switch was due to consistent LBT failure.
  • an indication for a serving cell controlled by the gNB-DU indicating the total number of times (or the average number of times) an UL BWP switch occurred in the serving cell, wherein the UL BWP switch is from the UL BWP in which the UE was last scheduled to another UL BWP in the same serving cell.
  • This may contain the BWP identifiers (IDs) of the BWPs from which the switch was performed, and the BWP IDs to which the switch was performed.
  • the indication may also comprise indication that the switch was due to consistent LBT failure.
  • an indication for a serving cell controlled by the gNB-DU indicating the total amount of UEs (or the average number, or the minimum number of UEs, or the maximum number of UEs) that have deactivated such serving cell due to UEs experiencing consistent LBT failures in such serving cell, wherein the total amount of UEs (or the average, or the minimum, or the maximum) is calculated within a certain time interval. This may contain also the identities of such UEs.
  • an indication for a cell controlled by the gNB-DU indicating the total number of times (or the average number of times) the cell has been deactivated due to UEs experiencing consistent LBT failures in such serving cell, wherein the total amount of times (or the average number of times) is calculated within a certain time interval. This may also contain the identities of such UEs.
  • an indication for a specific UE indicating the total amount of consistent LBT failures (or the average number, or the minimum number or the maximum number of consistent LBT failures) that have been experienced by the UE within a certain time interval, or the total amount of consistent LBT failures (or the average number or the minimum number or the maximum number of consistent LBT failures) experienced by the UE within a certain time interval for each configured serving cells.
  • an indication for a specific UE indicating the specific serving cells e.g., the serving cell identities/indexes
  • the specific serving cells e.g., the serving cell identities/indexes
  • an indication for a specific UE indicating the specific serving cells e.g., the serving cell identities/indexes in which the UE switched the active UL BWP from the UL BWP in which the UE was last scheduled to another UL BWP in the same serving cell, wherein the switch was due to experiencing consistent LBT failures within a certain time interval in the respective serving cell(s).
  • the above information may be conveyed in the following fashion, depending on whether the above information is sent to the first network node (i.e., a gNB-CU-UP) or by the third network node (i.e., a gNB-CU-CP):
  • the first network node receives from the second network node (i.e., gNB-DU) the second set of unlicensed spectrum assistance information in a DL DATA DELIVERY STATUS frame (i.e., the PDU Type 1 of the GTP-U protocol) indicating for example “LBT outage”.
  • This message can be used for example if the information conveyed therein is associated to DL transmissions (e.g., the DU includes the average amount of consistent LBT failures over a period of time experienced by the second network node for DL transmissions in a certain serving cell).
  • the first network node receives from the second network node (gNB-DU) the second set of unlicensed spectrum assistance information in an ASSISTANCE INFORMATION DATA frame (i.e., the PDU Type 2 of the GTP-U protocol), e.g. via an Assistance Information Type field indicating that one or more unlicensed spectrum assistance information is provided and a Radio Quality Assistance Information field encoding unlicensed spectrum assistance information.
  • an Assistance Information Type field indicating that one or more unlicensed spectrum assistance information is provided
  • a Radio Quality Assistance Information field encoding unlicensed spectrum assistance information.
  • the third network node, gNB-CU-CP receives from the second network node (gNB-DU), the second set of unlicensed spectrum assistance information for a UE in an Fl AP message, e g. UE CONTEXT MODIFICATION REQUIRED.
  • the third network node, CU-CP receives from the second network node (gNB-DU), the second set of unlicensed spectrum assistance information for a cell in an F1AP message, e g. DU-CU RADIO INFORMATION TRANSFER.
  • the first network node receives the information from the second network node with messages as per the previous methods, and the first network node forwards such information to the third network node via El interface.
  • the third network node receives the information from the second network node with messages as per the previous methods, and the third network node forwards such information to the first network node via El interface.
  • the transmission of certain information in the second set of unlicensed spectrum assistance information from the second network node to the first network node or to the third network node may depend on the reception by the second network node of a first set of unlicensed spectrum assistance information transmitted by the UE to the second network node.
  • the information in the second set of unlicensed spectrum assistance information contains UL-related information (e.g.
  • the second network node transmits the second set of unlicensed spectrum assistance information after receiving the first set of unlicensed spectrum assistance information.
  • Such first set of unlicensed spectrum assistance information received by the second network node may comprise the following:
  • the gNB-DU receives from a UE, LBT failure MAC Control Element(s), indicating that the UE has experienced consistent LBT failures in one or more SCells upon which the UE deactivates such SCells in which the consistent LBT failures were detected.
  • the gNB-DU receives from the UE, a random access attempt (e.g., Physical Random Access Channel (PRACH)) in an SpCell in an UL BWP different from the UL BWP in which the UE was last scheduled for UL transmissions of this SpCell. From this, the gNB-DU deduces that the UE experienced consistent LBT failures in the SpCell.
  • a random access attempt e.g., Physical Random Access Channel (PRACH)
  • PRACH Physical Random Access Channel
  • the second network node receives from a UE, the first set of unlicensed spectrum assistance information pertaining to the UE and comprising channel availability information, e.g. UL LBT statistics indicating the amount of LBT failures the UE experienced in a given serving cell, the amount of successful LBT attempts the UE experienced in a given serving cell, the ratio between the amount of LBT failures and the overall amount of LBT attempts in a given serving cell, the time spent in a measurement period by the UE in performing LBT procedure before an UL transmission.
  • channel availability information e.g. UL LBT statistics indicating the amount of LBT failures the UE experienced in a given serving cell, the amount of successful LBT attempts the UE experienced in a given serving cell, the ratio between the amount of LBT failures and the overall amount of LBT attempts in a given serving cell, the time spent in a measurement period by the UE in performing LBT procedure before an UL transmission.
  • the third network node may have sent a request to the second network node or to the first network node or to UE(s) to receive second set of unlicensed spectrum assistance information. Examples are as follows:
  • a gNB-CU-CP can request to a gNB-DU to report Assistance
  • NR-U Initiation Request e.g. “NR-U Measurement Initiation”
  • NR-U Measurement Initiation e.g. “NR-U Measurement Initiation”
  • a specific Information Element such as “LBT Failure Information”, or “Consistent LBT Failure”, or “Request LBT Failure Information” within a F1AP UE CONTEXT SETUP message
  • the gNB-DU can then report to gNB-CU-UP the requested Assistance information concerning LBT failures for one or more cells in a new UE-associated Fl AP signaling procedure, e.g. “NR-U Notification”, or as part of an existing UE-associated F1AP signaling, e.g. a new Information Element (e.g. “Cells with consistent LBT Failure List”) as part of existing Fl AP procedures, such as F1AP UE Context Modification Required (gNB-DU initiated) procedure or Fl AP Notify procedure.
  • a new Information Element e.g. “Cells with consistent LBT Failure List”
  • the gNB-CU-CP could configure a set of events to the gNB-DU wherein the event is associated to the consistent LBT failure related notifications.
  • the event could be one or more of the following: (a) the gNB-DU shall indicate to the CU-CP upon experiencing consistent LBT failure for at least one UE on a serving cell controlled by the gNB-DU; (b) the gNB-DU shall indicate to the CU-CP upon experiencing consistent LBT failure for at least ‘X’ number of UEs on a serving cell controlled by the gNB-DU; (c) the gNB-DU shall indicate to the CU-CP upon experiencing consistent LBT failure for at least ‘ Y’ of the serving cells configured to a UE that is controlled by the gNB-DU; and (d) any combination of the above.
  • the gNB-CU-CP can request to the gNB-CU-UP information concerning consistent LBT failure events in a serving cell or events concerning UL BWP switch by the UE.
  • the gNB-CU-UP requests the reporting of such information to the gNB-DU.
  • the gNB-CU-UP once receiving the information from the gNB-DU forwards it to the gNB-CU-CP.
  • the gNB-CU-CP can request to the gNB-CU-UP information concerning consistent LBT failure events or events concerning the deactivation of a serving cell by the UE.
  • the gNB-CU-UP requests the reporting of such information to the gNB-DU.
  • the gNB-CU-UP once receiving the information from the gNB-DU forwards it to the gNB-CU-CP.
  • a first network node based on the received second set of unlicensed spectrum assistance information from the second network node (DU): (i) determines first control information associated to unlicensed spectrum operation for regulating user plane data transmission and reception from the first network node to/from a second network node (e.g.
  • control information related to the user data flow management of data radio bearers uses first control information associated to unlicensed spectrum operation for regulating sending and receiving of user plane data amongst the dual connectivity cells associated to the UE, i.e., routing more traffic from Master Cell Group (MCG) compared to Secondary Cell Group (SCG) or vice-versa; or (iii) (optionally) sends first control information associated to unlicensed spectrum operation to a third network node for controlling UE configuration and operation via El interface.
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the first control information associated to unlicensed spectrum operation at the first network node (gNB-CU-UP) based on the reception of the second set of unlicensed spectrum assistance information can be one or more of the following:
  • a gNB-CU-UP uses received unlicensed spectrum assistance information (e.g., information related to consistent LBT failures) to adapt flow control parameters regulating the sending of downlink user data (e.g., Downlink NR PDCP PDUs) towards a gNB-DU.
  • unlicensed spectrum assistance information e.g., information related to consistent LBT failures
  • the gNB-CU-UP may decide to locally buffer traffic when the gNB-DU reports one or more events of LBT failure and deliver the buffered data in one or more bursts when the gNB- DU ceases to flag LBT failure events.
  • the first control information associated to unlicensed spectrum operation is used to determine on which transmission leg of a multi connectivity configuration with a UE to deliver traffic to and from the UE. For example, if the multi -connectivity is achieved by means of dual connectivity involving a first gNB-DU serving an MCG and a second gNB-DU serving an SCG, and if the first gNB-DU reports to the gNB-CU one or more event of LBT failure or an event of consistent LBT failures, the gNB-CU-UP may decide to switch traffic transmission to the other transmission leg associated to the second gNB- DU.
  • the CU-UP might include additional indication towards the second gNB-DU that the increase in data towards the second gNB-DU is due to the LBT issues experienced on the first gNB-DU.
  • the gNB-CU-UP may resume transmission of traffic via the first gNB-DU. The above method applies to both DL leg switch and UL leg switch.
  • the first control information associated to unlicensed spectrum operation at the CU-UP can be indication(s) to reduce downlink data due to consistent LBT failure.
  • the first control information associated to unlicensed spectrum operation at the CU-UP can be indication(s) to increase downlink data due to recovery from consistent LBT failure.
  • the first control information associated to unlicensed spectrum operation at the CU- UP can be indication(s) to switch traffic to a different transmission leg.
  • the first control information associated to unlicensed spectrum operation at the CU- UP can be indication triggering the signaling to the gNB-DU to discard one or more DL PDUs (e.g., in case such PDUs are decided to be transmitted via a different transmission leg).
  • the first control information associated to unlicensed spectrum operation at the CU-UP can be indication triggering the signaling to the gNB-DU of the polling flag for one of the PDU types containing the unlicensed Spectrum assistance information. This could be triggered if the first node wants to monitor LBT failure events in a specific way.
  • a third network node (CU-CP) based on the received second set of unlicensed spectrum assistance information:
  • (d) (optionally) sends second control information associated to unlicensed spectrum operation to the first network node via El interface for controlling DL/UL user plane transmissions.
  • the second control information associated to unlicensed spectrum operation at the CU- CP, based on reception of the second set of unlicensed spectrum assistance information can be one or more of the following:
  • the third network node i.e. gNB-CU-CP, based on second control information associated to unlicensed spectrum operation, determines updated values for RRC parameters related to Energy Detection Threshold for unlicensed spectrum channel access (e.g. maxEnergyDetectionThreshold or energyDetectionThresholdOffset), and/or RRC parameters for detection of consistent uplink LBT failures for operation with shared spectrum channel access (e.g. Ibt-FailurelnstanceMaxCount or Ibt-FailureDetectionTimer).
  • RRC parameters related to Energy Detection Threshold for unlicensed spectrum channel access e.g. maxEnergyDetectionThreshold or energyDetectionThresholdOffset
  • RRC parameters for detection of consistent uplink LBT failures for operation with shared spectrum channel access e.g. Ibt-FailurelnstanceMaxCount or Ibt-FailureDetectionTimer.
  • the third network node is a gNB-CU-CP, which, based on second control information associated to unlicensed spectrum operation, indicates to other gNB-DUs connected to the gNB-CU-CP and/or other gNB-CU-CPs that could also benefit from the knowledge of certain cells experiencing LBT issues.
  • CU-CP might be aware of which all cells on the same frequency are neighbors of each other. In such a scenario, upon realizing that at least one of those cells experienced consistent LBT issues, the CU-CP could convey this information to the rest of the neighbors of this cell either via Fl interface or via X2/Xn interface or via NG/S1 interface.
  • the first network node may have sent a request to the second network node to receive second control information associated to unlicensed spectrum operation.
  • the third network node may have sent a request to the second network node to receive second control information associated to unlicensed spectrum operation.
  • the second set of unlicensed spectrum assistance information transmitted by the second network node to the first or third network node may be transmitted periodically in which case the unlicensed spectrum assistance information message will the plurality of information disclosed above as collected within the time interval between two message transmissions; alternatively, they may be transmitted when a certain event occur, e.g. when the first network node receives from the wireless terminal the first set of unlicensed spectrum assistance information disclosed above.
  • the second network node upon receiving the first set of unlicensed spectrum assistance information associated to a serving cell from a UE, refrains from scheduling other UEs served by the same serving cell.
  • the second network node may also deactivate the serving cell, a SCell, for the UE that transmitted the first set of unlicensed spectrum assistance information and for other UEs which currently have this SCell activated.
  • the second network node may resume scheduling operation or may reactivate the concerned SCell upon receiving a second first set of unlicensed spectrum assistance information from the UE indicating that the LBT issues are alleviated, e.g. the second received first set of unlicensed spectrum assistance information indicates less LBT failures or less consistent LBT failures in the serving cell over the measured period compared with the first received first set of unlicensed spectrum assistance information.
  • the unlicensed spectrum assistance information can be passed between different nodes or entities in different ways, across different interfaces, with various orders, and in different directions. So forth, a third, a second and a fourth network nodes have been referred to, but chain of information transfer involving a fourth network node (and even more network nodes) are also conceivable. The following are descriptions of some examples of chains of transfer of unlicensed spectrum assistance information.
  • Figure 8, Figure 9, Figure 10, Figure 11, Figure 12, and Figure 13 illustrate non-limiting examples of chains of transfer of unlicensed spectrum assistance information.
  • this may be optional, i.e. the same example of information transfer chain can be conceived without the UE generating and transferring any assistance information (i.e., without the UE involved in the chain).
  • each instance of transfer of unlicensed spectrum assistance information some part(s) of the information may be removed and/or some additional information may be added.
  • each of the instances of transfer of unlicensed spectrum assistance information may have been preceded by a request from the receiver of the unlicensed spectrum assistance information to the sender of the unlicensed spectrum assistance information, requesting the sender of the unlicensed spectrum assistance information to send such unlicensed spectrum assistance information.
  • each receiver of unlicensed spectrum assistance information may previously have sent an indication to the corresponding sender of unlicensed spectrum assistance information, where the indication is an initiation of a subscription for unlicensed spectrum assistance information, whenever this becomes available, or the indication is a request for unlicensed spectrum assistance information to be sent periodically, or the indication is a request for unlicensed spectrum assistance information to be sent whenever the unlicensed spectrum assistance information implies that a certain condition has been fulfilled, e.g. in terms of a threshold frequency of LBT failures.
  • a wireless terminal receives from a third network node a new configuration obtained according to second control information associated to unlicensed spectrum operation and applies the new configuration.
  • the wireless terminal may also contribute to the generation of assistance information related to unlicensed spectrum operation, e.g. in terms of channel availability (the uplink perspective) statistics.
  • the wireless terminal may transfer such assistance information to the first network node, the second network node or the third network node, e.g. to a gNB-DU (e.g., via MAC signaling), a gNB-CU (e.g., via RRC signaling) or a gNB-CU-CP (e.g., via RRC signaling).
  • a gNB-DU e.g., via MAC signaling
  • a gNB-CU e.g., via RRC signaling
  • a gNB-CU-CP e.g., via RRC signaling
  • Unlicensed spectrum assistance information can be one or more of the following:
  • radio bearers i.e., both data radio bearers and signaling radio bearers
  • radio bearers i.e., both data radio bearers and signaling radio bearers
  • radio bearers i.e., both data radio bearers and signaling radio bearers
  • - average for radio bearers i.e., both data radio bearers and signaling radio bearers
  • Such indication is relative to a specific amount of time. Such amount of time may be explicitly included in the assistance information
  • Such indication is relative to a specific threshold, i.e. if the channel was determined to be unavailable for a time equal or higher than the threshold the indication is triggered Such indication is relative to the overall amount of time the RAN node used to sense the channel, where such sensing process led to determining that the channel is occupied.
  • unlicensed spectrum assistance information where it may be applicable to distinguish/separate information pertaining to the UL and information pertaining to the DL and optionally information pertaining to both the UL and the DL (e.g., combining information pertaining to the UL and information pertaining to the DL), and where such a separation of the information has not been done, such a separation is conceivable, resulting in a further multitude of examples.
  • Figure 14 The process of Figure 14 involves a UE 1400, a first network node 1402 (e.g., gNB-CU-UP), a second network node 1404 (e.g., gNB-DU), and a third network node 1406 (e.g., eNB-CU-CP).
  • the steps of Figure 14 are as follows:
  • the UE1400 sends, to the second network node 1404 (e.g., the gNB-DU), a first set of unlicensed spectrum assistance information. Details regarding the first set of unlicensed spectrum assistance information are provided above and, as such, are not repeated here.
  • the third network node 1406 (e.g., the gNB-CU-CP) sends, to the first network node 1402 (e.g., the gNB-CU-UP), a request for second control information associated to unlicensed spectrum operation. Details regarding the second control information associated to unlicensed spectrum operation are provided above and, as such, are not repeated here.
  • the first network node 1402 (e.g., the gNB-CU-UP) sends, to the second network node 1404 (e.g., the gNB-DU), a request for unlicensed spectrum assistance information.
  • the second network node 1404 (e.g., the gNB-DU) sends, to the first network node 1402 (e.g., the gNB-CU-UP), a second set of unlicensed spectrum assistance information, which may be the same information as the first set of unlicensed spectrum assistance information sent by the UE 1400 (in step 1408) or new unlicensed spectrum assistance information generated by the second network node 1404 (e.g., the gNB-DU).
  • the second network node 1404 (e.g., the gNB-DU) sends, to the third network node 1406 (e.g., the gNB-CU-UP), a second set of unlicensed spectrum assistance information (e.g., the gNB-CU-CP), which may be the same information as the first set of unlicensed spectrum assistance information sent by the UE 1400 (in step 1408) or new unlicensed spectrum assistance information generated by the second network node 1404 (e.g., the gNB-DU).
  • the third network node 1406 e.g., the gNB-CU-UP
  • a second set of unlicensed spectrum assistance information e.g., the gNB-CU-CP
  • the first network node 1402 determines first control information for regulating user plane data transmission (TX) or reception (RX). Details regarding the first control information are provided above and, as such, are not repeated here.
  • the first network node 1402 determines second control information for controlling configuration or operation of the UE 1400.
  • the first network node 1402 (e.g., the gNB-CU-UP) sends, to the third network node 1406 (e.g., the gNB-CU-CP), the second control information associated to unlicensed spectrum operation.
  • the third network node 1406 e.g., the gNB-CU-CP
  • the third network node 1406 (e.g., the gNB-CU-CP) uses the second control information associated to unlicensed spectrum operation for configuring or reconfiguring UEs and cells.
  • the third network node 1406 e.g., the gNB-CU-CP reconfigures the UE 1400 based on the second control information associated to unlicensed spectrum operation.
  • step 1426 the UE 1400 applies reconfiguration determined based on the second control information associated to unlicensed spectrum operation.
  • the DL DATA DELIVERY STATUS frame may also include an indication of detected radio link outage or radio link resume or LBT outage for the concerned data radio bearer.
  • the node hosting the NR PDCP entity When receiving an indication of radio link outage detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is unavailable at the corresponding node both in UL and DL.
  • the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is available at the corresponding node both in UL and in DL.
  • the node hosting the NR PDCP entity When receiving an indication of UL or DL radio link outage detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is unavailable at the corresponding node for UL or DL, depending on the indicated outage.
  • the node hosting the NR PDCP entity When receiving an indication of UL or DL radio link resume detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is available at the corresponding node in UL or in DL, depending on the indicated resume.
  • the node hosting the NR PDCP entity When receiving an indication of LBT outage detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is unavailable at the corresponding node both in UL and DL.
  • This parameter indicates specific events reported by the corresponding node.
  • the DL Radio Quality Index is a numerical index expressing the radio quality of the data radio bearer or the RLC entity in DL, where the value 0 represents the lowest quality.
  • the UL Radio Quality Index is a numerical index expressing the radio quality of the data radio bearer or the RLC entity in UL, where the value 0 represents the lowest quality.
  • the averaging window for the Average CQI, Average HARQ Failure and Average HARQ Retransmission is set by means of configuration.
  • Power Headroom Report is PHR MAC control element reported by as defined in 3GPP TS 36.321 [4] and 3GPP TS 38.321 [5], The averaging period for Average number of LBT Failure is set by means of configuration.
  • This message is sent by the gNB-CU to request the setup of a UE context.
  • the purpose of the UE Context Modification Required procedure is to modify the established UE Context, e.g., modifying and releasing radio bearer resources, or sidelink radio bearer resources or candidate cells in conditional handover or conditional PSCell change.
  • the procedure uses UE-associated signalling.
  • the F1AP UE CONTEXT MODIFICATION REQUIRED message is initiated by the gNB- DU.
  • the gNB-CU reports the successful update of the UE context in the UE CONTEXT MODIFICATION CONFIRM message.
  • the gNB-CU shall consider that only the resources reserved for the candidate cells identified by the included NR CGIs and associated to the UE-associated signaling identified by the gNB-CU UE F1AP ID IE and the gNB-CU UE F1AP ID IE are about to be released by the gNB-DU.
  • the gNB-CU should not consider the cells included in the Cells with consistent LBT Failure List IE for Carrier Aggregation and MR-DC operation.
  • This message is sent by the gNB-DU to request the modification of a UE context.
  • Figure 18 shows an example of a communication system 1800 in accordance with some embodiments.
  • the communication system 1800 includes a telecommunication network 1802 that includes an access network 1804, such as a Radio Access Network (RAN), and a core network 1806, which includes one or more core network nodes 1808.
  • the access network 1804 includes one or more access network nodes, such as network nodes 1810A and 1810B (one or more of which may be generally referred to as network nodes 1810), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • 3GPP Third Generation Partnership Project
  • the network nodes 1810 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 1812A, 1812B, 1812C, and 1812D (one or more of which may be generally referred to as UEs 1812) to the core network 1806 over one or more wireless connections.
  • UE User Equipment
  • a network node can be a RAN node, a gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, gNB- CU-UP, gNB-DU, eNB-CU, eNB-CU-CP, eNB-CU-UP, eNB-DU, Integrated Access and Backhaul (lAB)-node, lAB-donor- DU, lAB-donor-CU, lAB-donor-CU-CP, lAB-donor-CU-UP, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB.
  • lAB Integrated Access and Backhaul
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1800 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1812 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1810 and other communication devices.
  • the network nodes 1810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1812 and/or with other network nodes or equipment in the telecommunication network 1802 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1802.
  • the core network 1806 connects the network nodes 1810 to one or more hosts, such as host 1816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1806 includes one more core network nodes (e.g., core network node 1808) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1808.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1816 may be under the ownership or control of a service provider other than an operator or provider of the access network 1804 and/or the telecommunication network 1802, and may be operated by the service provider or on behalf of the service provider.
  • the host 1816 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1800 of Figure 18 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 1800 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile
  • the telecommunication network 1802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1802. For example, the telecommunication network 1802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and/or massive Machine Type Communication (mMTC)/massive Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 1812 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1804.
  • a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. be configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi-Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 1814 communicates with the access network 1804 to facilitate indirect communication between one or more UEs (e.g., UE 1812C and/or 1812D) and network nodes (e.g., network node 1810B).
  • the hub 1814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1814 may be a broadband router enabling access to the core network 1806 for the UEs.
  • the hub 1814 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • Commands or instructions may be received from the UEs, network nodes 1810, or by executable code, script, process, or other instructions in the hub 1814.
  • the hub 1814 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1814 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 1814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • VR Virtual Reality
  • the hub 1814 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 1814 may have a constant/persistent or intermittent connection to the network node 1810B.
  • the hub 1814 may also allow for a different communication scheme and/or schedule between the hub 1814 and UEs (e.g., UE 1812C and/or 1812D), and between the hub 1814 and the core network 1806.
  • the hub 1814 is connected to the core network 1806 and/or one or more UEs via a wired connection.
  • the hub 1814 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 1804 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 1810 while still connected via the hub 1814 via a wired or wireless connection.
  • the hub 1814 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1810B.
  • the hub 1814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 1810B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • eMTC
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehi cl e-to- Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle- to-Everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input/output interface 1906, a power source 1908, memory 1910, a communication interface 1912, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 19. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1910.
  • the processing circuitry 1902 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1902 may include multiple Central Processing Units (CPUs).
  • the input/output interface 1906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 1900.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1908 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1908 may further include power circuitry for delivering power from the power source 1908 itself, and/or an external power source, to the various parts of the UE 1900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 1908.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1908 to make the power suitable for the respective components of the UE 1900 to which power is supplied.
  • the memory 1910 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1910 includes one or more application programs 1914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1916.
  • the memory 1910 may store, for use by the UE 1900, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1910 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD-DVD High Density Digital Versatile Disc
  • HDDS Holographic Digital Data Storage
  • DIMM Dual In-line Memory Module
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 1910 may allow the UE 1900 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 1910, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1902 may be configured to communicate with an access network or other network using the communication interface 1912.
  • the communication interface 1912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1922.
  • the communication interface 1912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1918 and/or a receiver 1920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1918 and receiver 1920 may be coupled to one or more antennas (e.g., the antenna 1922) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1912 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS Global Positioning System
  • Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband CDMA
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR Fifth Generation
  • UMTS Worldwide Interoperability for Mobile communications
  • WiMax Ethernet
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • SONET Synchronous Optical Networking
  • ATM Asynchronous Transfer Mode
  • QUIC Quick User Datagram Protocol Internet Connection
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 1912, or via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare.
  • Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • FIG 20 shows a network node 2000 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment in a telecommunication network.
  • Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
  • APs e.g., radio APs
  • BSs Base Stations
  • eNBs evolved Node Bs
  • gNBs NR Node Bs
  • BSs may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto BSs, pico BSs, micro BSs, or macro BSs.
  • a BS may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio BS may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi -Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR Transmission Point
  • MSR Multi -Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • the network node 2000 includes processing circuitry 2002, memory 2004, a communication interface 2006, and a power source 2008.
  • the network node 2000 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 2000 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node 2000 may be configured to support multiple RATs.
  • the network node 2000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 2000.
  • the processing circuitry 2002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node 2000 components, such as the memory 2004, to provide network node 2000 functionality.
  • the processing circuitry 2002 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 2002 includes one or more of Radio Frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014. In some embodiments, the RF transceiver circuitry 2012 and the baseband processing circuitry 2014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 2012 and the baseband processing circuitry 2014 may be on the same chip or set of chips, boards, or units.
  • SOC System on a Chip
  • the processing circuitry 2002 includes one or more of Radio Frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014.
  • RF transceiver circuitry 2012 and the baseband processing circuitry 2014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 2012 and the baseband processing circuitry
  • the memory 2004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 2002.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer-
  • the memory 2004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 2002 and utilized by the network node 2000.
  • the memory 2004 may be used to store any calculations made by the processing circuitry 2002 and/or any data received via the communication interface 2006.
  • the processing circuitry 2002 and the memory 2004 are integrated.
  • the communication interface 2006 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 2006 comprises port(s)/terminal(s) 2016 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 2006 also includes radio front-end circuitry 2018 that may be coupled to, or in certain embodiments a part of, the antenna 2010.
  • the radio front-end circuitry 2018 comprises filters 2020 and amplifiers 2022.
  • the radio front-end circuitry 2018 may be connected to the antenna 2010 and the processing circuitry 2002.
  • the radio front-end circuitry 2018 may be configured to condition signals communicated between the antenna 2010 and the processing circuitry 2002.
  • the radio front-end circuitry 2018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 2018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 2020 and/or the amplifiers 2022.
  • the radio signal may then be transmitted via the antenna 2010.
  • the antenna 2010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2018.
  • the digital data may be passed to the processing circuitry 2002.
  • the communication interface 2006 may comprise different components and/or different combinations of components.
  • the network node 2000 does not include separate radio front-end circuitry 2018; instead, the processing circuitry 2002 includes radio front-end circuitry and is connected to the antenna 2010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2012 is part of the communication interface 2006. In still other embodiments, the communication interface 2006 includes the one or more ports or terminals 2016, the radio front-end circuitry 2018, and the RF transceiver circuitry 2012 as part of a radio unit (not shown), and the communication interface 2006 communicates with the baseband processing circuitry 2014, which is part of a digital unit (not shown).
  • the antenna 2010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 2010 may be coupled to the radio front-end circuitry 2018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 2010 is separate from the network node 2000 and connectable to the network node 2000 through an interface or port.
  • the antenna 2010, the communication interface 2006, and/or the processing circuitry 2002 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 2000. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 2010, the communication interface 2006, and/or the processing circuitry 2002 may be configured to perform any transmitting operations described herein as being performed by the network node 2000. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 2008 provides power to the various components of the network node 2000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 2008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2000 with power for performing the functionality described herein.
  • the network node 2000 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2008.
  • the power source 2008 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 2000 may include additional components beyond those shown in Figure 20 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 2000 may include user interface equipment to allow input of information into the network node 2000 and to allow output of information from the network node 2000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2000.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hardwired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by a system including a first network node (e.g., an gNB-CU-UP), a second network node (e.g., an gNB-DU), and a third network node (e.g., an gNB-CU-CP), comprising:
  • a first network node e.g., an gNB-CU-UP
  • a second network node e.g., an gNB-DU
  • a third network node e.g., an gNB-CU-CP
  • the first network node e.g., an gNB-CU-UP
  • the second network node e.g., an gNB-DU
  • the second network node e.g., an gNB-DU: o receiving (1408), from a User Equipment, UE, a first set of unlicensed spectrum assistance information; and o sending (1414), to the first network node (e.g., an gNB-CU-UP), a second set of the unlicensed spectrum assistance information;
  • Embodiment 2 The method of embodiment 1 further comprising, at the first network node (e.g., an gNB-CU-UP), determining (1418) second control information associated to unlicensed spectrum operation based on the second set of unlicensed spectrum assistance information.
  • the first network node e.g., an gNB-CU-UP
  • Embodiment 3 The method of embodiment 2 further comprising, at the first network node (e.g., an gNB-CU-UP), sending (1420), to the third network node (e.g., an gNB-CU-CP), the second control information associated to unlicensed spectrum operation.
  • the first network node e.g., an gNB-CU-UP
  • the third network node e.g., an gNB-CU-CP
  • Embodiment 4 The method of any of embodiments 1 to 3 further comprising, at the second network node (e.g., an gNB-DU), sending (1414A), to the third network node (e.g., an gNB-CU-CP), the second set of unlicensed spectrum assistance information.
  • the second network node e.g., an gNB-DU
  • sending 1414A
  • the third network node e.g., an gNB-CU-CP
  • Embodiment 5 A method performed by a first network node (e.g., an gNB-CU-UP) for reconfiguring a User Equipment, UE, operating in unlicensed spectrum, comprising:
  • Embodiment 6 The method of embodiment 5, further comprising sending (1420), to a third network node (e.g., an gNB-CU-CP), the second control information associated to unlicensed spectrum operation.
  • a third network node e.g., an gNB-CU-CP
  • the second set of unlicensed spectrum assistance information comprises one or more of:
  • Embodiment 8 The method of any of embodiments 5 to 7 further comprising determining (1416) first control information for regulating user plane data transmission or reception.
  • Embodiment 9 The method of any of embodiments 5 to 8, wherein the first control information comprises one or more of:
  • Embodiment 10 The method of any of embodiments 5 to 9, wherein the second control information associated to unlicensed spectrum operation comprises one or more of: (a) reconfiguration for a UE if the second set of unlicensed spectrum assistance information indicates that a certain cell is subject to be deactivated due to consistent Listen-Before-Talk, LBT, failures, (b) reconfiguration for a UE if the second set of unlicensed spectrum assistance information indicates that LBT performances are improving.
  • Embodiment 11 The method of any of embodiments 5 to 10 further comprising:
  • Embodiment 12 T method performed by a second network node (e.g., an gNB-DU) for reconfiguring a User Equipment, UE, operating in unlicensed spectrum, comprising:
  • Embodiment 13 The method of embodiment 12, further comprising sending (1414A), to a third network node (e.g., an gNB-CU-CP), the second set of unlicensed spectrum assistance information.
  • a third network node e.g., an gNB-CU-CP
  • Embodiment 14 The method of embodiment 12 or 13, further comprising receiving (1412), from the first network node (e.g., an gNB-CU-UP), a request for the second set of unlicensed spectrum assistance information.
  • the first network node e.g., an gNB-CU-UP
  • Embodiment 15 The method of any of embodiments 12 to 14, wherein the second set of unlicensed spectrum assistance information comprises one or more of:
  • Embodiment 16 A method performed by a third network node (e.g., an gNB-CU-CP) for reconfiguring a User Equipment, UE, operating in unlicensed spectrum, comprising:
  • Embodiment 17 The method of embodiment 16, further comprising sending (1410) a request for the second control information associated to an unlicensed spectrum operation.
  • Embodiment 18 The method of embodiment 16 or 17, determining (1422) reconfiguration of the UE based on the second control information associated to unlicensed spectrum operation comprises (a) reconfiguration of the UE if the second set of unlicensed spectrum assistance information indicates that a certain cell is subject to be deactivated due to consistent Listen -Before-Talk, LBT, failures or (b) reconfiguration for a UE if the second set of unlicensed spectrum assistance information indicates that LBT performances are improving.
  • Embodiment 19 The method of any of embodiments 16 to 18, wherein the second control information associated to unlicensed spectrum operation comprises one or more of: (a) reconfiguration for a UE if the second set of unlicensed spectrum assistance information indicates that a certain cell is subject to be deactivated due to consistent Listen-Before-Talk, LBT, failures, (b) reconfiguration for a UE if the second set of unlicensed spectrum assistance information indicates that LBT performances are improving.
  • Embodiment 20 A method performed by a User Equipment, UE, operating in unlicensed spectrum, comprising:
  • Embodiment 21 The method of embodiment 20, wherein the first set of unlicensed spectrum assistance information comprises one or more of:
  • Embodiment 22 The method of embodiment 20 or 21, wherein reconfiguration instruction is determined, by the third network node (e.g., an gNB-CU-CP), based on second control information associated to unlicensed spectrum operation.
  • the third network node e.g., an gNB-CU-CP
  • Embodiment 23 A first network node (e.g., an gNB-CU-UP) adapted to:
  • Embodiment 24 The first network node (e.g., an gNB-CU-UP) of embodiment 23 wherein the first network node (e.g., an gNB-CU-UP) is further adapted to perform the method of any of embodiments 6 to 11.
  • the first network node e.g., an gNB-CU-UP
  • Embodiment 25 A first network node (e.g., an gNB-CU-UP) comprising processing circuitry configured to cause the first network node (e.g., an gNB-CU-UP) to:
  • a first network node e.g., an gNB-CU-UP
  • processing circuitry configured to cause the first network node (e.g., an gNB-CU-UP) to:
  • Embodiment 26 The first network node (e.g., an gNB-CU-UP) of embodiment 25 wherein the processing circuitry is further configured to cause the first network node (e.g., an gNB-CU-UP) to perform the method of any of embodiments 6 to 11.
  • the processing circuitry is further configured to cause the first network node (e.g., an gNB-CU-UP) to perform the method of any of embodiments 6 to 11.
  • Embodiment 27 A second network node (e.g., an gNB-DU) adapted to:
  • Embodiment 28 The second network node (e.g., an gNB-DU) of embodiment 27 wherein the second network node (e.g., an gNB-DU) is further adapted to perform the method of any of embodiments 13 to 15.
  • Embodiment 29 A second network node (e.g., an gNB-DU) comprising processing circuitry configured to cause the second network node (e.g., an gNB-DU) to:
  • Embodiment 30 The second network node (e.g., an gNB-DU) of embodiment 29 wherein the processing circuitry is further configured to cause the second network node (e.g., an gNB-DU) to perform the method of any of embodiments 13 to 15.
  • the processing circuitry is further configured to cause the second network node (e.g., an gNB-DU) to perform the method of any of embodiments 13 to 15.
  • Embodiment 31 A third network node (e.g., an gNB-CU-CP) adapted to:
  • Embodiment 32 The third network node (e.g., an gNB-CU-CP) of embodiment 31 wherein the third network node (e.g., an gNB-CU-CP) is further adapted to perform the method of any of embodiment 17 to 19.
  • the third network node e.g., an gNB-CU-CP
  • Embodiment 33 A third network node (e.g., an gNB-CU-CP) comprising processing circuitry configured to cause the third network node (e.g., an gNB-CU-CP) to:
  • a third network node e.g., an gNB-CU-CP
  • processing circuitry configured to cause the third network node (e.g., an gNB-CU-CP) to:
  • Embodiment 34 The third network node (e.g., an gNB-CU-CP) of embodiment 33 wherein the processing circuitry is further configured to cause the third network node (e.g., an gNB-CU-CP) to perform the method of any of embodiment 17 to 19.
  • the processing circuitry is further configured to cause the third network node (e.g., an gNB-CU-CP) to perform the method of any of embodiment 17 to 19.
  • Embodiment 35 A User Equipment, UE, adapted to:
  • Embodiment 36 The UE of embodiment 35 wherein the UE is further adapted to perform the method of embodiment 21 or 22.
  • Embodiment 37 A User Equipment, UE, comprising:
  • processing circuitry associated with the one or more transmitters and the one or more receivers configured to cause the UE to: o send (1408), to a second network node (e.g., an gNB-DU), a first set of unlicensed spectrum assistance information; o receive (1424), from a third network node (e.g., an gNB-CU-CP), a reconfiguration instruction; and o apply (1426) the reconfiguration instruction.
  • Embodiment 38 The UE of embodiment 37 wherein the processing circuitry is further configured to cause the UE to perform the method of embodiment 21 or 22.

Landscapes

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

Abstract

Sont divulgués des systèmes et procédés qui permettent de prendre en considération des informations d'assistance de spectre sans licence dans une optimisation de réseau d'accès radio (RAN) et une reconfiguration potentielle d'équipements utilisateurs (UE) utilisant un spectre sans licence. Dans un mode de réalisation, un procédé réalisé par un système comprenant une partie plan utilisateur d'unité centrale de station de base (CU-UP), une unité distribuée de station de base (DU) et une partie de plan de commande d'unité centrale de station de base (CU-CP) consiste, au niveau de la station de base DU, à envoyer un ensemble d'informations d'assistance de spectre sans licence à la CU-UP de station de base et/ou à la CU-CP de station de base. Le procédé consiste en outre, au niveau de la CU-UP de station de base et/ou de la CU-CP de station de base, à recevoir l'ensemble d'informations d'assistance de spectre sans licence en provenance de la DU de station de base et à réaliser une ou plusieurs actions associées à une opération de spectre sans licence sur la base de l'ensemble d'informations d'assistance de spectre sans licence.
PCT/SE2022/051226 2022-01-07 2022-12-22 Informations d'assistance pour spectre sans licence dans une architecture distribuée WO2023132766A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263297491P 2022-01-07 2022-01-07
US63/297,491 2022-01-07

Publications (1)

Publication Number Publication Date
WO2023132766A1 true WO2023132766A1 (fr) 2023-07-13

Family

ID=84799595

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/051226 WO2023132766A1 (fr) 2022-01-07 2022-12-22 Informations d'assistance pour spectre sans licence dans une architecture distribuée

Country Status (1)

Country Link
WO (1) WO2023132766A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180367273A1 (en) * 2017-06-16 2018-12-20 Kyungmin Park Distributed Unit Status Information
EP3512247A1 (fr) * 2018-01-11 2019-07-17 Comcast Cable Communications LLC Rapport d'échec de connexion
GB2597793A (en) * 2020-08-06 2022-02-09 Nec Corp Communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180367273A1 (en) * 2017-06-16 2018-12-20 Kyungmin Park Distributed Unit Status Information
EP3512247A1 (fr) * 2018-01-11 2019-07-17 Comcast Cable Communications LLC Rapport d'échec de connexion
GB2597793A (en) * 2020-08-06 2022-02-09 Nec Corp Communication system

Non-Patent Citations (10)

* Cited by examiner, † Cited by third party
Title
3GPP TECHNICAL SPECIFICATION (TS) 38.300, December 2021 (2021-12-01)
3GPP TS 36.321
3GPP TS 37.213, September 2021 (2021-09-01)
3GPP TS 38.321
3GPP TS 38.321, vol. 2021-12, December 2021 (2021-12-01)
3GPP TS 38.331, December 2021 (2021-12-01)
3GPP TS 38.401, December 2021 (2021-12-01)
3GPP TS 38.425
3GPP TS 38.425, April 2021 (2021-04-01)
3GPP TS 38.473, 23 December 2021 (2021-12-23)

Similar Documents

Publication Publication Date Title
US11924875B2 (en) Transmission in unlicensed frequency spectrum
WO2023209668A1 (fr) Signalisation et mécanismes pour scénarios de liaison latérale à sauts multiples de transmission de message de découverte d'ue relais
WO2023041033A1 (fr) Dispositif terminal, nœud de réseau, et procédés en leur sein
US20240223326A1 (en) Handling of Medium Access Control (MAC) Entity during Secondary Cell Group (SCG) Deactivation/Reactivation
WO2023163629A1 (fr) Adaptation de puissance de transmission de réseau économe en énergie
WO2023073210A1 (fr) Déclenchement et rétablissement après défaillance de liaison radio en cas d'agrégation de porteuses de liaison latérale
EP4381892A1 (fr) Rapport de libération de réseau initiée par un ue
WO2023132766A1 (fr) Informations d'assistance pour spectre sans licence dans une architecture distribuée
TWI827287B (zh) 基於混合arq考量之控制通道監控
WO2024198690A1 (fr) Transmission avec contrainte sur des occasions de psfch sautées
WO2024208193A1 (fr) (re)sélection d'une procédure de priorisation de canal logique (lcp) et gestion de ressources radioélectriques
US20240187991A1 (en) User Equipment (UE) Feedback for Improved Energy Efficiency Configuration
WO2024099218A1 (fr) Communication de liaison latérale avec de multiples ressources de rétroaction
WO2023217659A1 (fr) Communication de liaison latérale entrelacée
CN118176819A (zh) 对于去激活的辅小区组（scg）的波束失败检测和恢复
WO2024210818A1 (fr) Rapport de défaillances d'écoute avant de parler de liaison montante cohérentes dans des canaux partagés
WO2024030060A1 (fr) Rapport d'informations d'accès aléatoire relatives à des événements ou à des opérations dans des canaux partagés
WO2024209448A1 (fr) Saut de transmission de liaison montante avec indication d'uto
WO2023146458A1 (fr) Collecte de mesures relatives à une couverture étendue d'un réseau d'accès radio (ran)
WO2024028840A1 (fr) Rapport d'informations d'assistance d'équipement utilisateur pour faciliter des économies d'énergie de réseau d'accès radio
WO2023106982A1 (fr) Configuration de groupes de cellules dans lesquels des signaux de référence ne sont pas émis par toutes les cellules
WO2024102039A1 (fr) Approches pour une gestion d'étalement de retard
WO2023249529A1 (fr) Gestion de problèmes de coexistence dans un dispositif
EP4409966A1 (fr) Indication de prise en charge de réseau de diverses fonctionnalités de liaison latérale (sl)
WO2024043826A1 (fr) Réutilisation par l'équipement utilisateur de l'avance temporelle obtenue lors de la réception de données pour la transmission ultérieure de données

Legal Events

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

Ref document number: 22835915

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE