WO2023148705A1 - Conception conjointe de disponibilité dans le domaine temporel et fréquentiel - Google Patents

Conception conjointe de disponibilité dans le domaine temporel et fréquentiel Download PDF

Info

Publication number
WO2023148705A1
WO2023148705A1 PCT/IB2023/051090 IB2023051090W WO2023148705A1 WO 2023148705 A1 WO2023148705 A1 WO 2023148705A1 IB 2023051090 W IB2023051090 W IB 2023051090W WO 2023148705 A1 WO2023148705 A1 WO 2023148705A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
node
tdm
mode
resource
Prior art date
Application number
PCT/IB2023/051090
Other languages
English (en)
Inventor
Magnus ÅSTRÖM
Boris Dortschy
Marco BELLESCHI
Lei BAO
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 WO2023148705A1 publication Critical patent/WO2023148705A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing

Definitions

  • the present disclosure relates to operations of a cellular communications systems for configuring Integrated Access and Backhaul (IAB) nodes.
  • IAB Integrated Access and Backhaul
  • the IAB donor node (in short IAB donor) has a wired connection to the core network and the lAB-nodes are wirelessly connected using NR to the IAB donor, either directly or indirectly via another IAB -node.
  • the connection between IAB donor/node and UEs is called access link, whereas the connection between two lAB-nodes or between an IAB donor and an IAB -node is called backhaul link.
  • the adjacent upstream node which is closer to the IAB donor node of an lAB-node is referred to as a parent lAB-node of the lAB-node.
  • the adjacent downstream node which is further away from the IAB donor node of an lAB-node is referred to as a child node of the lAB-node.
  • the backhaul link between the parent lAB-node and the lAB-node is referred to as parent (backhaul) link, whereas the backhaul link between the lAB-node and the child node is referred to as child (backhaul) link.
  • an lAB-donor contains both CU and DU functions. In particular, it contains all CU functions of the lAB-nodes under the same lAB-donor. Each IAB- node then hosts the DU function(s) of a gNB.
  • each lAB-node has a mobile termination (MT), a logical unit providing a necessary set of UE-like functions.
  • MT mobile termination
  • the lAB-node establishes RLC-channel to UEs and/or to MTs of the connected lAB-node(s).
  • the lAB-node establishes the backhaul radio interface towards the serving lAB-node or lAB-donor.
  • Figure 3 shows a reference diagram for a two-hop chain of lAB-nodes under an lAB-donor.
  • Wireless backhaul links are vulnerable to blockage, e.g., due to moving objects such as vehicles, due to seasonal changes (foliage), severe weather conditions (rain, snow or hail), or due to infrastructure changes (new buildings). Such vulnerability also applies to lAB-nodes. Also, traffic variations can create uneven load distribution on wireless backhaul links leading to local link or node congestion. In view of those concerns, the IAB topology supports redundant paths as another difference compared to the Rel-10 LTE relay.
  • one lAB-node can have multiple child lAB-nodes and/or have multiple parent lAB-nodes.
  • the multi-connectivity or route redundancy may be used for back-up purposes. It is also possible that redundant routes are used concurrently, e.g., to achieve load balancing, reliability, etc.
  • the lAB-node In case of in-band operation, the lAB-node is typically subject to the half-duplex constraint, i.e., an lAB-node can only be in either transmission or reception mode at a time.
  • Rel- 16 IAB mainly consider the time-division multiplexing (TDM) case where the MT and DU resources of the same lAB-node are separated in time. Based on this consideration, the following resource types have been defined for IAB MT and DU, respectively.
  • the child link has the following types of time resources:
  • NA Not-available (NA) time resources (resources not to be used for communication on the DU child links)
  • Each of the downlink, uplink and flexible time-resource types of the DU child link can belong to one of two categories:
  • the IAB DU resources are configured per cell, and the H/S/NA attributes for the DU resource configuration are explicitly indicated per-resource type (D/U/F) in each slot.
  • the semi-static time-domain resources of the DU part can be of seven types in total: Downlink- Hard (DL-H), Downlink-Soft (DL-S), Uplink-Hard (UL-H), Uplink-Soft (UL-S), Flexible-Hard (F-H), Flexible-Soft (F-S), and Not-Available (NA).
  • DL-H Downlink- Hard
  • DL-S Downlink-Soft
  • U-Hard Uplink-Hard
  • U-S Uplink-Soft
  • F-H Flexible-Hard
  • F-S Flexible-Soft
  • Not-Available (NA) Not-Available
  • Availability Indication uses DO format 2_5 (interchangeable with DO 2_5) for dynamically indicating the availability of DU Soft resource in a slot.
  • FIG. 5 illustrates the signaling design for the DO format 2_5.
  • the I AB -DU is provided with a cell identity (cell-ID), information about the location of Al information (position of information) in a DO format 2_5 and a set of availability combinations.
  • Each availability combination contains a sequence (resourceAvailability) of elements indicating the availability of soft symbols in one or more slots for the IAB-DU serving cell and an identity number (availabilityCombinationld) to map between symbol availability combinations provided by resourceAvailability and information provided via DO format 2_5 (the indices in DO format 2_5).
  • the provisioning to the lAB-node of the combination of the cell-ID, location information and the set of availability combinations is by using an RRC information element.
  • an IAB-DU function may correspond to multiple cells, including cells operating on different carrier frequencies.
  • an IAB-MT function may correspond to multiple carrier frequencies. This can either be implemented by one IAB-MT unit operating on multiple carrier frequencies or be implemented by multiple IAB-MT units, each operating on different carrier frequencies.
  • the H/S/NA attributes for the per-cell DU resource configuration should take into account the associated IAB-MT carrier frequency(ies).
  • One of the objectives in the Rel-17 IAB WID RP-211548 is to have “specification of enhancements to the resource multiplexing between child and parent links of an lAB-node, including: support of simultaneous operation (transmission and/or reception) of lAB-node’s child and parent links (i.e., MT Tx/DU Tx, MT Tx/DU Rx, MT Rx/DU Tx, MT Rx/DU Rx).”
  • MT Tx/DU Tx MT Tx/DU Rx
  • MT Rx/DU Tx MT Rx/DU Tx
  • the simultaneous operation includes both frequency-division multiplexing (FDM) and spatial-division multiplexing (SDM).
  • FDM frequency-division multiplexing
  • SDM spatial-division multiplexing
  • H/S/NA configurations for an lAB-node are provided separately in addition to the Rel-16 H/S/NA
  • DO Format 2_5 is reused to support soft resource availability indications for frequencydomain resources
  • the semi-static configuration of H/S/NA resource type in frequency domain is provided per RB set, per D/U/F resource type within a slot.
  • An IAB node (or parent node) cannot operate under a given non-TDM multiplexing mode until:
  • a single DO format 2_5 can be received indicating availability for the soft resources of the respective RB sets corresponding to a given time resource of the child IAB-DU cell.
  • FFS Extension of AvailabilityCombination to include multiple RB sets in a resourceAvailabiltiy indication
  • FFS Update resourceAvailability mapping table defined in TS38.213 so that the indication of availability can be applied over soft resources in frequency-domain for DL or UL or Flexible symbols.
  • FFS Need for extension of the maximum payload size of DO format 2_5 to increase the number of I AB -DU cells that can be provided with availability information for Soft resources to accommodate the maximum number of possible RB sets for a given DU cell (if defined), or other backwards compatible signaling extensions in case the principal indication capabilities of DO format 2_5 are increased.
  • DO format 2_5 indicating availability for the soft resources of the respective RB sets corresponding to a given time resource of the child IAB-DU cell:
  • AvailabilityCombination can be extended to include multiple resourceAvailability, where each resourceAvailability includes availability indication for one RB set group •
  • One RB set group consists of one or multiple RB sets
  • Availability Indication uses DO Format 2_5 (in the following also referred to as DO 2_5) for dynamically indicating the availability of the IAB-DU soft resource in a slot. It has been agreed in Rel-17 enhanced IAB that configuring frequency-domain H/S/NA is supported to allow for increased resource utilization flexibility, reduced cross-link interference (CLI) and reduced latency.
  • CLI cross-link interference
  • the frequency domain H/S/NA is provided per RB (Resource Block) set, per D/U/F resource type within a slot, and a single DO format 2_5 can be received to indicate availability of the soft resources of the respective RB sets corresponding to a given time resource of the child IAB-DU cells.
  • RB Resource Block
  • DO format 2_5 can be received to indicate availability of the soft resources of the respective RB sets corresponding to a given time resource of the child IAB-DU cells.
  • the figure shows for example the first AvailabilityCombinationld (0) is associated to two IAB-DU RB set groups: the first RB set group contains RB set 0 and RB set 1 ; and the second RB set group is associated to RB sets 2-4.
  • Rel-17 IAB will support co-existence of TDM and FDM operation modes.
  • TDM or FDM multiplexing mode is applied, see an example in Figure 9 that the IAB-DU cell operates in the TDM mode in slot 0-2, 5-6, and switches to the FDM mode in slot 3-4.
  • an lAB-node which is capable of FDM operation, it will need to maintain two AvailabilityCombinations tables for each IAB-DU cell, one for TDM operation and one for FDM operation, respectively. If the switching between TDM and FDM operations occur frequently, the parent node will need to provide a new DO format 2_5 every time when the multiplexing mode is changed. As shown in Figure 9, it could need three DO format 2_5 to provide availability indication for the 7 slots. Since DO is a scarce resource, there is a need of methods to enable efficient coexistence of time domain and frequency domain availabilityCombinations and resourceAvailabilities, and thereby configure a joint DO format 2_5 for time and frequency domain soft resources.
  • Some embodiments may provide solutions to these or other challenges. Some embodiments include methods to allow a parent lAB-node to efficiently indicate time-domain and frequency-domain resourceAvailabilities via one shared availabilityCombinations and configure one joint DO format 2_5 for time and frequency soft resources, and thereby enable coexistence of TDM and FDM operations with reduced signaling overhead.
  • a method in an lAB-node, associated with a parent node, the lAB-node having at least one IAB-DU cell which can alternate between TDM and FDM modes of operation, for determining availability indication the method comprises
  • Receiving semi-static resource configuration including TDD patterns, and/or H/S/NA configurations
  • a method in a network node to provide availabilityCombinations and resource configuration to an lAB-node for resource multiplexing configuration between IAB-DU and IAB-MT parts comprising,
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the invention enables the usage of the both soft time-domain resources and soft frequency-domain resources at an I AB -node to provide efficient time and frequency multiplexing between IAB-MT and collocated IAB-DU for multiple IAB-DU cells.
  • the parent node can use one DO format 2_5 and one AvailabilityCombinations table to provide availability indication for both TDM and FDM soft resources. In doing so, the capacity of the lAB-node can be greatly increased, in turn resulting in increased network performance, reduced latency and improved user experience.
  • Embodiments of a method performed by a network node implementing an IAB node for determining availability, wherein the IAB node is configured to selectively alternate between a Time-Division Multiplexing (TDM) mode of operation and a Frequency-Division Multiplexing (FDM) mode of operation, are disclosed.
  • the method comprises receiving, from a parent IAB node, a Downlink Control Information (DO) format 2_5 message that addresses a TDM mode of operation and an FDM mode of operation.
  • DO Downlink Control Information
  • the method further comprises identifying an availabilityCombinationlD associated with the received DO format 2_5 message.
  • the method also comprises determining a resourceAvailability indication associated with the FDM mode of operation based on the selected availabilityCombinationld.
  • the method additionally comprises determining a resourceAvailability indication associated with the TDM mode of operation, based on the determined resourceAvailability indication associated with the FDM mode of operation.
  • the method further comprises determining one of the TDM mode of operation and the FDM mode of operation as a configured mode of operation.
  • the method also comprises applying one of the resourceAvailability indication associated with the TDM mode of operation and the resourceAvailability indication associated with the FDM mode of operation based on the configured mode of operation.
  • the method further comprises, prior to receiving the DO format 2_5 message, providing an indication of resource multiplexing capability of the IAB node, receiving an AvailabilityCombinations table, and receiving one or more semi-static resource configurations comprising a Time Division Duplex (TDD) pattern and/or a Hard/Soft/Not Available (H/S/NA) configuration.
  • the resourceAvailability indication associated with the TDM mode of operation is indicated in the received AvailabilityCombinations table.
  • Some such embodiments may provide that a resourceAvailability indication of an FDM Resource Block (RB) set group to be associated with the resourceAvailability indication associated with the TDM mode of operation.
  • RB FDM Resource Block
  • Embodiments of a network node implementing an IAB node for determining availability wherein the IAB node is configured to selectively alternate between a TDM mode of operation and a FDM mode of operation, are also disclosed.
  • the network node comprises a network interface, and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the network node to receive, from a parent IAB node, a DCI format 2_5 message that addresses a TDM mode of operation and an FDM mode of operation.
  • the processing circuitry is further configured to cause the network node to identify an availabilityCombinationlD associated with the received DCI format 2_5 message.
  • the processing circuitry is also configured to cause the network node to determine a resourceAvailability indication associated with the FDM mode of operation based on the selected availabilityCombinationld.
  • the processing circuitry is additionally configured to cause the network node to determine a resourceAvailability indication associated with the TDM mode of operation, based on the determined resourceAvailability indication associated with the FDM mode of operation.
  • the processing circuitry is further configured to cause the network node to determine one of the TDM mode of operation and the FDM mode of operation as a configured mode of operation.
  • the processing circuitry is also configured to cause the network node to apply one of the resourceAvailability indication associated with the TDM mode of operation and the resourceAvailability indication associated with the FDM mode of operation based on the configured mode of operation.
  • the processing circuitry is further configured cause the network node to perform any of the operation attributed to the network node above.
  • Embodiments of a network node implementing an IAB node for determining availability wherein the IAB node configured to selectively alternate between a TDM mode of operation and a FDM mode of operation, are also disclosed.
  • the network node is adapted to receive, from a parent IAB node, a DCI format 2_5 message that addresses a TDM mode of operation and an FDM mode of operation.
  • the network node is further adapted to identify an availabilityCombinationlD associated with the received DCI format 2_5 message.
  • the network node is also adapted to determine a resourceAvailability indication associated with the FDM mode of operation based on the selected availabilityCombinationld.
  • the network node is additionally adapted to determine a resourceAvailability indication associated with the TDM mode of operation, based on the determined resourceAvailability indication associated with the FDM mode of operation.
  • the network node is further adapted to determine one of the TDM mode of operation and the FDM mode of operation as a configured mode of operation.
  • the network node is also adapted to apply one of the resourceAvailability indication associated with the TDM mode of operation and the resourceAvailability indication associated with the FDM mode of operation based on the configured mode of operation.
  • the network node is further adapted to perform any of the operations attributed to the network node above.
  • Embodiments of a method performed by a network node implementing an IAB parent node for providing a resource availability indication are also disclosed.
  • the method comprises determining a plurality of multiplexing modes for a corresponding plurality of slots of at least one IAB Distributed Unit (IAB -DU) cell of an IAB child node of the IAB parent node, wherein the IAB -DU cell is at least partially overlapping with a Bandwidth Part (BWP) of the IAB child node that is serviced by the IAB parent node, and the IAB child node is capable of operation in simultaneous operation.
  • IAB -DU IAB Distributed Unit
  • BWP Bandwidth Part
  • the method further comprises determining an availabilityCombinationlD and an Availability Indicator index (Al-index) for the at least one IAB -DU cell and the plurality of slots.
  • the method also comprises transmitting a DO format 2_5 message comprising the availabilityCombination ID and the Al-index to the IAB child node.
  • the method further comprises, prior to transmitting the DO format 2_5 message, receiving an indication of resource multiplexing capability of at least one IAB -DU cell of the IAB child node, and receiving a shared availabilityCombinations table for a TDM soft resource and a FDM soft resource.
  • the shared AvailabilityCombinations table indicates a TDM resourceAvailability.
  • the shared AvailabilityCombinations table indicates a TDM resourceAvailability by mapping TDM to a specific RB set group or includes a separate TDM row for an AvailabilityCombinationld.
  • the method further comprises, prior to receiving the shared availabilityCombinations table, transmitting, to the IAB child node, an indication of the RB set group to be associated with the TDM resourceAvailability.
  • the RB set group to be associated with the TDM resourceAvailability is determined from a specification or read from a file.
  • determining the availabilityCombinationlD and the Al-index is based on one or more of an expected traffic need, past traffic statistics, buffer utilization, propagation channel conditions, timing, and/or power control conditions between parent and child backhaul links.
  • Embodiments of a network node implementing an IAB parent node for providing a resource availability indication are also disclosed.
  • the network node comprises a network interface, and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the network node to determine a plurality of multiplexing modes for a corresponding plurality of slots of at least one IAB -DU cell of an IAB child node of the IAB parent node, wherein the IAB -DU cell is at least partially overlapping with a BWP of the IAB child node that is serviced by the IAB parent node, and the IAB child node is capable of operation in simultaneous operation.
  • the processing circuitry is further configured to cause the network node to determine an availabilityCombinationlD and an Al-index for the at least one IAB-DU cell and the plurality of slots.
  • the processing circuitry is also configured to cause the network node to transmit a DO format 2_5 message comprising the availabilityCombination ID and the Al-index to the IAB child node.
  • Some embodiments may provide that the processing circuitry is further configured cause the network node to perform any of the operations attributed to the network node above.
  • Embodiments of a network node implementing an IAB parent node for providing a resource availability indication are also disclosed.
  • the network node is adapted to determine a plurality of multiplexing modes for a corresponding plurality of slots of at least one IAB-DU cell of an IAB child node of the IAB parent node, wherein the IAB-DU cell is at least partially overlapping with a BWP of the IAB child node that is serviced by the IAB parent node, the IAB child node is capable of operation in simultaneous operation.
  • the network node is further adapted to determine an availabilityCombinationlD and an Al-index for the at least one IAB-DU cell and the plurality of slots.
  • the network node is also adapted to transmit a DO format 2_5 message comprising the availabilityCombination ID and the Al-index to the IAB child node.
  • the network node is further adapted to perform any of the operations attributed to the network node above.
  • Embodiments of a method performed by a network node implementing an IAB donor node to provide availabilityCombinations and resource configuration to an IAB node for resource multiplexing configuration between IAB-DU and IAB Mobile Termination (IAB -MT) parts are also disclosed.
  • the method comprises receiving an indication of multiplexing capability from the IAB node for at least one IAB-DU cell.
  • the method further comprises configuring a shared time-/frequency-domain availabilityCombinations for each of the at least one IAB-DU cell.
  • the method also comprises transmitting the shared time-/frequency-domain availabilityCombinations to the IAB node and an IAB parent node of the IAB node.
  • the method additionally comprises determining a semi-static IAB-DU resource configuration including a TDD pattern, a TDM configuration, and/or a H/S/NA configuration.
  • the method further comprises signaling the semistatic IAB-DU resource configuration to the IAB node.
  • the method further comprises signaling an IAB-DU cell/carrier configuration to the IAB parent node.
  • the processing circuitry is configured to cause the network node to receive an indication of multiplexing capability from the IAB node for at least one IAB-DU cell.
  • the processing circuitry is further configured to cause the network node to configure a shared time- /frequency-domain availabilityCombinations for each of the at least one IAB-DU cell.
  • the processing circuitry is also configured to cause the network node to transmit the shared time- /frequency-domain availabilityCombinations to the IAB node and an IAB parent node of the IAB node.
  • the processing circuitry is additionally configured to cause the network node to determine a semi-static IAB-DU resource configuration including a TDD pattern, a TDM configuration, and/or a H/S/NA configuration.
  • the processing circuitry is further configured to cause the network node to signal the semi-static IAB-DU resource configuration to the IAB node. Some embodiments may provide that the processing circuitry is further configured cause the network node to perform any of the operations attributed to the network node above.
  • Embodiments of a network node implementing an IAB donor node to provide availabilityCombinations and resource configuration to an IAB node for resource multiplexing configuration between IAB Distributed Unit IAB-DU and IAB-MT parts are also disclosed.
  • the network node is adapted to receive an indication of multiplexing capability from the IAB node for at least one IAB-DU cell.
  • the network node is further adapted to configure a shared time- /frequency-domain availabilityCombinations for each of the at least one IAB-DU cell.
  • the network node is also adapted to transmit the shared time -/frequency-domain availabilityCombinations to the IAB node and an IAB parent node of the IAB node.
  • the network node is additionally adapted to determine a semi-static IAB-DU resource configuration including a TDD pattern, a TDM configuration, and/or a H/S/NA configuration.
  • the network node is further adapted to signal the semi-static IAB-DU resource configuration to the IAB node.
  • the network node is further adapted to perform any of the operations attributed to the network node above.
  • Figure 1 illustrates an Integrated Access and Backhaul (IAB) deployment in which multiple hops are supported, according to some exemplary embodiments
  • Figure 2 illustrates an IAB deployment in which an adjacent upstream node that is closer to an IAB donor node of an lAB-node is referred to as a parent lAB-node of the lAB-node, according to some exemplary embodiments;
  • Figure 3 illustrates a reference diagram for a two-hop chain of lAB-nodes under an IAB -donor, according to some exemplary embodiments
  • Figure 4 illustrates IAB topologies including a spanning tree (ST) topology and a directed acyclic graph (DAG) topology, according to some exemplary embodiments;
  • Figure 5 illustrates signaling design for Downlink Control Information (DO) format 2_5, according to some exemplary embodiments
  • FIG. 6 illustrates an exemplary Distributed Unit (DU) configuration, according to some exemplary embodiments
  • Figure 7 illustrates an exemplary frequency-domain DU resource configuration, according to some exemplary embodiments
  • Figure 8 illustrates one possible solution for frequency domain AvailabilityCombinations, in which each AvailabilityCombinationld is mapped to one or multiple Resource Block (RB) set groups, where each RB set group of an IAB -DU cell is provided with a dedicated resourceAvailability, according to some exemplary embodiments;
  • RB Resource Block
  • FIG. 9 illustrates an example in which a IAB-DU cell operates in Time-Division Multiplexing (TDM) mode and switches to Frequency-Division Multiplexing (FDM) mode, according to some exemplary embodiments;
  • TDM Time-Division Multiplexing
  • FDM Frequency-Division Multiplexing
  • Figure 10 illustrates a system model including IAB network comprising a parent or lAB-donor, an lAB-node, and/or a child node, according to some exemplary embodiments;
  • Figure 11 provides a flowchart illustrating operations that enable an IAB DU-cell to be configured with one shared availabilityCombinations table, and operations that enable an IAB node to determine soft resource availability indication by the parent node, according to some exemplary embodiments;
  • Figure 12 provides a flowchart illustrating operations performed by an IAB parent node, according to some exemplary embodiments;
  • Figure 13 provides flowchart illustrating operations performed by an IAB donor node, according to some exemplary embodiments
  • Figure 14 illustrates an example of availabilityCombinationlds in the availabilityCombinations that can be reserved only for availability indication for TDM soft resources, according to some exemplary embodiments
  • Figure 15 illustrates an example where the availabilityCombinations table has been modified to include a dedicated TDM resourceAvailability also for availabilityCombinationlds defined for FDM, according to some exemplary embodiments;
  • Figure 16 illustrates an example of the usage of a dedicated availabilityCombinationld for FDM resourceAvailability in mixed TDM and FDM slots, according to some exemplary embodiments
  • Figure 17 illustrates an example of a shared availabilityCombinationld for TDM and FDM resourceAvailabilities that can be used to configure a DO format 2_5 for a sequence of mixed TDM and FDM soft slots, according to some exemplary embodiments;
  • Figure 18 provides a flowchart illustrating exemplary operations in an IAB node, according to some exemplary embodiments.
  • Figure 19 provides a flowchart illustrating exemplary operations in a IAB parent node, according to some exemplary embodiments.
  • Figure 20 provides a flowchart illustrating exemplary operations in an IAB donor, according to some exemplary embodiments.
  • Figure 21 illustrates an example of a communication system, according to some exemplary embodiments.
  • Figure 22 illustrates an example of a User Equipment (UE), according to some exemplary embodiments
  • Figure 23 illustrates an example of a network node, according to some exemplary embodiments.
  • Figure 24 illustrates an example of a host, according to some exemplary embodiments
  • Figure 25 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to some exemplary embodiments; and [0075] Figure 26 provides a communication diagram illustrating a host communicating via a network node with a UE over a partially wireless connection, according to some exemplary embodiments.
  • Figure 10 illustrates a system model that concerns an IAB network comprising a parent or lAB-donor, an lAB-node and possibly also a child node.
  • one or more UEs may be connected to each node, just as one or more child nodes may be connected to an IAB- node, and grandchild nodes may be connected to the child nodes.
  • Figures 11-13 illustrate operations that enable an IAB DU-cell to be configured with one shared availabilityCombinations table which contains both time-domain and frequencydomain availability combinations and resource Availabilities to an IAB -DU cell with mixed TDM and FDM slots.
  • Figure 11 illustrates an IAB node aspect, which is a method in an lAB-node, that is associated with a parent node, the lAB-node capable of alternating between TDM and FDM modes of operation with at least one IAB -DU cell, for determining soft resource availability indication by the parent node.
  • the lAB-node reports the resource multiplexing capability of the IAB-DU cells to the parent node and the network (e.g., donor-CU), including TDM, and/or FDM, and/or SDM etc.
  • the signaling can be an Fl message.
  • the lAB-node receives a shared table of time-domain and frequency-domain availability combinations for the said IAB-DU cell from the network (e.g., donor-CU).
  • the signaling can be an RRC message.
  • the lAB- node receives the semi-static multiplexing resource configurations for the said IAB-DU cell, from the network node (e.g., donor-CU), including e.g., the TDD pattern, the time-domain and/or frequency domain H/S/NA configurations.
  • the network node e.g., donor-CU
  • the lAB-node receives DO format 2_5 indication for the said IAB-DU cell from the parent node, or another indication of dynamic resource availability.
  • the lAB-node identifies the availabilityCombinationld from the DO format 2_5.
  • the lAB-node is allocated an Al index in the DO and determines the availabilityCombinationld from that Al index, see Figure 8.
  • the lAB-node determines the time-domain and frequency domain resourceAvailability sequences based on the availabilityCombinationld from step 104.
  • the lAB-node may optionally receive information about the association information for the TDM resourceAvailabilities to a certain RB set.
  • a certain RB set In one example it can be an RB set with specific RB set index. In another example it can be an RB set with specific resource configuration, e.g., Hard or NA configurations.
  • the signaling can be e.g., a MAC CE message from the parent node, or e.g., a RRC or an Fl message from the donor-DU.
  • the lAB-node identifies time-domain and/or frequency domain resourceAvailability elements based on the operation mode of each slot.
  • the TDM resourceAvailability is determined from the FDM resourceAvailability, e.g., in one of the following ways:
  • One RB set group may be specified to be used for TDM, either by specification or indicated by the table from, e.g., the parent lAB-node or the donor-node, etc.
  • the lAB-node configures the IAB-DU cell to operate according the received DO format 2_5.
  • Figure 12 depicts a flowchart for an IAB parent node aspect of the invention.
  • the parent node receives the resource multiplexing capability of at least one IAB-DU cell from the lAB-node, including TDM, and/or FDM, and/or SDM etc.
  • the signaling can be an Fl message.
  • the parent node receives a shared availabilityCombinations for time-domain and frequency-domain availability combinations for the said IAB-DU cell from the network (e.g., donor-CU).
  • the signaling can be an RRC message or via 0AM (Operation, Administration, Management).
  • the donor- CU can update the availability combinations (e.g., the length and values of a resourceAvailability) based operational information (or feedback) from the parent and IAB- nodes.
  • the parent node can send to the lAB-node the association information for the TDM resourceAvailabilities to a certain RB set.
  • it can be an RB set with specific RB set index.
  • it can be an RB set with specific resource configuration, e.g., Hard or NA configurations.
  • the signaling can be, e.g., a MAC CE message.
  • the parent node receives the semi-static TDM and FDM resource configuration of the said at least one IAB-DU cell from the network (e.g., donor-CU).
  • the signaling can be an Fl message.
  • the parent node determines multiplexing mode for a sequence of slots of at least one IAB-DU cell. This is achieved by handshaking process with the lAB-node including receiving multiplexing condition requests (for simultaneous operations) from the lAB-node on for example timing, power control and beam restriction; and providing acknowledgement to the said multiplexing condition requests.
  • the parent node determines the AvailabilityCombinationld and AI- indices for the at least one IAB-DU cell.
  • the determination of the resource Availabilities, and the corresponding AvailabilityCombinationld and Al-indices is based on one or more of
  • the parent node sends the DO format 2_5 to the lAB-node.
  • Figure 13 depicts a flowchart for an IAB donor node aspect of the invention.
  • the IAB -donor receives the resource multiplexing capability of at least one IAB-DU cell from the lAB-node, including TDM, and/or FDM, and/or SDM etc.
  • the signaling can be an Fl message.
  • the lAB-donor configures a shared availabilityCombinations for time-domain and frequency-domain availability combinations for each (at least one) IAB-DU cell.
  • the availabilitycombinations table includes an additional “RB set group” row, including the TDM configuration.
  • the TDM configuration would, per definition, apply to all RB sets but its format would be identical to that of an RB set group, why an additional such row could be used.
  • a specific index can be used, e.g., an index exceeding the configured # RB set groups.
  • the donor-CU can update the availability combinations (e.g., the length and values of a resourceAvailability) based operational information (or feedback) from the parent and IAB -nodes.
  • the lAB-donor sends the shared time-/frequency-domain availabilityCombinations to both the parent node and lAB-node.
  • the signaling can be an RRC message or via 0AM (Operation, Administration, Management).
  • the IAB- donor can send to the parent node and the lAB-node about the association information for the TDM resourceAvailabilities to a certain RB set. In one example it can be an RB set with specific RB set index. In another example it can be an RB set with specific resource configuration, e.g., Hard or NA configurations.
  • the signaling can be e.g., a RRC or an Fl message.
  • the IAB -donor provides the semi-static TDM and/or FDM multiplexing resource configuration to the lAB-node, and optionally to the parent node.
  • one or multiple availabilityCombinationlds in the availabilityCombinations can be reserved only for availability indication for TDM soft resources, i.e., TDM and FDM resource Availabilities have separate or separate sets of availabilityCombinationsIds.
  • TDM and FDM resource Availabilities have separate or separate sets of availabilityCombinationsIds.
  • the donor-CU or the parent node can send a higher layer parameter (e.g., via Fl, or RRC, or MAC CE) to indicate which resourceAvailability (with respect to the RB set) is associated to Al for TDM soft resource.
  • the TDM resourceAvailability can exploit the RB sets which only contains Hard or NA frequency resource, i.e., the TDM resourceAvailability is provided using a Hard, or NA RB set. Since the semi-static H/S/NA configuration is known to donor-CU, parent-node, and the lAB-node, thereby a higher layer signaling to indicate an association between the TDM resourceAvailability and an RB set can be avoided.
  • FIG. 15 presents an example where the availabilityCombinations table has been modified to include a dedicated TDM resourceAvailability also for availabilityCombinationlds defined for FDM.
  • availabilityCombinationld 0 includes a TDM row, indicating the resourceAvailability to use for TDM operation.
  • TDM can, e.g., be indicated with an RB set group index that is outside of the set of configured RB set group indices.
  • a time-domain resourceAvailability is provided to a sequence of mixed TDM and FDM slots, it can only provide valid availability indication to TDM slots.
  • a frequency-domain resourceAvailability is provided to a sequence of mixed TDM and FDM slots, it is only valid to FDM slots.
  • FIG 16 shows an example of the usage of a dedicated availabilityCombinationld for FDM resourceAvailability in mixed TDM and FDM slots.
  • a shared availabilityCombinationld for TDM and FDM resourceAvailabilities can be used to configure a DO format 2_5 for a sequence of mixed TDM and FDM soft slots.
  • An example is given in where the IAB DU cell is configured with three FDM soft slots (Slot 0,1,5), two FDM hard slots (Slot 2, 6), one TDM hard slot (slot 3) and one TDM Soft slot (slot 4).
  • a shared availabilityCombinationld 0
  • availabilityCombinationld 0
  • the Al for TDM soft slots can use the resourceAvailability elements from the TDM resourceAvailability, which is configured for RB set 0; while the Al for FDM soft slots can use the resourceAvailability elements from the FDM resourceAvailability, which is configured for RB set 2,3.
  • the resourceAvailability elements for the 4 TDM and FDM soft slots are marked as shaded cells in Figure 17. Compared to the case with separated TDM and FDM availabilityCombinations in Figure 9, the number of the dynamic provision of DO format 2_5 is greatly reduced.
  • the donor CU configures the parent node with a list of resource availabilities and with a list of RB set group (rbSetGroups) associated to each entry of the resource availability list.
  • rbSetGroups a list of resource availabilities (and hence each list of RB set group) is associated to a specific configured availability combination ID (configAvailabilityCombinationld) configured in availabilityCombinations. Additionally, it can be indicated if the RB set group IDs associated to a configured availability combination ID and to a configured entry of the resource availability list are applicable only to FDM or to TDM or both.
  • the IAB node receiving the configuration assumes that both FDM and TDM may be applied for the associated entry of the resource availability list.
  • the RB set groups can be configured only for those resource availability entries associated to FDM, and that optionally they may be applied also to TDM.
  • the resourceAvailability associated to TDM operation mode can be derived, i.e. the ‘FDM’ flag will never be present since it will be assumed that FDM will be always applicable for the associated sets of RB set group IDs.
  • the RBSetGroup is included in ResourceAvailabilityPerCell, it refers to the resourceAvailability included in AvailabilityCombination-rl6, whereas all the other RB set groups included in ResourceAvailability-rl7 are associate to the respective entries in resource availability entries included in ResourceAvailability-rl 7.
  • Figure 18 provides a flowchart illustrating exemplary operations in an IAB node embodiment according to some embodiments disclosed herein.
  • operations begin in some embodiments with the IAB node providing an indication of resource multiplexing capability of the IAB node (block 1800).
  • the IAB node may receive an AvailabilityCombinations table (block 1802).
  • the IAB node may also receive one or more semi- static resource configurations comprising a TDD pattern and/or a H/S/NA configuration (block 1804).
  • the IAB node receive, from a parent IAB node, a DO format 2_5 message that addresses a TDM mode of operation and an FDM mode of operation (block 1806).
  • the IAB node identifies an availabilityCombinationlD associated with the received DO format 2_5 message (block 1808).
  • the IAB node determines a resource Availability indication associated with the FDM mode of operation based on the selected availabilityCombinationld (block 1810).
  • the IAB node determines a resourceAvailability indication associated with the TDM mode of operation, based on the determined resourceAvailability indication associated with the FDM mode of operation (block 1812).
  • the IAB node determines one of the TDM mode of operation and the FDM mode of operation as a configured mode of operation (block 1814). The IAB node then applies one of the resourceAvailability indication associated with the TDM mode of operation and the resourceAvailability indication associated with the FDM mode of operation based on the configured mode of operation (block 1816).
  • Figure 19 provides a flowchart illustrating exemplary operations in a IAB parent node embodiment according to some embodiments disclosed herein. Operations in Figure 19 in some examples begins with the IAB parent node receiving an indication of resource multiplexing capability of at least one IAB -DU cell of an IAB child node (block 1900). The IAB parent node may transmit, to the IAB child node, an indication of the RB set group to be associated with the TDM resourceAvailability (block 1902). The IAB parent node may receive a shared availabilityCombinations table for a TDM soft resource and a FDM soft resource (block 1904).
  • the IAB parent node determines a plurality of multiplexing modes for a corresponding plurality of slots of at least one IAB -DU cell of an IAB child node of the IAB parent node, wherein the IAB -DU cell is at least partially overlapping with a BWP of the IAB child node that is serviced by the IAB parent node; and the IAB child node is capable of operation in simultaneous operation (block 1906).
  • the IAB parent node determines an availabilityCombinationlD and an Al-index for the at least one IAB-DU cell and the plurality of slots (block 1908).
  • the IAB parent node then transmits a DO format 2_5 message comprising the availabilityCombination ID and the Al-index to the IAB child node (block 1910).
  • Figure 20 provides a flowchart illustrating exemplary operations in an IAB donor embodiment according to some embodiments disclosed herein.
  • operations begin with the IAB donor node receiving an indication of multiplexing capability from the IAB node for at least one IAB-DU cell (block 2000).
  • the IAB donor node configures a shared time- /frequency-domain availabilityCombinations for each of the at least one IAB-DU cell (block 2002).
  • the IAB donor node transmits the shared time-/frequency-domain availabilityCombinations to the IAB node and an IAB parent node of the IAB node (block 2004).
  • the IAB donor node determines a semi-static IAB-DU resource configuration including a TDD pattern, a TDM configuration, and/or a H/S/NA configuration (block 2006). The IAB donor node then signals the semi-static IAB-DU resource configuration to the IAB node (block 2008). In some embodiments, the IAB donor node may also signal an IAB-DU cell/carrier configuration to the IAB parent node (block 2010).
  • FIG. 21 shows an example of a communication system 2100 in accordance with some embodiments.
  • the communication system 2100 includes a telecommunication network 2102 that includes an access network 2104, such as a Radio Access Network (RAN), and a core network 2106, which includes one or more core network nodes 2108.
  • the access network 2104 includes one or more access network nodes, such as network nodes 2110A and 2110B (one or more of which may be generally referred to as network nodes 2110), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • 3GPP Third Generation Partnership Project
  • the network nodes 2110 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 2112A, 2112B, 2112C, and 2112D (one or more of which may be generally referred to as UEs 2112) to the core network 2106 over one or more wireless connections.
  • UE User Equipment
  • 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 2100 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 2100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 2112 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 2110 and other communication devices.
  • the network nodes 2110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 2112 and/or with other network nodes or equipment in the telecommunication network 2102 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 2102.
  • the core network 2106 connects the network nodes 2110 to one or more hosts, such as host 2116. These connections may be direct or indirect via one or more intermediary networks or devices.
  • the core network 2106 includes one more core network nodes (e.g., core network node 2108) 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 2108.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 2116 may be under the ownership or control of a service provider other than an operator or provider of the access network 2104 and/or the telecommunication network 2102, and may be operated by the service provider or on behalf of the service provider.
  • the host 2116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 2100 of Figure 21 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 2100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS
  • the telecommunication network 2102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 2102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 2102. For example, the telecommunication network 2102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and/or massive Machine Type Communication (mMTC)/massive Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 2112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 2104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 2104.
  • a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. be configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi-Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 2114 communicates with the access network 2104 to facilitate indirect communication between one or more UEs (e.g., UE 2112C and/or 2112D) and network nodes (e.g., network node 2110B).
  • the hub 2114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 2114 may be a broadband router enabling access to the core network 2106 for the UEs.
  • the hub 2114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 2114 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 2114 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 2114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 2114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 2114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 2114 may have a constant/persistent or intermittent connection to the network node 2110B.
  • the hub 2114 may also allow for a different communication scheme and/or schedule between the hub 2114 and UEs (e.g., UE 2112C and/or 2112D), and between the hub 2114 and the core network 2106.
  • the hub 2114 is connected to the core network 2106 and/or one or more UEs via a wired connection.
  • the hub 2114 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 2104 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 2110 while still connected via the hub 2114 via a wired or wireless connection.
  • the hub 2114 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 2110B.
  • the hub 2114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 2110B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 22 shows a UE 2200 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.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehicle-to- Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle- to-Everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by,
  • the UE 2200 includes processing circuitry 2202 that is operatively coupled via a bus 2204 to an input/output interface 2206, a power source 2208, memory 2210, a communication interface 2212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 22. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 2202 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 2210.
  • the processing circuitry 2202 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 2202 may include multiple Central Processing Units (CPUs).
  • the input/output interface 2206 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 2200.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 2208 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 2208 may further include power circuitry for delivering power from the power source 2208 itself, and/or an external power source, to the various parts of the UE 2200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 2208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 2208 to make the power suitable for the respective components of the UE 2200 to which power is supplied.
  • the memory 2210 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 2210 includes one or more application programs 2214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2216.
  • the memory 2210 may store, for use by the UE 2200, any of a variety of various operating systems or combinations of operating systems.
  • the memory 2210 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD- DVD High Density Digital Versatile Disc
  • HD- DVD High Density Digital Versatile Disc
  • HD- DVD Compact
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 2210 may allow the UE 2200 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 2210, which may be or comprise a device-readable storage medium.
  • the processing circuitry 2202 may be configured to communicate with an access network or other network using the communication interface 2212.
  • the communication interface 2212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2222.
  • the communication interface 2212 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 2218 and/or a receiver 2220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 2218 and receiver 2220 may be coupled to one or more antennas (e.g., the antenna 2222) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 2212 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS Global Positioning System
  • Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband CDMA
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR Fifth Generation
  • UMTS Worldwide Interoperability for Mobile communications
  • WiMax Ethernet
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • SONET Synchronous Optical Networking
  • ATM Asynchronous Transfer Mode
  • QUIC Quick User Datagram Protocol Internet Connection
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 2212, or via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. 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 loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare.
  • Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a
  • 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, 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.
  • FIG. 23 shows a network node 2300 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment in a telecommunication network.
  • Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
  • APs e.g., radio APs
  • BSs Base Stations
  • eNBs evolved Node Bs
  • gNBs NR Node Bs
  • BSs may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto BSs, pico BSs, micro BSs, or macro BSs.
  • a BS may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio BS may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR Transmission Point
  • MSR Multi-Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes
  • the network node 2300 includes processing circuitry 2302, memory 2304, a communication interface 2306, and a power source 2308.
  • the network node 2300 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 2300 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node 2300 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 2304 for different RATs) and some components may be reused (e.g., an antenna 2310 may be shared by different RATs).
  • the network node 2300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 2300.
  • the processing circuitry 2302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node 2300 components, such as the memory 2304, to provide network node 2300 functionality.
  • the processing circuitry 2302 includes a System on a Chip (SOC).
  • the processing circuitry 2302 includes one or more of Radio Frequency (RF) transceiver circuitry 2312 and baseband processing circuitry 2314.
  • RF Radio Frequency
  • the RF transceiver circuitry 2312 and the baseband processing circuitry 2314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of the RF transceiver circuitry 2312 and the baseband processing circuitry 2314 may be on the same chip or set of chips, boards, or units.
  • the memory 2304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 2302.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)
  • the memory 2304 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 2302 and utilized by the network node 2300.
  • the memory 2304 may be used to store any calculations made by the processing circuitry 2302 and/or any data received via the communication interface 2306.
  • the processing circuitry 2302 and the memory 2304 are integrated.
  • the communication interface 2306 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 2306 comprises port(s)/terminal(s) 2316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 2306 also includes radio front-end circuitry 2318 that may be coupled to, or in certain embodiments a part of, the antenna 2310.
  • the radio front-end circuitry 2318 comprises filters 2320 and amplifiers 2322.
  • the radio front-end circuitry 2318 may be connected to the antenna 2310 and the processing circuitry 2302.
  • the radio front-end circuitry 2318 may be configured to condition signals communicated between the antenna 2310 and the processing circuitry 2302.
  • the radio front-end circuitry 2318 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 2318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 2320 and/or the amplifiers 2322.
  • the radio signal may then be transmitted via the antenna 2310.
  • the antenna 2310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2318.
  • the digital data may be passed to the processing circuitry 2302.
  • the communication interface 2306 may comprise different components and/or different combinations of components.
  • the network node 2300 does not include separate radio front-end circuitry 2318; instead, the processing circuitry 2302 includes radio front-end circuitry and is connected to the antenna 2310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2312 is part of the communication interface 2306. In still other embodiments, the communication interface 2306 includes the one or more ports or terminals 2316, the radio front-end circuitry 2318, and the RF transceiver circuitry 2312 as part of a radio unit (not shown), and the communication interface 2306 communicates with the baseband processing circuitry 2314, which is part of a digital unit (not shown).
  • the antenna 2310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 2310 may be coupled to the radio front-end circuitry 2318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 2310 is separate from the network node 2300 and connectable to the network node 2300 through an interface or port.
  • the antenna 2310, the communication interface 2306, and/or the processing circuitry 2302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 2300. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 2310, the communication interface 2306, and/or the processing circuitry 2302 may be configured to perform any transmitting operations described herein as being performed by the network node 2300. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 2308 provides power to the various components of the network node 2300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 2308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2300 with power for performing the functionality described herein.
  • the network node 2300 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2308.
  • the power source 2308 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 2300 may include additional components beyond those shown in Figure 23 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 2300 may include user interface equipment to allow input of information into the network node 2300 and to allow output of information from the network node 2300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2300.
  • FIG 24 is a block diagram of a host 2400, which may be an embodiment of the host 2116 of Figure 21, in accordance with various aspects described herein.
  • the host 2400 may be or comprise various combinations of 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 2400 may provide one or more services to one or more UEs.
  • the host 2400 includes processing circuitry 2402 that is operatively coupled via a bus 2404 to an input/output interface 2406, a network interface 2408, a power source 2410, and memory 2412.
  • processing circuitry 2402 that is operatively coupled via a bus 2404 to an input/output interface 2406, a network interface 2408, a power source 2410, and memory 2412.
  • 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 22 and 23, such that the descriptions thereof are generally applicable to the corresponding components of the host 2400.
  • the memory 2412 may include one or more computer programs including one or more host application programs 2414 and data 2416, which may include user data, e.g. data generated by a UE for the host 2400 or data generated by the host 2400 for a UE.
  • Embodiments of the host 2400 may utilize only a subset or all of the components shown.
  • the host application programs 2414 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), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Coding
  • the host application programs 2414 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. Accordingly, the host 2400 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 2414 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 (DASH or MPEG-DASH), etc.
  • FIG. 25 is a block diagram illustrating a virtualization environment 2500 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 2500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs Virtual Machines
  • the node may be entirely virtualized.
  • Applications 2502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 2504 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 2506 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 2508A and 2508B (one or more of which may be generally referred to as VMs 2508), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 2506 may present a virtual operating platform that appears like networking hardware to the VMs 2508.
  • the VMs 2508 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 2506.
  • Different embodiments of the instance of a virtual appliance 2502 may be implemented on one or more of the VMs 2508, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV).
  • NFV 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 2508 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 2508, and that part of the hardware 2504 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 2508, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 2508 on top of the hardware 2504 and corresponds to the application 2502.
  • the hardware 2504 may be implemented in a standalone network node with generic or specific components.
  • the hardware 2504 may implement some functions via virtualization.
  • the hardware 2504 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 2510, which, among others, oversees lifecycle management of the applications 2502.
  • the hardware 2504 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 RAN or a BS.
  • some signaling can be provided with the use of a control system 2512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 26 shows a communication diagram of a host 2602 communicating via a network node 2604 with a UE 2606 over a partially wireless connection in accordance with some embodiments.
  • the host 2602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 2602 also includes software, which is stored in or is accessible by the host 2602 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 2606 connecting via an OTT connection 2650 extending between the UE 2606 and the host 2602.
  • a host application may provide user data which is transmitted using the OTT connection 2650.
  • the network node 2604 includes hardware enabling it to communicate with the host 2602 and the UE 2606 via a connection 2660.
  • the connection 2660 may be direct or pass through a core network (like the core network 2106 of Figure 21) 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 2606 includes hardware and software, which is stored in or accessible by the UE 2606 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 the UE 2606 with the support of the host 2602.
  • 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 the UE 2606 with the support of the host 2602.
  • an executing host application may communicate with the executing client application via the OTT connection 2650 terminating at the UE 2606 and the host 2602.
  • 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 2650 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
  • the OTT connection 2650 may extend via the connection 2660 between the host 2602 and the network node 2604 and via a wireless connection 2670 between the network node 2604 and the UE 2606 to provide the connection between the host 2602 and the UE 2606.
  • the connection 2660 and the wireless connection 2670, over which the OTT connection 2650 may be provided, have been drawn abstractly to illustrate the communication between the host 2602 and the UE 2606 via the network node 2604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 2602 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 2606.
  • the user data is associated with a UE 2606 that shares data with the host 2602 without explicit human interaction.
  • the host 2602 initiates a transmission carrying the user data towards the UE 2606.
  • the host 2602 may initiate the transmission responsive to a request transmitted by the UE 2606.
  • the request may be caused by human interaction with the UE 2606 or by operation of the client application executing on the UE 2606.
  • the transmission may pass via the network node 2604 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2612, the network node 2604 transmits to the UE 2606 the user data that was carried in the transmission that the host 2602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2614, the UE 2606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2606 associated with the host application executed by the host 2602.
  • the UE 2606 executes a client application which provides user data to the host 2602.
  • the user data may be provided in reaction or response to the data received from the host 2602.
  • the UE 2606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 2606. Regardless of the specific manner in which the user data was provided, the UE 2606 initiates, in step 2618, transmission of the user data towards the host 2602 via the network node 2604.
  • the network node 2604 receives user data from the UE 2606 and initiates transmission of the received user data towards the host 2602.
  • the host 2602 receives the user data carried in the transmission initiated by the UE 2606.
  • factory status information may be collected and analyzed by the host 2602.
  • the host 2602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 2602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 2602 may store surveillance video uploaded by a UE.
  • the host 2602 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 2602 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 2650 may be implemented in software and hardware of the host 2602 and/or the UE 2606.
  • sensors may be deployed in or in association with other devices through which the OTT connection 2650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 2650 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 2604. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 2602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2650 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by a network node implementing an Integrated Access and Backhaul (IAB) node for determining availability, the IAB node configured to selectively alternate between a Time-Division Multiplexing (TDM) mode of operation and a Frequency-Division Multiplexing (FDM) mode of operation, the method comprising:
  • Embodiment 2 The method of embodiment 1, further comprising, prior to receiving the DO format 2_5 message:
  • TDD Time Division Duplex
  • H/S/NA Hard/Soft/Not Available
  • Embodiment 3 The method of embodiment 2, wherein the resource Availability indication associated with the TDM mode of operation is indicated in the received AvailabilityCombinations table.
  • Embodiment 4 The method of any one of embodiments 1-2, wherein a resourceAvailability indication of an FDM Resource Block (RB) set group to be associated with the resourceAvailability indication associated with the TDM mode of operation.
  • RB FDM Resource Block
  • Embodiment 5 A network node (2300) implementing an Integrated Access and Backhaul (IAB) node for determining availability, the IAB node configured to selectively alternate between a Time-Division Multiplexing (TDM) mode of operation and a Frequency- Division Multiplexing (FDM) mode of operation, the network node comprising:
  • processing circuitry associated with the network interface, the processing circuitry configured to cause the network node to:
  • Embodiment 6 The network node of embodiment 5, wherein the processing circuitry is further configured cause the network node to perform the method of any one of embodiments 2-4.
  • Embodiment 7 A network node (2300) implementing an Integrated Access and
  • IAB Time-Division Multiplexing
  • FDM Frequency- Division Multiplexing
  • Embodiment 8 The network node of embodiment 7, wherein the network node is further adapted to perform the method of any one of embodiments 2-4.
  • Embodiment 9 A method performed by a network node implementing an Integrated Access and Backhaul (IAB) parent node for providing a resource availability indication, the method comprising:
  • IAB-DU IAB Distributed Unit
  • the IAB-DU cell is at least partially overlapping with a Bandwidth Part (BWP) of the IAB child node that is serviced by the IAB parent node; and
  • BWP Bandwidth Part
  • Embodiment 10 The method of embodiment 9, further comprising, prior to transmitting the DO format 2_5 message:
  • TDM Time-Division Multiplexing
  • FDM Frequency-Division Multiplexing
  • Embodiment 11 The method of embodiment 10, wherein the shared AvailabilityCombinations table indicates a TDM resourceAvailability.
  • Embodiment 12 The method of embodiment 11, wherein the shared AvailabilityCombinations table indicates a TDM resourceAvailability by mapping TDM to a specific Resource Block (RB) set group or includes a separate TDM row for an AvailabilityCombinationld.
  • RB Resource Block
  • Embodiment 13 The method of embodiment 12, further comprising, prior to receiving the shared availabilityCombinations table, transmitting (1902), to the IAB child node, an indication of the RB set group to be associated with the TDM resourceAvailability.
  • Embodiment 14 The method of embodiment 12, wherein the RB set group to be associated with the TDM resourceAvailability is determined from a specification or read from a file.
  • Embodiment 15 The method of any one of embodiments 9-14, wherein determining the availabilityCombinationlD and the Al-index is based on one or more of an expected traffic need, past traffic statistics, buffer utilization, propagation channel conditions, timing, and/or power control conditions between parent and child backhaul links.
  • Embodiment 16 A network node (2300) implementing an Integrated Access and Backhaul (IAB) parent node for providing a resource availability indication, the network node comprising:
  • processing circuitry associated with the network interface, the processing circuitry configured to cause the network node to:
  • IAB-DU IAB Distributed Unit
  • BWP Bandwidth Part
  • Embodiment 17 The network node of embodiment 16, wherein the processing circuitry is further configured cause the network node to perform the method of any one of embodiments 10-15.
  • Embodiment 18 A network node (2300) implementing an Integrated Access and Backhaul (IAB) parent node for providing a resource availability indication, the network node adapted to:
  • IAB Integrated Access and Backhaul
  • IAB-DU IAB Distributed Unit
  • the IAB-DU cell is at least partially overlapping with a Bandwidth Part (BWP) of the IAB child node that is serviced by the IAB parent node; and
  • BWP Bandwidth Part
  • Embodiment 19 The network node of embodiment 18, wherein the network node is further adapted to perform the method of any one of embodiments 10-15.
  • Embodiment 20 A method performed by a network node implementing an Integrated Access and Backhaul (IAB) donor node to provide availabilityCombinations and resource configuration to an IAB node for resource multiplexing configuration between IAB Distributed Unit IAB-DU and IAB Mobile Termination (IAB-MT) parts, the method comprising,
  • a semi-static IAB-DU resource configuration including a Time Division Duplex (TDD) pattern, a Time Division Multiplexing (TDM) configuration, and/or a Hard/Soft/Not Available (H/S/NA) configuration; and
  • TDD Time Division Duplex
  • TDM Time Division Multiplexing
  • H/S/NA Hard/Soft/Not Available
  • Embodiment 21 The method of embodiment 20, further comprising signaling (2010) an IAB-DU cell/carrier configuration to the IAB parent node.
  • Embodiment 22 A network node (2300) implementing an Integrated Access and Backhaul (IAB) donor node to provide availabilityCombinations and resource configuration to an IAB node for resource multiplexing configuration between IAB Distributed Unit IAB-DU and IAB Mobile Termination (IAB-MT) parts, the network node comprising:
  • IAB Integrated Access and Backhaul
  • processing circuitry associated with the network interface, the processing circuitry configured to cause the network node to:
  • a semi- static IAB-DU resource configuration including a Time- Division Duplex (TDD) pattern, a Time-Division Multiplexing (TDM) configuration, and/or a Hard/Soft/Not Available (H/S/NA) configuration; and
  • TDD Time- Division Duplex
  • TDM Time-Division Multiplexing
  • H/S/NA Hard/Soft/Not Available
  • Embodiment 23 The network node of embodiment 22, wherein the processing circuitry is further configured cause the network node to perform the method of embodiment 21.
  • Embodiment 24 A network node (2300) implementing an Integrated Access and Backhaul (IAB) donor node to provide availabilityCombinations and resource configuration to an IAB node for resource multiplexing configuration between IAB Distributed Unit IAB-DU and IAB Mobile Termination (IAB-MT) parts, the network node adapted to:
  • IAB Integrated Access and Backhaul
  • TDD Time-Division Multiplexing
  • H/S/NA Hard/Soft/Not Available
  • Embodiment 25 The network node of embodiment 24, wherein the network node is further adapted to perform the method of embodiment 21.

