WO2024035296A1 - Ue non connecté desservi par un iab sur le même véhicule - Google Patents

Ue non connecté desservi par un iab sur le même véhicule Download PDF

Info

Publication number
WO2024035296A1
WO2024035296A1 PCT/SE2023/050754 SE2023050754W WO2024035296A1 WO 2024035296 A1 WO2024035296 A1 WO 2024035296A1 SE 2023050754 W SE2023050754 W SE 2023050754W WO 2024035296 A1 WO2024035296 A1 WO 2024035296A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
reselection
iab node
measurement
iab
Prior art date
Application number
PCT/SE2023/050754
Other languages
English (en)
Inventor
Antonino ORSINO
Marco BELLESCHI
Ritesh SHREEVASTAV
Lei BAO
Filip BARAC
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 WO2024035296A1 publication Critical patent/WO2024035296A1/fr

Links

Classifications

    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • 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
    • H04W84/00—Network topologies
    • H04W84/005—Moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations

Definitions

  • the present application relates generally to the field of wireless networks, and more specifically to integrated access backhaul (IAB) networks in which the available wireless communication resources are shared between user access to the network and backhaul of user traffic within the network (e.g., to/from a core network).
  • IAB integrated access backhaul
  • 5G fifth generation
  • 3GPP Third-Generation Partnership Project
  • 5G is developed for maximum flexibility to support various use cases including enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device- to-device (D2D), and several others.
  • eMBB enhanced mobile broadband
  • MTC machine type communications
  • URLLC ultra-reliable low latency communications
  • D2D side-link device- to-device
  • FIG. 1 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation Radio Access Network (NG-RAN, 199) and a 5G Core (5GC, 198).
  • the NG-RAN can include one or more gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs (100, 150) connected via respective interfaces (102, 152). More specifically, the gNBs can be connected to one or more Access and Mobility Management Functions (AMFs) in the 5GC via respective NG-C interfaces and to one or more User Plane Functions (UPFs) in 5GC via respective NG-U interfaces.
  • the 5GC can include various other network functions (NFs), such as Session Management Function(s) (SMF).
  • NFs Session Management Function(s) (SMF).
  • the 5GC can be replaced by an Evolved Packet Core (EPC), which conventionally has been used together with a Long-Term Evolution (LTE) Evolved UMTS RAN (E-UTRAN).
  • EPC Evolved Packet Core
  • LTE Long-Term Evolution
  • E-UTRAN Evolved UMTS RAN
  • gNBs e.g., 100, 150
  • MMEs Mobility Management Entities
  • SGWs Serving Gateways
  • each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • Each of the gNBs can serve a geographic coverage area including one or more cells and, in some cases, can also use various directional beams to provide coverage in the respective cells.
  • a DL “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE.
  • RS network-transmitted reference signal
  • 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 logical nodes and interfaces between them are defined as part of the RNL.
  • NG, Xn, Fl the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signaling transport.
  • the NG RAN logical nodes shown in Figure 1 include a Central Unit (CU or gNB-CU, e.g., 110) and one or more Distributed Units (DU or gNB-DU, e.g., 120, 130).
  • CUs are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs.
  • DUs are decentralized logical nodes that host lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions.
  • each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, communication circuitry, etc.
  • a gNB-CU connects to one or more gNB-DUs over respective Fl logical interfaces (e.g., 122 and 132 shown in Figure 1).
  • a gNB-DU can be connected to only a single gNB-CU.
  • the gNB-CU and its connected gNB-DU(s) are only visible to other gNBs and the 5GC as a gNB.
  • the Fl interface is not visible beyond gNB-CU.
  • Fl supports control plane (CP) and user plane (UP) separation into Fl-AP and Fl-U protocols, respectively, such that a gNB-CU may also be separated into CP and UP logical entities or functions (discussed below).
  • the Fl interfaces separates the RNL and the TNL.
  • the Fl-U protocol conveys control information related to the user data flow management of data radio bearers (DRBs), as defined in 3GPP TS 38.425 (vl5.6.0).
  • Fl-U protocol data is conveyed by the GTP-U protocol, more specifically by a “RAN Container” GTP-U extension header as defined in 3GPP TS 29.281 (vl5.6.0).
  • GTP-U protocol over user datagram protocol (UDP) over Internet Protocol (IP) carries data streams on the Fl interface.
  • UDP user datagram protocol
  • IP Internet Protocol
  • Densification via the deployment of more base stations is one way to satisfy the increasing demand for bandwidth and/or capacity in mobile networks, which is mainly driven by the increasing use of video streaming services. Due to the availability of more spectrum in the millimeter wave (mmw) band, deploying small cells that operate in this band is an attractive deployment option for these purposes.
  • mmw millimeter wave
  • deploying small cells that operate in this band is an attractive deployment option for these purposes.
  • the normal approach of connecting the small cells to the operator’s backhaul network with optical fiber can end up being expensive and impractical.
  • Employing wireless links for connecting the small cells to the operator’s network is a cheaper and more practical alternative.
  • One such approach is an integrated access backhaul (IAB) network where the operator can repurpose radio resources conventionally used for network access (e.g.
  • LTE Rel-10 includes an IAB architecture based on a Relay Node (RN) with the functionality of an LTE eNB and UE modem.
  • the RN is connected to a donor eNB, which has a S1/X2 proxy functionality that hides the RN from the rest of the network.
  • the donor eNB is aware of UEs served by an RN but hides any UE mobility between donor eNB and connected RN(s) from the CN.
  • Each IAB node can include the functionality of a gNB-DU (also referred to as “IAB-DU”) that terminates the radio interface layers of access links towards served UEs and backhaul links towards immediately “downstream” IAB nodes.
  • gNB-DU also referred to as “IAB-DU”
  • Each IAB node can also include a Mobile-Termination function (referred to as MT or “IAB-MT”) that terminates the radio interface layers of a backhaul link towards an immediately upstream (or “parent”) DU, i.e., either an IAB-DU or a donor gNB.
  • MT Mobile-Termination function
  • the MT function is similar to UE functionality and has been specified by 3 GPP as part of the Mobile Equipment (ME).
  • each IAB-DU also has an upstream Fl connection to the CU part of a donor gNB, also referred to as an “lAB-donor CU”.
  • This connection is via a particular DU of the donor gNB, also referred to as an “lAB-donor DU.”
  • Each lAB-donor CU may be associated with multiple lAB-donor DUs, like the arrangement shown in Figure 1.
  • IAB features include support for multi -hop, multi-path backhaul with directed acyclic graph (DAG) topology (i.e., no mesh topologies), QoS prioritization of backhaul traffic, and flexible resource allocation between access and backhaul.
  • DAG directed acyclic graph
  • Rel-17 is focused on IAB topology enhancements and partial migration of IAB nodes for radio link failure (RLF) recovery and load balancing.
  • RLF radio link failure
  • One expected focus for Rel-18 is mobile IAB, such as vehicle-mounted IAB nodes that provide cell coverage to UEs that are onboard and/or in the vicinity of the vehicle.
  • the non-connected UE will periodically or occasionally perform measurements to search for cells that are available for connecting to the RAN.
  • the UE will find the cell provided by the mobile IAB node (“inside cell”) but may also find other cells provided by other RAN nodes, such as overlay coverage cells (“outside cells”) provided by fixed RAN nodes (e.g., base stations).
  • the UE may measure a higher signal strength on an outside cell than on the inside cell. If the vehicle is moving through the RAN coverage area, the UE is likely to find different outside cells over time and the measured signal strength on outside cells may vary over time. This can cause various problems, issues, and/or difficulties for the UE, particularly when the UE selects an outside cell for connecting to the RAN based on highest measured signal strength.
  • An object of embodiments of the present disclosure is to address these and other UE cell selection problems, issues, and/or difficulties in relation to mobile IAB nodes, thereby facilitating the otherwise advantageous deployment of mobile IAB solutions.
  • Some embodiments include methods (e.g., procedures) for a UE configured to communicate with IAB nodes in a RAN.
  • These exemplary methods include receiving from an IAB node a configuration for the UE to apply while in a non-connected state towards the RAN.
  • the configuration includes one or more of the following:
  • These exemplary methods also include, while in the non-connected state, selectively performing one or more of the following based on whether one or more criteria in the configuration have been met: relaxed measurements in the cell and/or in one or more neighbor cells, and cell reselection.
  • the one or more relaxation and reselection conditions include one or more of the following:
  • selectively performing cell reselection includes, when the UE is camping in the cell provided by the IAB node, refraining from performing cell reselection to a second cell based on determining that the following criteria have been met:
  • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile
  • the second cell is not in the list of cells and/or frequencies to which reselection is allowed, as indicated by the one or more relaxation and reselection conditions.
  • selectively performing cell reselection includes, when the UE is camping in a second cell that is not provided by the IAB node, performing cell reselection to the cell provided by the IAB node based on determining that the following criteria have been met:
  • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile
  • the cell is in the list of cells and/or frequencies to which reselection is allowed, as indicated by the one or more relaxation and reselection conditions.
  • the one or more criteria include the one or more conditions for entering or remaining in relaxed measurement state, which include one or more of the following:
  • signal strength of the cell is static or quasi-static for at least a duration
  • the UE has camped in the cell or in another cell provided by the IAB node for at least the cell-specific camping time threshold.
  • the one or more conditions for exiting or refraining from entering relaxed measurement state include one or more of the following: • difference between IAB node speed or velocity and UE speed or velocity is at least a threshold;
  • signal strength of the cell is static or quasi-static for at least a duration
  • signal strength of a cell not provided by the IAB node is better than signal strength of the cell for at least a duration.
  • selectively performing cell reselection includes performing cell reselection based on determining that any of the following criteria have been met:
  • the one or more relaxation and reselection conditions include different first and second sets of cell reselection rules, with each set including at least one of the following:
  • selectively performing cell reselection includes the following operations:
  • the particular one of the criteria determined to have been met is that the UE is located in a vehicle.
  • the measurement configuration includes one or more of the following:
  • each measurement requirement configuration includes one or more of the following:
  • Tl a first duration
  • T2 a second duration
  • Nl a first number of measurement samples that the UE should acquire for cell reselection on each individual frequency or cell indicated in the measurement configuration
  • N2 a second number of measurement samples that the UE should acquire for cell reselection on all frequencies or cells indicated in the measurement configuration
  • N3 a third number of measurement samples that the UE should acquire for cell reselection on a subset of the frequencies or cells indicated in the measurement configuration
  • the measurement configuration includes a plurality of measurement requirement configurations associated with a corresponding plurality of sets of applicability conditions.
  • Each set of applicability conditions includes one or more of the following:
  • inventions include methods (e.g, procedures) for an IAB node configured to provide a cell for UEs co-located with the IAB node in a vehicle.
  • these exemplary methods are complementary to the exemplary methods for a UE, summarized above.
  • These exemplary methods can include transmitting, in the cell, a configuration for UEs to apply while in a non-connected state towards a RAN that includes the IAB node.
  • the configuration includes one or more of the following:
  • the configuration for UEs to apply while in a non-connected state is transmitted according to one of the following: as respective dedicated messages to one or more UEs in a connected state towards the RAN, and via broadcast in the cell.
  • the measurement configuration can include any of the content and/or have any of the structure summarized above for the measurement configuration related to UE embodiments.
  • each measurement requirement configuration e.g., in the measurement configuration
  • the one or more relaxation and reselection conditions can include any of the content and/or have any of the structure summarized above for the relaxation and reselection conditions related to UE embodiments.
  • the following criteria indicate that UEs camping in the cell provided by the I AB node are not allowed to perform cell reselection to a second cell:
  • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile
  • the second cell is not in the list of cells and/or frequencies to which reselection is allowed, as indicated by the one or more relaxation and reselection conditions.
  • the following criteria indicate that UEs camping in a second cell, not provided by the IAB node, are allowed to perform cell reselection to the cell provided by the IAB node:
  • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile
  • the cell is in the list of cells and/or frequencies to which reselection is allowed, as indicated by the one or more relaxation and reselection conditions.
  • UE e.g., wireless devices
  • IAB nodes e.g, IAB-MT and IAB-DU
  • Other embodiments also include non-transitory, computer-readable media storing computer-executable instructions that, when executed by processing circuitry, configure such UEs and IAB nodes to perform operations corresponding to any of the exemplary methods described herein.
  • embodiments described herein can reduce and/or prevent unnecessary transitions between cells for UEs operating in mobile IAB scenarios, thereby reducing and/or avoiding UE energy consumption and service degradation due to these unnecessary transitions.
  • Embodiments can also reduce unnecessary signaling and wasted radio resources in outside cells for handovers of UEs in these scenarios.
  • embodiments improve the robustness of mobile IAB deployments, e.g., on public transportation. In this manner, embodiments can facilitate deployment and/or use of IAB architectures, which can reduce overall network deployment cost and/or improve network coverage.
  • Figure 1 shows a high-level view of an exemplary 5G network architecture.
  • Figure 2 shows control-plane (CP) and user-plane (UP) interfaces within the architecture shown in Figure 1.
  • CP control-plane
  • UP user-plane
  • Figure 3 shows an exemplary' logic diagram for UE cell reselection in RRC IDLE and RRC INACTIVE states.
  • Figure 4 shows an exemplary IAB network.
  • Figure 5 shows an exemplary scenario that illustrates use of a mobile IAB node on public transportation.
  • Figure 6 shows an exemplary method (e.g, procedure) for a UE, according to various embodiments of the present disclosure.
  • Figure 7 shows an exemplary method (e.g, procedure) for an IAB node, according to various embodiments of the present disclosure.
  • Figure 8 shows a communication system according to various embodiments of the present disclosure.
  • Figure 9 shows a UE according to various embodiments of the present disclosure.
  • Figure 10 shows a network node according to various embodiments of the present disclosure.
  • Figure 11 shows a host computing system according to various embodiments of the present disclosure.
  • Figure 12 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
  • Figure 13 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (e.g., gNB in a 3GPP 5G/NR network or an enhanced or eNB in a 3 GPP LTE network), base station distributed components (e.g, CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g., gNB in a 3GPP 5G/NR network or an enhanced or eNB in a 3 GPP LTE network
  • base station distributed components e.g, CU and DU
  • a high-power or macro base station e.g., a low-power base station (e.g., micro, pic
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW PDN Gateway
  • PCRF Policy and Charging Rules Function
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • Charging Function CHF
  • PCF Policy Control Function
  • AUSF Authentication Server Function
  • LMF location management function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • wireless device is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.
  • Radio Node As used herein, a “radio node” can be either a “radio access node” (or equivalent term) or a “wireless device.”
  • Network Node As used herein, a “network node” is any node that is either part of the radio access network (e.g., a radio access node or equivalent term) or of the core network (e.g., a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g, administration) in the cellular communications network.
  • node can be any type of node that can in or with a wireless network (including RAN and/or core network), including a radio access node (or equivalent term), core network node, or wireless device.
  • a wireless network including RAN and/or core network
  • radio access node or equivalent term
  • core network node or wireless device.
  • node may be limited to a particular type (e.g., radio access node) based on its specific characteristics in any given context.
  • parent node refers to a network node immediately upstream from a particular IAB node in an IAB network (e.g., an IAB node one hop closer to a donor gNB). Even so, a parent node may be only one of the network nodes upstream from the particular IAB node in the network, e.g. , if there are multiple hops to a donor gNB.
  • ancestor node refers to any network node upstream from a particular IAB node (e.g., towards a donor gNB) in an IAB network, including a parent node.
  • Child node refers to a network node immediately downstream from a particular IAB node (e.g. , an IAB node one hop further from a donor gNB) in an IAB network. Even so, a child node may be only one of the network nodes downstream from the particular IAB node in the network, e.g., if there are multiple hops to served UEs.
  • Descendant node refers to any network node downstream from a particular IAB node (e.g., away from a donor gNB) in an IAB network, including a child node.
  • centralized CP protocols e.g, PDCP-C and RRC
  • centralized UP protocols e.g, PDCP-U
  • a gNB-CU can be separated into a CU-CP function (including RRC and PDCP for SRBs) and CU-UP function (including PDCP for UP).
  • Figure 2 shows an exemplary gNB architecture that includes two DUs, a CU-CP, and one or more CU-UPs.
  • a single CU-CP can be associated with multiple CU-UPs in a gNB.
  • the CU-CP and CU-UP communicate with each other using the El -AP protocol over the El interface, as specified in 3 GPP TS 38.463 (vl5.4.0). Furthermore, the Fl interface between CU and DU (see Figure 1) is functionally split into Fl-C between DU and CU-CP and Fl-U between DU and CU-UP.
  • Three deployment scenarios for the split gNB architecture shown in Figure 2 are defined in 3GPP TR 38.806 (V15.0.0):
  • the RRC layer controls communications between a UE and a gNB at the radio interface, as well as the mobility of a UE between cells in the NGRAN.
  • a UE After a UE is powered ON it will be in the RRC IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC_CONNECTED state (e.g., where data transfer can occur).
  • the UE returns to RRC IDLE after the connection with the network is released.
  • RRC_ IDLE state the UE does not belong to any cell, no RRC context has been established for the UE (e.g., in NGRAN), and the UE is out of UL synchronization with the network. Even so, a UE in RRC IDLE state is known in the 5GC and has an assigned IP address.
  • an RRC_IDLE UE receives system information (SI) broadcast by a serving cell, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel for pages from the EPC via an eNB serving the cell in which the UE is camping.
  • SI system information
  • a UE must perform a random-access (RA) procedure to move from RRC IDLE to RRC CONNECTED state.
  • RRC CONNECTED state the cell serving for the UE is known and an RRC context is established for the UE in the RAN node (e.g., gNB) serving the cell, such that the UE and RAN node can communicate.
  • a Cell Radio Network Temporary Identifier (C-RNTI) - a UE identity used for signaling between UE and network - is configured for a UE in RRC CONNECTED state.
  • C-RNTI Cell Radio Network Temporary Identifier
  • NR UEs In addition to the RRC IDLE and RRC CONNECTED states, NR UEs also support an RRC_INACTIVE state. Hie main principle of RRC_INACTIVE state is that the UE can return to RRC CONNECTED state as quickly and efficiently as possible. When the UE transitions to RRC_INACTIVE state, both the UE and the RAN store all the information necessary to quickly resume the connection. Hie message that transitions the UE to RRC_INACTIVE state contains a set of parameters for UE operation in RRC_INACTIVE state operation, such as a RAN Notification Area (RNA) within which the UE is allowed to move without notifying the network. Further, the message includes parameters needed for secure transition back to the RRC_CONNECTED state, such as a UE identifier and security’ information needed to support encrypted resume messages.
  • RNA RAN Notification Area
  • Figure 3 shows an exemplary' logic diagram for UE cell reselection in RRC IDLE and RRC INACTIVE states.
  • the procedure starts at the top (at (1)) whenever the UE selects a new public land mobile network (PLMN) or standalone non-public network (SNPN).
  • PLMN public land mobile network
  • SNPN standalone non-public network
  • the UE proceeds through the logic based on stored information, cell measurements, and information obtained from the PLMN/SNPN (e.g., from broadcast SI).
  • the procedure is further described in 3GPP TS 38.304 (V17.0.0).
  • a UE can be configured to relax neighbor cell measurements for cell reselection when the UE meets one or more relaxed measurement criteria (RMC).
  • the UE can be configured for applying relaxed measurements via higher layer signalling such as SI block 2 (SIB2).
  • SIB2 SI block 2
  • Example RMC include low mobility, not-at-cell-edge, stationary, or combinations thereof.
  • FIG 4 shows a reference diagram for an IAB network in standalone mode, as further explained in 3GPP TR 38.874 (v!6.0.0).
  • the IAB network shown in Figure 3 includes one IAB- donor (440) and multiple lAB-nodes (411-415), all of which can be part of a radio access network (RAN, 499) such as an NG-RAN.
  • the IAB donor includes DUs (421, 422) connected to a CU (430), which includes CU-CP (431) and CU-UP (432) functions.
  • the IAB donor can communicate with core network (CN, 450) via the CU functionality shown.
  • Each of the IAB nodes connects to the lAB-donor via one or more wireless backhaul links (also referred to herein as “hops”). More specifically, the Mobile-Termination (MT) function of each lAB-node terminates the radio interface layers of a wireless backhaul link towards a corresponding “upstream” DU function.
  • This MT functionality is similar to functionality that enables UEs to access the IAB network and, in fact, has been specified by 3GPP as part of the Mobile Equipment (ME).
  • IAB functionality is transparent to UEs, such that UEs are unaware if they are being served by a conventional gNB or an lAB-donor gNB via one or more intermediate IAB nodes.
  • upstream DUs can include either DU of the IAB donor and, in some cases, a DU function of an intermediate IAB node that is “downstream” from the IAB donor.
  • lAB-node (414) is downstream from lAB-node (412) and DU (421)
  • lAB-node (412) is upstream from lAB-node (414) but downstream from DU (421)
  • DU (421) is upstream from lAB-nodes (412, 414).
  • IAB- nodes 411, 413, 414) can be considered “access IAB nodes” for UEs (401, 403, 402), respectively, and that term will be used in the same manner hereinafter.
  • the lAB-donor can be treated as a single logical node that comprises a set of functions including the DUs, the CU-CP, the CU-UP, and possibly other functions.
  • the lAB-donor can be split according to these functions, which can all be either co-located or non-co-located as allowed by the 3GPP NG-RAN architecture.
  • some of the functions presently associated with the lAB-donor can be moved outside of the lAB-donor if such functions do not perform lAB-specific tasks.
  • each lAB-node DU connects to the lAB-donor CU using a modified form of Fl, which is referred to as Fl*.
  • Fl* The user-plane portion of Fl* (referred to as “Fl*-U”) runs over RLC channels on the wireless backhaul between the MT on the serving lAB-node and the DU on the IAB donor.
  • Each DU (donor or IAB node) initiates an Fl setup with the IAB-CU with which it has a TNL connection.
  • the IAB donor CU sends a GNB-CU CONFIGURATION UPDATE to optionally indicate the DU cells to be activated.
  • the Fl interface is also used for IAB node mobility signaling with the IAB donor CU.
  • a Backhaul Adaptation Protocol (BAP) layer has been introduced in IAB nodes and IAB donors.
  • the BAP layer routes packets to the appropriate downstream/upstream node.
  • the BAP layer also maps UE bearer data to the proper backhaul RLC channel (also referred to herein as “backhaul RLC bearer”), as well as between ingress and egress backhaul RLC channels in intermediate IAB nodes.
  • a node is a receiver on its ingress BH RLC channels and a transmitter on its egress BH RLC channels, regardless of whether the receiving or transmitting direction is upstream or downstream in the IAB network.
  • the BAP layer can be configured to satisfy the end to end QoS requirements of bearers.
  • the BAP sublayer contains one BAP entity at the MT function and a separate collocated BAP entity at the DU function.
  • the BAP sublayer contains only one BAP entity. Each BAP entity has a transmitting part and a receiving part.
  • Each transmitting part of a BAP entity on one end of a backhaul link has a corresponding receiving part of a BAP entity at the other end of the backhaul link across the backhaul link (e.g., in an lAB-node or an lAB-donor-DU, as the case may be).
  • a BAP sublayer expects lower layers per RLC entity to provide acknowledged or unacknowledged data transfer service for BAP SDUs.
  • the BAP sublayer supports the following functions:
  • the BAP sublayer determines whether the packet has reached its final destination, in which case the packet will be transmitted to UEs for which the IAB node is an access node. In this case, the BAP layer passes the packet to higher layers in the IAB node which are in charge of mapping the packet to the various QoS flows and hence DRBs which are included in the packet. Otherwise, the IAB node will forward it to another IAB node in the right path. If the BAP sublayer determines that the packet has not reached its final destination, the BAP sublayer determines the proper egress BH RLC channel on the basis of the BAP destination, path IDs, and ingress BH RLC channel. Similar routing techniques are applied in the upstream direction, with the final destination being a specific donor DU/CU.
  • the BAP layer must be configured with a routing table mapping ingress RLC channels to egress RLC channels, which may be different depending on the specific BAP destination and path of the packet.
  • the BAP destination and path ID are included in the header of the BAP packet so that the BAP layer can determine where to forward the packet.
  • the BAP layer is involved in hop-by-hop flow control. For example, a child node can inform the parent node about possible congestions experienced locally at the child node, so that the parent node can throttle the traffic towards the child node. The parent node can also use the BAP layer to inform the child a node in case of radio link failure (RLF) issues experienced by the parent, so that the child can possibly re-establish its connection to another parent node.
  • RLF radio link failure
  • 3GPP Rel-17 includes IAB topology enhancements and partial migration of IAB nodes for radio link failure (RLF) recovery and load balancing.
  • mobile IAB such as vehicle-mounted IAB nodes that provide cell coverage to UEs that are onboard and/or in vicinity of the vehicle.
  • vehicle-mounted IAB nodes that provide cell coverage to UEs that are onboard and/or in vicinity of the vehicle.
  • a mobile IAB node mounted on a public transportation vehicle e.g., bus, tram, train, etc.
  • a public transportation vehicle e.g., bus, tram, train, etc.
  • FIG. 5 shows an exemplary scenario that illustrates the use case of mobile IAB on public transportation.
  • the vehicle is a bus travelling on a route that is covered by four different stationary parent IAB nodes (IAB parents 1-4, 521-524), each of which backhauls traffic to/from one of two IAB donors (X, 531 and Y, 532).
  • the bus includes a mobile IAB node (510).
  • the IAB nodes and the IAB donors are part of a RAN (599, e.g., NG-RAN).
  • Each IAB node (mobile and parents) includes a DU that provides access to UEs (e.g., 540) around it and an MT that provides a backhaul (BH) connection to the DU of a parent IAB node or to donor DU.
  • the parent IAB nodes backhaul their own traffic together with traffic from the mobile IAB node.
  • the CUs in IAB donors X, Y maintain respective Fl connections to their two descendant IAB parent nodes (i.e., 1-2 for X, 3-4 for Y), as well as to the mobile IAB node when it is connected to either of the two IAB parent nodes.
  • FIG. 5 shows four discrete positions (A-D) for the mobile IAB node, each of which has the following characteristics:
  • the mobile IAB must change the Fl connection from IAB donor X to IAB donor Y when moving from position B to C, thus requiring an Fl handover and setup of BH RLC channels.
  • the 3GPP Rel-18 mobile IAB work item (WI) includes the following objectives:
  • Enhancements for mobility of an lAB-node together with its served UEs including aspects related to group mobility. No optimizations for the targeting of surrounding UEs. Solutions should avoid touching upon topics where Rel-17 discussions already occurred and where the topic was excluded from Rel-17, except for enhancements that are specific to lAB- node mobility. • Mitigation of interference due to lAB-node mobility, including the avoidance of potential reference and control signal collisions (e.g., PCI, RACH).
  • potential reference and control signal collisions e.g., PCI, RACH
  • the WI also specifies that mobile lAB-nodes should be able to serve legacy UEs and that optimizations for mobile I AB may include Rel-18 UE enhancements, provided that such enhancements are backwards compatible.
  • 3GPP RAN4 working group (WG) will conduct a coexistence study to assess the impact of moving cells and, based on the study outcome, specify RF and RRM requirements and mechanisms for the mobile lAB-node to enable co-existence, if needed.
  • RAN4 WG will also specify RRM requirements for the mobile lAB-node to enable IAB- node mobility, if needed.
  • a UE and a mobile IAB node are within the same vehicle, and the UE is in a non-connected state (e.g., RRC IDLE or RRC INACTIVE) with respect to the RAN (which including the mobile IAB node).
  • the non-connected UE will periodically or occasionally perform measurements to search for cells that are available for connecting to the RAN.
  • the UE will find the cell provided by the mobile IAB node (“inside cell”) but may also find other cells provided by other RAN nodes, such as overlay coverage cells (“outside cells”) provided by fixed RAN nodes (e.g., base station).
  • the UE is likely to find different outside cells over time and the measured signal strength on any outside cell may vary over time. In some cases, the UE may measure a higher signal strength on an outside cell than on the inside cell. This can cause various problems, issues, and/or difficulties for the UE.
  • the UE may select an outside cell for the connection based on that cell having a measured signal strength greater than inside cell.
  • this relation between signal strengths for inside and outside cells will be temporary due to the vehicle’s movement.
  • the UE may select the outside cell when the UE and vehicle have a relatively direct line of sight (LOS) to the outside cell, but the signal strength degrades quickly after the UE/vehicle loses the LOS. This scenario is common at higher frequencies.
  • the UE’s signal strength for the outside cell may also degrade as the UE moves away from the transmitter for that cell.
  • the UE initiates access to outside cell with a temporarily high signal strength but will shortly detect that the signal strength has significantly degraded due to movement, causing the UE to perform additional measurements to select a new cell for handover of the connection.
  • the process will be repeated so long as the UE selects an outside cell rather than the inside cell for handover of the connection.
  • the overall result for the UE is a significant number of cell measurements, unnecessary handover procedures, and excessive energy consumption.
  • the overall result for the RAN is unnecessary signaling and wasted radio resources in outside cells for UE handover(s).
  • Embodiments of the present disclosure address these and other problems, issues, and/or difficulties by techniques for a non-connected UE (e.g., in RRC IDLE or RRC INACTIVE), in the coverage of a cell provided by a mobile IAB node co-located with the UE on or in a vehicle, to perform measurements less frequently and/or extensively than when in the coverage of a cell provided by a fixed RAN node.
  • the RAN can provide the UE a mobile IAB measurement configuration with a relaxed and/or reduced number of measurement and cell search attempts.
  • embodiments can reduce and/or prevent unnecessary transitions between cells for UEs operating in mobile IAB scenarios. Consequently, embodiments can reduce UE energy consumption and service degradation due to these unnecessary transitions. Additionally, embodiments can reduce unnecessary signaling and wasted radio resources in outside cells for handovers of UEs in these scenarios. At a high level, embodiments improve the robustness of mobile IAB deployments, e.g., on public transportation.
  • m-IAB mobile IAB node
  • m-IAB node an IAB node configured to provide a cell for UEs co-located with the IAB node in a vehicle (e.g., bus or other public transportation).
  • the UEs may be within coverage of the cell provided by the mobile IAB node, which may also be referred to as “camping” in the cell.
  • camping in the cell.
  • co-located in a vehicle should be understood as being in, on, or attached to the same vehicle (including different portions) and/or having the same movement as the vehicle.
  • UE speed can be expressed in terms of distance per unit time (e.g., km/h) and/or in Doppler frequency (e.g., Hz) for a received carrier frequency.
  • UE velocity is UE speed along the direction of UE movement (e.g., relative to principal directions N, S, E, or W).
  • Some embodiments include methods for a UE configured to access a cell provided by an IAB node co-located with the UE in a vehicle (i.e., a mobile IAB node).
  • the UE can receive from the mobile IAB node a message including a configuration for the UE to apply while in a nonconnected state (e.g., RRC IDLE or RRC INACTIVE) towards a RAN that includes the mobile IAB node.
  • the message can be an RRC message.
  • the configuration can include one or more of the following:
  • measurement configuration to be used while the UE is in RRC IDLE/ RRC INACTIVE including one or more of the following: o a measurement requirement configuration that includes one or more requirements, conditions, and/or events for performing measurements for cell (re)selection purposes while the UE is in RRC IDLE/RRC INACTIVE; o an indication of whether the measurement requirement configuration is valid while:
  • the UE is within coverage of a cell provided by the mobile IAB node; and/or 2) the UE is physically located in the vehicle with the mobile IAB node; o a validity duration for the measurement configuration; o a measurement identifier (ID); o one or more frequencies, cells (e.g., PCIs), or reference signals to be measured. o identifiers of one or more cells (e.g., PCIs, CGIs) provided by the mobile IAB node; o a request for the UE’s speed or velocity; o a request for the UE’s location; o an indication that the cell (i.e., in which the UE received the measurement configuration) is mobile.
  • ID measurement identifier
  • o identifiers of one or more cells e.g., PCIs, CGIs
  • one or more relaxation and reselection conditions applicable while the UE is in coverage of a cell provided by the mobile IAB node including one or more of the following: o an indication that the cell is mobile; o a cell-specific threshold for signal strength, indicating that the UE should remain camped in a cell provided by the mobile IAB node when measured signal strength for that cell is above the threshold and/or variance in measured signal strength is within certain margin; o a cell-specific threshold for camping time, indicating that the UE is physically located in the vehicle when the camping time in in a cell provided by the mobile IAB node is above the threshold; o velocity or speed of the mobile IAB node; o one or more conditions for entering relaxed measurement state for serving and/or neighbor cells; o one or more conditions for exiting relaxed measurement state for serving and/or neighbor cells; o a list of neighbor cells/frequencies provided by other RAN nodes, to which the UE can apply relaxed measurements if the one or more conditions for entering relaxed measurement state are met; o
  • the UE can determine one of the following:
  • the configuration received by the UE from the RAN can include one or more measurement configurations such as described above, with each measurement configuration including an indication on whether it should be applied only when physically inside the vehicle in which the mobile IAB is mounted, only when the UE is not physically inside (i.e. outside) the vehicle in which the mobile IAB is mounted, or regardless of whether the UE is physically inside the vehicle in which the mobile IAB is mounted.
  • one measurement configuration may contain only serving cells of the mobile IAB while another measurement configuration may contain neighbor stationary cells (e.g., determined by the mobile IAB node based on measurement report from the IAB-MT).
  • one or more of the measurement configurations may include respective durations of validity or relative priorities (e.g., relative to other measurement configurations).
  • the measurement requirement configuration can include one or more of the following: • a unique identifier.
  • Tl a first duration (Tl), indicating how often the UE should perform measurements for cell (re)selection purposes on a single frequency or cell (PCI) included in the measurement configuration. If the UE initiates a first timer with Tl, the UE should perform measurements on the single frequency /cell every time the first timer expires.
  • T2 a second duration (T2), indicating how often the UE should perform measurements for cell (re)selection purposes on all frequencies or cells (PCIs) included in the measurement configuration. If the UE initiates a second timer with T2, the UE should perform measurements on all frequencies/cells before the second timer expires.
  • T2 a second duration
  • PCIs e.g., all cells provided by the mobile IAB node
  • the UE should perform measurements for cell (re)selection purposes, among the ones configured within the measurement configuration.
  • N2 a second number of measurement samples
  • PCIs frequencies or cells
  • N3 • a third number of measurement samples (N3) the UE should acquire for cell (re)selection purposes on a subset of the frequencies or cells (PCIs) included in the measurement configuration.
  • PCIs frequencies or cells
  • the UE in non-connected state based upon an indication (e.g., in the measurement configuration) that the cell is mobile, the UE in non-connected state enters into relaxed neighbor cell monitoring as long as the indicated mobile IAB serving cell(s)’ signal strength threshold (RSRP) is above the provided threshold.
  • RSRP signal strength threshold
  • the one or more conditions for entering relaxed measurement state can include one or more of the following: • difference between speed (or velocity) of the mobile IAB node and speed (or velocity) of UE is less than a threshold;
  • signal strength e.g., RSRP
  • cell-specific signal strength threshold which can be included in the configuration for performing cell selection and/or relaxed measurements
  • signal strength (e.g., RSRP) of cell provided by mobile IAB node is static or quasi-static for at least a duration
  • the indication that the UE’s serving cell is mobile e.g., provided by a mobile IAB node
  • UE has camped in the same cell (or in a cells provided by the mobile IAB node) for at least a cell-specific threshold for camping time (which can be included in the configuration for performing cell (re)selection and/or relaxed measurements).
  • Entering relaxed measurement state may include the UE in RRC IDLE/ RRC INACTIVE performing relaxed measurements on the cells that are not controlled by the mobile IAB node, and performing non-relaxed (or normal) measurements on the cells controlled by the mobile IAB node.
  • the one or more conditions for exiting relaxed measurement state can include one or more of the following:
  • signal strength e.g., RSRP
  • a cell-specific signal strength threshold which can be included in the configuration for performing cell selection and/or relaxed measurements
  • signal strength (e.g., RSRP) of cell provided by mobile IAB node is neither static nor quasi-static for at least a duration
  • a UE may be provided with first and second sets of cell reselection rules to be used when camping in a cell provided by a mobile IAB node.
  • Each set of cell reselection rules includes at least one of the following: • a list of cells/frequencies to which reselection is allowed so long as relevant thresholds are met; and
  • the UE applies the first set based on determining that one or more conditions are met, and applies the second set based on determining that the one or more conditions are not met.
  • the RAN may provide first and second cell reselection priority lists (i.e., of relative priorities), wherein the UE uses the first cell reselection priority list based on determining that one or more conditions are met, and uses the second cell reselection priority list based on determining that the one or more conditions are not met.
  • first and second cell reselection priority lists i.e., of relative priorities
  • the one or more conditions can include whether the UE is physically located in a vehicle.
  • the UE uses the first set of cell reselection rules when it determines that it is physically located in the vehicle (so long as any other relevant conditions are met) and uses the second set of cell reselection rules when it determines that it is not physically located in a vehicle.
  • Some embodiments include methods for a mobile IAB node configured to provide a cell to UEs co-located with the mobile IAB node in a vehicle.
  • the mobile IAB node can transmit to one or more UEs a message including a configuration to apply while the UEs are in a nonconnected state (e.g., RRC IDLE or RRC INACTIVE) towards a RAN that includes the mobile IAB node.
  • the message can be an RRC message.
  • the configuration can include any of the information discussed above in relation to UE embodiments.
  • the RAN may decide to send the configuration via dedicated RRC signaling or via broadcast (e.g., in system information). If the RAN wants to provide a configuration specific to a cell served by the mobile IAB node, the RAN can broadcast this configuration in the cell so it is obtained by all UEs connected to the cell. In a variant, one or more cell-specific configurations can be provided to all UEs (e.g., via RRC) and later activated by an indication broadcast in SI for the cell provided by the mobile IAB node.
  • the RAN can provide UE-specific configurations via dedicated RRC messages.
  • the RAN can provide a UE-specific configuration via an RRC message (e.g., RRCRelease, RRCReject, etc.) that releases a UEs connection and sends it to a nonconnected state (e.g., RRC IDLE, RRC INACTIVE), so that the UE has the configuration to use after entering the non-connected state.
  • the RAN can send the configuration to the UE via MAC CE while the UE is connected before entering the non-connected state.
  • the RAN may provide different measurement requirement configurations that should be applied by the UE under different sets of conditions, with each set of conditions including one or more of the following:
  • Figures 6- 7, depict exemplary methods (e.g., procedures) performed by a UE and a IAB node in a RAN (e.g., NG-RAN), respectively.
  • a RAN e.g., NG-RAN
  • various features of the operations described below correspond to various embodiments described above.
  • the exemplary methods shown in Figures 6-7 can be complementary to each other such that they can be used cooperatively to provide benefits, advantages, and/or solutions to problems described herein.
  • the exemplary methods are illustrated in Figures 6-7 by specific blocks in particular orders, the operations corresponding to the blocks can be performed in different orders than shown and can be combined and/or divided into blocks and/or operations having different functionality than shown.
  • Optional blocks and/or operations are indicated by dashed lines.
  • Figure 6 illustrates an exemplary method (e.g, procedure) for a UE configured to communicate with IAB nodes in a RAN, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 6 can be performed by a UE (e.g., wireless device) such as described elsewhere herein.
  • the exemplary method can include the operations of block 610, where the UE can receive from an IAB node a configuration for the UE to apply while in a non-connected state towards the RAN.
  • the configuration includes one or more of the following:
  • the exemplary method can also include the operations of block 620, where while in the non-connected state, the UE can selectively perform one or more of the following based on whether one or more criteria in the configuration have been met: relaxed measurements in the cell and/or in one or more neighbor cells, and cell reselection.
  • the UE is co-located with the IAB node in a vehicle.
  • the message is received according to one or more of the following: while the UE is in a connected state towards the RAN, and via broadcast in the cell.
  • the one or more relaxation and reselection conditions include one or more of the following:
  • selectively performing cell reselection in block 620 includes the operations of sub-block 621, where when the UE is camping in the cell provided by the IAB node, the UE can refrain from performing cell reselection to a second cell based on determining that the following criteria have been met:
  • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile
  • selectively performing cell reselection in block 620 includes the operations of sub-block 622, where when the UE is camping in a second cell that is not provided by the IAB node, the UE can perform cell reselection to the cell provided by the IAB node based on determining that the following criteria have been met:
  • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile
  • the cell is in the list of cells and/or frequencies to which reselection is allowed, as indicated by the one or more relaxation and reselection conditions.
  • the one or more criteria include the one or more conditions for entering or remaining in relaxed measurement state, which include one or more of the following:
  • signal strength of the cell is static or quasi-static for at least a duration
  • the UE has camped (e.g., in the non-connected state) in the cell or in another cell provided by the IAB node for at least the cell-specific camping time threshold.
  • the one or more conditions for exiting or refraining from entering relaxed measurement state include one or more of the following:
  • signal strength of the cell is static or quasi-static for at least a duration
  • signal strength of a cell not provided by the IAB node is better than signal strength of the cell for at least a duration.
  • selectively performing cell reselection in block 620 includes the operations of sub-block 623, where the UE performs cell reselection based on determining that any of the following criteria have been met:
  • the one or more relaxation and reselection conditions include different first and second sets of cell reselection rules, with each set including at least one of the following:
  • selectively performing cell reselection in block 620 includes the following operations, labelled with corresponding sub-block numbers:
  • the particular one of the criteria determined to have been met is that the UE is located in a vehicle.
  • the measurement configuration includes one or more of the following:
  • each measurement requirement configuration includes one or more of the following:
  • a validity duration for the measurement requirement configuration • a first duration (Tl), indicating how often the UE should perform measurements for cell reselection on each individual frequency or cell indicated in the measurement configuration;
  • T2 a second duration
  • Nl a first number of measurement samples that the UE should acquire for cell reselection on each individual frequency or cell indicated in the measurement configuration
  • N2 a second number of measurement samples that the UE should acquire for cell reselection on all frequencies or cells indicated in the measurement configuration
  • N3 a third number of measurement samples that the UE should acquire for cell reselection on a subset of the frequencies or cells indicated in the measurement configuration
  • the measurement configuration includes a plurality of measurement requirement configurations associated with a corresponding plurality of sets of applicability conditions.
  • Each set of applicability conditions includes one or more of the following:
  • Figure 7 illustrates an exemplary method (e.g., procedure) for an IAB node configured to provide a cell for UEs co-located with the IAB node in a vehicle, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 7 can be performed by a mobile IAB node (e.g., IAB-DU and IAB-MT) such as described elsewhere herein.
  • the exemplary method can include the operations of block 710, where the IAB node can transmit, in the cell, a configuration for UEs to apply while in a non-connected state towards a RAN that includes the IAB node.
  • the configuration includes one or more of the following:
  • the configuration for UEs to apply while in a non-connected state is transmitted according to one of the following: in respective dedicated messages to one or more UEs in a connected state towards the RAN, and via broadcast in the cell.
  • the measurement configuration can include any of the content and/or have any of the structure discussed above for the measurement configuration in relation to UE embodiments shown in Figure 6.
  • each measurement requirement configuration (e.g., in the measurement configuration) can include any of the content and/or have any of the structure discussed above for the measurement requirement configuration in relation to UE embodiments shown in Figure 6.
  • the one or more relaxation and reselection conditions can include any of the content and/or have any of the structure discussed above for the relaxation and reselection conditions in relation to UE embodiments shown in Figure 6.
  • the following criteria indicate that UEs camping in the cell provided by the IAB node are not allowed to perform cell reselection to a second cell:
  • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile
  • the second cell is not in the list of cells and/or frequencies to which reselection is allowed, as indicated by the one or more relaxation and reselection conditions.
  • the following criteria indicate that UEs camping in a second cell, not provided by the IAB node, are allowed to perform cell reselection to the cell provided by the IAB node: • the one or more relaxation and reselection conditions include an indication that the cell provided by the IAB node is mobile; and
  • the cell is in the list of cells and/or frequencies to which reselection is allowed, as indicated by the one or more relaxation and reselection conditions.
  • the one or more relaxation and reselection conditions can include different first and second sets of cell reselection rules, with each set including at least one of the following:
  • the first set of cell reselection rules are applicable when the UE is located in a vehicle and the second set of cell reselection rules are applicable when the UE is not located in a vehicle.
  • FIG. 8 shows an example of a communication system 800 in accordance with some embodiments.
  • communication system 800 includes a telecommunication network 802 that includes an access network 804 (e.g., RAN) and a core network 806, which includes one or more core network nodes 808.
  • Access network 804 includes one or more access network nodes, such as network nodes 810a-b (one or more of which may be referred to as network nodes 810), or any other similar 3GPP access node or non-3GPP access point.
  • Network nodes 810 facilitate direct or indirect connection of UEs, such as by connecting UEs 812a-d (one or more of which may be generally referred to as UEs 812) to core network 806 over one or more wireless connections.
  • 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.
  • communication system 800 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.
  • Communication system 800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • UEs 812 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 810 and other communication devices.
  • the network nodes 810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with UEs 812 and/or with other network nodes or equipment in telecommunication network 802 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in telecommunication network 802.
  • core network 806 connects the network nodes 810 to one or more hosts, such as host 816. 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.
  • Core network 806 includes one or more core network nodes (e.g., 808) that include 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 core network node 808.
  • 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
  • Host 816 may be under the ownership or control of a service provider other than an operator or provider of access network 804 and/or telecommunication network 802, and may be operated by the service provider or on behalf of the service provider.
  • Host 816 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.
  • communication system 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 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 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 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 Telecommunications System
  • LTE Long Term Evolution
  • telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunication network 802 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 802. For example, telecommunication network 802 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 loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • UEs 812 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be configured to transmit information to access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 804.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi -radio dual connectivity
  • hub 814 communicates with access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812c and/or 812d) and network nodes (e.g., network node 810b).
  • UEs e.g., UE 812c and/or 812d
  • network nodes e.g., network node 810b
  • hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • hub 814 may be a broadband router enabling access to core network 806 for the UEs.
  • hub 814 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 810, or by executable code, script, process, or other instructions in hub 814.
  • hub 814 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.
  • hub 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • hub 814 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.
  • Hub 814 may have a constant/persistent or intermittent connection to the network node 810b. Hub 814 may also allow for a different communication scheme and/or schedule between hub 814 and UEs (e.g., UE 812c and/or 812d), and between hub 814 and core network 806. In other examples, hub 814 is connected to core network 806 and/or one or more UEs via a wired connection. Moreover, hub 814 may be configured to connect to an M2M service provider over access network 804 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via hub 814 via a wired or wireless connection.
  • UEs may establish a wireless connection with the network nodes 810 while still connected via hub 814 via a wired or wireless connection.
  • hub 814 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 810b.
  • hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 810b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 9 shows a UE 900 in accordance with some embodiments.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, 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 3GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-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.
  • 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
  • UE 900 includes processing circuitry 902 that is operatively coupled via bus 904 to input/output interface 906, power source 908, memory 910, communication interface 912, and/or any other component, or any combination thereof.
  • processing circuitry 902 that is operatively coupled via bus 904 to input/output interface 906, power source 908, memory 910, communication interface 912, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 9. 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.
  • Processing circuitry 902 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 memory 910.
  • Processing circuitry 902 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.
  • processing circuitry 902 may include multiple central processing units (CPUs).
  • input/output interface 906 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 UE 900.
  • 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
  • power source 908 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. Power source 908 may further include power circuitry for delivering power from power source 908 itself, and/or an external power source, to the various parts of UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from power source 908 to make the power suitable for the respective components of UE 900 to which power is supplied.
  • an external power source e.g., an electricity outlet
  • Photovoltaic device e.g., or power cell
  • Power source 908 may further include power circuitry for delivering power from power source 908 itself, and/or an external power source, to the various parts of UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example,
  • Memory 910 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916.
  • Memory 910 may store, for use by UE 900, any of a variety of various operating systems or combinations of operating systems.
  • Memory 910 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 random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or 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 external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • Memory 910 may allow UE 900 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 memory 910, which may be or comprise a device-readable storage medium.
  • Processing circuitry 902 may be configured to communicate with an access network or other network using communication interface 912.
  • Communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922.
  • Communication interface 912 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 transmitter 918 and/or receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., 922) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of communication interface 912 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, 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.
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 912, 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., an alert is sent when moisture is detected), 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 Internet of Things (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.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, 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 Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • 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 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and 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.
  • Figure 10 shows a network node 1000 in accordance with some embodiments.
  • network nodes include, but are not limited to, access points (e.g., radio access points) and base stations (e.g., radio base stations, Node Bs, eNBs, and gNBs).
  • access points e.g., radio access points
  • base stations e.g., radio base stations, Node Bs, eNBs, and gNBs.
  • Base stations 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 base stations, pico base stations, micro base stations, or macro base stations.
  • a base station 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 base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station 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 base station 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)), IAB nodes, and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SM
  • Network node 1000 includes processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008.
  • Network node 1000 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 1000 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 NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 1000 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, 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 network node 1000.
  • wireless technologies for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, 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 network node 1000.
  • RFID Radio Frequency Identification
  • Processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, 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 1000 components, such as memory 1004, to provide network node 1000 functionality.
  • processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, RF transceiver circuitry 1012 and baseband processing circuitry 1014 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 RF transceiver circuitry 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014.
  • RF transceiver circuitry 1012 and baseband processing circuitry 1014 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 RF transceiver circuitry 1012 and baseband processing
  • Memory 1004 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, random access memory (RAM), read-only memory (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 processing circuitry 1002.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (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-vola
  • Memory 1004 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 (collectively denoted computer program 1004a, which may be in the form of a computer program product) capable of being executed by processing circuitry 1002 and utilized by network node 1000.
  • Memory 1004 may be used to store any calculations made by processing circuitry 1002 and/or any data received via communication interface 1006.
  • processing circuitry 1002 and memory 1004 is integrated.
  • Communication interface 1006 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, communication interface 1006 comprises port(s)/terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. Communication interface 1006 also includes radio frontend circuitry 1018 that may be coupled to, or in certain embodiments a part of, antenna 1010. Radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. Radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002.
  • Radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1020 and/or amplifiers 1022. The radio signal may then be transmitted via antenna 1010. Similarly, when receiving data, antenna 1010 may collect radio signals which are then converted into digital data by radio front-end circuitry 1018. The digital data may be passed to processing circuitry 1002. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
  • network node 1000 does not include separate radio front-end circuitry 1018, instead, processing circuitry 1002 includes radio front-end circuitry and is connected to antenna 1010. Similarly, in some embodiments, all or some of RF transceiver circuitry 1012 is part of communication interface 1006. In still other embodiments, communication interface 1006 includes one or more ports or terminals 1016, radio front-end circuitry 1018, and RF transceiver circuitry 1012, as part of a radio unit (not shown), and communication interface 1006 communicates with baseband processing circuitry 1014, which is part of a digital unit (not shown). Antenna 1010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 1010 may be coupled to radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 1010 is separate from network node 1000 and connectable to network node 1000 through an interface or port.
  • Antenna 1010, communication interface 1006, and/or processing circuitry 1002 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, antenna 1010, communication interface 1006, and/or processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • Power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1000 with power for performing the functionality described herein.
  • network node 1000 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of power source 1008.
  • power source 1008 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 network node 1000 may include additional components beyond those shown in Figure 10 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.
  • network node 1000 may include user interface equipment to allow input of information into network node 1000 and to allow output of information from network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1000.
  • FIG 11 is a block diagram of a host 1100, which may be an embodiment of host 816 of Figure 8, in accordance with various aspects described herein.
  • host 1100 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • Host 1100 may provide one or more services to one or more UEs.
  • Host 1100 includes processing circuitry 1102 that is operatively coupled via bus 1104 to input/output interface 1106, network interface 1108, power source 1110, and memory 1112. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 9 and 10, such that the descriptions thereof are generally applicable to the corresponding components of host 1100.
  • Memory 1112 may include one or more computer programs including one or more host application programs 1114 and data 1116, which may include user data, e.g., data generated by a UE for host 1100 or data generated by host 1100 for a UE.
  • host 1100 may utilize only a subset or all of the components shown.
  • Host application programs 1114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • Host application programs 1114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • host 1100 may select and/or indicate a different host for over-the-top services for a UE.
  • Host application programs 1114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real- Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HTTP Live Streaming HLS
  • RTMP Real-Time Messaging Protocol
  • RTSP Real- Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 12 is a block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in virtualization environment 1200 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1204 includes processing circuitry, memory that stores software and/or instructions (collectively denoted computer program 1204a, which may be in the form of a computer program product) executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1208a-b (one or more of which may be generally referred to as VMs 1208), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.
  • VMs 1208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1206.
  • VMs 1208 may be implemented on one or more of VMs 1208, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • each VM 1208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each VM 1208, and that part of hardware 1204 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of the hardware 1204 and corresponds to application 1202.
  • Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of applications 1202.
  • hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 13 shows a communication diagram of a host 1302 communicating via a network node 1304 with a UE 1306 over a partially wireless connection in accordance with some embodiments.
  • host 1302 Like host 1100, embodiments of host 1302 include hardware, such as a communication interface, processing circuitry, and memory. Host 1302 also includes software, which is stored in or accessible by host 1302 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as UE 1306 connecting via an over-the-top (OTT) connection 1350 extending between UE 1306 and host 1302.
  • OTT over-the-top
  • Network node 1304 includes hardware enabling it to communicate with host 1302 and UE 1306.
  • Connection 1360 may be direct or pass through a core network (like core network 806 of Figure 8) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • UE 1306 includes hardware and software, which is stored in or accessible by UE 1306 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1306 with the support of host 1302.
  • client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1306 with the support of host 1302.
  • an executing host application may communicate with the executing client application via OTT connection 1350 terminating at UE 1306 and host 1302.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • OTT connection 1350 may transfer both the request data and the user data.
  • OTT connection 1350 may extend via a connection 1360 between host 1302 and network node 1304 and via a wireless connection 1370 between network node 1304 and UE 1306 to provide the connection between host 1302 and UE 1306.
  • Connection 1360 and wireless connection 1370, over which OTT connection 1350 may be provided, have been drawn abstractly to illustrate the communication between host 1302 and UE 1306 via network node 1304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • host 1302 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with UE 1306.
  • the user data is associated with a UE 1306 that shares data with host 1302 without explicit human interaction.
  • host 1302 initiates a transmission carrying the user data towards UE 1306.
  • Host 1302 may initiate the transmission responsive to a request transmitted by UE 1306. The request may be caused by human interaction with UE 1306 or by operation of the client application executing on UE 1306.
  • the transmission may pass via network node 1304, in accordance with the teachings of the embodiments described throughout this disclosure.
  • network node 1304 transmits to UE 1306 the user data that was carried in the transmission that host 1302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • UE 1306 receives the user data carried in the transmission, which may be performed by a client application executed on UE 1306 associated with the host application executed by host 1302.
  • UE 1306 executes a client application which provides user data to host 1302.
  • the user data may be provided in reaction or response to the data received from host 1302.
  • UE 1306 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of UE 1306.
  • UE 1306 initiates, in step 1318, transmission of the user data towards host 1302 via network node 1304.
  • network node 1304 receives user data from UE 1306 and initiates transmission of the received user data towards host 1302.
  • host 1302 receives the user data carried in the transmission initiated by UE 1306.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 1306 using OTT connection 1350, in which wireless connection 1370 forms the last segment. More precisely, embodiments described herein can reduce and/or prevent unnecessary transitions between cells for UEs operating in mobile IAB scenarios. Consequently, embodiments can reduce UE energy consumption and service degradation due to these unnecessary transitions. Embodiments can also reduce unnecessary signaling and wasted radio resources in outside cells for handovers of UEs in these scenarios.
  • embodiments improve the robustness of mobile I AB deployments, e.g., on public transportation. As such, embodiments can facilitate deployment and/or use of IAB architectures, which can reduce overall network deployment cost and/or improve network coverage. By improving networks in this manner, embodiments increase the value of OTT services delivered over improved networks to both end users and service providers.
  • factory status information may be collected and analyzed by host 1302.
  • host 1302 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • host 1302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • host 1302 may store surveillance video uploaded by a UE.
  • host 1302 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • host 1302 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • 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 may be implemented in software and hardware of host 1302 and/or UE 1306.
  • sensors (not shown) may be deployed in or in association with other devices through which OTT connection 1350 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 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 1304. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like, by host 1302.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1350 while monitoring propagation times, errors, etc.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • 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 Processor (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 to one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
  • Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:
  • a method for a user equipment (UE) configured to communicate with an integrated access backhaul (IAB) node comprising: receiving from the IAB node a message including a configuration for the UE to apply while in a non-connected state towards a radio access network (RAN) that includes the IAB node, wherein the configuration includes one or more of the following: a measurement configuration to be used while the UE is in the non-connected state, one or more indications of whether the UE should initiate cell reselection while in the non-connected state, and one or more relaxation and reselection conditions applicable while the UE is in the non-connected state in coverage of a cell provided by the IAB node; while in the non-connected state, determining that one or more criteria in the received configuration have been met; and based on determining that the one or more criteria in the configuration have been met, performing one or more of the following: relaxed measurements in the cell and/or in one or more neighbor cells, and cell reselection based on the relaxed measurements or non
  • the measurement configuration includes one or more of the following: at least one measurement requirement configuration that includes one or more requirements, conditions, and/or events for performing measurements for cell reselection; an indication of whether the measurement requirement configuration is valid while the UE is within coverage of the cell provided by the IAB node; an indication of whether the measurement requirement configuration is valid while the UE is physically co-located with the IAB node; a validity duration for the measurement configuration; a measurement identifier; identifiers of one or more frequencies, cells, or reference signals to be measured, identifiers of one or more cells provided by the IAB node; a request for the UE’s speed or velocity; a request for the UE’s location; and an indication that the cell provided by the IAB node is mobile.
  • each measurement requirement configuration includes one or more of the following: a unique identifier of the measurement requirement configuration; a validity duration for the measurement requirement configuration; a first duration (Tl), indicating how often the UE should perform measurements for cell reselection on each individual frequency or cell indicated in the measurement configuration; a second duration (T2), indicating how often the UE should perform measurements for cell reselection purposes on all frequencies or cells indicated in the measurement configuration; a subset of the frequencies or cells indicated in the measurement configuration, on which the UE should perform measurements for cell reselection; a first number of measurement samples (Nl) the UE should acquire for cell reselection on each individual frequency or cell indicated in the measurement configuration; a second number of measurement samples (N2) the UE should acquire for cell reselection on all frequencies or cells indicated in the measurement configuration; a third number of measurement samples (N3) the UE should acquire for cell (re)selection purposes on a subset of the frequencies or cells indicated in the measurement
  • the measurement configuration includes a plurality of measurement requirement configurations associated with a corresponding plurality of sets of applicability conditions, wherein each set of applicability conditions includes one or more of the following: whether the UE is connected to a mobile IAB node;
  • UE position relative to IAB node position whether UE speed or velocity is above a first threshold and below a second threshold; whether UE speed or velocity is above a third threshold; whether UE speed or velocity is below a fourth threshold; whether the UE’s measured signal strength for a cell is above a cell-specific signal strength threshold; and respective priorities of the measurement requirement configurations.
  • the one or more relaxation and reselection conditions include one or more of the following: an indication of whether the cell is mobile; a cell-specific signal strength threshold; a cell-specific camping time threshold; velocity or speed of the IAB node; one or more conditions for entering or remaining in relaxed measurement state for the cell and/or neighbor cells; one or more conditions for exiting or refraining from entering relaxed measurement state for the cell and/or neighbor cells; a list of neighbor cells and/or frequencies provided by other RAN nodes, on which the UE can perform relaxed measurements if the one or more conditions for entering relaxed measurement state are met; a list of cells and/or frequencies to which reselection is allowed so long as other relevant reselection conditions are met; and relative priority of the cells/frequencies to which reselection is allowed.
  • the one or more criteria include the one or more conditions for entering or remaining in relaxed measurement state, which include one or more of the following: difference between speed or velocity of the IAB node and speed or velocity of UE is less than a threshold; signal strength of the cell is greater than the cell-specific signal strength threshold; signal strength of the cell is static or quasi-static for at least a duration; the indication, which indicates that the cell is mobile; and the UE has camped in the cell or in another cell provided by the IAB node for at least the cell-specific camping time threshold.
  • any of embodiments A4-A6, wherein the one or more conditions for exiting or refraining from entering relaxed measurement state include one or more of the following: difference between speed or velocity of the IAB node and speed or velocity of UE is at least a threshold; difference between position of IAB node and position of UE is greater than a threshold for at least a duration; signal strength of the cell is not more than the cell-specific signal strength threshold; signal strength of the cell is static or quasi-static for at least a duration; the indication, which indicates that the cell is not mobile; and signal strength of a cell not provided by the IAB node is better than signal strength of the cell for at least a duration.
  • the one or more relaxation and reselection conditions include different first and second sets of cell reselection rules, with each set including at least one of the following: a list of cells and/or frequencies to which reselection is allowed so long as other relevant reselection conditions are met; and relative priority of the cells/frequencies to which reselection is allowed.
  • a method for an integrated access backhaul (IAB) node configured to provide a cell for user equipment (UEs) co-located with the IAB node in a vehicle, the method comprising: transmitting, in the cell, a message including a configuration for a receiving UE to apply while in a non-connected state towards a radio access network (RAN) that includes the IAB node, wherein the configuration includes one or more of the following: a measurement configuration to be used while the UE is in the non-connected state; one or more indications of whether the UE should initiate cell reselection while in the non-connected state, and one or more relaxation and reselection conditions applicable while the UE is in the non-connected state in coverage of a cell provided by the IAB node.
  • IAB integrated access backhaul
  • Bia The method of embodiment Bl, wherein the message is transmitted according to one of the following: as respective dedicated messages to one or more UEs in a connected state towards the RAN, and via broadcast in the cell.
  • the measurement configuration includes one or more of the following: at least one measurement requirement configuration that includes one or more requirements, conditions, and/or events for performing measurements for cell reselection; an indication of whether the measurement requirement configuration is valid while the UE is within coverage of the cell provided by the IAB node; an indication of whether the measurement requirement configuration is valid while the UE is physically co-located with the IAB node; a validity duration for the measurement configuration; a measurement identifier; identifiers of one or more frequencies, cells, or reference signals to be measured, identifiers of one or more cells provided by the IAB node; a request for the UE’s speed or velocity; a request for the UE’s location; and an indication that the cell provided by the IAB node is mobile.
  • each measurement requirement configuration includes one or more of the following: a unique identifier of the measurement requirement configuration; a validity duration for the measurement requirement configuration; a first duration (Tl), indicating how often the UE should perform measurements for cell reselection on each individual frequency or cell indicated in the measurement configuration; a second duration (T2), indicating how often the UE should perform measurements for cell reselection purposes on all frequencies or cells indicated in the measurement configuration; a subset of the frequencies or cells indicated in the measurement configuration, on which the UE should perform measurements for cell reselection; a first number of measurement samples (Nl) the UE should acquire for cell reselection on each individual frequency or cell indicated in the measurement configuration; a second number of measurement samples (N2) the UE should acquire for cell reselection on all frequencies or cells indicated in the measurement configuration; a third number of measurement samples (N3) the UE should acquire for cell (re)selection purposes on a subset of the frequencies or cells indicated in the measurement
  • the measurement configuration includes a plurality of measurement requirement configurations associated with a corresponding plurality of sets of applicability conditions, wherein each set of applicability conditions includes one or more of the following: whether the UE is connected to a mobile IAB node;
  • UE position relative to IAB node position whether UE speed or velocity is above a first threshold and below a second threshold; whether UE speed or velocity is above a third threshold; whether UE speed or velocity is below a fourth threshold; whether the UE’s measured signal strength for a cell is above a cell-specific signal strength threshold; and respective priorities of the measurement requirement configurations.
  • the one or more relaxation and reselection conditions include one or more of the following: an indication of whether the cell is mobile; a cell-specific signal strength threshold; a cell-specific camping time threshold; velocity or speed of the IAB node; one or more conditions for entering or remaining in relaxed measurement state for the cell and/or neighbor cells; one or more conditions for exiting or refraining from entering relaxed measurement state for the cell and/or neighbor cells; a list of neighbor cells and/or frequencies provided by other RAN nodes, on which the UE can perform relaxed measurements if the one or more conditions for entering relaxed measurement state are met; a list of cells and/or frequencies to which reselection is allowed so long as other relevant reselection conditions are met; and relative priority of the cells/frequencies to which reselection is allowed.
  • the one or more conditions for entering or remaining in relaxed measurement state include one or more of the following: difference between speed or velocity of the IAB node and speed or velocity of UE is less than a threshold; signal strength of the cell is greater than the cell-specific signal strength threshold; signal strength of the cell is static or quasi-static for at least a duration; the indication, which indicates that the cell is mobile; and the UE has camped in the cell or in another cell provided by the IAB node for at least the cell-specific camping time threshold.
  • any of embodiments B5-B6, wherein the one or more conditions for exiting or refraining from entering relaxed measurement state include one or more of the following: difference between speed or velocity of the IAB node and speed or velocity of UE is at least a threshold; difference between position of IAB node and position of UE is greater than a threshold for at least a duration; signal strength of the cell is not more than the cell-specific signal strength threshold; signal strength of the cell is static or quasi-static for at least a duration; the indication, which indicates that the cell is not mobile; and signal strength of a cell not provided by the IAB node is better than signal strength of the cell for at least a duration.
  • the one or more relaxation and reselection conditions include different first and second sets of cell reselection rules, with each set including at least one of the following: a list of cells and/or frequencies to which reselection is allowed so long as other relevant reselection conditions are met; and relative priority of the cells/frequencies to which reselection is allowed.
  • a user equipment (UE) configured to communicate with an integrated access backhaul (IAB) node, the UE comprising: communication interface circuitry configured to communicate with the IAB node; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments Al -Al 1.
  • IAB integrated access backhaul
  • a user equipment (UE) configured to communicate with an integrated access backhaul (IAB) node, the UE being further configured to perform operations corresponding to any of the methods of embodiments Al -Al l.
  • IAB integrated access backhaul
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to communicate with an integrated access backhaul (IAB) node, configure the UE to perform operations corresponding to any of the methods of embodiments Al -All.
  • UE user equipment
  • IAB integrated access backhaul
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to communicate with an integrated access backhaul (IAB) node, configure the UE to perform operations corresponding to any of the methods of embodiments Al -Al 1.
  • UE user equipment
  • IAB integrated access backhaul
  • An integrated access backhaul (IAB) node configured to provide a cell for user equipment (UEs) co-located with the IAB node in a vehicle, the IAB node comprising: communication interface circuitry and processing circuitry configured as a mobile terminal (IAB-MT) and a distributed unit (IAB-DU), wherein the processing circuitry and communication interface circuitry are further configured to perform operations corresponding to any of the methods of embodiments B1-B9.
  • IAB-MT mobile terminal
  • IAB-DU distributed unit
  • An integrated access backhaul (IAB) node configured to provide a cell for user equipment (UEs) co-located with the IAB node in a vehicle, the IAB node being further configured as a mobile terminal (IAB-MT) and a distributed unit (IAB-DU) and being further configured to perform operations corresponding to any of the methods of embodiments B1-B9.
  • IAB integrated access backhaul
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of an integrated access backhaul (IAB) node configured to provide a cell for user equipment (UEs) co-located with the IAB node in a vehicle, configure the IAB node to perform operations corresponding to any of the methods of embodiments B1-B9.
  • IAB integrated access backhaul
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of an integrated access backhaul (IAB) node configured to provide a cell for user equipment (UEs) co-located with the IAB node in a vehicle, configure the IAB node to perform operations corresponding to any of the methods of embodiments B1-B9.
  • IAB integrated access backhaul

Landscapes

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

Abstract

Des modes de réalisation comprennent des procédés pour un équipement utilisateur (UE) configuré pour communiquer avec des nœuds de liaison terrestre et d'accès intégré (IAB) dans un réseau d'accès radio (RAN). De tels procédés consistent à recevoir d'un nœud IAB une configuration pour l'UE pour une application lorsqu'il se trouve dans un état non connecté vers le RAN. La configuration comprend une configuration de mesure à utiliser tandis que l'UE est dans l'état non connecté, une ou plusieurs indications indiquant si l'UE doit initier une resélection de cellule tout en étant dans l'état non connecté et/ou une ou plusieurs conditions de relaxation et de resélection applicables pendant que l'UE est dans l'état non connecté. De tels procédés comprennent, tout en étant dans l'état non connecté, la réalisation sélective d'un ou de plusieurs des éléments suivants sur la base du fait qu'un ou plusieurs critères dans la configuration reçue ont été satisfaits : des mesures relâchées dans la cellule et/ou dans une ou plusieurs cellules voisines et une resélection de cellule. D'autres modes de réalisation comprennent des procédés complémentaires pour un nœud IAB.
PCT/SE2023/050754 2022-08-09 2023-07-25 Ue non connecté desservi par un iab sur le même véhicule WO2024035296A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263396453P 2022-08-09 2022-08-09
US63/396,453 2022-08-09

Publications (1)

Publication Number Publication Date
WO2024035296A1 true WO2024035296A1 (fr) 2024-02-15

Family

ID=87554694

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050754 WO2024035296A1 (fr) 2022-08-09 2023-07-25 Ue non connecté desservi par un iab sur le même véhicule

Country Status (1)

Country Link
WO (1) WO2024035296A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200022054A1 (en) * 2018-07-11 2020-01-16 Lg Electronics Inc. Method and apparatus for supporting fast link recovery and link status reporting in wireless communication system
US20200275340A1 (en) * 2019-02-26 2020-08-27 Lg Electronics Inc. Relaxation of mobility condition based on serving cell quality
WO2021230648A1 (fr) * 2020-05-13 2021-11-18 엘지전자 주식회사 Procédé pour mettre en oeuvre des mesures de resélection de cellule
US20220046485A1 (en) * 2020-08-05 2022-02-10 Lg Electronics Inc. Method and apparatus for triggering reselection for relay
WO2022079296A2 (fr) * 2020-10-16 2022-04-21 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Défaillance de lien iab

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200022054A1 (en) * 2018-07-11 2020-01-16 Lg Electronics Inc. Method and apparatus for supporting fast link recovery and link status reporting in wireless communication system
US20200275340A1 (en) * 2019-02-26 2020-08-27 Lg Electronics Inc. Relaxation of mobility condition based on serving cell quality
WO2021230648A1 (fr) * 2020-05-13 2021-11-18 엘지전자 주식회사 Procédé pour mettre en oeuvre des mesures de resélection de cellule
US20230180079A1 (en) * 2020-05-13 2023-06-08 Lg Electronics Inc. Method for performing measurements for cell reselection
US20220046485A1 (en) * 2020-08-05 2022-02-10 Lg Electronics Inc. Method and apparatus for triggering reselection for relay
WO2022079296A2 (fr) * 2020-10-16 2022-04-21 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Défaillance de lien iab

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
3GPP TR 38.806
3GPP TR 38.874
3GPP TS 29.281
3GPP TS 38.304
3GPP TS 38.425
3GPP TS 38.463

Similar Documents

Publication Publication Date Title
US20240129704A1 (en) Public Warning System (PWS) Reception by Aerial User Equipment (UE)
WO2023113674A1 (fr) Fonctionnement d'équipement utilisateur (ue) avec configuration d'économie d'énergie de station de base
WO2024035296A1 (fr) Ue non connecté desservi par un iab sur le même véhicule
US20240172074A1 (en) Handling of User Equipment (UE) Context Information after Inter-System Handover
US20240187953A1 (en) Handling Configurations in Source Integrated Access Backhaul (IAB) Donor during Temporary Topology Adaptations
WO2024005700A1 (fr) Configuration de candidats de mobilité inter-du l1/l2
WO2024033396A1 (fr) Signalisation pour la prise en charge d'accès intégré mobile et de liaison terrestre
WO2023027619A1 (fr) Gestion de mesures de couche d'application configurées pendant un transfert intercellulaire
WO2023249534A1 (fr) Gestion de reconfigurations conditionnelles après exécution, par un équipement utilisateur (ue), d'une procédure de mobilité
WO2023001491A1 (fr) Indication de préférence de libération persistante de transfert
WO2024035293A1 (fr) Sélection d'équipement utilisateur (ue) de cellules candidates à mesurer pour une mobilité inter-cellules l1/l2
WO2024038116A1 (fr) Signalisation d'informations de réalité étendue
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2023075657A1 (fr) Gestion d'une configuration de rapport de transfert intercellulaire (shr) réussie au niveau d'un équipement utilisateur (ue) et d'un réseau
WO2023022645A1 (fr) Gestion de mesures de couche d'application configurées en réponse à un message d'établissement de connexion
WO2023014258A1 (fr) Prédiction et gestion proactive de défaillances de liaison radio (rlf)
WO2024035287A1 (fr) Évitement de situations de concurrence entre mobilité l1/l2 et l3
WO2022264090A1 (fr) Journalisation et notification d'informations spécifiques à un équipement utilisateur aérien
WO2023287337A1 (fr) Contrôle d'accès pour double connectivité
WO2024125813A1 (fr) Systèmes et procédés par un nœud de réseau de gestion pour réduire la probabilité d'utilisation conflictuelle de ressources par des équipements utilisateur
WO2024033272A1 (fr) Extension cag pour nœud iab mobile
EP4360369A1 (fr) Configuration de décalages de cadencement dans des réseaux d'accès et de raccordement intégrés (iab) avec de multiples modes de cadencement disponibles
WO2023239272A1 (fr) Reconfiguration conditionnelle impliquant de multiples nœuds de réseau
WO2024072274A1 (fr) Gestion d'ue en veille-inactifs pendant un transfert intercellulaire avec iab mobile
WO2024005702A1 (fr) Mesures de couche radio et de couche application alignées dans le temps pour connectivité double

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

Country of ref document: EP

Kind code of ref document: A1