WO2023239279A1 - Noeud de réseau radio, équipement utilisateur et procédés exécutés dans celui-ci - Google Patents

Noeud de réseau radio, équipement utilisateur et procédés exécutés dans celui-ci Download PDF

Info

Publication number
WO2023239279A1
WO2023239279A1 PCT/SE2023/050557 SE2023050557W WO2023239279A1 WO 2023239279 A1 WO2023239279 A1 WO 2023239279A1 SE 2023050557 W SE2023050557 W SE 2023050557W WO 2023239279 A1 WO2023239279 A1 WO 2023239279A1
Authority
WO
WIPO (PCT)
Prior art keywords
measurement
lbt
delay
network node
radio network
Prior art date
Application number
PCT/SE2023/050557
Other languages
English (en)
Inventor
Johan Rune
Angelo Centonza
Marco BELLESCHI
Pradeepa Ramachandra
Luca LUNARDI
Tahmineh TORABIAN ESFAHANI
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 WO2023239279A1 publication Critical patent/WO2023239279A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]

Definitions

  • Embodiments herein relate to a radio network node, a user equipment (UE) and methods performed therein regarding wireless communication. Furthermore, a computer program and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication, such as handling or controlling measurements, in a wireless communications network.
  • UE user equipment
  • UEs also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN).
  • the RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB.
  • the service area or cell is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node.
  • the radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.
  • DL downlink
  • UL uplink
  • a Universal Mobile Telecommunications System is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM).
  • the UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipment.
  • WCDMA wideband code division multiple access
  • HSPA High-Speed Packet Access
  • 3GPP Third Generation Partnership Project
  • telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity.
  • 3GPP Third Generation Partnership Project
  • radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto.
  • RNC radio network controller
  • BSC base station controller
  • the RNCs are typically connected to one or more core networks.
  • the Evolved Packet System comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN also known as the Long-Term Evolution (LTE) radio access network
  • EPC also known as System Architecture Evolution (SAE) core network.
  • E- UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network.
  • the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.
  • Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions.
  • a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.
  • NG-RAN 5G RAN
  • the next generation (NG)-RAN architecture can be further described as follows.
  • the NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface.
  • An gNB can support frequency division duplex (FDD) mode, time division duplex (TDD) mode or dual mode operation.
  • gNBs can be interconnected through the Xn interface.
  • a gNB may consist of a gNB-central unit (CU) and gNB-distributed units (DU).
  • CU gNB-central unit
  • DU gNB-distributed units
  • a gNB-CU and a gNB-DU are connected via the F1 logical interface.
  • one gNB-DU is connected to only one gNB-CU.
  • a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation.
  • NG, Xn and F1 are logical interfaces.
  • the NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the NG-RAN architecture i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, F1 For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signalling transport.
  • a gNB may also be connected to an LTE eNB via the X2 interface.
  • nr-gNB an LTE eNB connected to the EPC network is connected over the X2 interface with a so called nr-gNB.
  • the latter is a gNB not connected directly to a CN and connected via X2 to an eNB for the sole purpose of performing dual connectivity.
  • the architecture in Fig. 1 can be expanded by splitting the gNB-Cll into two entities: One gNB-CU-user plane (UP), which serves the user plane and hosts the packet data convergence protocol (PDCP) protocol and one gNB-CU-control plane (CP), which serves the control plane and hosts the PDCP and radio resource control (RRC) protocol.
  • UP packet data convergence protocol
  • CP gNB-CU-control plane
  • RRC radio resource control
  • a gNB-CU-CP and a gNB-CU-UP communicate over the E1 interface.
  • a gNB-DU hosts the radio link control (RLC), media access control (MAC) and physical (PHY) protocols.
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • NR 5 th generation of cellular system
  • MTC machine type communication
  • URLLC ultra-reliable low- latency communication
  • D2D side-link device-to-device
  • a slot consists of 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 kHz the OFDM symbol duration is ⁇ 33 ps.
  • a slot with 14 symbols for the same subcarrier spacing (SOS) is 500 ps long, including cyclic prefixes.
  • NR also supports flexible bandwidth configurations for different UEs on the same serving cell.
  • 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 signalled to a UE, where a bandwidth part consists of a group of contiguous physical resource blocks (PRB). Reserved resources can be configured within the bandwidth part.
  • the bandwidth of a bandwidth part equals to or is smaller than the maximal bandwidth capability supported by a UE.
  • NR is targeting both licensed and unlicensed spectrum 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, i.e., 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. Some NR features are adapted in NR-ll to comply with the special characteristics of the unlicensed band as well as different regulations. The technology primarily targets subcarrier spacings of 15 kHz or 30 kHz in carrier frequencies below 6 GHz.
  • LBT listen before talk
  • CCA Clear Channel Assessment
  • the sensing is done over 20 MHz channels and this is also the sensing bandwidth used in NR-ll, where such 20 MHz bandwidths/channels are often referred to as bandwidth parts (BWP), when the full NR-ll operating bandwidth is greater than 20 MHz.
  • BWP bandwidth parts
  • Many devices are capable of transmitting, and receiving, over a wide bandwidth including of multiple sub-bands/channels, e.g., multiple LBT sub-bands, i.e. , the frequency part with a bandwidth equal to LBT bandwidth.
  • a device is only allowed to transmit on the sub-bands, i.e., 20 MHz BWPs, where the medium is sensed as free. Again, there are different flavours 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 subbands were sensed as free.
  • CC component carrier
  • the other way is that the device operates almost independent processing chains for each channel.
  • 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 (RAT), as well as independent systems with the same RAT.
  • a radio device applies a CCA check, i.e., channel sensing before any transmission.
  • the transmitter involves energy detection (ED) over a time period compared to a certain threshold, also referred to as ED threshold, in order to determine if a channel is idle.
  • ED threshold energy detection
  • LBT parameter settings including ED threshold, 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 ETSI harmonized standard in Europe as well as the 3GPP specification for operation of LTE- License Assisted Access (LAA) I NR-ll in unlicensed spectrum.
  • LAA LTE- License Assisted Access
  • FBE Frame-Based Equipment
  • LBE Load-Based Equipment
  • a channel access priority classes (CAPC) based on the service type quality class identifier (QCI) and/or 5G QoS Identifier (5QI) has been defined for the channel access.
  • QCI quality class identifier
  • 5QI 5G QoS Identifier
  • 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 channel occupancy time (COT), other LBT categories allow a very short sensing period.
  • COT shared channel occupancy time
  • Sensing is done typically for a random number of sensing intervals with this random number being a number within the range of 0 to contention window (CW), where CW represents a contention window size.
  • CW contention window
  • 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.
  • the contention window size (CWS) is doubled.
  • the transmitter is only allowed to perform transmission up to a maximum time duration, namely, the maximum channel occupancy time (MCOT).
  • MCOT maximum channel occupancy time
  • QoS differentiation a channel access priority based on the service type has been defined. For example, there are four LBT priority classes that are defined for differentiation of contention window sizes and MCOT between services.
  • the gNB assigns Fixed Frame Periods (FFP), senses the channel for 9 ps 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.
  • FFP Fixed Frame Periods
  • DL/LIL transmissions are only allowed within the COT, 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 ms and can be changed after a minimum of 200 ms.
  • L2 measurements are performed per data radio bearer (DRB) and are divided into L2 measurements performed by the gNB and L2 measurements performed by the UE. Possible L2 measurement include:
  • the L2 measurements of packet delays performed by the gNB can further divide into DL-related packet measurements and UL-related packet measurement which include also the delay experienced at the UE side.
  • the RAN part of DL packet delay measurement comprises:
  • D1 (DL delay in over-the-air interface), referring to Average delay DL airinterface in TS 28.552 v.17.6.0.
  • D2 (DL delay on gNB-DU), referring to Average delay in RLC sublayer of gNB-DU in TS 28.552.
  • D4 (DL delay in CU-UP), referring to Average delay DL in CU-UP in TS 28.552.
  • the DL packet delay measurements i.e. , D1 (the DL delay in over-the-air interface), D2 (the DL delay in gNB-DU), D3 (the DL delay on F1-U) and D4 (the DL delay in CU-UP), should be measured per DRB per UE.
  • the RAN part (including UE) of UL packet delay measurement comprises:
  • the LBT issues may also affect the scheduling delays because also the scheduling request (SR) may be subject to LBT failures before being transmitted over the air interface.
  • the uplink grant, allocating uplink transmission resources, transmitted by the gNB may be subject to LBT failures and hence it may be delayed.
  • Other signalling may also be affected.
  • the UE will include the buffer size in the BSR MAC control element (CE) as measured when the BSR is triggered.
  • the transmission of the BSR may be postponed at physical layer due to LBT issues, and it may be eventually transmitted at a later point in time at another scheduling occasion.
  • the actual UE buffer status may be different, e.g., it may have increased.
  • the network obviously does not know that, and it may provide an uplink grant which is for a smaller amount of data than what the UE needs.
  • measurements may not be correct leading to a non-optimized handling of communication in the wireless communications network.
  • An object herein is to provide a mechanism to handle measurements of a UE in an efficient manner in the wireless communications network.
  • the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling measurements in a wireless communications network.
  • the UE performs a measurement of a parameter related to an LBT delay when accessing a channel.
  • the UE may measure a LBT delay, number of LBT failures, or a measurement that is affected by the LBT delay, or similar.
  • the object is achieved, according to embodiments herein, by providing a method performed by a radio network node for handling communication in a wireless communications network.
  • the radio network node may obtain an indication of a measured parameter related to an LBT delay of a UE accessing a channel and/or a measurement related to the LBT delay, i.e. , a measurement affected by the measured parameter.
  • the radio network node may receive the indication or the measurement, or measure the parameter or perform the measurement.
  • the object is achieved, according to embodiments herein, by providing a UE and a radio network node configured to perform the methods herein, respectively.
  • a UE for handling measurements in a wireless communications network is configured to perform a measurement of a parameter related to an LBT delay when accessing a channel.
  • a radio network node for handling communication in a wireless communications network.
  • the radio network node is configured to obtain an indication of a measured parameter related to an LBT delay of a UE accessing a channel and/or a measurement related to the LBT delay, i.e., a measurement affected by the measured parameter.
  • a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE or the radio network node, respectively.
  • a computer-readable storage medium having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the methods herein, as performed by the UE or the radio network node, respectively.
  • the proposed solution allows the radio network node to better evaluate and possibly optimize the system performance when operating in shared spectrum.
  • the obtained parameter and/or measurement indicates the LBT delay or the effect of the LBT delay that may be used to optimize performance or similar at the wireless communications network.
  • Fig. 1 shows a scenario according to prior art
  • Fig. 2 shows a scenario according to prior art
  • FIG. 3 shows an overview depicting a wireless communications network according to embodiments herein;
  • Fig. 4 shows a combined signalling scheme and flowchart depicting embodiments herein;
  • FIG. 5 shows a flowchart depicting a method performed by a UE according to embodiments herein;
  • Fig. 6 shows a flowchart depicting a method performed by a radio network node according to embodiments herein;
  • Fig. 7 shows a schematic overview depicting some embodiments herein;
  • Fig. 8 shows a block diagram depicting embodiments of a UE according to embodiments herein;
  • Fig. 9 shows a block diagram depicting embodiments of a radio network node according to embodiments herein;
  • Fig. 10 schematically illustrates a telecommunication network connected via an intermediate network to a host computer
  • Fig. 11 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection
  • Figs. 12,13,14,15 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.
  • Embodiments herein relate to wireless communications networks in general.
  • Fig. 3 is a schematic overview depicting a wireless communications network 1.
  • the wireless communications network 1 comprises one or more RANs and one or more CNs.
  • the wireless communications network 1 may use one or a number of different technologies.
  • Embodiments herein relate to recent technology trends that are of particular interest in a NR context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA).
  • WCDMA Wideband Code Division Multiple Access
  • a user equipment (UE) 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and/or a wireless terminal, is comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN).
  • AN e.g. radio access network
  • CN core networks
  • UE is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.
  • NB-loT narrowband internet of things
  • MTC Machine Type Communication
  • D2D Device to Device
  • the wireless communications network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar.
  • the radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g.
  • a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the radio network node depending e.g. on the first radio access technology and terminology used.
  • gNB gNodeB
  • eNB evolved Node B
  • eNode B evolved Node B
  • NodeB a NodeB
  • a base transceiver station such as a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a
  • the radio network node 12 may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving radio network node communicates with the UE in form of DL transmissions to the UE 10 and UL transmissions from the UE 10. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.
  • the UE 10 is configured, either preconfigured or configured by the radio network node 12, to measure a parameter related to an LBT delay when accessing a channel.
  • a parameter related to an LBT delay may be any parameter that is affected by the LBT delay.
  • the UE 10 may further transmit an indication of the measured parameter.
  • the proposed solution allows the radio network node 12 to better evaluate and possibly optimize the system performance when operating in shared spectrum. For example, the radio network node 12 may classify on the basis of the impacts on packet transmission delays, or scheduling delays how severe is the impact of LBT in the system performances in a given carrier. If it is determined that LBT has a major impact, the radio network node 12 may reduce the load in the specific shared carrier and move the traffic in a less loaded shared carrier or in a licensed carrier.
  • Fig. 4 is a combined signalling scheme and flowchart according to embodiments herein.
  • the radio network node 12 may transmit configuration data to the UE 10 for configuring the UE 10 to perform methods herein. It should be noted that the radio network node 12 may request the UE 10 to report any measurement, e.g., the average PDCP delay, and then the UE considers the LBT delay when it calculates this legacy measurement.
  • any measurement e.g., the average PDCP delay
  • the UE 10 performs a measurement of a parameter related to an LBT delay when accessing a channel. For example, the UE may measure a LBT delay, number of LBT failure or similar. The UE 10 may perform any measurement such as DL- related packet measurements and/or UL-related packet measurement that is affected by the LBT delay.
  • the UE 10 may then transmit to the radio network node 12, an indication such as a value or an index of the measured parameter, or the measurement affected by the LBT delay.
  • the radio network node 12 may then trigger an action based on the received indication. For example, the radio network node 12 may reduce the load in a specific shared carrier and move the traffic in a less loaded shared carrier or in a licensed carrier.
  • the UE 10 may receive configuration data from the radio network node 12 for configuring the UE 10 to perform methods herein.
  • the UE 10 then performs the measurement of the parameter related to the LBT delay when accessing a channel. For example, the UE 10 may measure a LBT delay, and/or count a number of LBT failures or similar. The UE 10 may perform any measurement such as DL-related packet measurements and/or UL-related packet measurement that is affected by the LBT delay.
  • the performed measurement may comprise one or more of the following: a packet data convergence protocol (PDCP) average delay in the UL per DRB; a point in time when a uplink medium access control protocol data unit (UL MAC PDU) including a first part of an uplink packet data convergence protocol service data unit (UL PDCP SDU) is transmitted over an air interface; a time elapsed between triggering a scheduling request (SR) and receiving a scheduling grant; a time elapsed between triggering a Buffer Status Report (BSR) at a MAC layer and transmitting the BSR in a buffer status report medium access control control element (BSR MAC CE) over an air interface at a physical layer; a difference between a buffer size included in a triggered BSR MAC CE and a buffer size of the UE at the time of the transmission over an air interface of the BSR MAC CE; deducting a cumulative LBT delay occurred during a time period during which a L2 measurement is performed and use the resulting time period minus the cumulative LBT delay
  • the measurement may be performed for each DRB for each CAPC; or for each CAPC within each DRB; or separately per shared spectrum channel bandwidth, or per shared spectrum operating band.
  • the performed measurement may take into account an impact of channel access procedure type and/or time division duplex (TDD) pattern.
  • Action 503. The UE 10 may store/log the measured parameter at the UE 10 and/or a measurement related to the measured parameter, for example, measurement affected by the LBT delay.
  • the UE 10 may then transmit or report, to the radio network node 12, an indication such as a value or an index of the measured parameter and/or a measurement related to a LBT delay, i.e. , a measurement affected by the LBT delay or affected by the measured parameter.
  • an indication such as a value or an index of the measured parameter and/or a measurement related to a LBT delay, i.e. , a measurement affected by the LBT delay or affected by the measured parameter.
  • the indication and/or the measurement may comprise a measured LBT delay and/or a counted number of LBT failures.
  • the indication and/or the measurement may be for each DRB for each CAPC; for each CAPC within each DRB; separately per shared spectrum channel bandwidth, or per shared spectrum operating band.
  • the radio network node 12 may then trigger an action based on the obtained indication and/or the measurement. For example, the radio network node 12 may reduce a load in a specific shared carrier and move the traffic to a less loaded shared carrier or to a licensed carrier. For example, the radio network node 12 may estimate performance taking the indication and/or the measurement into account.
  • the measurements performed in the following embodiment may be computed separately for each DRB, or for each CAPC, or for each CAPC within each DRB, or considering the band or the channel bandwidth used for shared spectrum.
  • Embodiments herein comprise, for example, a method in which the UE 10 or the radio network node 12, such as a gNB, may measure the “LBT delay” experienced by the UE 10 or the radio network node 12for transmitting a PDCP SDU.
  • the “LBT delay” may be measured at physical layer as the time elapsed between the reception of a transport block (TB), including one or more parts of the PDCP SDU, from MAC layer and the transmission over the air interface of the TB or until the time the channel is declared busy, upon which the TB transmission does not occur.
  • TB transport block
  • the LBT delay is computed as the time difference between the point in time when the UL MAC protocol data unit (PDU) k including the first part of UL PDCP SDU i is transmitted over the air-interface and the point in time in which this UL MAC PDU k is scheduled for transmission:
  • the tDeliv(i) includes the LBT delay experienced by the MAC PDU:
  • the measurement may be the delay experienced until the first over the air transmission, this transmissions may fail and there might be a retransmission but such a retransmission is not part of this measurement, after the LBT procedure while attempting to transmit a MAC PDU and such a measurement may be defined as follows:
  • the measurement may be the delay experienced until the first over the air successful transmission after the LBT procedure while attempting to transmit a MAC PDU, this may include delay due to the retransmissions, and such a measurement may be defined as follows:
  • the above measurement may be taken per CAPC of the packets to be transmitted.
  • the cumulative LBT delay may then consider all the PDCP SDUs of a certain DRB and/or CAPC, i.e. , for all the TBs containing such PDCP SDUs, transmitted by the UE 10 over certain time window, e.g. as in the following formula: Number of LBT failures per PDCP SDU.
  • the UE 10 and/or the radio network node 12 may measure the number of LBT failures experienced by the UE 10 for a PDCP SDU before transmitting it entirely, i.e., all the parts of the PDCP SDU, over the air interface.
  • the number of LBT failures is measured as the number of TBs whose transmission was not performed due to LBT failure, i.e., channel sensed busy by the LBT procedure, and that included at least one part of the PDCP SDU.
  • the number of LBT failures may be averaged over a certain time window for all the PDCP SDU of a certain DRB and/or CAPC, and/or channel bandwidth. Alternatively, a sliding average may be used, or an exponential average.
  • the UE 10 may measure a Buffer Status Report (BSR) LBT Delay, i.e., the time elapsed between triggering the BSR at MAC layer and transmitting the BSR in a BSR MAC CE over the air interface at the physical layer.
  • BSR LBT Delay may be defined as the time from the start, or end, of the first LBT procedure to the start, or end, of the successful LBT procedure which precedes the, delayed, transmission. This time is thus zero if the LBT succeeds for the first transmission attempt.
  • An example of how such a measurement is defined as follows.
  • the buffer size content gap is computed as the buffer size difference between the buffer size measured at the moment in which the BSR is triggered, i.e. , the buffer size indicated in the BSR MAC CE, and the buffer size measured at the point in time in which the Physical Uplink Shared Channel (PUSCH) transmission including this BSR MAC CE is transmitted over the air interface:
  • Fig. 7 shows a buffer size gap in L2 measurement.
  • the size of the buffer referred below is the size of UL MAC buffer at the UE 10. Scheduling LBT Delay.
  • the radio network node 12 may measure a “Scheduling LBT Delay”, i.e., the gap between the scheduling of a MAC SDU and the transmission over the air-interface of the corresponding scheduling grant.
  • Embodiments herein may be applied to, or combined with, any of the previously described embodiments involving delay measurements where delay caused by LBT failures may constitute a part of the total delay.
  • the UE 10 or the radio network node 12 may log or store and/or report the LBT delay and the remainder of the total delay, i.e., the LBT independent part of the total delay, separately.
  • UE 10 or the radio network node 12 may log or store and/or report the total delay as one item and the LBT delay, i.e., the part of the total delay that is caused by LBT procedures, as another item.
  • the radio network node 12 may configure the UE 10, e.g., through the system information or using dedicated signalling, e.g. radio resource control (RRC) signalling, how to log or store, and/or report delays where LBT procedures, in particular delay caused by LBT failures, may be part of the delay.
  • RRC radio resource control
  • the radio network node 12 may configure the UE 10 to log or store, and/or report such delays in accordance with any of the above described variants.
  • a buffer size gap which may result from a delay of the transmission of a BSR, e.g. caused by LBT failure(s) and/or delay. As previously described, this may have an adverse impact on the scheduling efficiency when the scheduling is based on outdated and incorrect information about the amount of data pending for transmission in the UE 10. In the embodiment described in this section, this negative impact may be mitigated by enabling more interaction between the MAC layer and the physical layer, i.e., the PHY layer.
  • the MAC layer after providing a BSR to the physical layer for transmission, before receiving an indication from the physical layer that the requested transmission has been performed, determines that the size of the content of the buffer has changed, the MAC layer may instruct the physical layer to cancel the previously requested transmission and discard the concerned transport block(s), and instead provide a new updated BSR to the physical layer for transmission, wherein the updated BSR reflects the current content of the buffer.
  • this MAC layer behaviour may be subject to a condition on the size of the change of the buffer content size, e.g., the actions are triggered only if the buffer size has increased more than a, configured, specified or hardcoded by implementation, threshold.
  • the condition that has to be fulfilled for the MAC layer to perform the above described actions is that the buffer size has increased more than a, configured, specified or hardcoded by implementation, first threshold-amount, e.g.
  • second threshold-amount e.g., measured in number of bytes, octets or bits, wherein the first and the second threshold-amounts may be different or equal to each other.
  • Other condition variants are conceivable, e.g., including aspects such as the ratio between the size of the buffer size change and the buffer size before the change.
  • Variants of the measurements described in the previous embodiments e.g., LBT delay, cumulative LBT delay, SR LBT delay, BSR LBT Delay, can be defined by taking into account the impact of:
  • channel access procedure type For example, for type 1 DL Channel Access procedure the time duration spanned by the sensing slots that are sensed to be idle before a downlink transmission(s) is random, while for Type 2 channel access procedure the time duration spanned by sensing slots that are sensed to be idle before a downlink transmission(s) is deterministic. In a possible implementation of cumulative LBT delay calculation, the deterministic time duration used for Type 2 channel access procedure can be made visible in the formula.
  • the impact of NR-U can be considered by deducting the cumulative LBT delay, or another form of LBT delay, e.g., average, occurred during the Time Period during which a L2 measurement is performed and use the resulting “Time Period - Cumulative LBT delay” to calculate one of the existing Layer 2 measurements, where LBT delay is excluded.
  • LBT delay or another form of LBT delay, e.g., average
  • Table 4.2.1.2.2-2 Parameter description for Average over-the-air packet delay in the UL per DRB per UE excluding LBT delay
  • TB transport block
  • TB transport block
  • the LBT delay is regarded as zero if the LBT succeeds for the first transmission attempt, while if the LBT fails at the first transmission attempt, the LBT delay is measured as the time from the start (or end) of the first LBT procedure to the start (or end) of the successful LBT procedure which precedes the (delayed) transmission.
  • a UE measures the “cumulative LBT delay” experienced by the UE/gNB for transmitting a PDCP SDU.
  • the “cumulative LBT delay” is the sum of all the “LBT delay” experienced by the UE for each of the TB including the parts of the PDCP SDU and measured over multiple scheduling occasions before the PDCP SDU is transmitted over the air interface.
  • the UE/gNB measures the “number of LBT failures” experienced by the UE for a PDCP SDU before transmitting it entirely (i.e. all the parts of the PDCP SDU) over the air interface.
  • the number of LBT failures is measured as the number of TBs whose transmission was not performed due to LBT failure (i.e. channel sensed busy by the LBT procedure) and that included at least one part of the PDCP SDU
  • SR LBT Delay as the time elapsed between triggering the SR (as indicated by the MAC layer) and transmitting the SR over the air interface at the physical layer, where this time hence is a part of the total time between the triggering of the SR and the reception of an uplink grant (triggered by the SR).
  • the SR LBT delay is measured as the time from the trigger of the SR until the actual transmission of the SR, minus the delay from the SR trigger to the first PUCCH occasions for SR transmission (since this part of the delay is independent of LBT).
  • the SR LBT delay is measured in a similar way as described above for PDCP SDUs, i.e.
  • the UE measures the “BSR LBT Delay”, i.e. the time elapsed between triggering the BSR at MAC layer and transmitting the BSR over the air interface at the physical layer.
  • the BSR LBT delay is measured as the time from the trigger of the BSR until the actual transmission of the BSR, minus the delay from the BSR trigger to the first PLICCH occasions for BSR transmission (since this part of the delay is independent of LBT).
  • the BSR LBT delay is measured in a similar way as described above for PDCP SDUs, i.e.
  • the BSR LBT delay is regarded as zero if the LBT succeeds for the first BSR transmission attempt, while if the LBT fails at the first BSR transmission attempt, the LBT delay is measured as the time from the start (or end) of the first LBT procedure to the start (or end) of the successful LBT procedure which precedes the (delayed) transmission
  • Fig. 8 is a block diagram depicting the UE 10 for handling communication or measurements in the wireless communications network 1 according to embodiments herein.
  • the UE 10 may comprise processing circuitry 701 , e.g., one or more processors, configured to perform the methods herein.
  • processing circuitry 701 e.g., one or more processors, configured to perform the methods herein.
  • the UE 10 may comprise a receiving unit 702, e.g., a receiver or a transceiver.
  • the UE 10, the processing circuitry 701 and/or the receiving unit 702 may be configured to obtain the configuration at the UE.
  • the configuration or the policy comprises one or more rules that indicate to log a measurement such as an LBT delay measurement.
  • the UE 10, the processing circuitry 701 and/or the receiving unit 702 may be configured to receive configuration data from the radio network node for configuring the UE 10 to perform the measurement.
  • the UE 10 may comprise a performing unit 703, e.g., a measuring unit.
  • the UE 10, the processing circuitry 701 and/or the performing unit 703 is configured to perform measurement of the parameter related to the LBT delay when accessing the channel.
  • the UE 10, the processing circuitry 701 and/or the performing unit 703 may be configured to measure a LBT delay, number of LBT failures or similar.
  • the performed measurement may comprise measuring the LBT delay and/or counting a number of LBT failures.
  • the measurement may be performed for each DRB; for each CAPC; or for each CAPC within each DRB; or separately per shared spectrum channel bandwidth, or per shared spectrum operating band.
  • the performed measurement may comprise one or more of the following: a PDCP average delay in the UL per DRB; a point in time when a UL MAC PDU, including a first part of an UL PDCP SDU, is transmitted over an air interface; a time elapsed between triggering a SR and receiving a scheduling grant; a time elapsed between triggering a BSR at a MAC layer and transmitting the BSR in a BSR MAC CE, over an air interface at a physical layer; a difference between a buffer size included in a triggered BSR MAC CE and a buffer size of the UE at the time of the transmission over an air interface of the BSR MAC CE; deducting a cumulative LBT delay occurred during a time period during which a L2 measurement is performed and use the resulting time period minus the cumulative LBT delay to calculate the L2 measurement.
  • the performed measurement may be affected by the LBT delay and/or consider an impact of the LBT delay in computation.
  • the performed measurement may
  • the UE 10 may comprise a transmitting unit 705, e.g. a transmitter or a transceiver.
  • the UE 10, the processing circuitry 701 and/or the transmitting unit 705 may further be configured to transmit or report, to the radio network node 12, the indication, such as a value or an index, of the measured parameter and/or a measurement related to the LBT delay.
  • the UE 10 may comprise a memory 706.
  • the memory 706 comprises one or more units to be used to store data on, such as data packets, one or more conditions, mobility events, measurements, events and applications to perform the methods disclosed herein when being executed, and similar.
  • the UE 10 may comprise a communication interface 709 such as comprising a transmitter, a receiver, a transceiver and/or one or more antennas.
  • the methods according to the embodiments described herein for the UE 10 are respectively implemented by means of, e.g., a computer program product 707 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10.
  • the computer program product 707 may be stored on a computer-readable storage medium 708, e g., a disc, a universal serial bus (USB) stick or similar.
  • the computer-readable storage medium 708, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10.
  • the computer-readable storage medium may be a transitory or a non-transitory computer- readable storage medium.
  • embodiments herein may disclose a UE 10 for handling measurements in a wireless communications network, wherein the UE 10 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said UE 10 is operative to perform any of the methods herein.
  • the radio network node 12 may comprise processing circuitry 801 , e.g., one or more processors, configured to perform the methods herein.
  • processing circuitry 801 e.g., one or more processors, configured to perform the methods herein.
  • the radio network node 12 may comprise a configuring unit 802, e.g., a transmitter or a transceiver.
  • the radio network node 12, the processing circuitry 801 and/or the configuring unit 802 is configured to configure the UE 10 to log the measurement related to the LBT delay.
  • the radio network node 12 may comprise an obtaining unit 803, e.g., receiver or transceiver.
  • the radio network node 12, the processing circuitry 801 and/or the receiving unit 803 may be configured to obtain the indication of the measurement of the parameter related to the LBT delay of the UE 10, when accessing the channel and/or a measurement related to the LBT delay.
  • the indication may be a measured value or an index indicating the measured value.
  • the indication and/or the measurement may be received from the UE 10 and/or measured at the radio network node 12.
  • the indication and/or the measurement may comprise the measured LBT delay and/or the counted number of LBT failures.
  • the indication and/or the measurement may be for each DRB; for each CAPC; for each CAPC within each DRB; separately per shared spectrum channel bandwidth, or per shared spectrum operating band.
  • the indication and/or the measurement may comprise one or more of the following: a PDCP average delay in the UL per DRB; a point in time when a UL MAC PDU, including a first part of an UL PDCP SDU, is transmitted over an air interface; a time elapsed between triggering a SR, and receiving a scheduling grant; a time elapsed between triggering a BSR at a MAC layer and transmitting the BSR in a BSR MAC CE, over an air interface at a physical layer; a difference between a buffer size included in a triggered BSR MAC CE and a buffer size of the UE at the time of the transmission over an air interface of the BSR MAC CE; deducting a cumulative LBT delay occurred during a time period during which a L2 measurement is performed and use the resulting
  • the radio network node 12 may comprise a memory 804.
  • the memory 804 comprises one or more units to be used to store data on, such as data packets, mobility events, measurements, indications, logged measurements, configurations, events and applications to perform the methods disclosed herein when being executed, and similar.
  • the radio network node 12 may comprise a communication interface 807 such as comprising a transmitter, a receiver, a transceiver and/or one or more antennas.
  • ASIC application-specific integrated circuit
  • processors or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and/or program or application data. Other hardware, conventional and/or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.
  • DSP digital signal processor
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211 , such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network node 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) 3291 being an example of the UE 10, located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291 , 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 10 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291 , 3292 are configured to communicate data and/or signalling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Fig.11) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in Fig.11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.
  • Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Fig. 11 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291 , 3292 of Fig. 10, respectively.
  • the inner workings of these entities may be as shown in Fig. 11 and independently, the surrounding network topology may be that of Fig. 10.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the performance since mobility may be handled more efficiently taking into account LBT issues and thereby provide benefits such as reduced user waiting time, and better responsiveness.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signalling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311 , 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • Fig. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • Fig. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • Fig. 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section.
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Fig. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • E1 The interface between a gNB-CU-CP and a gNB-CU-UP in the split RAN architecture in NR.
  • F1 The interface between a gNB-Cll and a gNB-Dll in the split RAN architecture in NR.
  • the user plane part of the F1 interface e.g. the interface between a gNB-Dll and a gNB-CU-UP.
  • GBR Guaranteed Bit Rate gNB A radio base station in NR gNB-CU gNB Centralized Unit gNB-CU-CP gNB Centralized Unit Control Plane gNB-CU-UP gNB Centralized Unit User Plane gNB-DU gNB Distributed Unit
  • NR-U NR Unlicensed (l.e. NR operated in shared (unlicensed) spectrum.)
  • V2X Vehicle-to-everything Or “Vehicle to X”, where X e.g. may be another vehicle or a network server.

