WO2024033396A1 - Signalisation pour la prise en charge d'accès intégré mobile et de liaison terrestre - Google Patents

Signalisation pour la prise en charge d'accès intégré mobile et de liaison terrestre Download PDF

Info

Publication number
WO2024033396A1
WO2024033396A1 PCT/EP2023/072000 EP2023072000W WO2024033396A1 WO 2024033396 A1 WO2024033396 A1 WO 2024033396A1 EP 2023072000 W EP2023072000 W EP 2023072000W WO 2024033396 A1 WO2024033396 A1 WO 2024033396A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
iab
mobile
information
mobile iab
Prior art date
Application number
PCT/EP2023/072000
Other languages
English (en)
Inventor
Antonino ORSINO
Ritesh SHREEVASTAV
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 WO2024033396A1 publication Critical patent/WO2024033396A1/fr

Links

Classifications

    • 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
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for signalling for support of mobile Integrated Access and Backhaul (IAB) functionalities.
  • IAB Integrated Access and Backhaul
  • BACKGROUND Fifth Generation (5G) networks are being designed and deployed to simultaneously serve more User Equipment (UEs) with higher throughput and lower delay especially within dense deployments of small cells.
  • UEs User Equipment
  • building a completely new infrastructure from scratch is costly and takes time.
  • Deploying a wireless backhaul is envisioned to be an economically and technically viable approach to enable flexible and dense network.
  • IAB Integrated Access and Backhaul
  • NG-RAN Next Generation-Radio Access Network
  • IAB is based on the Centralized Unit-Distributed Unit (CU-DU) split that was standardized in Release 15.
  • the Centralized Unit (CU) is in charge of the radio resource control (RRC) and the packet data convergence (PCDP) protocol, whereas the Distributed Unit (DU) is in charge of the radio link control (RLC) and multiple access control (MAC).
  • RRC radio resource control
  • PCDP packet data convergence
  • DU Radio link control
  • MAC multiple access control
  • the F1 interface connects the CU and the DU.
  • FIGURE 1 illustrates the basic architecture of IAB.
  • the basic architecture depicted in FIGURE 1 consists of a single IAB donor connected to the core network.
  • the IAB donor serves three direct IAB child nodes through two collocated DUs at the donor for wireless backhauling.
  • the center IAB node in turn serves two IAB nodes through wireless backhaul. All IAB nodes in FIGURE 1 handle backhaul traffic both related to the UEs connected to it from downstream IAB nodes.
  • IAB Node A node that allows access to the UEs while also backhauling the traffic to other nodes.
  • the IAB node consists of a DU that provides access to connected UEs.
  • the node also consists of a mobile termination (MT) that connects to other IAB nodes or donors in the uplink (UL) direction for backhaul.
  • IAB Donor A node that provides UEs an interface to the core network and wireless functionality to other IAB-nodes to backhaul their traffic to the core network.
  • the defining feature of IAB is the use of wireless spectrum for both access of UEs and backhauling of data through IAB donors.
  • IAB In Release 16, IAB was standardized with basic support for multi-hop multi-path backhaul for directed acyclic graph (DAG) topology; no mesh-based topology was supported. Release 16 also supports Quality of Service (QoS) prioritization of backhaul traffic and flexible resource usage between access and backhaul.
  • QoS Quality of Service
  • Current discussions in Release 17 are on topology enhancements for IAB with partial migration of IAB nodes for Radio Link Failure (RLF) recovery and load balancing. The following sources may be referred to for further information about already standardized IAB work: ⁇ Madapatha, Charitha et al.
  • One of the main use cases of mobile IAB cell is to serve the UEs residing in the vehicle with the vehicle mounted relay.
  • Other relevant use cases for mobile IABs involve a mobile/nomadic IAB network node mounted on a vehicle to provide extended coverage. This involves scenarios where additional coverage is required during special events like concerts and during disasters.
  • the nomadic IAB node provides access to surrounding UEs while the backhaul traffic from the nomadic IAB node is then wirelessly with the help of IAB donors or Non-terrestrial networks (NTN).
  • NTN Non-terrestrial networks
  • a nomadic IAB node also reduces or even eliminates signal strength loss due to vehicle penetration for UEs that are present in the vehicles.
  • F1 interface The F1 interface connects the CU to the DU in the split architecture of the IAB architecture.
  • the F1 interface connects the CU from an IAB donor to IAB DU in the child IAB nodes.
  • the F1 interface also supports control and user plane separation through F1-C and F1-U respectively. This interface holds even during IAB mobility where an IAB node moves and connects to parent/donor IAB nodes. In such a scenario, the DU present in the mobile IAB node connects to the CU present in the IAB donor.
  • the IAB-DU initiates a F1 setup with the IAB-CU with which it has a Transport Network Layer (TNL) connection.
  • the initial F1 setup is described in section 8.5 of 3GPP TS 38.401.
  • the IAB donor CU optionally sends a GNB-CU CONFIGURATION UPDATE to indicate the DU cells to be activated.
  • Mobile IAB In most use cases, it is expected that the mobile IAB will be mounted on public transport vehicles and, to a large extent, moved in a pre-determined route. For example, FIGURE 2 illustrates a mobile IAB mounted on a bus travelling on a route that is covered by four different stationary parent IAB nodes (parents 1, 2, 3, and 4).
  • the parent nodes backhaul their traffic through two donor nodes (donor X and Y).
  • An IAB node has a DU that provides access to UEs around it and an MT that provides a backhaul connection of the IAB node to its parent(s) and the rest of the network.
  • the parent IAB nodes consist of DUs that provide access to UEs and the mobile IAB present in their coverage. They also consist of MTs that backhaul its traffic together with traffic from the mobile IAB node.
  • the two donor nodes consist of DU that provides access and CU that is connected to the core network. The CUs in both donor nodes maintain a F1 connection to parent nodes under it.
  • the mobile IAB architectures involves Intra-Donor, Inter-Donor (same CU) and Inter-CUs.
  • the mobile IAB node maintains an connection to the donor (one donor at a time).
  • the mobile IAB connects to the following nodes in the different positions as described below: 1) Position A: BH through parent node 1, F1 connection to donor node X 2) Position B: BH through parent node 2, F1 connection to donor node X 3) Position C: BH through parent node 3, F1 connection to donor node Y 4) Position D: BH through parent node 4, F1 connection to donor node Y
  • the mobile IAB must change the F1 connection from donor X to donor Y when moving from position B to C, thus requiring a F1 handover and setup of backhaul Radio Link Control (RLC) channels.
  • RLC Radio Link Control
  • WI new work item
  • NR mobile IAB NR mobile IAB
  • ⁇ Provide enhancements for mobility of an IAB-node, together with its served UEs, including aspects related to group mobility. No optimizations for the targeting of surrounding UEs. [RAN3, RAN2] ⁇ Mitigation of interference due to IAB-node mobility, including the avoidance of potential reference and control signal collisions (e.g.
  • this new IAB node is not a “static” IAB node as was specified in Release 16 and Release 17. Rather, the new IAB node is “mobile”. This implies that mobility procedures need to be taken into account and that this network node is a “new type” of IAB node. As such, an old network node may not be able to provide a configuration in order to configure a mobile IAB. Additionally, a legacy IAB configuration may not be enough for supporting and configuring mobile IAB functionalities on the mobile IAB node. SUMMARY Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
  • a method by a first node for supporting for mobile IAB functionalities includes transmitting, to a second node, a message indicating that the first node supports at least one mobile IAB functionality.
  • a first node for supporting for mobile IAB functionalities includes processing circuitry configured to transmit, to a second node, a message indicating that the first node supports at least one mobile IAB functionality.
  • a method by a second node for supporting mobile IAB functionalities includes receiving, from a first node, a message indicating that the first node supports at least one mobile IAB functionality.
  • a second node for supporting for mobile IAB functionalities includes processing circuitry configured to receive, from a first node, a message indicating that the first node supports at least one mobile IAB functionality.
  • certain embodiments may provide a technical advantage of facilitating admission control decisions. For example, once the CU knows that it is a mobile IAB MT that needs connectivity, the CU may perform additional admission control checks and subsequently may accept or redirect the mobile IAB MT to a different cell or carrier. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.
  • FIGURE 1 illustrates the basic architecture of IAB
  • FIGURE 2 illustrates a mobile IAB architectures involving Intra-Donor, Inter-Donor (same CU) and Inter-CUs
  • FIGURE 3 illustrates an overview of the system structure, according to certain embodiments
  • FIGURE 4 illustrates an example method by a first node such as, for example, a UE (e.g., mIAB-MT), according to certain embodiments
  • FIGURE 5 illustrates a sequence diagram of one example where a network node transmits, to a UE (e.g., mIAB-MT), a message to indicate support for mobile IAB functionalities, according to certain embodiments
  • FIGURE 6 illustrates an example method performed by a UE (e.g., mIAB-MT) that includes the UE receiving, from a second node
  • node can be a network node or a UE.
  • NodeB NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g.
  • a node in a gNB, Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E- SMLC), etc.
  • UE user equipment
  • UE user equipment
  • UE user equipment
  • Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.
  • D2D device to device
  • V2V vehicular to vehicular
  • MTC UE machine type UE
  • MTC UE machine type UE
  • M2M machine to machine
  • PDA Personal Digital Assistant
  • Tablet mobile terminals
  • smart phone laptop embedded equipment
  • LME laptop mounted equipment
  • USB Unified Serial Bus
  • Network node may comprise base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), etc.
  • eNB evolved Node B
  • gNodeB gNodeB
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • Central Unit e.g. in a gNB
  • Distributed Unit e.g. in a gNB
  • Baseband Unit Centralized Baseband
  • C-RAN C-RAN
  • AP access point
  • the term radio access technology may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc.
  • UTRA Universal Terrestrial Radio Access Network
  • E-UTRA Evolved Universal Terrestrial Radio Access Network
  • NB-IoT narrow band internet of things
  • WiFi next generation RAT
  • NR next generation RAT
  • NR next generation RAT
  • 4G 4G
  • 5G 5G
  • the scenario targeted includes a mobile IAB node that is mounted in a vehicle (in the inside or outside part of it) and one or several UEs that should connect to the mobile IAB only when located inside the vehicle (e.g., a bus).
  • the terms “m-IAB”, “mobile IAB” and “m-IAB node” are used interchangeably.
  • the terminology “UE connected to a mobile IAB” is used to characterize a UE that is physically inside the vehicle in which the mobile IAB node is mounted.
  • the UE speed can be expressed in terms of distance per unit time (e.g., Y1 km/hour) and/or in Doppler frequency (e.g., Y2 Hertz).
  • the “UE velocity” is UE speed along the direction of movement (e.g., North, South, East, West).
  • FIGURE 3 illustrates an overview of the system structure 100, according to certain embodiments.
  • FIGURE 3 illustrates the main entities.
  • the mIAB-MT 115 is a UE, which is a wireless terminal, such as a wireless module within the mobile IAB node 110.
  • the IAB node 110 also includes mIAB-DU 120.
  • the mIAB-MT 115 is connected to a network node 105, which is sometimes known as the (serving) base station, (serving) gNB, or (serving) eNB.
  • first node such as, for example, the UE (or in a particular case, the mobile IAB-MT 115) to indicate, to a second node such as, for example, a network node 105, support for mobile IAB functionalities.
  • FIGURE 4 illustrates an example method 300 performed by a first node such as, for example, a UE (e.g., mIAB-MT 115) that includes a step 302 in which the UE transmits, to a network node 105, a message to indicate support for mobile IAB functionalities.
  • a first node such as, for example, a UE (e.g., mIAB-MT 115) that includes a step 302 in which the UE transmits, to a network node 105, a message to indicate support for mobile IAB functionalities.
  • the mobile IAB functionalities comprise an indication that the UE is a mobile IAB-MT 115 of a mobile IAB node 110.
  • additional information may also be provided by mobile IAB-MT such as the current speed and expected duration for which the service is needed from the cell (e.g., how long the mobile IAB may stay camped/connected in a cell (belonging to static parent IAB node or gNB).
  • additional information that is provided may include current UL and downlink (DL) throughput measured by IAB-MT 115 and IAB-DU 120 and/or total upstream and downstream traffic volume
  • a method at a first node such as, for example, a UE (e.g., a mIAB-MT 115), is provided and includes the mIAB-MT 115 indicating support for mobile IAB functionalities by including a field within a message, which may further include at least one of: a. indication that this UE is an mIAB-MT 115; b. indication for configuration of mobile IAB functionalities; c.
  • RANs Radio Access Networks
  • LTE Long Term Evolution
  • UE capabilities e.g., per UE, per band, per band combination, per feature set, per feature set per CC
  • UE capability information message which may also include segmented UE capabilities and/or capabilities defined by a UE capability identifier (ID)
  • ID UE capability identifier
  • j duration for how long the service is needed when accessing via a parent IAB node/cell
  • k the speed at which the mobile IAB node 110 is moving
  • l total volume of DL and UL data that it is carrying.
  • a second node such as, for example, a network node 105 to receive, from a first node such as, for example, a UE (e.g., the mobile IAB-MT 115), indication of support for mobile IAB functionalities.
  • the method may include receiving, from the UE (e.g., the mobile IAB-MT 115), a message, to indicate support for mobile IAB functionalities.
  • the mobile IAB functionalities comprise an indication that the UE is a mobile IAB-MT 115 of a mobile IAB node 110.
  • additional information may also be mobile IAB-MT 110 such as the current speed and expected duration for which the service is needed from the cell (e.g., how long the mobile IAB may stay camped/connected in a cell (belonging to static parent IAB node or gNB).
  • additional information may include current UL and DL throughput measured by IAB-MT 115 and IAB-DU 120, total upstream and downstream traffic volume.
  • such additional information may be regarded as UE Assistance Information, which the UE may be requested by a network node such as CU to provide.
  • the UE may provide such information such as, for example, using Information Elements (IEs) by extending a UEAssistanceInformation message.
  • IEs Information Elements
  • a method at or by the second node such as, for example, a network node includes the second node receiving an indication of first node such as, for example, a UE (i.e., the mIAB-MT 115), support for network mobile IAB functionalities in a field within a message.
  • the information may include a message defined as UE capability information message, which may include segmented UE capabilities and/or capabilities defined by a UE capability ID.
  • the message is received from a UE (i.e., the mIAB- MT 115).
  • the message is received from another node such as, for example, a core network node, a master node, secondary node or standalone node.
  • the message indicates a duration for how long the service is needed when accessing via a parent IAB node/cell.
  • the message indicates a speed at which the mobile IAB node 110 is moving.
  • the message indicates a total volume of DL and UL data that it is carrying.
  • the method by the second node 105 may further include at least one of: a. retrieving the support that this UE is an mIAB-MT 115; b. retrieving the mIAB support for receiving a configuration of mobile IAB functionalities; c. retrieving support of number of UEs that can be served with the mobile IAB node d. deriving the support for functionalities via different fields for multiple frequency ranges (e.g., FR1, FR2, and FR2-2); e. deriving the support for mobile IAB functionalities via different fields for multiple band or band combinations; f.
  • UE capabilities e.g., per UE, per band, per band combination, per feature set, and per feature set per CC.
  • a method is provided for a second node such as, for example, a network node 105 to indicate, to a first node such as, for example, a UE (e.g., the mobile IAB-MT 115), support for mobile IAB functionalities.
  • FIGURE 5 illustrates a sequence diagram 300 of one example where a network node 105 transmits, to the mIAB-MT 110, a message to indicate support for mobile IAB functionalities.
  • the mobile IAB functionalities comprise an indication that the network node 105 is able to provide a configuration for a mobile IAB 110.
  • the network node 105 may configure different parameters and criteria for cells supporting mobile IAB traffic such as mobile IAB-MT may only be allowed to access the cell if one or more of: speed is below certain threshold; RSRP is above certain threshold; data volume requirement is below certain threshold; and/or the duration of connection needed via parent IAB node/serving cell is within certain time (e.g., max 5 minutes).
  • the information is provided by System Information (SI), which may be broadcast as SIB1 or IAB specific SIB, for example.
  • SIB1 System Information
  • IAB specific SIB for example.
  • the information may be provided via dedicated signaling and the mobile IAB node 110 is expected to store such information and (re)use it when accessing.
  • a method at or by the network node 105 includes the network indicating support for configuring mobile IAB functionalities by including an indication, which may include at least one of: a. an indication in a new or existing RRC messages such as, for example, an RRCReconfiguration message, an RRCResume message, an RRCSetup message, or an RRCRelease message; b. an indication where the indication is included in a system information block (SIB); c.
  • SIB system information block
  • a method is provided for a first node such as, for example, a UE (e.g., the mobile IAB-MT 115) to receive, from a second node such as, for example, a network node 105, indication of support for mobile IAB functionalities.
  • a first node such as, for example, a UE (e.g., the mobile IAB-MT 115) to receive, from a second node such as, for example, a network node 105, indication of support for mobile IAB functionalities.
  • FIGURE 6 illustrates an example method 400 performed by a UE (e.g., mIAB-MT 115) that includes a step 402 where the UE receives, from a second node such as, for example, a network node 105, a message, to indicate support for mobile IAB functionalities.
  • the mobile IAB functionalities include an indication that the network is able to support a mobile IAB 110 and, thus, in a particular embodiment, to provide a configuration for a mobile IAB 110.
  • the method may include the first node receiving, from the second node, a message indicating the criteria to be able to access a cell.
  • the message may configure different parameters and criteria for cells supporting mobile IAB traffic such as, for example, the mobile IAB-MT 115 may only be allowed to access the cell if one or more of: speed is below certain threshold; RSRP is above certain threshold; data volume requirement is below certain threshold; and/or the duration of connection needed in this parent IAB node/serving cell is within certain time (e.g., max 5 minutes).
  • the message may for example be an RRC message, such as a SI message, SIB, or an RRC Release message.
  • a method at or by a UE includes receiving an indication of a network node for support for configuring mobile IAB functionalities. For example, in a field within a message.
  • the method may further include retrieving support of mobile IAB functionalities for a mobile IAB node 110.
  • the message may be received from or via another node (e.g., core network, a master node, secondary node, or standalone node).
  • a UE may provide capability information, according to certain embodiments.
  • FIGURE 7 illustrates an example sequence diagram 500 of one example that includes a step 502 where the mIAB-MT 115 transmits, to the network node 105, a UE capability information message to indicate its support for mobile IAB functionalities.
  • 3GPP Specification Implementation A first example implementation of one embodiment for modifying 3GPP TS 38.331 v17.1.0 is provided below.
  • the UE Capability Information message is enhanced to indicate UE (e.g., mIAB-MT) support for mobile IAB functionalities. Additions to the specification is marked with underline.
  • the UE capability is added in the UE-NR-Capability IE indicating support for mobile IAB functionalities.
  • UE-NR-Capability :: SEQUENCE ⁇ accessStratumRelease AccessStratumRelease, pdcp-Parameters PDCP-Parameters, rlc-Parameters RLC-Parameters OPTIONAL, mac-Parameters MAC-Parameters OPTIONAL, phy-Parameters Phy-Parameters, rf-Parameters RF-Parameters, measAndMobParameters MeasAndMobParameters OPTIONAL, fdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode OPTIONAL, tdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX
  • SIB1 is enhanced to indicate network support for mobile IAB functionalities. Additions to the specification is marked with underline.
  • SIB1 message -- ASN1START -- TAG-SIB1-START SIB1 :: SEQUENCE ⁇ cellSelectionInfo SEQUENCE ⁇ q-RxLevMin Q-RxLevMin, q-RxLevMinOffset INTEGER (1..8) OPTIONAL, -- Need S q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R q-QualMin Q-QualMin OPTIONAL, -- Need S q-QualMinOffset INTEGER (1..8) OPTIONAL -- Need S ⁇ OPTIONAL, -- Cond Standalone cellAccessRelatedInfo CellAccessRelatedInfo, connEstFailureControl ConnEstFailureControl OPTIONAL, -- Need R si-SchedulingInfo SI-SchedulingInfo OPTIONAL, -- Need R servingCellConfigCommon
  • the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a RAN, and a core network 606, which includes one or more core network nodes 608.
  • the access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • the network nodes 610 facilitate direct or indirect connection of UE, such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 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.
  • the communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 600 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 612 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 610 and other communication devices.
  • the network nodes 610 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 612 and/or with other network nodes or equipment in the telecommunication network 602 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 602.
  • the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. These connections may be direct or indirect via one or more intermediary networks or devices.
  • the core network 606 includes one more core network nodes (e.g., core network node 608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 608.
  • 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).
  • the host 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and/or the telecommunication network 602, and may be operated by the service provider or on behalf of the service provider.
  • the host 616 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.
  • data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 600 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, 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
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • the telecommunication network 602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, the telecommunications network 602 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 IoT services to yet further UEs. In some examples, the UEs 612 are configured to transmit and/or receive information without direct human interaction.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 612 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604.
  • 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
  • the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and/or 612d) and network nodes (e.g., network node 610b).
  • the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 614 may be a broadband router enabling access to the core network 606 for the UEs.
  • the hub 614 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 610, or by executable code, script, process, or other instructions in the hub 614.
  • the hub 614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 614 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 614 may have a or intermittent connection to the network node 610b.
  • the hub 614 may also allow for a different communication scheme and/or schedule between the hub 614 and UEs (e.g., UE 612c and/or 612d), and between the hub 614 and the core network 606.
  • the hub 614 is connected to the core network 606 and/or one or more UEs via a wired connection.
  • the hub 614 may be configured to connect to an M2M service provider over the access network 604 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection.
  • the hub 614 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 610b.
  • the hub 614 may be a non- dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIGURE 9 shows a UE 700, in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over 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.
  • VoIP voice over IP
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • 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).
  • 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 to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 700 includes processing 702 that is operatively coupled via a bus 704 to an input/output interface 706, a power source 708, a memory 710, a communication interface 712, 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.
  • certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 710.
  • the processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 702 may include multiple central processing units (CPUs).
  • the input/output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 700.
  • 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.
  • a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • the power source 708 is structured as a battery or battery pack.
  • Other types of power sources such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 708 may further include power circuitry for delivering power from the power source 708 itself, and/or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for for charging of the power source 708.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.
  • the memory 710 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.
  • the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716.
  • the memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.
  • the memory 710 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.’
  • the memory 710 may allow the UE 700 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.
  • the processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712.
  • the communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722.
  • the communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 718 and/or a receiver 720 appropriate to provide network communications (e.g., electrical, frequency allocations, and so forth).
  • the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 712 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.
  • GPS global positioning system
  • 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/internet 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 712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input 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 (IoT) 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.
  • IoT Internet of Things
  • Non-limiting examples of such an IoT 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 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- tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • UAV Unmanned Ae
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 700 shown in FIGURE 9.
  • 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.
  • 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 800 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • Base stations may be categorized 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. 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)), 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-SMLCs)
  • the network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808.
  • the network node 800 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.
  • the network node 800 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.
  • the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs).
  • the network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, 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 800.
  • RFID Radio Frequency Identification
  • the processing circuitry 802 may 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 800 components, such as the memory 804, to provide network node 800 functionality.
  • the processing circuitry 802 includes a system on a chip (SOC).
  • the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 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 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.
  • the memory 804 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 the processing circuitry 802.
  • 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-
  • the memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800.
  • the memory 804 may be used to store any calculations made by the processing circuitry 802 and/or any data received via the communication interface 806.
  • the processing circuitry 802 and memory 804 is integrated.
  • the communication interface 806 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 806 comprises port(s)/terminal(s) 816 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 806 also includes radio front- end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810.
  • Radio front-end circuitry 818 comprises filters 820 and amplifiers 822.
  • the radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802.
  • the radio front- end circuitry may be configured to communicated between antenna 810 and processing circuitry 802.
  • the radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and/or amplifiers 822.
  • the radio signal may then be transmitted via the antenna 810.
  • the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818.
  • the digital data may be passed to the processing circuitry 802.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810.
  • all or some of the RF transceiver circuitry 812 is part of the communication interface 806.
  • the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).
  • the antenna 810 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.
  • the antenna 810, communication interface 806, and/or the processing circuitry 802 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, the antenna 810, the communication interface 806, and/or the processing circuitry 802 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.
  • the power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein.
  • the network node 800 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 the power source 808.
  • the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 800 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.
  • the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.
  • FIGURE 11 is a block diagram of a host 900, which may be an embodiment of the host 616 of FIGURE 8, in accordance with various aspects described herein.
  • the host 900 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.
  • the host 900 may provide one or more services to one or more UEs.
  • the host 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a network interface 908, a power source 910, and a memory 912.
  • 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 7 and 8, such that the descriptions thereof are generally applicable to the corresponding components of host 900.
  • the memory 912 may include one or more computer programs including one or more host application programs 914 and data 916, which may include user data, e.g., data generated by a UE for the host 900 or data generated by the host 900 for a UE.
  • Embodiments of the host 900 may utilize only a subset or all of the components shown.
  • the host application programs 914 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 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).
  • the host application programs 914 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.
  • the host 900 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 914 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.
  • FIGURE 12 is a block diagram illustrating a virtualization environment 1000 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 1000 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
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Hardware 1004 includes processing circuitry, memory that stores software and/or instructions 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 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1006 may present a operating platform that appears like networking hardware to the VMs 1008.
  • the VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, and the implementations may be made in different ways.
  • NFV network function virtualization
  • 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.
  • a VM 1008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1008, and that part of hardware 1004 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 1008 on top of the hardware 1004 and corresponds to the application 1002.
  • Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 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 1010, which, among others, oversees lifecycle management of applications 1002.
  • hardware 1004 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 1012 which may alternatively be used for communication between hardware nodes and radio units.
  • FIGURE 13 shows a communication diagram of a host 1102 communicating via a network node 1104 with a UE 1106 over a partially wireless connection in accordance with some embodiments.
  • UE such as a UE 612a of FIGURE 8 and/or UE 700 of FIGURE 9
  • network node such as network node 610a of FIGURE 8 and/or network node 800 of FIGURE 10
  • host such as host 616 of FIGURE 8 and/or host 900 of FIGURE 11
  • embodiments of host 1102 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1102 also includes software, which is stored in or accessible by the host 1102 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 the UE 1106 connecting via an over-the-top (OTT) connection 1150 extending between the UE 1106 and host 1102.
  • a host application may provide user data which is transmitted using the OTT connection 1150.
  • the network node 1104 includes hardware enabling it to communicate with the host 1102 and UE 1106.
  • the connection 1160 may be direct or pass through a core network (like core network 606 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.
  • the UE 1106 includes hardware and software, which is stored in or accessible by UE 1106 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 1106 with the support of the host 1102.
  • 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 1106 with the support of the host 1102.
  • an executing host application may communicate with the executing client application via the OTT connection 1150 terminating at the UE 1106 and host 1102.
  • 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.
  • the OTT connection 1150 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1150.
  • the OTT connection 1150 may extend via a connection 1160 between the host 1102 and the network node 1104 and via a wireless connection 1170 between the network node 1104 and the UE 1106 to provide the connection between the host 1102 and the UE 1106.
  • the connection 1160 and wireless connection 1170, over which the OTT connection 1150 may be provided, have been drawn abstractly to illustrate the communication between the host 1102 and the UE 1106 via the network node 1104, without explicit to any intermediary devices and the precise routing of messages via these devices.
  • the host 1102 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1106.
  • the user data is associated with a UE 1106 that shares data with the host 1102 without explicit human interaction.
  • the host 1102 initiates a transmission carrying the user data towards the UE 1106.
  • the host 1102 may initiate the transmission responsive to a request transmitted by the UE 1106.
  • the request may be caused by human interaction with the UE 1106 or by operation of the client application executing on the UE 1106.
  • the transmission may pass via the network node 1104, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1112, the network node 1104 transmits to the UE 1106 the user data that was carried in the transmission that the host 1102 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1114, the UE 1106 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1106 associated with the host application executed by the host 1102. In some examples, the UE 1106 executes a client application which provides user data to the host 1102. The user data may be provided in reaction or response to the data received from the host 1102.
  • the UE 1106 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1106. Regardless of the specific manner in which the user data was provided, the UE 1106 initiates, in step 1118, transmission of the user data towards the host 1102 via the network node 1104.
  • the network node 1104 receives user data from the UE 1106 and initiates transmission of the received user data towards the host 1102.
  • the host 1102 receives the user data carried in the transmission initiated by the UE 1106.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1106 using the OTT connection 1150, in which the wireless connection 1170 forms the last segment. More precisely, the teachings of these embodiments may improve one or more of, for example, data rate, latency, and/or power consumption and, thereby, provide benefits such as, for example, reduced user waiting relaxed restriction on file size, improved content resolution, better responsiveness, and/or extended battery lifetime.
  • factory status information may be collected and analyzed by the host 1102.
  • the host 1102 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1102 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1102 may store surveillance video uploaded by a UE.
  • the host 1102 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1102 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 the host 1102 and/or UE 1106.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1150 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 the OTT connection 1150 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1104.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1102.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1150 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • FIGURE 14 illustrates a method 1200 by first node 105, 110 for supporting for mobile IAB functionalities, according to certain embodiments.
  • the method includes the first node 105, 110 transmitting, to a second node 110, 105, a message indicating that the first node supports at least one mobile IAB functionality, at step 1202.
  • the second node is an IAB node that is a parent to the second node and the first node is a mobile IAB-MT.
  • the information indicates that the first node is the UE, that is the mobile IAB-MT.
  • the information comprises at least one of: a speed of the first node; and a location of the first node.
  • the information comprises at least one of: a UE capability identifier; at least one segmented UE capability; an expected time duration for which a service is needed from a cell; a current UL and/or DL throughput; and a total upstream and/or downstream traffic volume.
  • the information comprises at least one of: an indication of a number of UEs that can be served by the mobile IAB node; an indication that the first node supports a configuration of the at least one IAB functionality; at least one indication that indicates support for the at least one mobile IAB functionality in an associated one of a plurality of frequency ranges; at least one indication that indicates support for the at least one mobile IAB functionality in an associated one of a plurality of bands; at least one indication that indicates support for the at least one mobile IAB functionality in an associated one of a plurality of RANs or RATs; and at least one indication that indicates support for the at least one mobile IAB functionality for an associated one of a plurality of types of mobility and/or vehicles.
  • the information comprises assistance information and the information is transmitted in a UEAssistanceInformation message.
  • the firsts node receives, from the second node, a request for the information.
  • the first node is an IAB node that is a parent to the second node, and the second node is a mobile IAB-MT.
  • the message includes capability information indicating that the first node supports a mobile IAB.
  • the message includes at least one parameter and/or at least one criteria for at least one cell supporting mobile IAB traffic.
  • the at least one parameter and/or at least one criteria indicates at least one of: a maximum speed for the at least one cell, a minimum RSRP for the at least one cell, a maximum data volume for the at least one cell, and a duration of a connection needed via a parent node and/or serving cell.
  • the message is transmitted via: a SIB; dedicated signaling for the second node; or at least one RRC message.
  • the first node is a mobile IAB-MT and the second node comprises a donor CU that performs at least one function related to admission control and/or redirection.
  • the first node receives, from the Donor CU, a message requesting information from the mobile IAB-MT relating to speed and/or location of the mobile IAB-MT.
  • FIGURE 15 illustrates a method 1300 by a second node 110, 105 for supporting mobile IAB, according to certain embodiments. The method includes the second node 110, 105 receiving, from a first node 105, 110 , a message indicating that the first node supports at least one mobile IAB functionality, at step 1302.
  • the is an IAB node that is a parent to the second node, and the first node comprises a mobile IAB-MT.
  • the information indicates that the first node comprises the UE that is the mobile IAB-MT. In a further particular embodiment, the information comprises at least one of: a speed of the first node; and a location of the first node. In a further particular embodiment, the information comprises at least one of: a UE capability identifier; at least one segmented UE capability; an expected time duration for which a service is needed from a cell; a current UL and/or DL throughput; and a total upstream and/or downstream traffic volume.
  • the information comprises at least one of: an indication of a number of UEs that can be served by the mobile IAB node; an indication that the first node supports a configuration of the at least one mobile IAB functionality; at least one indication that indicates support for the at least one mobile IAB functionality in an associated one of a plurality of frequency ranges; at least one indication that indicates support for the at least one mobile IAB functionality in an associated one of a plurality of bands; at least one indication that indicates support for the at least one mobile IAB functionality in an associated one of a plurality of RANs or RATs; and at least one indication that indicates support for the at least one mobile IAB functionality for an associated one of a plurality of types of mobility and/or vehicles.
  • the information comprises assistance information and the information is received in a UEAssistanceInformation message.
  • the second node transmits, to the first node, a request for the information.
  • the first node is an IAB node that is a parent to the second node, and the second node is a mobile IAB-MT.
  • the message includes capability information indicating that the first node supports a mobile IAB.
  • the message includes at least one parameter and/or at least one criteria for at least one cell supporting mobile IAB traffic.
  • the at least one parameter and/or at least one criteria indicates at least one of: a maximum speed for the at least one cell, a minimum RSRP for the at least one cell, a maximum data volume for the at least one cell, and a duration of a connection needed via a parent node and/or serving cell.
  • message is transmitted via: a SIB; dedicated signaling for the second node; or at least one RRC message.
  • the first node is a mobile IAB-MT and the second node comprises a donor CU
  • the second node performs at least one of: performing at least one function related to admission control and/or redirection; and transmitting, to the mobile IAB-MT, a message requesting information relating to speed and/or location of the mobile IAB- MT.
  • some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • a method by a user equipment for supporting mobile IAB functionalities comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.
  • Example Embodiment A2. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above.
  • Example Embodiment A3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node.
  • Group B Example Embodiments
  • Example Embodiment B1 A method by a network node for supporting mobile IAB functionalities, the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.
  • Example Embodiment B2 The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above.
  • Example Embodiment B3. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Group C Example Embodiments Example Embodiment C1.
  • a method by a user equipment (UE) for supporting for mobile IAB functionalities the method comprising: transmitting, to a network node, information indicating support for mobile IAB functionalities.
  • Example Embodiment C2. The method of Example Embodiment C1, wherein the information indicates that the UE is a mobile IAB-MT of a mobile IAB node.
  • Example Embodiments C1 to C2 wherein the information comprises at least one of: a UE capability identifier; at least one segmented UE capability; a speed of the UE; an expected time duration for which a service is needed from a cell; a current uplink (UL) and/or downlink (DL) throughput measured by at least one of the UE and/or a IAB-DU; and a total upstream and downstream traffic volume.
  • a UE capability identifier at least one segmented UE capability
  • a speed of the UE an expected time duration for which a service is needed from a cell
  • UL current uplink
  • DL downlink
  • IAB-DU IAB-DU
  • the information comprises at least one of: an indication of a number of UEs that can be served by the mobile IAB node; an indication that the UE supports a configuration of at least one mobile IAB functionality; at least one indication that indicates support for at least one mobile IAB functionality in an associated one of a plurality of frequency ranges; at least one indication that indicates support for at least one mobile IAB functionality in an associated one of a plurality of bands; at least one indication that indicates support for at least one mobile IAB functionality in an associated one of a plurality of Radio Access Networks (RANs) or Radio Access Technologies (RATs); and at least one indication that indicates support for at least one mobile IAB functionality for an associated one of a plurality of types of mobility and/or vehicles.
  • RANs Radio Access Networks
  • RATs Radio Access Technologies
  • Example Embodiment C5. The method of any one of Example Embodiments C1 to C4, wherein the information comprises assistance information.
  • Example Embodiment C6 The method of Example Embodiment C5, wherein the information is transmitted in a message.
  • Example Embodiment C7. The method of any one of Example Embodiments C1 to C6, comprising receiving, from the network node, a request for the information.
  • Example Embodiment C8. The method of any one of Example Embodiments C1 to C7, wherein the information is transmitted in at least one field of a message.
  • Example Embodiment C10 The method of any one of Example Embodiments C1 to C7, wherein the information is transmitted in a plurality of fields of a message, each field containing a portion of the information.
  • Example Embodiment C10 The method of Example Embodiments C1 to C9, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Example Embodiment C11 A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C10.
  • a wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C10.
  • Example Embodiment C13 Example Embodiment C13.
  • a computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C10.
  • Example Embodiment C14 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C10.
  • Example Embodiment C15 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example embodiments C1 to C10. Group D
  • Example Embodiments Example Embodiment D1 A method by a network node for supporting mobile IAB functionalities, the method comprising: receiving, from a user equipment (UE), information indicating support for mobile IAB functionalities.
  • Example Embodiment D1 wherein the information indicates that the UE is a mobile IAB-MT of a mobile IAB node.
  • Example Embodiment D3. The method of any one of Example Embodiments D1 to D2, wherein the information comprises at least one of: a UE capability identifier; at least one segmented UE capability; a speed of the UE; an expected time duration for which a service is needed from a cell; a current uplink (UL) downlink (DL) throughput measured by at least one of the UE and/or a IAB-DU; and a total upstream and downstream traffic volume.
  • the information comprises at least one of: an indication of a number of UEs that can be served by the mobile IAB node; an indication that the UE supports a configuration of at least one mobile IAB functionality; at least one indication that indicates support for at least one mobile IAB functionality in an associated one of a plurality of frequency ranges; at least one indication that indicates support for at least one mobile IAB functionality in an associated one of a plurality of bands; at least one indication that indicates support for at least one mobile IAB functionality in an associated one of a plurality of Radio Access Networks (RANs) or Radio Access Technologies (RATs); and at least one indication that indicates support for at least one mobile IAB functionality for an associated one of a plurality of types of mobility and/or vehicles.
  • RANs Radio Access Networks
  • RATs Radio Access Technologies
  • Example Embodiment D5 The method of any one of Example Embodiments D1 to D4, wherein the information comprises assistance information.
  • Example Embodiment D6 The method of Example Embodiment D5, wherein the information is received in a UEAssistanceInformation message.
  • Example Embodiment D7 The method of any one of Example Embodiments D1 to D6, comprising transmitting, to the UE, a request for the information.
  • Example Embodiment D8 The method of any one of Example Embodiments D1 to D7, wherein the information is received in at least one field of a message.
  • Example Embodiment D11 The method of any one of Example Embodiments D1 to D7, wherein the information is received a plurality of fields of a message, each field containing a portion of the information.
  • Example Embodiment D11 The method of any one of Example Embodiments D1 to D10, wherein the network node comprises a gNodeB (gNB).
  • Example Embodiment D12. The method of any of the previous Example Embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Example Embodiment D13 A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments D1 to D12.
  • Example Embodiment D14 Example Embodiment D14.
  • a computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D12.
  • Example Embodiment D15 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D12.
  • Example Embodiment D16 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D1 to D12. Group E Example Embodiments Example Embodiment E1.
  • a method by a user equipment (UE) for supporting mobile IAB functionalities comprising: receiving a message from a network node; and determining, based on the message, that the network node supports mobile IAB functionalities.
  • UE user equipment
  • Example Embodiment E2 The method of Example Embodiment E1, wherein the determining is based on receiving the message from the network node (i.e., the message is an implicit indication that the network node supports mobile IAB functionalities).
  • Example Embodiment E3. The method of Example Embodiment E1, wherein the message comprises capability information indicating that the network node supports mobile IAB functionalities.
  • Example Embodiment E4. The method of any one of Example Embodiments E1 to E3, wherein the message comprises at least one parameter and/or at least one criteria associated with at least one cell supporting mobile IAB traffic.
  • Example Embodiment E4 wherein the at least one parameter and/or at least one criteria indicates at least one of: a maximum speed for the at least one cell, a minimum RSRP for the at least one cell, a maximum data volume for the at least one cell, and a duration of a connection needed via a parent node and/or serving cell.
  • Example Embodiment E6 The method of any one of Example Embodiments E1 to E5, wherein the message comprises a plurality of fields, each one of the plurality of fields indicating an associated one of a plurality of mobile IAB functionalities that are supported by the network node.
  • Example Embodiment E7 Example Embodiment E7.
  • Example Embodiment E6 The method of any one of Example Embodiments E1 to E6, wherein the information is received in a System Information Block (SIB).
  • SIB System Information Block
  • Example Embodiment E8 The method of any one of Example Embodiments E1 to E6, wherein the information is received via dedicated signaling for the UE.
  • Example Embodiment E9. The method of any one of Example Embodiments E1 to E6, wherein the information is received via at least one Radio Resource Control (RRC) message.
  • RRC Radio Resource Control
  • Example Embodiment E10 The method of any one of Example Embodiments E1 to E9, wherein the UE comprises a mobile IAB- Example Embodiment E11.
  • Example Embodiment E12 A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments E1 to E11.
  • Example Embodiment E13 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments E1 to E11.
  • Example Embodiment E14 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments E1 to E11.
  • Example Embodiment E15 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments E1 to E11.
  • Example Embodiments Example Embodiment F1 A method by a network node for supporting mobile IAB functionalities, the method comprising: transmitting, to a user equipment (UE), a message to indicate support for mobile IAB functionalities by the network node.
  • Example Embodiment F2. The method of Example Embodiment F1, wherein the message is an implicit indication that the network node supports mobile IAB functionalities.
  • Example Embodiment F3. The method of Example Embodiment F1, wherein the message comprises capability information indicating that the network node supports a mobile IAB.
  • Example Embodiment F5 The method of any one of Example Embodiments F1 to F3, comprising transmitting, to the UE, at least one parameter and/or at least one criteria for at least one cell supporting mobile IAB traffic.
  • Example Embodiment F5. The method of Example Embodiment F4, wherein the at least one parameter and/or at least one criteria indicates at least one of: a maximum speed for the at least one cell, a minimum RSRP for the at least one cell, a maximum data volume for the at least one cell, and a duration of a connection needed via a parent node and/or serving cell.
  • Example Embodiment F6 Example Embodiment F6.
  • Example Embodiment F5 The method of any one of Example Embodiments F1 to F5, wherein the message comprises a plurality of fields, each one of the plurality of fields indicating an associated one of a plurality of mobile IAB functionalities that are supported by the network node.
  • Example Embodiment F7 The method of any one of Example Embodiments F1 to F6, wherein the information is transmitted in a System Information Block (SIB).
  • the method of any one of Example Embodiments F1 to F6, wherein the information is transmitted via dedicated signaling for the UE.
  • Example Embodiment F9. The method of any one of Example Embodiments F1 to F6, wherein the information is received via at least one Radio Resource Control (RRC) message.
  • RRC Radio Resource Control
  • Example Embodiments F1 to F8 wherein the UE comprises a mobile IAB-MT.
  • Example Embodiment F11 The method of any one of Example Embodiments F1 to F10, wherein the network node comprises a gNodeB (gNB).
  • Example Embodiment F12. The method of any of the previous Example Embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Example Embodiment F13 A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments F1 to F12.
  • Example Embodiment F14. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments F1 to F12.
  • Example Embodiment F15 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments F1 to F12.
  • Example Embodiment F16 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments F1 to F12.
  • Group G Example Embodiments Example Embodiment G1.
  • a user equipment for supporting mobile IAB functionalities, the UE comprising: processing circuitry configured to perform any of the steps of any of the Group A, C, and E Example Embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • a network node for supporting mobile IAB functionalities comprising: processing circuitry configured to perform any of the steps of any of the Group B, D, and F Example Embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • processing circuitry configured to perform any of the steps of any of the Group B, D, and F Example Embodiments
  • power supply circuitry configured to supply power to the processing circuitry.
  • a user for supporting mobile IAB functionalities, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A, C, and E Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • Example Embodiment G4 Example Embodiment G4.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, and E Example Embodiments to receive the user data from the host.
  • Example Embodiment G5. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • Example Embodiment G6 Example Embodiment G6.
  • Example Embodiment G7 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.
  • Example Embodiment G9 The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Example Embodiment G9. The method of the previous Example Embodiment, further comprising: at the host, transmitting input to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, and E Example Embodiments to transmit the user data to the host.
  • Example Emboidment G11 The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • Example Embodiment G13 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A, C, and E Example Embodiments to transmit the user data to the host.
  • Example Embodiment G14 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A, C, and E Example Embodiments to transmit the user data to the host.
  • Example Embodiment G15 The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Example Embodiment G16 Example Embodiment
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, D, and F Example Embodiments to transmit the user data from the host to the UE.
  • Example Embodiment G17 Example Embodiment G17.
  • Example Embodiment G18 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B, D, and F Example Embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • Example Embodiment G19 The method of the previous Example Embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Example Emboidment G20 The method of any of the previous 2 Example Embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • a communication system configured to provide an over-the- top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, D, and F Example Embodiments to transmit the user data from the host to the UE.
  • Example Embodiment G22 The communication system of the previous Example Embodiment, further comprising: the network node; and/or the user equipment.
  • Example Embodiment G23 The communication system of the previous Example Embodiment, further comprising: the network node; and/or the user equipment.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry network node configured to perform any of the operations of any of the Group B, D, and F
  • UE user equipment
  • Example Embodiment G25 The host of the any of the previous 2 Example Embodiments, wherein the initiating receipt of the user data comprises requesting the user data. 10 Example Embodiment G26.

Landscapes

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

Abstract

Un procédé (1200) exécuté par un premier nœud (105, 110) pour prendre en charge des fonctionnalités d'accès intégré mobile et de liaison terrestre (IAB) consiste à transmettre (1202), à un second nœud (110, 105), un message indiquant que le premier nœud prend en charge au moins une fonctionnalité IAB mobile.
PCT/EP2023/072000 2022-08-09 2023-08-09 Signalisation pour la prise en charge d'accès intégré mobile et de liaison terrestre WO2024033396A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263396388P 2022-08-09 2022-08-09
US63/396,388 2022-08-09

Publications (1)

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

Family

ID=87571121

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/072000 WO2024033396A1 (fr) 2022-08-09 2023-08-09 Signalisation pour la prise en charge d'accès intégré mobile et de liaison terrestre

Country Status (1)

Country Link
WO (1) WO2024033396A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210044958A1 (en) * 2019-08-08 2021-02-11 Qualcomm Incorporated Signaling to support mobile integrated access and backhaul
WO2021098063A1 (fr) * 2020-02-17 2021-05-27 Zte Corporation Procédés et systèmes de transmission d'informations d'accès et de raccordement intégrés
WO2022047805A1 (fr) * 2020-09-07 2022-03-10 Nokia Shanghai Bell Co., Ltd. Procédés, appareils et supports lisibles par ordinateur pour une communication iab (integrated access and backhaul)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210044958A1 (en) * 2019-08-08 2021-02-11 Qualcomm Incorporated Signaling to support mobile integrated access and backhaul
WO2021098063A1 (fr) * 2020-02-17 2021-05-27 Zte Corporation Procédés et systèmes de transmission d'informations d'accès et de raccordement intégrés
WO2022047805A1 (fr) * 2020-09-07 2022-03-10 Nokia Shanghai Bell Co., Ltd. Procédés, appareils et supports lisibles par ordinateur pour une communication iab (integrated access and backhaul)

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"Study on IAB", 3GPP TR 38.874
3GPP TR 22.839
3GPP TS 38.300
3GPP TS 38.331
3GPP TS 38.401
MADAPATHA, CHARITHA ET AL.: "On Integrated Access and Backhaul Networks: Current Status and Potentials", IEEE OPEN JOURNAL OF THE COMMUNICATIONS SOCIETY, vol. 1, 2020, pages 1374 - 1389, XP011812066, DOI: 10.1109/OJCOMS.2020.3022529
QUALCOMM INCORPORATED: "Enhancements for mobility of IAB-node and its served UEs", vol. RAN WG3, no. electronic; 20220815 - 20220826, 8 August 2022 (2022-08-08), XP052264670, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_117-e/Docs/R3-224505.zip R3-224505 Enhancements for mobility of IAB-node and served UEs.docx> [retrieved on 20220808] *

Similar Documents

Publication Publication Date Title
WO2023105073A1 (fr) Commande d&#39;admission inter-nœuds de réseau pour un ue relais de liaison latérale
WO2023277775A1 (fr) Enregistrement de types de défaillance différents pour des procédures de requête d&#39;informations de système à la demande
WO2023007022A1 (fr) Procédés et appareils de commande de rapport de charge
WO2022260569A1 (fr) Procédés pour des communications d&#39;uav sur liaison latérale
WO2024033396A1 (fr) Signalisation pour la prise en charge d&#39;accès intégré mobile et de liaison terrestre
US20240259921A1 (en) Signalling Approaches for Disaster PLMNS
US20240212508A1 (en) Acquisition of Flight Information for UAV Communications
US20240276320A1 (en) Handling of rejection of candidate target cells for conditional pscell change
WO2024169687A1 (fr) Procédé et appareil pour l&#39;application d&#39;une configuration au niveau d&#39;un dispositif terminal
WO2024072274A1 (fr) Gestion d&#39;ue en veille-inactifs pendant un transfert intercellulaire avec iab mobile
WO2024027838A9 (fr) Procédé et appareil pour arrêter un rapport de localisation
WO2024035287A1 (fr) Évitement de situations de concurrence entre mobilité l1/l2 et l3
WO2023244155A1 (fr) Gestion de changement de zone de suivi/ran d&#39;un nœud iab mobile
WO2024035296A1 (fr) Ue non connecté desservi par un iab sur le même véhicule
WO2024033272A1 (fr) Extension cag pour nœud iab mobile
WO2024005700A1 (fr) Configuration de candidats de mobilité inter-du l1/l2
WO2024035305A1 (fr) Rapport de réussite de changement ou d&#39;ajout de pscell
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2023152683A1 (fr) Changement de pscell conditionnel initié par un nœud secondaire
WO2024079636A1 (fr) Coordination pour migration de nœud iab mobile
WO2024125813A1 (fr) Systèmes et procédés par un nœud de réseau de gestion pour réduire la probabilité d&#39;utilisation conflictuelle de ressources par des équipements utilisateur
WO2024068739A1 (fr) Systèmes et procédés de gestion de changement de cellule secondaire primaire conditionnel déclenché par un nœud secondaire dans configuration de transfert conditionnel
WO2024095187A1 (fr) Procédés et nœud de réseau pour signaler une migration du iab mobile
WO2023046956A1 (fr) Surveillance et récupération sur défaillance de faisceau dans une liaison latérale
WO2024015000A1 (fr) Transmission de petites données à terminaison mobile

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

Country of ref document: EP

Kind code of ref document: A1