Landscapes

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

Abstract

Sont divulgués des systèmes et des procédés de conception conjointe de combinaisons de disponibilité dans le domaine temporel et fréquentiel pour des nœuds de liaison terrestre et d'accès intégré (IAB). Dans un mode de réalisation, un procédé exécuté par un nœud réseau mettant en œuvre un nœud IAB consiste à recevoir, d'un nœud IAB parent, un message de format 2_5 d'informations de commande de liaison descendante (DCI) concernant un mode de fonctionnement TDM et un mode de fonctionnement FDM. Le procédé consiste également à identifier un ID de combinaison de disponibilité associé au message, à déterminer une indication de disponibilité de ressource associée au FDM d'après l'ID de combinaison de disponibilité sélectionné, ainsi qu'à déterminer un TDM associé à une indication de disponibilité de ressource d'après l'indication de disponibilité de ressource déterminée associée au FDM. Le procédé consiste également à déterminer un mode de fonctionnement TDM et FDM en tant que mode de fonctionnement configuré, ainsi qu'à appliquer l'indication de disponibilité de ressource associée au FDM et l'indication de disponibilité de ressource associée au FDM d'après le mode de fonctionnement configuré.
PCT/IB2023/051090 2022-02-07 2023-02-07 Conception conjointe de disponibilité dans le domaine temporel et fréquentiel WO2023148705A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263307442P 2022-02-07 2022-02-07
US63/307,442 2022-02-07