Landscapes

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

Abstract

Des modes de réalisation de la présente invention concernent, par exemple, un procédé mis en oeuvre par un UE (10) pour gérer des mesures dans un réseau de communication sans fil. L'UE (10) effectue une mesure d'un paramètre lié à un retard LBT lors de l'accès à un canal.
PCT/SE2023/050557 2022-06-07 2023-06-04 Noeud de réseau radio, équipement utilisateur et procédés exécutés dans celui-ci WO2023239279A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263365952P 2022-06-07 2022-06-07
US63/365,952 2022-06-07

Publications (1)

Publication Number Publication Date
WO2023239279A1 true WO2023239279A1 (fr) 2023-12-14

Family

ID=87074705

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050557 WO2023239279A1 (fr) 2022-06-07 2023-06-04 Noeud de réseau radio, équipement utilisateur et procédés exécutés dans celui-ci

Country Status (2)

Country Link
TW (1) TW202415108A (fr)
WO (1) WO2023239279A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031366A1 (fr) * 2020-08-07 2022-02-10 Qualcomm Incorporated Informations de défaillance d'accès à un canal sur un spectre partagé

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031366A1 (fr) * 2020-08-07 2022-02-10 Qualcomm Incorporated Informations de défaillance d'accès à un canal sur un spectre partagé

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "NR-U enhancements for UL MLB and MRO", vol. RAN WG3, no. Online ;20221010 - 20221018, 27 September 2022 (2022-09-27), XP052278210, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_117bis-e/Docs/R3-225554.zip R3-225554 - NR-U enhancements for UL MLB and MRO.docx> [retrieved on 20220927] *
ERICSSON: "SoD_CB: # SONMDT12_NRU", vol. RAN WG3, no. Online; 20220117 - 20220126, 21 January 2022 (2022-01-21), XP052102254, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_114bis-e/Inbox/R3-221027.zip R3-221027_SoD_CB_SONMDT12_NRU_v01.doc> [retrieved on 20220121] *
ERICSSON: "Supporting NR-U in the SON/MDT framework", vol. RAN WG2, no. Electronic meeting; 20220817 - 20220826, 10 August 2022 (2022-08-10), XP052261490, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_119-e/Docs/R2-2208178.zip R2-2208178 - Supporting NR-U in the SON-MDT framework.docx> [retrieved on 20220810] *
NOKIA ET AL: "Discussion on the remaining "FFS" statements for MLB and MRO optimisation", vol. RAN WG3, no. E-meeting; 20211101 - 20211111, 21 October 2021 (2021-10-21), XP052067816, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_114-e/Docs/R3-214815.zip R3-214815 SON_NR-U.docx> [retrieved on 20211021] *
QUALCOMM INCORPORATED: "NR-U Related Enhancements", vol. RAN WG2, no. Electronic; 20211101 - 20211112, 21 October 2021 (2021-10-21), XP052067360, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_116-e/Docs/R2-2110921.zip R2-2110921 - NR-U Related Enhancements.docx> [retrieved on 20211021] *

