WO2024134606A1 - Détermination d'indications dynamiques de faisceaux multiples dans des réseaux répéteurs - Google Patents

Détermination d'indications dynamiques de faisceaux multiples dans des réseaux répéteurs Download PDF

Info

Publication number
WO2024134606A1
WO2024134606A1 PCT/IB2023/063161 IB2023063161W WO2024134606A1 WO 2024134606 A1 WO2024134606 A1 WO 2024134606A1 IB 2023063161 W IB2023063161 W IB 2023063161W WO 2024134606 A1 WO2024134606 A1 WO 2024134606A1
Authority
WO
WIPO (PCT)
Prior art keywords
received
determining
indications
time resources
bits
Prior art date
Application number
PCT/IB2023/063161
Other languages
English (en)
Inventor
Magnus ÅSTRÖM
Boris Dortschy
Behrooz MAKKI
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 WO2024134606A1 publication Critical patent/WO2024134606A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H04B7/026—Co-operative diversity, e.g. using fixed or mobile stations as relays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H04L5/0025—Spatial division following the spatial signature of the channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H04B7/1555—Selecting relay station antenna mode, e.g. selecting omnidirectional -, directional beams, selecting polarizations

Definitions

  • the present disclosure relates to a cellular communications network and, more specifically, to the use of network-controlled repeaters in a cellular communications network.
  • Network densification refers to the deployment of multiple access points of different types in, e.g., metropolitan areas. Particularly, it is expected that in the future small nodes, such as relays, Integrated Access and Backhaul (IAB) nodes, repeaters, etc. will be densely deployed to support existing macro base stations (BS) serving UEs.
  • small nodes such as relays, Integrated Access and Backhaul (IAB) nodes, repeaters, etc.
  • the IAB node can well extend the coverage and/or increase the throughput of the system.
  • the IAB node may be a relatively complex and expensive node and thereby, depending on the deployment, alternative nodes with low complexity/cost may be required for, e.g., coverage blind spot removal.
  • a candidate type of network node is the radio frequency (RF) repeater which simply amplifies-and-forwards any signal that it receives.
  • RF repeaters have been considered in 2 nd Generation (2G), 3 rd Generation (3G), and 4 th Generation (4G) systems to supplement the coverage provided by regular full-stack base stations.
  • 2G 2 nd Generation
  • 3G 3 rd Generation
  • 4G 4 th Generation
  • the RF repeater lacks in, e.g., accurate beamforming which may limit its efficiency in, for instance, Frequency Range 2 (FR2).
  • FR2 Frequency Range 2
  • NCRs network-controlled repeaters
  • gNB New Radio
  • NCR is based on an amplify-and- forward relaying scheme, and it is likely to be limited to single-hop communication in stationary deployments with the focus on FR2.
  • NCR is an enhancement over conventional RF repeaters with the capability to receive and process side control information from the network.
  • Side control information could allow an NCR to perform an amplify-and-forward operation in a more efficient manner.
  • Potential benefits could include, for instance, mitigation of unnecessary noise amplification, transmissions and receptions with better spatial directivity, simplified network integration, etc.
  • NR NCR supports the following features as described in RP-222673, New WID on NR network-controlled repeaters, 3GPP TSG RAN Meeting #97-e, September 2022:
  • Figure 1 gives an example of an NCR deployment.
  • the NCR consists of two principal building blocks, namely, the NCR mobile termination (NCR-MT) and the NCR forwarding (NCR-Fwd) with the following functions (see “Chairman’s Notes”, 3GPP TSG RAN WG1 Meeting #109-e, May 2022):
  • the NCR-MT is defined as a functional entity to communicate with a NR base station (gNB) via Control link (C-link) to enable information exchanges.
  • the C-link is based on NR Uu interface.
  • the NCR-Fwd is defined as a functional entity to perform the amplify-and-forwarding of uplink (UL) / downlink (DL) RF signal between gNB and UE via backhaul link and access link.
  • the behavior of the NCR-Fwd will be controlled according to the received side control information from gNB.
  • the NCR is equipped with an antenna configuration, where a signal is first received in DL (or UL), and, e.g., after power amplification, transmitted further in DL (or UL). Since the NCR-Fwd module only amplifies and (analogously) beamforms the signal, no advanced receiver or transmitter chains are required, which reduces the cost and energy consumption compared to, for example, a normal Transmission and Reception Point (TRP).
  • TRP Transmission and Reception Point
  • the NCR-MT module is able to and used to exchange control and status signaling with a gNB, in the C-link shown in Figure 1, wherein this signaling controls the NCR.
  • the NCR-MT module supports at least a sub-set of UE functions.
  • the NCR-MT module might be equipped with antennae separated from the antennae used by the NCR-Fwd module.
  • the NCR-MT and NCR-Fwd modules will share antenna configurations. Particularly, motivated by cost-efficient implementation and a unified beamforming framework for the NCR-MT and NCR-Fwd functionalities, it is beneficial to have an architecture with shared NCR-MT and NCR-Fwd antennas on the BS-side.
  • the NCR-MT and the NCR-Fwd modules could be operating at the same, different, or overlapping frequencies.
  • the NCR-Fwd could operate at a high frequency band (FR2) and the NCR-MT could be operating at a low frequency band (FR1).
  • FR2 high frequency band
  • FR1 low frequency band
  • controlling the backhaul link will be much simplified if the NCR-MT and NCR-Fwd operate in the same carrier.
  • the NCR-Fwd’ s amplify-and-forward operation is controlled through the NCR-MT.
  • the NCR- MT could be directly responsible for the beamforming control on the access antenna side, i.e., to/from served UEs.
  • the beamforming on the access antenna side is operated by the NCR-Fwd under control of the NCR-MT.
  • the NCR-MT could be directly responsible for the beamforming control.
  • the beam control of the NCR UE-side should be conducted smoothly to minimize the impact on cell-common and UE-specific signals/channels which are forwarded towards the UEs.
  • a beam arrangement including both wider and narrower beams is required to accommodate both broadcast and unicast signals.
  • a method in a repeater node for dynamically configuring communication between a wireless network node to which the repeater node is associated and a wireless communication device comprises determining a number of bits used for a beam indication field in a Downlink Control Information (DO) from the wireless network node and determining a number of bits used for a time resource indication field in a DO.
  • the method further comprises receiving a DO from the wireless network node, determining a number of beam indications and associated time resources carried in the received DO, and applying the received DO according to the determined number of beam indications and the associated time resources carried in the received DO.
  • DO Downlink Control Information
  • repeater node is enabled to determine the number of beam indications and associated time resources carried in a DO for beam management of the repeater forwarding unit for operation of an associated access link, which in turn improves the flexibility and efficiency of the repeater-assisted network.
  • the repeater node decodes or interprets the received DO in accordance with the determined number of bits used for the beam indication field, the determined number of bits used for the time resource indication field, and the determined number of beam indications and associated time resources carried in the received DO.
  • determining the number of the bits for the beam indication field comprises determining the number of bits for the beam indication field explicitly based on beam configuration information from the wireless network node.
  • determining the number of the bits for the beam indication field comprises either: determining the number of bits for the beam indication field based on access link beams supported by the repeater node or determining the number of bits for the beam indication field based on access link beams used by the repeater node.
  • determining the number of the bits for the beam indication field comprises determining the number of bits for the beam indication field explicitly based on beam configuration information from the wireless network node, wherein the beam configuration information comprises either or both of: beam index mapping and requested service range or coverage area.
  • the beam configuration information comprises the beam index mapping, and the beam index mapping is associated to either or both of: beam types (e.g., wide or narrow) and spatial beam relations of an associated beam arrangement or constellation.
  • determining the number of the bits for the beam indication field comprises determining the number of the bits for the beam indication field based on a specified maximum number of beams that the repeater node can expect.
  • determining the number of bits for the time resource configuration comprises implicitly deriving the number of bits for the time resource indication field from one or more higher layer configured time resource parameters.
  • the one or more higher layer configured time resource parameters comprises a higher layer configured time resource identifier (ID).
  • the higher layer configured time resource ID is associated to either a single time resource or multiple time resources.
  • determining the number of beam indications and associated time resources carried in the received DO comprises deriving the number of beam indications carried in the received DO based on a higher layer configuration.
  • determining the number of beam indications and associated time resources carried in the received DO comprises: (a) determining the number of beam indications carried in the received DO based on an explicit indication in the received DO; or (b) determining the number of beam indications carried in the received DO based on an explicit indication in the received DO, based on a defined specification; or (c) determining the number of beam indications carried in the received DO based on an explicit indication in the received DO, according to a higher layer configuration.
  • determining the number of beam indications and associated time resources carried in the received DO comprises: (a) determining the number of beam indications and associated time resources carried in the received DO based on an explicit indication in the received DCI; or (b) determining the number of beam indications and associated time resources carried in the received DCI based on an explicit indication in the received DCI with a configured variable length bitfield; or (c) implicitly determining the number of beam indications and associated time resources carried in the received DCI based on a time resource indication; or (d) determining the number of beam indications and associated time resource carried in the received DCI based on a beam indication.
  • determining the number of beam indications and associated time resources carried in the received DCI is based on an explicit indication, and the explicit indication comprises: a beam number indication, an ending position of DCI information comprised in the DCI, or an indication of valid resource configurations.
  • the number of time resources indicated by the time resource indication field is larger than the number of beam indications provided in the received DCI, and an explicit signaling received by the repeater node from the wireless network node informs the repeater node about a number of valid time resources in the time resource indication.
  • a special beam index is used to indicate an end of a sequence of valid beams in the received DCI.
  • the number of beam indications is zero-padded such that a set of zero beams is configured for one or more bits in the received DCI not used for beam or time indication.
  • determining the number of beam indications and associated time resources carried in the received DCI comprises determining the number of beam indications and associated time resources based on a bitfield, comprised in the received DCI, for indicating the number of beam indications and associated time resources, and the bitfield for indicating the number of beam indications and associated time resources has a fixed starting location in the received DCI.
  • a subcarrier spacing or numerology associated to the time resources are either: explicitly indicated in the received DCI or implicitly provided.
  • a repeater node for dynamically configuring communication between a wireless network node to which the repeater node is associated and a wireless communication device is adapted to determine a number of bits used for a beam indication field in a DCI from the wireless network node and determine a number of bits used for a time resource indication field in a DCI.
  • the repeater node is further adapted to receive a DCI from the wireless network node, determine a number of beam indications and associated time resources carried in the received DCI, and apply the received DCI according to the determined number of beam indications and the associated time resources carried in the received DCI.
  • a repeater node for dynamically configuring communication between a wireless network node to which the repeater node is associated and a wireless communication device comprises processing circuitry configured to cause the repeater node to determine a number of bits used for a beam indication field in a DO from the wireless network node and determine a number of bits used for a time resource indication field in a DO.
  • the processing circuitry is further configured to cause the repeater node to receive a DCI from the wireless network node, determine a number of beam indications and associated time resources carried in the received DCI, and apply the received DCI according to the determined number of beam indications and the associated time resources carried in the received DCI.
  • Figure 1 gives an example of a Network-Controlled Repeater (NCR) deployment
  • Figure 2 gives an example to illustrate time domain operations at a New Radio (NR) base station
  • gNB and a repeater node, with respect to different periodic and aperiodic signals/channels, over ten (10) consecutive slots (SL), when serving first and second User Equipments (UEs), UE1 and UE2;
  • Figure 3 illustrates one example of a system in which embodiments of the present disclosure may be implemented
  • FIG 4 is a flowchart that illustrates a procedure performed by a repeater node (e.g., repeater node of Figure 3) in which the repeater node determines the number of beam indications and associated time resources carried in one Downlink Control Information (DCI), in accordance with one embodiment of the present disclosure;
  • a repeater node e.g., repeater node of Figure 3
  • DCI Downlink Control Information
  • Figure 5 shows an example where resources in one slot can be scheduled to one or multiple UEs, where switching between access link beams within one slot might be needed;
  • Figure 6 illustrates a beam mapping, i.e., a mapping between a beam index and a logical beam, that is specified with consideration to, for example, beam types (e.g., wide vs narrow beam), and/or the spatial relation of the beam constellation, in accordance with an embodiment of the present disclosure;
  • beam mapping i.e., a mapping between a beam index and a logical beam, that is specified with consideration to, for example, beam types (e.g., wide vs narrow beam), and/or the spatial relation of the beam constellation, in accordance with an embodiment of the present disclosure
  • FIG. 7 illustrates a scenario in which each Time Resource (TR) ID of the higher layer (e.g., RRC) parameter corresponds to one single time resource consisting of consecutive symbols within one slot;
  • TR Time Resource
  • FIG. 8 illustrates another scenario in which each Time Resource (TR) ID of the higher layer parameter will correspond to multiple time resources where each single time resource still consists of consecutive symbols;
  • Figure 9 shows an example of a communication system in accordance with some embodiments.
  • Figure 10 shows a UE in accordance with some embodiments
  • Figure 11 shows a network node in accordance with some embodiments
  • Figure 12 is a block diagram of a host, which may be an embodiment of the host of Figure 9, in accordance with various aspects described herein;
  • Figure 13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • repeater spatial filters refers to repeater node beams, or spatial precoders.
  • the legacy beam indication is used to help the User Equipment (UE) to find a suitable reception (Rx) beam for downlink (DL) reception and/or a suitable transmission (Tx) beam for uplink (UL) transmission.
  • the beam indication for DL is conveyed to the UE by indicating a Transmission Configuration Indicator (TCI) state to the UE, while in UL the beam indication can be conveyed by indicating a DL Reference Signal (DL-RS) or UL Reference Signal (UL-RS) as spatial relation (in NR Rel-15/16) or a TCI state (in NR Rel-17).
  • TCI Transmission Configuration Indicator
  • the beam mapping between a UL/DL beam index and a DL-RS or UL-RS in a TCI state is left to the implementation of the NR base station (gNB) and UE.
  • the gNB and the UE do not need to know about the beam arrangement at the other side.
  • the gNB will need to know about all the repeater beams and spatial relations between them, e.g., through repeater beam indices.
  • the repeater mobile termination (repeater- MT) (e.g., the NCR-MT in the case of an NCR) may know about the semi-static Time Division Duplexing (TDD) pattern (e.g., from System Information Block (SIB) 1, i.e., “SIB1”), i.e., slots and symbols used for different signals/channel, but neither the repeater-MT nor the repeater forwarding (repeater-Fwd) (e.g., NCR-Fwd in the case of an NCR) knows, and will not need to know, the instantaneous UE scheduling, for example: • If there is any UE scheduled for Physical Downlink Shared Channel (PDSCH) / Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH)/ . . .
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • Figure 2 gives an example to illustrate time domain operations at the gNB and the repeater node, with respect to different periodic and aperiodic signals/channels (e.g., Physical Downlink Control Channel (PDCCH)/PDSCH/PUSCH/PUCCH/Synchronization Signal Block (SSB)/Physical Random Access Channel (PRACH)), over 10 consecutive slots (SL), when serving UE1 and UE2.
  • PDCCH Physical Downlink Control Channel
  • SSB Synchromonization Signal Block
  • PRACH Physical Random Access Channel
  • SLO the cell common PDCCH is broadcasted to the repeater node and both UE1 and UE2, whilst the PDSCH is scheduled to UE1, repeater node (i.e., repeater-MT), and UE2 in SLO, SL1, and SL3, respectively.
  • the diagonal line indicates the time resource is NOT used in communication, e.g., between gNB and the repeater node, or between the repeater node and UE1, etc.
  • the wide-spaced downward diagonal striped patten represents the time resource when the repeater-Fwd is in use, i.e., where a repeater beam switching may take place.
  • the close-spaced upward diagonal striped pattern indicates the time resource in which the Repeater- Fwd forwards the periodic signals/channels between the gNB and UEs, while the vertical striped pattern indicates the time resource in which the Repeater-Fwd forwards the dynamic scheduled signals/channels between the gNB and the UEs.
  • a method in a network-controlled repeater for dynamically configuring communication between a wireless network node to which the network-controlled repeater is associated and a wireless communication device comprises determining a number of bits used for a beam indication field in a DO, determining a number of bits used for a time resource indication field in a DO, receiving a DO from the wireless network node, determining a number of beam indications and associated time resources carried in the received DO (e.g., based on the determined number of bits used for the beam indication field and the determined number of bits used for the time resource field), and applying the received DO according to the determined number of beam indications and the associated time resources carried in the received DO.
  • determining the number of the bits for the beam indication field comprises either: (a) determining the number of bits for the beam indication field implicitly based on access link beams supported by the network-controlled repeater node; or (b) determining the number of bits for the beam indication field implicitly based on access link beams used by the network-controlled repeater node; or (c) determining the number of bits for the beam indication field explicitly based on beam configuration information from the wireless network node.
  • determining the number of the bits for the beam indication field comprises determining the number of bits for the beam indication field explicitly based on beam configuration information from the wireless network node, wherein the beam configuration information comprises either or both of: beam index mapping and request service range, etc.
  • the beam configuration information comprises the beam indication mapping, and the beam index mapping is associated to either or both of: beam types (e.g., wide or narrow beams) and spatial beam relations of an associated beam arrangement or constellation.
  • determining the number of the bits for the beam indication field comprises determining the number of the bits for the beam indication field based on a specified maximum number of beams that the network-controlled repeater can expect.
  • determining the number of bits for the time resource configuration comprises implicitly deriving the number of bits for the time resource configuration from one or more higher layer configured time resource parameters.
  • the one or more higher layer configured time resource parameters comprises a higher layer configured time resource ID.
  • the higher layer configured time resource ID is associated to either a single time resource or multiple time resources.
  • determining the number of beam indications and associated time resources carried in the received DO comprises: (a) determining the number of beam indications carried in the received DO based on an explicit indication in the received DO; or (b) determining the number of beam indications carried in the received DO based on an explicit indication in the received DO, based on a defined specification; or (c) determining the number of beam indications carried in the received DO based on an explicit indication in the received DO, according to a higher layer configuration (e.g., provided via RRC); or (d) implicitly deriving the number of beam indications carried in the received DO based on a higher layer configuration (e.g., provided via RRC).
  • a higher layer configuration e.g., provided via RRC
  • implicitly deriving the number of beam indications carried in the received DO based on a higher layer configuration (e.g., provided via RRC).
  • determining the number of beam indications and associated time resources carried in the received DO comprises: (a) determining the number of beam indications and associated time resources carried in the received DO based on an explicit indication in the received DO; or (b) determining the number of beam indications and associated time resources carried in the received DO based on an explicit indication in the received DCI with a configured variable length bitfield; or (c) implicitly determining the number of beam indications and associated time resources carried in the received DCI based on a time resource indication.
  • the explicit indication comprises a beam number indication or an ending position of DCI information comprised in the DCI or indication of valid resource configurations.
  • the number of time resources indicated by the time resource indication field is larger than the number of beam indications provided in the received DCI, and an explicit signaling received by the network-controlled repeater from the wireless network node informs the network-controlled repeater about a number of valid time resources in the time resource indication.
  • a special beam index is used to indicate an end of a sequence of valid beams.
  • the number of beam indications is zero-padded such that a set of zero beams is configured for one or more remaining DCI bits.
  • the bitfield for indicating the number of beam indications and associated time resources has a fixed starting location in the received DCI.
  • a subcarrier spacing or numerology associated to the time resources are either: explicitly indicated in the DCI or implicitly provided (e.g., following an active bandwidth part of a repeater-MT of the network-controlled repeater).
  • Embodiments of the present disclosure may enable the repeater node to determine the number of beam indications and associated time resources carried in one DCI for the beam management of the repeater-FWD unit for operation of the access links. This enables proper beam configuration of the beamforming management and improves the flexibility and efficiency of the repeater-assisted networks and addresses one of the main objectives of the 3GPP Rel-18 WID on NCRs.
  • FIG. 3 illustrates one example of a system 300 in which embodiments of the present disclosure may be implemented.
  • the system 300 includes a network node 302 (e.g., a gNB) communicating with one or more destination nodes 306-1, 306-2, and 306-3 (e.g., User Equipments (UEs)) in wireless communication links, at least some of which are relayed by a repeater node 304 (e.g., network- controlled repeater).
  • UEs User Equipments
  • the repeater node 304 performs the procedure of Figure 4. As such, the details of the embodiments described above about the procedure of Figure 4 and the operation of an NCR are applicable here to the repeater node 304.
  • FIG. 4 is a flowchart that illustrates a procedure performed by a repeater node (e.g., repeater node 304) in which the repeater node determines the number of beam indications and associated time resources carried in one DO, in accordance with one embodiment of the present disclosure.
  • one DO may consist of a sequence of spatial resource indications, i.e., beams, and associated time resources (e.g., in slots and/or symbols).
  • each beam indication will be allocated one beam indication field, while each time resource indication field can potentially be assigned to one time resource or to multiple time resources.
  • Figure 5 shows an example where resources in one slot can be scheduled to one or multiple UEs, where switching between access link beams within one slot might be needed.
  • Figure 5 shows an example illustrating multiple UEs scheduled in the same slot. The UEs could be served by different access link beams, therefore beam switching could be needed within a slot or between different slots.
  • the solid white boxes in Figure 5 represent time resources allocated to periodic channels which are controlled by semi-static beam configurations. Depending on the scheduling horizon of the controlling network node, one DO may carry beam indications and the associated time resources for single or multiple slots.
  • the repeater node determines the number of bits assigned to one beam indication field in the DO, based on for example (not limited to) the number of beams to be used for access link.
  • the determination may rely on the number of repeater node supported beams, e.g., when all supported beams are to be used for access link (opposite to using only a subset of supported beams).
  • the determination may be based on the beam configuration from a controlling network node.
  • the repeater node receives the beam configuration information from the controlling network node, which can be an Operations and Management (0AM) node, gNB, etc.
  • the beam configuration information may contain information regarding beam mapping, and/or required coverage information etc.
  • the beam mapping i.e., a mapping between a beam index and a logical beam is specified with consideration to, for example, beam types (e.g., wide vs narrow beam), and/or the spatial relation of the beam constellation, as illustrated in Figure 6.
  • the number of bits is related to a specified maximum number of beams that the repeater node can expect.
  • the repeater node determines the number of bits used for one time resource indication field in the DO from the higher layer configured time resource parameters.
  • Two examples are given below in Figure 7 and Figure 8, illustrating the case of a time resource indication field indicating one time resource or multiple time resources, respectively.
  • the number of bits used for one time resource indication field is a function of the size (in terms of number of entries/rows) of the higher layer configured time resource parameters. It could be the minimum number of required bits to index all table entries.
  • FIG. 7 illustrates a scenario that each Time Resource (TR) ID of the higher layer (e.g., RRC) parameter corresponds to one single time resource consisting of consecutive symbols within one slot.
  • the single time resource can be, for example, described by a combination of a slot offset, a starting symbol and a duration of consecutive symbols (see Figure 7).
  • each beam indication field in the DO has a corresponding time resource indication field, which means there will be equal number of time indication and beam indication fields in the DO.
  • each Time Resource (TR) ID of the higher layer parameter will correspond to multiple time resources where each single time resource still consists of consecutive symbols.
  • the DO consists of a single time resource indication field and multiple beam indication fields.
  • Each Time Resource ID may be mapped to a different number of time resources.
  • the repeater node receives a DO from the gNB and determines the number of beam indications carried in the DO and the associated time resources carried in the DO.
  • the number of beam indications and the associated time resources are explicitly indicated in the DO, for example there is a dedicated field located in the DO (depicted as the “beam number’’ field).
  • the bitfield can be allocated with fixed number of bits and fixed location in the DO, as provided in a specification.
  • the number of beam indications and the associated time resources is explicitly indicated in the DO, with a configured (e.g., by Radio Resource Control (RRC)) variable length of the bitfield.
  • RRC Radio Resource Control
  • the network flexibility is improved on a selection of the number bits used for the beam indication field and the number of bits used for the time resource indication.
  • the length of the bitfield is explicitly provided in the higher layer parameter (e.g., RRC etc.).
  • the length of the bitfield is implicitly derived based on the total number of the configured Time Resource IDs (i.e., the number of rows in the RRC configuration table in Figure 7 and Figure 8).
  • the number of beam indications and the associated time resources is implicitly determined from time resource indication itself.
  • Time Resource ID When a higher layer configured Time Resource ID is assigned to multiple time resources, it may not need an additional explicit signaling to inform the repeater node about the number of beam indications carried in the DCI, if all the time resources will have a corresponding beam indication in the DCI.
  • the number of beams can be derived from the number of time resources, and the field indicated as “beam number” in Figure 8 can be omitted.
  • the number of time resources indicated by a single time resource indication field may be larger than the number of beam indications provided in the DCI, and an explicit signaling can be used to inform about the number of valid time resources in the single time resource indication.
  • the explicit signaling may not indicate the number of valid resources but indicate a starting and/or ending position of the valid time resources in the sequence of multiple indicated time resources (e.g., TRs could start for TR ID 2 from TR 2_1 in Figure 8).
  • a special beam index is used to indicate the end of, for example, a sequence of valid beams, i.e., beams to be used for access link operation (can be RRC or 0AM configured).
  • the number of beam indications is zero-padded such that a set of zero beams, or null beam (implying dynamically indicating that no beam is to be used) is configured for the remaining DCI bits.
  • the bitfield for indicating the number of beam indications (field beam number in Figure 7 and Figure 8) and associated time resources has a fixed starting location in the DCI, for example from bit 0 etc.
  • the repeater node applies the received DCI according to the determined number of beam indications and the associated time resource. Note that the repeater node decodes or interprets the received DCI in accordance with the determined number of bits used for the beam indication field, the determined number of bits used for the time resource indication field, and the determined number of beam indications and associated time resources carried in the received DCI
  • a reference subcarrier spacing (SCS) or numerology configuration for the time resource indication is explicitly provided, for example in the same beam indication DCI.
  • the SCS/numerology configuration for the dynamic beam indication is implicitly provided, for example following the active bandwidth part (BWP) of the repeater-MT.
  • Figure 9 shows an example of a communication system 900 in accordance with some embodiments.
  • the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a Radio Access Network (RAN), and a core network 906, which includes one or more core network nodes 908.
  • the access network 904 includes one or more access network nodes, such as network nodes 910A and 910B (one or more of which may be generally referred to as network nodes 910), 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 910 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 912A, 912B, 912C, and 912D (one or more of which may be generally referred to as UEs 912) to the core network 906 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 900 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 900 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 912 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 910 and other communication devices.
  • the network nodes 910 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 912 and/or with other network nodes or equipment in the telecommunication network 902 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 902.
  • the core network 906 connects the network nodes 910 to one or more hosts, such as host 916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 906 includes one or more core network nodes (e.g., core network node 908) 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 908.
  • 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 (SIDE), 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
  • SIDE Subscription Identifier De- Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and/or the telecommunication network 902, and may be operated by the service provider or on behalf of the service provider.
  • the host 916 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 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 900 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 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.
  • WiMax Worldwide Interoperability for Microwave Access
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave
  • NFC Near Field Communication
  • LiFi LiFi
  • LPWAN Low Power Wide Area Network
  • the telecommunication network 902 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 902. For example, the telecommunication network 902 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 912 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904.
  • 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 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912C and/or 912D) and network nodes (e.g., network node 910B).
  • the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 914 may be a broadband router enabling access to the core network 906 for the UEs.
  • the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 914 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 914 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 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 914 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 914 may have a constant/per sis tent or intermittent connection to the network node 91 OB.
  • the hub 914 may also allow for a different communication scheme and/or schedule between the hub 914 and UEs (e.g., UE 912C and/or 912D), and between the hub 914 and the core network 906.
  • the hub 914 is connected to the core network 906 and/or one or more UEs via a wired connection.
  • the hub 914 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 904 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection.
  • the hub 914 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 910B.
  • the hub 914 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 910B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • eMTC
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Every thing (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehicle-to- Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle-to-Every thing
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a power source 1008, memory 1010, a communication interface 1012, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 10. 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 1002 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 1010.
  • the processing circuitry 1002 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 1002 may include multiple Central Processing Units (CPUs).
  • the input/output interface 1006 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 1000.
  • Examples of an input device include a touch-sensitive or presencesensitive 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 1008 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 1008 may further include power circuitry for delivering power from the power source 1008 itself, and/or an external power source, to the various parts of the UE 1000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 1008.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied.
  • the memory 1010 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 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016.
  • the memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1010 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD-DVD High Density Digital Versatile Disc
  • HDDS Holographic Digital Data Storage
  • DIMM Dual In-line Memory Module
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 1010 may allow the UE 1000 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 1010, which may be or comprise a device -readable storage medium.
  • the processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012.
  • the communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022.
  • the communication interface 1012 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 1018 and/or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., the antenna 1022) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1012 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 1012, 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 item-tracking device,
  • AR
  • a UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1000 shown in Figure 10.
  • 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.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • FIG. 11 shows a network node 1100 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment in a telecommunication network.
  • network nodes examples 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)). Note that this description of the network node 1100 is also applicable to a network controlled repeater (NCR) such as that described above.
  • 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).
  • RRUs Remote Radio Units
  • RRHs Remote Radio Heads
  • Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • 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 e.g.,
  • the network node 1100 includes processing circuitry 1102, memory 1104, a communication interface 1106, and a power source 1108.
  • the network node 1100 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 1100 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 1100 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., an antenna 1110 may be shared by different RATs).
  • the network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, 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 1100.
  • the processing circuitry 1102 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 1100 components, such as the memory 1104, to provide network node 1100 functionality.
  • the processing circuitry 1102 includes a System on a Chip (SOC).
  • the processing circuitry 1102 includes one or more of Radio Frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114.
  • RF Radio Frequency
  • the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 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 1112 and the baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units.
  • the memory 1104 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 1102.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer
  • the memory 1104 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 1102 and utilized by the network node 1100.
  • the memory 1104 may be used to store any calculations made by the processing circuitry 1102 and/or any data received via the communication interface 1106.
  • the processing circuitry 1102 and the memory 1104 are integrated.
  • the communication interface 1106 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 1106 comprises port(s)/terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110.
  • the radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122.
  • the radio front-end circuitry 1118 may be connected to the antenna 1110 and the processing circuitry 1102.
  • the radio front-end circuitry 1118 may be configured to condition signals communicated between the antenna 1110 and the processing circuitry 1102.
  • the radio front-end circuitry 1118 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 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1120 and/or the amplifiers 1122.
  • the radio signal may then be transmitted via the antenna 1110.
  • the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118.
  • the digital data may be passed to the processing circuitry 1102.
  • the communication interface 1106 may comprise different components and/or different combinations of components.
  • the network node 1100 does not include separate radio frontend circuitry 1118; instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes the one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112 as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).
  • the antenna 1110 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port.
  • the antenna 1110, the communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1100. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node 1100. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 1108 provides power to the various components of the network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein.
  • the network node 1100 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 1108.
  • the power source 1108 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 1100 may include additional components beyond those shown in Figure 11 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 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100.
  • FIG 12 is a block diagram of a host 1200, which may be an embodiment of the host 916 of Figure 9, in accordance with various aspects described herein.
  • the host 1200 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 1200 may provide one or more services to one or more UEs.
  • the host 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and memory 1212. 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 10 and 11, such that the descriptions thereof are generally applicable to the corresponding components of the host 1200.
  • the memory 1212 may include one or more computer programs including one or more host application programs 1214 and data 1216, which may include user data, e.g. data generated by a UE for the host 1200 or data generated by the host 1200 for a UE.
  • Embodiments of the host 1200 may utilize only a subset or all of the components shown.
  • the host application programs 1214 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 (HE VC), Advanced Video Coding (A VC), 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
  • HE VC High Efficiency Video Coding
  • a VC 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 (A
  • the host application programs 1214 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 1200 may select and/or indicate a different host for Over- The-Top (OTT) services for a UE.
  • the host application programs 1214 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. 13 is a block diagram illustrating a virtualization environment 1300 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 1300 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 virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1300 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1304 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 1306 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1308 A and 1308B (one or more of which may be generally referred to as VMs 1308), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1306 may present a virtual operating platform that appears like networking hardware to the VMs 1308.
  • the VMs 1308 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1306.
  • Different embodiments of the instance of a virtual appliance 1302 may be implemented on one or more of the VMs 1308, 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 1308 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 1308, and that part of the hardware 1304 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 1308, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1308 on top of the hardware 1304 and corresponds to the application 1302.
  • the hardware 1304 may be implemented in a standalone network node with generic or specific components.
  • the hardware 1304 may implement some functions via virtualization.
  • the hardware 1304 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 1310, which, among others, oversees lifecycle management of the applications 1302.
  • the hardware 1304 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 1312 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 14 shows a communication diagram of a host 1402 communicating via a network node 1404 with a UE 1406 over a partially wireless connection in accordance with some embodiments.
  • the UE such as the UE 912A of Figure 9 and/or the UE 1000 of Figure 10
  • the network node such as the network node 910A of Figure 9 and/or the network node 1100 of Figure 11
  • the host such as the host 916 of Figure 9 and/or the host 1200 of Figure 12
  • embodiments of the host 1402 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1402 also includes software, which is stored in or is accessible by the host 1402 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 1406 connecting via an OTT connection 1450 extending between the UE 1406 and the host 1402. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1450.
  • the network node 1404 includes hardware enabling it to communicate with the host 1402 and the UE 1406 via a connection 1460.
  • connection 1460 may be direct or pass through a core network (like the core network 906 of Figure 9) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like the core network 906 of Figure 9
  • 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 1406 includes hardware and software, which is stored in or accessible by the UE 1406 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 1406 with the support of the host 1402.
  • 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 1406 with the support of the host 1402.
  • an executing host application may communicate with the executing client application via the OTT connection 1450 terminating at the UE 1406 and the host 1402.
  • 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 1450 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 1450 may extend via the connection 1460 between the host 1402 and the network node 1404 and via a wireless connection 1470 between the network node 1404 and the UE 1406 to provide the connection between the host 1402 and the UE 1406.
  • the connection 1460 and the wireless connection 1470, over which the OTT connection 1450 may be provided, have been drawn abstractly to illustrate the communication between the host 1402 and the UE 1406 via the network node 1404, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1402 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 1406.
  • the user data is associated with a UE 1406 that shares data with the host 1402 without explicit human interaction.
  • the host 1402 initiates a transmission carrying the user data towards the UE 1406.
  • the host 1402 may initiate the transmission responsive to a request transmitted by the UE 1406.
  • the request may be caused by human interaction with the UE 1406 or by operation of the client application executing on the UE 1406.
  • the transmission may pass via the network node 1404 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1412, the network node 1404 transmits to the UE 1406 the user data that was carried in the transmission that the host 1402 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1414, the UE 1406 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1406 associated with the host application executed by the host 1402.
  • the UE 1406 executes a client application which provides user data to the host 1402.
  • the user data may be provided in reaction or response to the data received from the host 1402.
  • the UE 1406 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 1406. Regardless of the specific manner in which the user data was provided, the UE 1406 initiates, in step 1418, transmission of the user data towards the host 1402 via the network node 1404.
  • the network node 1404 receives user data from the UE 1406 and initiates transmission of the received user data towards the host 1402.
  • the host 1402 receives the user data carried in the transmission initiated by the UE 1406.
  • factory status information may be collected and analyzed by the host 1402.
  • the host 1402 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1402 may store surveillance video uploaded by a UE.
  • the host 1402 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 1402 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 1450 may be implemented in software and hardware of the host 1402 and/or the UE 1406.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1450 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 1450 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1404. 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 1402.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1450 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 in a repeater node for dynamically configuring communication between a wireless network node to which the repeater node is associated and a wireless communication device, the method comprising:
  • Embodiment 2 The method of embodiment 1 wherein the repeater node decodes or interprets the received DCI in accordance with the determined number of bits used for the beam indication field, the determined number of bits used for the time resource indication field, and the determined number of beam indications and associated time resources carried in the received DCI.
  • Embodiment 3 The method of embodiment 1 or 2 wherein determining (400) the number of the bits for the beam indication field comprises either:
  • Embodiment 4 The method of embodiment 1 or 2 wherein determining (400) the number of the bits for the beam indication field comprises determining (400) the number of bits for the beam indication field explicitly based on beam configuration information from the wireless network node, wherein the beam configuration information comprises either or both of:
  • Embodiment 5 The method of embodiment 4 wherein the beam configuration information comprises the beam indication mapping, and the beam index mapping is associated to either or both of:
  • beam types e.g., wide or narrow beams
  • Embodiment 6 The method of embodiment 1 or 2 wherein determining (400) the number of the bits for the beam indication field comprises determining (400) the number of the bits for the beam indication field based on a specified maximum number of beams that the repeater node can expect.
  • Embodiment 7 The method of any of embodiments 1 to 6 wherein determining (402) the number of bits for the time resource configuration comprises implicitly deriving the number of bits for the time resource configuration from one or more higher layer configured time resource parameters.
  • Embodiment 8 The method of embodiment 7 wherein the one or more higher layer configured time resource parameters comprises a higher layer configured time resource ID.
  • Embodiment 9 The method of embodiment 8 wherein the higher layer configured time resource ID is associated to either a single time resource or multiple time resources.
  • Embodiment 10 The method of any of embodiments 1 to 9 wherein determining (404) the number of beam indications and associated time resources carried in the received DO comprises:
  • Embodiment 11 The method of any of embodiments 1 to 9 wherein determining (404) the number of beam indications and associated time resources carried in the received DO comprises:
  • Embodiment 12 The method of embodiments 10 or 11 wherein determining (404) the number of beam indications and associated time resources carried in the received DCI comprises either (a), (b), or (c) of embodiment 10 or either (a) or (b) of embodiment 11, and the explicit indication comprises:
  • Embodiment 13 The method any of embodiments 1 to 12 wherein the number of time resources indicated by the time resource indication field is larger than the number of beam indications provided in the received DCI, and an explicit signaling received by the repeater node from the wireless network node informs the repeater node about a number of valid time resources in the time resource indication.
  • Embodiment 14 The method of any of embodiments 1 to 13 wherein a special beam index is used to indicate an end of a sequence of valid beams in the received DCI.
  • Embodiment 15 The method of any of embodiments 1 to 14 wherein the number of beam indications is zero-padded such that a set of zero beams (or null beams) is configured for one or more remaining DCI bits (e.g., one or more bits in the received DCI not used for beam or time indication).
  • Embodiment 16 The method of any of embodiments 1 to 15 wherein the bitfield for indicating the number of beam indications and associated time resources has a fixed starting location in the received DCI.
  • Embodiment 17 The method of any of embodiments 1 to 16 wherein a subcarrier spacing or numerology associated to the time resources are either: explicitly indicated in the DCI or implicitly provided (e.g., following an active bandwidth part of a repeater-MT of the repeater node).
  • Embodiment 18 A repeater node adapted to perform the method of any of embodiments 1 to 17.
  • Embodiment 19 A repeater node comprising processing circuitry configured to cause the repeater node to perform the method of any of embodiments 1 to 17.

Landscapes

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

Abstract

L'invention concerne des systèmes et des procédés de détermination d'indications dynamiques de faisceaux multiples dans un réseau répéteur. Dans un mode de réalisation, un procédé dans un nœud répéteur permettant d'établir de manière dynamique une communication entre un nœud de réseau sans fil auquel est associé le nœud répéteur et un dispositif de communication sans fil, consiste en la détermination d'un nombre de bits utilisés pour un champ d'indication de faisceau dans des informations de commande de liaison descendante (DCI) provenant du nœud de réseau sans fil et la détermination d'un nombre de bits utilisés pour un champ d'indication de ressource temporelle dans une DCI. Le procédé consiste en outre en la réception de DCI en provenance du nœud de réseau sans fil, la détermination d'un nombre d'indications de faisceau et de ressources temporelles associées transportées dans les DCI reçues, et l'application des DCI reçues en fonction du nombre déterminé d'indications de faisceau et des ressources temporelles associées transportées dans les DCI reçues.
PCT/IB2023/063161 2022-12-22 2023-12-22 Détermination d'indications dynamiques de faisceaux multiples dans des réseaux répéteurs WO2024134606A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263434561P 2022-12-22 2022-12-22
US63/434,561 2022-12-22

Publications (1)

Publication Number Publication Date
WO2024134606A1 true WO2024134606A1 (fr) 2024-06-27

Family

ID=89619555

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/063161 WO2024134606A1 (fr) 2022-12-22 2023-12-22 Détermination d'indications dynamiques de faisceaux multiples dans des réseaux répéteurs

Country Status (1)

Country Link
WO (1) WO2024134606A1 (fr)

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"Chairman's Notes", 3GPP TSG RAN WG1 MEETING #109-E, May 2022 (2022-05-01)
"Chairman's Notes", 3GPP TSG RAN WG1 MEETING #110-BIS-E, October 2022 (2022-10-01)
"With these recommendations, NR NCR supports the following features as described in RP-222673, New WID on NR network-controlled repeaters", 3GPP TECHNICAL REPORT (TR) 38.867 V1.0.0., September 2022 (2022-09-01)
CATT: "Discussion on signaling for side control information for NR", vol. RAN WG1, no. Toulouse, France; 20220822 - 20220826, 12 August 2022 (2022-08-12), XP052274346, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_110/Docs/R1-2206414.zip> [retrieved on 20220812] *
SEUNGHEE HAN ET AL: "Discussions on L1/L2 signaling and configuration for side control information", vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), XP052221977, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_111/Docs/R1-2211413.zip> [retrieved on 20221107] *