Publications (1)

Publication Number Publication Date
WO2023148705A1 true WO2023148705A1 (fr) 2023-08-10

Family

ID=85321166

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/051090 WO2023148705A1 (fr) 2022-02-07 2023-02-07 Conception conjointe de disponibilité dans le domaine temporel et fréquentiel

Country Status (1)

Country Link
WO (1) WO2023148705A1 (fr)

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.213
CEWIT ET AL: "Discussions on enhancements to resource multiplexing between child and parent links of an IAB node", vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 7 August 2021 (2021-08-07), XP052038842, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_106-e/Docs/R1-2108161.zip R1-2108161.docx> [retrieved on 20210807] *
ERICSSON: "Resource multiplexing and dual connectivity in enhanced IAB", vol. RAN WG1, no. Online; 20211011 - 20211019, 1 October 2021 (2021-10-01), XP052059264, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_106b-e/Docs/R1-2110331.zip R1-2110331 Resource multiplexing and DC in enhanced IAB.docx> [retrieved on 20211001] *
INTEL CORPORATION: "Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node", vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 7 August 2021 (2021-08-07), XP052038516, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_106-e/Docs/R1-2107607.zip R1-2107607.docx> [retrieved on 20210807] *

Similar Documents

Publication Publication Date Title
WO2023203240A1 (fr) Cas d&#39;utilisation du découpage du réseau pour l&#39;accès sans fil fixe (fwa)
WO2023174858A1 (fr) Tables de ports d&#39;antenne pour canal partagé de liaison descendante physique avec un nombre accru de codes de division de fréquence
WO2023148705A1 (fr) Conception conjointe de disponibilité dans le domaine temporel et fréquentiel
WO2023088903A1 (fr) Indication de disponibilité pour l&#39;utilisation de ressources logicielles d&#39;un domaine temporel et d&#39;un domaine fréquentiel à accès et raccordement intégrés
WO2024125362A1 (fr) Procédé et appareil de commande de liaison de communication entre dispositifs de communication
WO2023141826A1 (fr) Procédés et appareils de planification de dispositif terminal
WO2023204751A1 (fr) Signalisation de nœud d&#39;iab
WO2023194485A1 (fr) Configuration de ressources dans des relais
WO2023095093A1 (fr) Signalisation mac ce destinée à supporter des fonctionnements à la fois conjoints et séparés de tci dl/ul
WO2024134606A1 (fr) Détermination d&#39;indications dynamiques de faisceaux multiples dans des réseaux répéteurs
WO2024035312A1 (fr) Dispositifs et procédés de commutation de transmission de liaison montante dynamique
WO2023078902A1 (fr) Transfert intercellulaire vers des nœuds iab mobiles
WO2023153991A1 (fr) Configuration de seuil de retard par support radio de données (drb)
WO2023083882A1 (fr) Autorisation configurée pour une transmission de liaison montante multi-panneau
WO2023075667A1 (fr) Calcul de l&#39;utilisation de blocs de ressources physiques dans une transmission de multiples points de transmission
WO2024072305A1 (fr) Systèmes et procédés de configuration de décalage bêta pour transmettre des informations de commande de liaison montante
WO2023211347A1 (fr) États de déclenchement apériodiques inactifs pour économie d&#39;énergie
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2024033731A1 (fr) Rapport de faisceau basé sur un groupe pour une transmission et une réception simultanées à panneaux multiples
WO2023203143A1 (fr) Configuration et programmation de porteuse pour systèmes en duplex intégral de sous-bande
WO2023166499A1 (fr) Systèmes et procédés pour partager un temps d&#39;occupation de canal dans des communications de liaison latérale
WO2023174859A1 (fr) Tables de port d&#39;antenne pour canal physique partagé de liaison montante ayant un nombre accru de codes de domaine de fréquence
WO2023152720A1 (fr) Systèmes et procédés de configuration de relation spatiale pour un signal de référence de sondage en vue d&#39;une compensation de retard de propagation
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2023170664A1 (fr) États de tci unifiés pour pdsch à multiples trp

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

Country of ref document: EP

Kind code of ref document: A1