Also Published As

Publication number Publication date
TW202415108A (zh) 2024-04-01

Similar Documents

Publication Publication Date Title
EP3925401B1 (fr) Équipement utilisateur, noeud de réseau radio et procédés de gestion de procédures de récupération à l&#39;intérieur de celui-ci
CN107852734B (zh) 无线基站以及无线通信方法
US11706820B2 (en) User equipment, network node and methods therein for handling a two-step random access procedure in a wireless communications network
US10840992B2 (en) User equipment, radio network node and methods performed therein for handling communication in a wireless communication network
KR20210099651A (ko) 비허가 스펙트럼에서 동작하는 방법 및 디바이스
CN111567133B (zh) 用户设备、网络节点及处理无线通信网络中的通信的方法
US20200305199A1 (en) User terminal, radio base station and radio communication method
TWI762839B (zh) 用於共享通訊通道之方法及設備
US20220150980A1 (en) Ue, network node and methods for handling 2-step and 4-step random access procedures
CN115835396A (zh) 用于指示失败事件的方法和装置
EP4094532A1 (fr) Sélection de faisceau dans un fonctionnement sans licence
EP4055976B1 (fr) Transmissions rach à deux étapes utilisant une bande de garde dans un spectre sans licence
US20220159506A1 (en) Communication Node and Method Performed Therein for Handling Communication Using Different BSR Formats
EP3942890B1 (fr) Équipement utilisateur, noeud de réseau radio et procédés mis en oeuvre dans ceux-ci permettant de gérer une communication
US20220312248A1 (en) Measurement objects merging for nr unlicensed spectrums
WO2022086420A1 (fr) Nœud de réseau radio, ue et procédé exécuté en son sein
WO2023239279A1 (fr) Noeud de réseau radio, équipement utilisateur et procédés exécutés dans celui-ci
US20240129864A1 (en) Radio network node and method performed in a communication network
US12126568B2 (en) Methods and devices for managing transmissions in a wireless communications network
EP4278830A1 (fr) Noeud de réseau radio, équipement utilisateur et procédés mis en oeuvre dans ce cadre
CN118120284A (zh) 处置无线通信网络中的通信
CN113661670A (zh) Ue、无线电网络节点和其中执行的方法

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: 23736882

Country of ref document: EP

Kind code of ref document: A1