Similar Documents

Publication Publication Date Title
US20240224371A1 (en) Network traffic management
WO2023048627A1 (fr) Procédés, appareil et supports lisibles par ordinateur liés à des services à faible latence dans des réseaux sans fil
WO2023048628A1 (fr) Procédés, appareil et supports lisibles par ordinateur relatifs à des services à faible latence dans des réseaux sans fil
WO2024134606A1 (fr) Détermination d&#39;indications dynamiques de faisceaux multiples dans des réseaux répéteurs
WO2023207433A1 (fr) Procédés et appareils de communication dans un système de communication sans fil avec une caractéristique d&#39;économie d&#39;énergie de réseau
WO2024100498A1 (fr) Configuration de faisceau dépendant de la couverture dans des réseaux de répéteurs
WO2023194485A1 (fr) Configuration de ressources dans des relais
WO2024138619A1 (fr) Procédés et appareils de communication sans fil
WO2024089605A1 (fr) Systèmes et procédés d&#39;indication de faisceau de liaison terrestre dans des répéteurs
WO2023209041A1 (fr) Configuration de comportement périodique de filtre spatial dans des réseaux assistés par répéteur
WO2024023321A1 (fr) Signalisation de latence de répéteur
WO2023209048A1 (fr) Configuration de comportement dynamique de filtre spatial dans des réseaux assistés par répéteur
WO2023208787A1 (fr) Rapport de faisceau d&#39;ue à répéteur conjoint dans des réseaux assistés par répéteur
WO2024033842A1 (fr) Configuration d&#39;activation/désactivation pour répéteur commandé par réseau
WO2024033731A1 (fr) Rapport de faisceau basé sur un groupe pour une transmission et une réception simultanées à panneaux multiples
WO2024028780A1 (fr) Sélection de filtres spatiaux dans des réseaux assistés par répéteur
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2023148705A1 (fr) Conception conjointe de disponibilité dans le domaine temporel et fréquentiel
WO2024035312A1 (fr) Dispositifs et procédés de commutation de transmission de liaison montante dynamique
WO2023232885A1 (fr) Fonctionnement de dispositif de communication
WO2024033814A1 (fr) Signalisation de prise en charge de fonctionnalités de répéteur commandé par réseau
WO2024054136A1 (fr) Transmission efficace de puissance et planification de dispositifs coopératifs dans la liaison montante
WO2023083882A1 (fr) Autorisation configurée pour une transmission de liaison montante multi-panneau
WO2024035305A1 (fr) Rapport de réussite de changement ou d&#39;ajout de pscell
WO2024096807A1 (fr) Pdsch pour équipement utilisateur à capacité réduite