[go: up one dir, main page]

WO2025078972A1 - Conception de ressources à trois ports de srs - Google Patents

Conception de ressources à trois ports de srs Download PDF

Info

Publication number
WO2025078972A1
WO2025078972A1 PCT/IB2024/059877 IB2024059877W WO2025078972A1 WO 2025078972 A1 WO2025078972 A1 WO 2025078972A1 IB 2024059877 W IB2024059877 W IB 2024059877W WO 2025078972 A1 WO2025078972 A1 WO 2025078972A1
Authority
WO
WIPO (PCT)
Prior art keywords
srs
port
ports
resource
transmitting
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/IB2024/059877
Other languages
English (en)
Inventor
Sven JACOBSSON
Andreas Nilsson
Robert Mark Harrison
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025078972A1 publication Critical patent/WO2025078972A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • 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—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • a UE capable of CA can transmit/receive on multiple CCs at the same time, where different CCs may be of different channel bandwidths and/or duplex schemes (i.e., TDD or FDD).
  • FR1 i.e., for operating bands n1—n105
  • FR2 i.e., for operating bands n257—n263
  • 3GPP TS 3GPP TS 38.101-1 and 3GPP TS 38.101-2 lists operating bands supporting (contiguous and non-contiguous) intra-band CA and inter-band CA for FR1 and FR2, respectively. With intra-band CA, CCs are in the same operating band.
  • a CC is referred to as a cell.
  • One of said cells is known as the PCell and is the cell that the UE initially connects to. After the UE is connected, one or multiple SCells can be additionally configured. Furthermore, said SCells can be dynamically (via MAC CE signaling) activated/deactivated.
  • CA When CA is not configured, UE will transmit/receive only on the PCell.
  • the number of cells need not be the same in the DL and UL. Typically, since there is often more DL traffic than UL traffic, there are more DL cells than UL cells.
  • SRS resource(s) will be transmitted as part of an SRS resource set, where each SRS resource set contains one or more SRS resources, and where all SRS resources in an SRS resource set must share the same time-domain behavior.
  • NR supports configuration of up to 16 SRS resource sets and 64 SRS resources per BWP. Furthermore, NR supports periodic (p-SRS), semi-persistent (sp-SRS), or aperiodic (ap- SRS) SRS transmissions: [0021] Periodic (p-SRS): SRS resource sets and SRS resources are RRC configured. SRS resource configuration includes slot periodicity and offset, which determines SRS transmission occasions.
  • SRS resource sets and SRS resources are RRC configured.
  • SRS resource configuration includes slot periodicity and offset, and SRS transmissions are activated/deactivated using MAC CE signaling.
  • Aperiodic (ap-SRS) SRS resource sets and SRS resources are RRC configured.
  • SRS resource set configuration includes slot offset, and SRS transmissions are dynamically triggered via 2-bit “SRS request” field in DCI.
  • the SRS resource-set configuration determines, e.g., SRS usage, PC parameters, and slot offset for ap-SRS.
  • the SRS resource configuration determines, e.g., the SRS time-and-frequency allocation, the SRS sequence, the periodicity and offset for p-SRS/sp-SRS.
  • the slot offset is configured by the higher-layer parameter slotOffset and sets the delay from the PDCCH trigger reception to the start of the SRS transmission.
  • the resource usage which is configured by the higher-layer parameter usage determines constraints and assumptions on the resource properties (see 3GPP TS 38.214 for further details).
  • SRS resource sets can be configured with one of four different usages: antennaSwitching, codebook, nonCodebook, or beamManagement.
  • An SRS resource set that is configured with usage antennaSwitching is used for reciprocity-based DL precoding (i.e., used to sound the channel in the UL so that the gNB can use reciprocity to set a suitable DL precoders).
  • the UE is expected to transmit one SRS port per UE antenna port.
  • An SRS resource set that is configured with usage codebook is used for CB-based UL transmission (i.e., used to sound the different UE antennas and help the gNB to determine/signal a suitable UL precoder, transmission rank, and MCS for PUSCH transmission).
  • An SRS resource set that is configured with usage nonCodebook is used for NCB-based UL transmission.
  • the UE transmits one SRS resource per analog beam, and the gNB will perform an RSRP measurement per transmitted SRS resource and, in this way, determine a suitable UE beam that is reported to the UE.
  • the associated CSI-RS (this configuration is only applicable for NCB-based UL transmission) for each of the possible resource types. - For ap-SRS, the associated CSI-RS resource is determined by the higher-layer parameter csi-RS. - For p-SRS/sp-SRS, the associated CSI-RS resource is determined by the higher-layer parameter associatedCSI-RS.
  • the PC parameters e.g., alpha and p0 are used for setting the SRS transmission power.
  • SRS has its own UL PC scheme in NR (see 3GPP TS 38.213 for further details), which specifies how the UE should split the available output power between two or more SRS ports during one SRS transmit occasion (an SRS transmit occasion is a time window within a slot where SRS transmission is performed).
  • an SRS transmit occasion is a time window within a slot where SRS transmission is performed.
  • dynamic/available SRS slot offset indication for ap-SRS was introduced and is configured by the higher-layer parameter availableSlotOffsetList-r17, which lists (up to) 4 slot offsets measured from the legacy slot offset ⁇ configured by the higher-layer parameter slotOffset.
  • the DCI triggering the ap-SRS includes a (up to) 2-bit “SRS offset indicator” which indicates a value ⁇ from the list of slot offsets. If the DCI is transmitted in slot ⁇ , the ap-SRS is transmitted in the ⁇ th available slot after slot ⁇ + ⁇ , where an available slot is a slot that fits all SRS resources in the SRS resource set and that satisfies UE capability on minimum timing requirement.
  • SRS resource configuration Each SRS resource is configured with the following in RRC (see below ASN code from 3GPP TS 38.331 version 17.2.0):
  • SRS-Resource :: SEQUENCE ⁇ srs-ResourceId SRS-ResourceId, nrofSRS-Ports ENUMERATED ⁇ port1, ports2, ports4 ⁇ , ptrs-PortIndex ENUMERATED ⁇ n0, n1 ⁇ OPTIONAL, -- Need R transmissionComb CHOICE ⁇ n2 SEQUENCE ⁇ combOffset-n2 INTEGER (0..1), cyclicShift-n2 INTEGER (0..7) ⁇ , n4 SEQUENCE ⁇ combOffset-n4 INTEGER (0..3), cyclicShift-n4 INTEGER (0..11) ⁇ ⁇ , resourceMapping SEQUENCE ⁇ startPosition INTEGER (0..5), nrofSymbols ENUMERATED
  • the transmission comb i.e., mapping to every 2 nd , 4 th , or 8 th (in NR Rel-17) subcarrier, configured by the higher-layer parameter transmissionComb, which includes: -
  • the higher-layer parameter combOffset determines the comb offset(s), i.e., which subcarriers that should be used for the SRS resource.
  • For four-port SRS resource it is possible for an SRS resource to occupy two comb offsets, with two SRS ports per SRS resource. Configuring different comb offsets over SRS resources enables multiplexing of multiple SRS resources on a same SRS bandwidth.
  • the higher-layer parameter cyclicShift determines the CS(s) for the SRS resource.
  • CSs For multi-port SRS resources, different SRS ports use different CSs, where the CSs are equidistantly spaced. Configuring different CSs over SRS resources enables multiplexing of multiple SRS resources on a same comb offset, but there is a limit on how many CSs that can be used per comb offset: 8 CSs for comb 2, 12 CSs for comb 4, and 6 CSs for comb 8.
  • the time-domain position within a given slot, configured with the higher-layer parameter resourceMapping which includes: - The time-domain start position that (in NR Rel-15) is limited to one of the last 6 symbols, configured by the higher-layer parameter startPosition.
  • NR Rel-16 the start position was extended to any of the symbols in a slot.
  • the number of symbols that (in NR Rel-15) can be set to 1, 2 or 4, configured by the higher-layer parameter nrofSymbols.
  • NR Rel-17 the number of symbols was extended to include 8, 10, 12, and 14.
  • the repetition factor that (in NR Rel-15) can be set to 1, 2 or 4, configured by the higher- layer parameter repetitionFactor. When the repetition factor is larger than 1, the same frequency resources are used multiple times across symbols, used to improve the coverage as this allows more energy to be collected by the receiver.
  • the repetition factor must be integer divisible by the number of symbols.
  • the repetition factor was extended to include also 5, 6, 7, 8, 10, 12, and 14.
  • the SRS frequency-hopping pattern, frequency-domain position, and frequency- domain position shift of an SRS resource is set through the following: - The higher-layer parameter the freqHopping which contains parameters c-SRS, b-SRS, and b-hop which determines the SRS bandwidth (the smallest possible sounding bandwidth is 4 RBs): • c-SRS, which determines “configured bandwidth” (see Figure 1). • b-hop, which determines the “hopping bandwidth” (see Figure 1). • b-SRS, which determines the “per-hop bandwidth” (see Figure 1).
  • FIG. 1 illustrates an example of how an SRS resource could be allocated in time and frequency within a slot in NR Rel-15/Rel-16/Rel-17 (note that semi-persistent/periodic SRS resources typically span several slots).
  • SRS can occupy up to 4 of the last 6 symbols in a slot.
  • NR Rel-16 SRS can occupy up to 4 of all symbols in a slot.
  • SRS can occupy up to 14 of all symbols in a slot.
  • SRS partial frequency sounding was introduced and is configured by the higher-layer parameter partialFreqSounding. When partial frequency sounding is configured, an SRS resource will span only a subset (one half or one quarter) of the SRS per-hop bandwidth, which subset of the sounding bandwidth is configurable and may vary over symbols). SRS partial frequency sounding can be combined with SRS repetition and SRS frequency hopping.
  • SRS port mapping [0045] An SRS port is mapped to a subset of the subcarriers in the configured SRS bandwidth.
  • ⁇ ⁇ ⁇ ⁇ $ and ⁇ ( ⁇ # , # ⁇ * )- $ is the starting position for frequency hopping and partial frequency sounding
  • ⁇ ⁇ !#$ is the frequency-domain shift.
  • the port-specific comb offset ⁇ ( ⁇ ) T C ⁇ depends on the RRC- configured comb offset ⁇ . TC as follows: ⁇ .
  • 1 TC is the comb
  • ⁇ 6 - 7 ⁇ - is the number of SRS ports
  • SRS resource ⁇ is configured with comb offset ⁇ .
  • the comb is 4 such that the number of CSs per comb offset is 12, the 4-port SRS resource 0 is configured with CS 0, the 2-port SRS resource 1 is configured with CS 2, the 1-port SRS resource 2 is configured with CS 5, and the 1-port SRS resource 3 is configured with CS 11.
  • Figure 3 shows an example of how multiple SRS resources (each with one or more SRS ports) can be mapped onto a same comb offset by configuring different cyclic shifts.
  • NR supports SRS antenna switching for UEs equipped with more Rx chains than Tx chains. If a UE support antenna switching, it will report so by means of UE-capability signaling (see, e.g., Table 1). Table 1 SRS antenna-switching capabilities supported by the UE (copied from 3GPP TS 38.306).
  • NW can configure 1T2R antenna switching with two one-port SRS resources in an SRS resource set with usage antennaSwitching.
  • the two SRS resources must be configured in different OFDM symbols and separated, at least, by a guard period that depends on the SCS (see Clause 6.2.1.2 of 3GPP TS 38.214 for further details) such that both antennas can be sounded, with an antenna switch in between.
  • DTER SRS antenna switching can be configured for a UE with D Tx chains and E Rx chains.
  • Figure 5 illustrates 1T2R (left), 2T4R (middle), and 4T8R (right) SRS antenna switching.
  • D E/2 Tx chains
  • E Rx chains E Rx chains.
  • additional UE capabilities for SRS antenna-switching were introduced, which are shown in the right column of Table 1.
  • UE can indicate support for sounding only a subset of Rx antennas, which can save UE power consumption and SRS overhead at the cost of reduced channel knowledge at the gNB.
  • the UE capability t1r1-t1r2 indicates that the gNB can configure one single-port SRS resource (no antenna switching) or two single-port SRS resources (same as for the capability t1r2 described above) per SRS resource set with usage antennaSwitching.
  • antenna switching was extended to up to 6 or 8 Rx ports, and 1, 2, or 4 Tx chains.
  • UE can indicate support for antenna-switching configurations beyond 4 Rx via higher- layer parameter srs-AntennaSwitchingBeyond4RX-r17 (see 3GPP TS 38.306 for further details).
  • SRS repetition and/or frequency hopping SRS coverage can be increased for an SRS resource through repetition and/or frequency hopping.
  • An example of SRS frequency hopping is provided in Figure 6 which illustrates SRS transmission over four symbols in one UL slot with frequency hopping.
  • different parts of the SRS bandwidth are sounded in each of four different OFDM symbols, which means that SRS coverage improves (by four times compared to SRS transmission in a single symbol), at the cost of more symbols being used for SRS and a shorter sequence length per OFDM symbol.
  • An example of SRS repetition is provided in Figure 6.
  • FIG. 7 illustrates SRS transmission over four symbols in one UL slot with repetition.
  • Figure 8 illustrates SRS transmission over two adjacent UL slots using both frequency hopping and repetition. It is worth pointing out that SRS repetition and frequency hopping can be used together and, that for p-SRS/sp-SRS, the frequency-hopping pattern continues beyond the slot boundary.
  • a p-SRS resource (with periodicity one) is shown over two adjacent UL slots.
  • a method performed by a User Equipment includes: receiving a configuration with a four-port SRS resource; receiving a control message to trigger/activate an SRS transmission; and transmitting three out of four SRS ports of 4-port SRS resource.
  • 3-port SRS resource design and 3-port SRS transmission is enables, thus enabling three transmit chain Uplink transmission.
  • the method also includes: reporting UE capability for transmitting three SRS ports. In some embodiments, the method also includes: being explicitly configured to transmit only three out of the four SRS ports. In some embodiments, being explicitly configured comprises: receiving an indication that one of the SRS ports is muted. In some embodiments, receiving the control message comprises: receiving a DCI to trigger SRS transmission. In some embodiments, receiving the control message comprises: receiving a MAC CE to activate SRS transmission. [0064] In some embodiments, the UE capability comprises: a new UE capability that explicitly informs the network that UE is capable of transmitting three SRS ports.
  • reporting the UE capability comprises: reporting a maximum number of SRS ports per SRS resource, ⁇ 6 - 7 ⁇ - . In some embodiments, if ⁇ 6 - 7 ⁇ - ⁇ 3, the UE is capable of transmitting three SRS ports. [0065] In some embodiments, being explicitly configured to transmit only three out of the four SRS ports comprises: a new field is added to SRS-Config IE such that the UE can be configured with muting of 4-port SRS resource. In some embodiments, the new field is present if and only if the number of SRS ports in the SRS resource is four. [0066] In some embodiments, the UE does not transmit the first SRS port in the SRS resource.
  • the UE does not transmit the last SRS port in the SRS resource. In some embodiments, which SRS port to mute is configured. In some embodiments, the method also includes supporting three used Cyclic Shifts, CSs, per comb offset if configured with muting of 4- port SRS resource. [0067] In some embodiments, the method also includes: reporting capability of supporting three CSs per comb offset if configured with muting of 4-port SRS resource. In some embodiments, the method also includes: reporting capability of supporting uneven number of CSs per comb offset if configured with muting of 4-port SRS resource.
  • the method also includes: splitting transmit power G - ⁇ -,H,I,J linearly over the three SRS ports, such that the total SRS power is G - ⁇ -,H,I,J .
  • a 3-port SRS resource maps all SRS ports onto a single comb offset and where the mapping is such that SRS ports are equidistantly spaced.
  • SRS ports in a 3-port SRS resource are mapped to CSs and comb offsets in such a way that two SRS ports is mapped to a first comb offset and one SRS port is mapped to a second offset.
  • 3 Tx UL transmission in a same cell has been proposed as a potential RAN1 work item in NR Rel-19 (see, e.g., RP-232612, AT&T, Moderator's summary for REL-19 RAN1 topic MIMO Evolution, September 2023), with strong support from, in particular, chipset/device vendors and operators.
  • Legacy NR i.e., up to Rel-18
  • an SRS resource only can be configured with 1, 2, 4, or 8 SRS ports
  • a TPMI field can only indicate a precoder over 1, 2, 4 or 8 SRS ports
  • an SRI field can only indicate up to 1, 2, 4 or 8 SRS resources.
  • Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
  • Some embodiments of the current disclosure describe three different solutions (and corresponding detailed embodiments) to introduce a 3-port SRS resource: • Blanking (muting of SRS port) of 4-port SRS resource, • Introduction of a new 3-port SRS resource, or • Combining two SRS resources, where a first SRS resource is configured with 2 SRS ports and a second SRS resource is configured with 1 SRS port.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • this field is present if and only if the number of SRS ports in the SRS resource is 4.
  • SRS-Resource :: SEQUENCE ⁇ ... nrofSRS-Ports ENUMERATED ⁇ port1, ports2, ports4 ⁇ , ... blanked-SRS-Port-r19 ENUMERATED ⁇ enable ⁇ OPTIONAL -- Cond ports4 ]] ⁇ [0104]
  • UE has indicated capability for 3-port SRS resource (in Step 1), it is understood (by both NW and UE) that UE will transmit only 3 out of the 4 ports if NW configures UE with 4-port SRS resource.
  • SRS-Resource SEQUENCE ⁇ ... nrofSRS-Ports ENUMERATED ⁇ port1, ports2, ports4 ⁇ , ... blanked-SRS-Port-r19 ENUMERATED ⁇ blank1, blank2, blank3, blank4 ⁇ OPTIONAL -- Cond ports4 ]] ⁇
  • SRS ports in a 4-port SRS resource can be mapped to CSs on 1 (for comb 2 and 4) or 2 (for comb 2, 4, or 8) comb offsets.
  • Figure 10 illustrates muting of SRS ports for 4-port SRS resources configured with comb 4 where all CSs are on a same comb offset.
  • FIG 10 an example is shown of muting of a 4-port SRS resource configured with comb 4 (such that there are 12 CSs per comb offset) for which all 4 CSs are on a same comb offset and where the last SRS port (SRS port 1003) is muted such that there are 3 used CSs on one comb offset.
  • 3 Tx UE must support 3 used CSs per comb offset if configured with muting of 4-port SRS resource.
  • UE may optionally report capability of supporting 3 CSs per comb offset if configured with muting of 4-port SRS resource.
  • UE is not expected to be configured with 4 (3 after blanking) CSs per comb offset if blanking of 4-port SRS resource is configured.
  • Figures 11A and 11B illustrate muting of SRS ports for 4-port SRS resources configured with comb 4 ( Figure 11A) and comb 8 ( Figure 11B) where CSs are spread over two comb offsets.
  • Figure 11A an example is shown of muting of a 4-port SRS resource configured with comb 4 (such that there are 12 CSs per comb offset) for which the 4 CSs are spread over two comb offset and where the last SRS port (SRS port 1003) is muted.
  • Figure 11B a similar example is shown of muting of a 4-port SRS resource configured with comb 8 (such that there are 6 CSs per comb offset).
  • UE may optionally report capability of supporting uneven number of CSs per comb offset if configured with muting of 4-port SRS resource. In an alternate embodiment, UE is not expected to be configured with uneven number of CSs per comb offset if blanking of 4-port SRS resource is configured.
  • comb 8 (for which the 4 SRS ports must be spread over multiple comb offsets, which is an optional configuration for comb 2 and 4) cannot be configured at the same time as muting of a 4-port SRS resource (UE is not expected be configured with muting and comb 8 at the same time).
  • UE splits the “transmit power G - ⁇ -,H,I,J on active UL BWP K of carrier L of serving cell M equally across the configured antenna ports for SRS”.
  • the UE splits transmit power G - ⁇ -,H,I,J linearly over 3 SRS ports, such that the total SRS power is G- ⁇ -,H,I,J.
  • the UE splits transmit power G - ⁇ -,H,I,J linearly over 4 SRS ports, such that the total SRS power is 0.75 ⁇ G- ⁇ -,H,I,J.
  • UE splits half of the transmit over the 2 SRS ports mapped to a first comb offset and half of the transmit power over the 1 SRS port mapped to a second comb offset, such that the total SRS power is G - ⁇ -,H,I,J .
  • Step 5 NW receives 3 out of 4 SRS ports. In other words, NW is expected to measure the channel (compute a channel estimate) only for 3 out of the 4 SRS ports in a 4-port SRS resource.
  • Figure 12 shows a flowchart related to embodiments in this section.
  • a new field for configuring the number of SRS ports is added in SRS-Config IE such that NW can configure 3-port SRS resource.
  • NW can configure 3-port SRS resource.
  • UE shall ignore the value of the field nrofSRS-ports.
  • the UE splits the power over 2-port SRS resource and 1-port SRS resource in such a way that the power per SRS port is split equally over the 3 SRS ports (i.e., 2/3 and 1/3 third of the SRS power will be used for the 2-port SRS resource and the 1-port SRS resource, respectively).
  • the 2-port SRS resource and 1-port SRS resource can be configured in non-overlapping OFDM symbols.
  • the SRS power in the OFDM symbol containing the 1-port SRS resource half of the SRS power in the OFDM symbol containing the 2-port SRS resource (such that the power per SRS ports is the same over the 3 SRS ports).
  • UE is required to transmit the two SRS resources such that coherence is maintained over, at least, a subset of the three SRS ports: •
  • SRS ports are in an SRS resource set with usage set to codebook, and if UE has reported capability for partially-coherent precoding, UE is expected to maintain coherence when transmitting PUSCH over the two SRS ports in the 2-port SRS resource (it is not required that these 2 SRS ports maintain coherence with the SRS port in the 1-port SRS resource).
  • UE is expected to maintain coherence when transmitting PUSCH over the three SRS ports in the 2-port SRS resource and the SRS port in the 1-port SRS resource. In other words, UE is expected to maintain coherence over multiple SRS resources in the same SRS resource set.
  • three 1-port SRS resources are combined.
  • FIG. 15 shows an example of a communication system 1500 in accordance with some embodiments.
  • the communication system 1500 includes a telecommunication network 1502 that includes an access network 1504, such as a Radio Access Network (RAN), and a core network 1506, which includes one or more core network nodes 1508.
  • the access network 1504 includes one or more access network nodes, such as network nodes 1510A and 1510B (one or more of which may be generally referred to as network nodes 1510), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs).
  • 3GPP Third Generation Partnership Project
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • network nodes include disaggregated implementations or portions thereof.
  • the telecommunication network 1502 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN Open-RAN
  • An ORAN network node is a node in the telecommunication network 1502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1502, including one or more network nodes 1510 and/or core network nodes 1508.
  • ORAN specification e.g., a specification published by the O-RAN Alliance, or any similar organization
  • Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
  • the network nodes 1510 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 1512A, 1512B, 1512C, and 1512D (one or more of which may be generally referred to as UEs 1512) to the core network 1506 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 1500 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 1500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1512 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 1510 and other communication devices.
  • the network nodes 1510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1512 and/or with other network nodes or equipment in the telecommunication network 1502 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 1502.
  • the core network 1506 connects the network nodes 1510 to one or more hosts, such as host 1516. 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 1506 includes one more core network nodes (e.g., core network node 1508) that are structured with hardware and software components.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1516 may be under the ownership or control of a service provider other than an operator or provider of the access network 1504 and/or the telecommunication network 1502, and may be operated by the service provider or on behalf of the service provider.
  • the host 1516 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 1500 of Figure 15 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 1500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 1502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1502. For example, the telecommunication network 1502 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 (IoT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • IoT massive Internet of Things
  • the UEs 1512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1504.
  • 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. being 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
  • the hub 1514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.
  • the hub 1514 may have a constant/persistent or intermittent connection to the network node 1510B.
  • the hub 1514 may also allow for a different communication scheme and/or schedule between the hub 1514 and UEs (e.g., UE 1512C and/or 1512D), and between the hub 1514 and the core network 1506.
  • the hub 1514 is connected to the core network 1506 and/or one or more UEs via a wired connection.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, 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 enhanced MTC
  • 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 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input/output interface 1606, a power source 1608, memory 1610, a communication interface 1612, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 16. 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 1602 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 1610.
  • the processing circuitry 1602 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 1602 may include multiple Central Processing Units (CPUs).
  • the input/output interface 1606 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 1600.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device.
  • the power source 1608 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 1608 may further include power circuitry for delivering power from the power source 1608 itself, and/or an external power source, to the various parts of the UE 1600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1608.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1608 to make the power suitable for the respective components of the UE 1600 to which power is supplied.
  • the memory 1610 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 1610 includes one or more application programs 1614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1616.
  • the memory 1610 may store, for use by the UE 1600, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1610 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
  • 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 1610 may allow the UE 1600 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 1610, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1602 may be configured to communicate with an access network or other network using the communication interface 1612.
  • the communication interface 1612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1622.
  • the communication interface 1612 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 1618 and/or a receiver 1620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1618 and receiver 1620 may be coupled to one or more antennas (e.g., the antenna 1622) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1612 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.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1612, 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.
  • 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 IoT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare.
  • Non-limiting examples of such an IoT 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, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • UAV Unmanned Ae
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1600 shown in Figure 16.
  • 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.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • Figure 17 shows a network node 1700 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.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs).
  • RRUs Remote Radio Units
  • RRHs Remote Radio Heads
  • RRUs Remote Radio Heads
  • Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR Transmission Point
  • MSR Multi-Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes
  • the network node 1700 includes processing circuitry 1702, memory 1704, a communication interface 1706, and a power source 1708.
  • the network node 1700 may be composed of multiple physically separate components (e.g., a NodeB 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 1700 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1700 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1704 for different RATs) and some components may be reused (e.g., a same antenna 1710 may be shared by different RATs).
  • the network node 1700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1700, 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 1700.
  • the processing circuitry 1702 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 1700 components, such as the memory 1704, to provide network node 1700 functionality.
  • the processing circuitry 1702 includes a System on a Chip (SOC).
  • the processing circuitry 1702 includes one or more of Radio Frequency (RF) transceiver circuitry 1712 and baseband processing circuitry 1714.
  • RF Radio Frequency
  • the RF transceiver circuitry 1712 and the baseband processing circuitry 1714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 1712 and the baseband processing circuitry 1714 may be on the same chip or set of chips, boards, or units.
  • the memory 1704 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 1702.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)
  • the memory 1704 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 1702 and utilized by the network node 1700.
  • the memory 1704 may be used to store any calculations made by the processing circuitry 1702 and/or any data received via the communication interface 1706.
  • the processing circuitry 1702 and the memory 1704 are integrated.
  • the communication interface 1706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1706 comprises port(s)/terminal(s) 1716 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1706 also includes radio front-end circuitry 1718 that may be coupled to, or in certain embodiments a part of, the antenna 1710.
  • the radio front-end circuitry 1718 comprises filters 1720 and amplifiers 1722.
  • the radio front-end circuitry 1718 may be connected to the antenna 1710 and the processing circuitry 1702.
  • the radio front-end circuitry 1718 may be configured to condition signals communicated between the antenna 1710 and the processing circuitry 1702.
  • the radio front-end circuitry 1718 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 1718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1720 and/or the amplifiers 1722. The radio signal may then be transmitted via the antenna 1710. Similarly, when receiving data, the antenna 1710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1718. The digital data may be passed to the processing circuitry 1702. In other embodiments, the communication interface 1706 may comprise different components and/or different combinations of components. [0169] In certain alternative embodiments, the network node 1700 does not include separate radio front-end circuitry 1718; instead, the processing circuitry 1702 includes radio front-end circuitry and is connected to the antenna 1710.
  • the RF transceiver circuitry 1712 is part of the communication interface 1706.
  • the communication interface 1706 includes the one or more ports or terminals 1716, the radio front-end circuitry 1718, and the RF transceiver circuitry 1712 as part of a radio unit (not shown), and the communication interface 1706 communicates with the baseband processing circuitry 1714, which is part of a digital unit (not shown).
  • the antenna 1710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1710 may be coupled to the radio front-end circuitry 1718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1710 is separate from the network node 1700 and connectable to the network node 1700 through an interface or port.
  • the antenna 1710, the communication interface 1706, and/or the processing circuitry 1702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1700. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1710, the communication interface 1706, and/or the processing circuitry 1702 may be configured to perform any transmitting operations described herein as being performed by the network node 1700.
  • the power source 1708 provides power to the various components of the network node 1700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1700 with power for performing the functionality described herein.
  • the network node 1700 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 1708.
  • an external power source e.g., the power grid or an electricity outlet
  • the power source 1708 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 1700 may include additional components beyond those shown in Figure 17 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 1700 may include user interface equipment to allow input of information into the network node 1700 and to allow output of information from the network node 1700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1700.
  • FIG 18 is a block diagram of a host 1800, which may be an embodiment of the host 1516 of Figure 15, in accordance with various aspects described herein.
  • the host 1800 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 1800 may provide one or more services to one or more UEs.
  • the host 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a network interface 1808, a power source 1810, and memory 1812. Other components may be included in other embodiments.
  • the memory 1812 may include one or more computer programs including one or more host application programs 1814 and data 1816, which may include user data, e.g., data generated by a UE for the host 1800 or data generated by the host 1800 for a UE.
  • Embodiments of the host 1800 may utilize only a subset or all of the components shown.
  • the host application programs 1814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Coding
  • the host application programs 1814 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 1800 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 1814 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.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • DASH or MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • 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 1900 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.
  • the virtualization environment 1900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
  • Applications 1902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1904 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.
  • the hardware 1904 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 1910, which, among others, oversees lifecycle management of the applications 1902.
  • the hardware 1904 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 base station.
  • the connection 2060 may be direct or pass through a core network (like the core network 1506 of Figure 15) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 2006 includes hardware and software, which is stored in or accessible by the UE 2006 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 2006 with the support of the host 2002.
  • an executing host application may communicate with the executing client application via the OTT connection 2050 terminating at the UE 2006 and the host 2002.
  • 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 2050 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 2050.
  • the OTT connection 2050 may extend via the connection 2060 between the host 2002 and the network node 2004 and via a wireless connection 2070 between the network node 2004 and the UE 2006 to provide the connection between the host 2002 and the UE 2006.
  • connection 2060 and the wireless connection 2070, over which the OTT connection 2050 may be provided have been drawn abstractly to illustrate the communication between the host 2002 and the UE 2006 via the network node 2004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 2002 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 2006.
  • the user data is associated with a UE 2006 that shares data with the host 2002 without explicit human interaction.
  • the host 2002 initiates a transmission carrying the user data towards the UE 2006.
  • the host 2002 may initiate the transmission responsive to a request transmitted by the UE 2006.
  • the request may be caused by human interaction with the UE 2006 or by operation of the client application executing on the UE 2006.
  • the transmission may pass via the network node 2004 in accordance with the teachings of the embodiments described throughout this disclosure.
  • the network node 2004 transmits to the UE 2006 the user data that was carried in the transmission that the host 2002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 2006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2006 associated with the host application executed by the host 2002.
  • the UE 2006 executes a client application which provides user data to the host 2002.
  • the user data may be provided in reaction or response to the data received from the host 2002. Accordingly, in step 2016, the UE 2006 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 2006. Regardless of the specific manner in which the user data was provided, the UE 2006 initiates, in step 2018, transmission of the user data towards the host 2002 via the network node 2004. In step 2020, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2004 receives user data from the UE 2006 and initiates transmission of the received user data towards the host 2002. In step 2022, the host 2002 receives the user data carried in the transmission initiated by the UE 2006.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 2006 using the OTT connection 2050, in which the wireless connection 2070 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime, etc. [0191] In an example scenario, factory status information may be collected and analyzed by the host 2002. As another example, the host 2002 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 2002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 2002 may store surveillance video uploaded by a UE.
  • the host 2002 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 2002 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 2050 may be implemented in software and hardware of the host 2002 and/or the UE 2006.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2050 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 2050 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 2004. 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 2002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2050 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice 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.
  • some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner.
  • the processing circuitry can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by a user equipment, the method comprising one or more of: reporting UE capability for transmitting 3 Sounding Reference Signal, SRS, ports; [0199] being configured with a 4-port SRS resource; being configured to transmit only 3 out of said 4 SRS ports (e.g., one of the SRS ports is ‘blanked’/’muted’); receiving a control message (e.g., a DCI) to trigger SRS transmission; receiving a control message (e.g., a MAC CE) to activate SRS transmission; and transmitting 3 out of 4 SRS ports of 4-port SRS resource.
  • a control message e.g., a DCI
  • a control message e.g., a MAC CE
  • Embodiment 2 A method performed by a user equipment, the method comprising one or more of: reporting UE capability for transmitting 3 SRS ports; being configured with a 3- port SRS resource; receiving a control message (e.g., a DCI) to trigger SRS transmission; receiving a control message (e.g., a MAC CE) to activate SRS transmission; and transmitting 3 SRS ports of the 3-port SRS resource.
  • a control message e.g., a DCI
  • a control message e.g., a MAC CE
  • Embodiment 3 A method performed by a user equipment, the method comprising one or more of: reporting UE capability for transmitting 3 SRS ports; being configured with a 2- port SRS resource and a 1-port SRS resource in a same SRS resource set; receiving a control message (e.g., a DCI) to trigger SRS transmission; receiving a control message (e.g., a MAC CE) to activate SRS transmission; and transmitting 3 SRS ports of the 2-port SRS resource and the 1- port SRS resource.
  • a control message e.g., a DCI
  • a control message e.g., a MAC CE
  • Embodiment 5 The method of any of the previous embodiments, wherein: UE reports a maximum number of SRS ports per SRS resource, ⁇ 6 - 7 ⁇ - .
  • Embodiment 6 The method of any of the previous embodiments, wherein: if ⁇ - ⁇ - 67 ⁇ 3, UE is capable of transmitting 3 SRS ports.
  • Embodiment 7 The method of any of the previous embodiments, wherein: a new field is added to SRS-Config IE such that NW can configure UE with blanking of 4-port SRS resource.
  • Embodiment 8 The method of any of the previous embodiments, wherein: the new field is present if and only if the number of SRS ports in the SRS resource is 4.
  • Embodiment 9 The method of any of the previous embodiments, wherein: if UE has indicated capability for 3-port SRS resource, it is understood (e.g., by both NW and UE) that UE will transmit only 3 out of the 4 ports if NW configures UE with 4-port SRS resource.
  • Embodiment 10 The method of any of the previous embodiments, wherein: UE does not transmit the first SRS port in the SRS resource (e.g., the SRS port with lowest port index: 1000).
  • Embodiment 11 The method of any of the previous embodiments, wherein: the UE does not transmit the last SRS port in the SRS resource (e.g., the SRS port with lowest port index: 1003).
  • Embodiment 12 The method of any of the previous embodiments, wherein: which SRS port to ‘blank’/‘mute’ is configured by the NW.
  • Embodiment 13 The method of any of the previous embodiments, wherein: 3 Tx UE must support 3 used CSs per comb offset if configured with muting of 4-port SRS resource.
  • Embodiment 14 The method of any of the previous embodiments, wherein: UE reports capability of supporting 3 CSs per comb offset if configured with muting of 4-port SRS resource.
  • Embodiment 15 The method of any of the previous embodiments, wherein: UE is not expected to be configured with 4 (3 after blanking) CSs per comb offset if blanking of 4-port SRS resource is configured.
  • Embodiment 16 The method of any of the previous embodiments, wherein: UE reports capability of supporting uneven number of CSs per comb offset if configured with muting of 4-port SRS resource.
  • Embodiment 17 The method of any of the previous embodiments, wherein: UE is not expected to be configured with uneven number of CSs per comb offset if blanking of 4-port SRS resource is configured.
  • Embodiment 18 The method of any of the previous embodiments, wherein: comb 8 (e.g., for which the 4 SRS ports must be spread over multiple comb offsets, which is an optional configuration for comb 2 and 4) cannot be configured at the same time as muting of a 4-port SRS resource (e.g., UE is not expected be configured with muting and comb 8 at the same time).
  • Embodiment 19 The method of any of the previous embodiments, wherein: for a muted 4-port SRS resource, the UE splits transmit power G - ⁇ -,H,I,J linearly over 3 SRS ports, such that the total SRS power is G - ⁇ -,H,I,J .
  • Embodiment 20 The method of any of the previous embodiments, wherein: for a muted 4-port SRS resource, the UE splits transmit power G - ⁇ -,H,I,J linearly over 4 SRS ports, such that the total SRS power is 0.75 ⁇ G - ⁇ -,H,I,J .
  • Embodiment 21 The method of any of the previous embodiments, wherein: for a muted 4-port SRS resource configured to map SRS ports to two different comb offsets, UE splits half of the transmit over the 2 SRS ports mapped to a first comb offset and half of the transmit power over the 1 SRS port mapped to a second comb offset, such that the total SRS power is G- ⁇ -,H,I,J.
  • Embodiment 22 The method of any of the previous embodiments, wherein: a new field for configuring the number of SRS ports is added in SRS-Config IE such that NW can configure 3-port SRS resource.
  • Embodiment 23 The method of any of the previous embodiments, wherein: when this new field is configured, UE shall ignore the value of the field nrofSRS-ports.
  • Embodiment 24 The method of any of the previous embodiments, wherein: a 3-port SRS resource maps all SRS ports onto a single comb offset (e.g., 3 ports per comb offset) and where the mapping is such that SRS ports are equidistantly spaced.
  • Embodiment 25 The method of any of the previous embodiments, wherein: a 3-port SRS resource cannot be configured with comb 2 (UE is not expected be configured with 3 SRS ports and comb 2 at the same time).
  • Embodiment 26 The method of any of the previous embodiments, wherein: 3 SRS ports is mapped to a single comb offset in such a way that CSs are not equidistantly separated (e.g., CS 0 + M, 3 + M, 6 + M for comb 2).
  • Embodiment 27 The method of any of the previous embodiments, wherein: SRS ports in a 3-port SRS resource are mapped to CSs and comb offsets in such a way that 2 SRS ports is mapped to a first comb offset and 1 SRS port is mapped to a second offset.
  • Embodiment 28 The method of any of the previous embodiments, wherein: for comb 4 and/or 8, SRS ports in a 3-port SRS resource are mapped to three different comb offsets.
  • Embodiment 29 The method of any of the previous embodiments, wherein: the SRS power in the OFDM symbol containing the 1-port SRS resource half of the SRS power in the OFDM symbol containing the 2-port SRS resource (e.g., such that the power per SRS ports is the same over the 3 SRS ports).
  • Embodiment 30 The method of any of the previous embodiments, wherein: UE is required to transmit the two SRS resources such that coherence is maintained over, at least, a subset of the three SRS ports.
  • Embodiment 31 The method of any of the previous embodiments, wherein: if SRS ports are in an SRS resource set with usage set to codebook, and if UE has reported capability for partially-coherent precoding, UE is expected to maintain coherence when transmitting PUSCH over the two SRS ports in the 2-port SRS resource.
  • Embodiment 32 The method of any of the previous embodiments, wherein: if SRS ports are in an SRS resource set with usage set to codebook, and if UE has reported capability for fully-coherent precoding, UE is expected to maintain coherence when transmitting PUSCH over the three SRS ports in the 2-port SRS resource and the SRS port in the 1-port SRS resource.
  • Embodiment 33 The method of any of the previous embodiments, wherein: instead of combining two SRS resources, three 1-port SRS resources are combined.
  • Embodiment 34 The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Embodiment 35 A method performed by a network node, the method comprising one or more of: receiving a report of UE capability for transmitting 3 SRS ports; configuring the UE with a 4-port SRS resource; configuring the UE to transmit only 3 out of said 4 SRS ports (e.g., one of the SRS ports is ‘blanked’/’muted’); transmitting a control message (e.g., a DCI) to trigger SRS transmission; transmitting a control message (e.g., a MAC CE) to activate SRS transmission; and receiving 3 out of 4 SRS ports of 4-port SRS resource.
  • a control message e.g., a DCI
  • a control message e.g., a MAC CE
  • Embodiment 36 A method performed by a network node, the method comprising one or more of: receiving a report of UE capability for transmitting 3 SRS ports; configuring the UE with a 3-port SRS resource; transmitting a control message (e.g., a DCI) to trigger SRS transmission; transmitting a control message (e.g., a MAC CE) to activate SRS transmission; and receiving 3 SRS ports of the 3-port SRS resource.
  • a control message e.g., a DCI
  • a control message e.g., a MAC CE
  • Embodiment 37 A method performed by a network node, the method comprising one or more of: receiving a report of UE capability for transmitting 3 SRS ports; configuring the UE with a 2-port SRS resource and a 1-port SRS resource in a same SRS resource set; transmitting a control message (e.g., a DCI) to trigger SRS transmission; transmitting a control message (e.g., a MAC CE) to activate SRS transmission; and receiving 3 SRS ports of the 2-port SRS resource and the 1-port SRS resource.
  • a control message e.g., a DCI
  • a control message e.g., a MAC CE
  • Embodiment 39 The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Group C Embodiments [0240]
  • Embodiment 40 A user equipment, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 41 A network node, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 42 A user equipment (UE), the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • Embodiment 43 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Embodiment 44 The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • Embodiment 45 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • Embodiment 46 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 47 The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 48 A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Embodiment 49 The communication system of the previous embodiment, further comprising: the network node; and/or the UE.
  • Embodiment 50 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • Embodiment 51 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 52 The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 57 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 58 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.
  • UE user equipment
  • Embodiment 59 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.
  • Embodiment 60 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

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 conception de ressources à trois ports de signal de référence de sondage (SRS). Dans certains modes de réalisation, un procédé mis en œuvre par un équipement utilisateur (UE) consiste à : recevoir une configuration avec une ressource à quatre ports de SRS ; recevoir un message de commande pour déclencher/activer une transmission de SRS ; et transmettre trois ports de SRS parmi quatre ports de SRS de la ressource à quatre ports de SRS. De cette manière, la conception de ressources à trois ports de SRS et la transmission de trois ports de SRS sont permises, permettant ainsi une transmission en liaison montante à trois chaînes de transmission.
PCT/IB2024/059877 2023-10-10 2024-10-09 Conception de ressources à trois ports de srs Pending WO2025078972A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363589127P 2023-10-10 2023-10-10
US63/589,127 2023-10-10

Publications (1)

Publication Number Publication Date
WO2025078972A1 true WO2025078972A1 (fr) 2025-04-17

Family

ID=93150546

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2024/059877 Pending WO2025078972A1 (fr) 2023-10-10 2024-10-09 Conception de ressources à trois ports de srs

Country Status (1)

Country Link
WO (1) WO2025078972A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022153283A1 (fr) * 2021-01-18 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Indication d'un sous-ensemble d'antennes tx/rx pour une commutation d'antenne srs via un mac-ce
WO2022153280A1 (fr) * 2021-01-18 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Signalisation de capacité d'ue de commutation d'antenne srs
US20230105787A1 (en) * 2020-03-12 2023-04-06 Qualcomm Incorporated Dynamic sounding reference signal (srs) resource allocation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230105787A1 (en) * 2020-03-12 2023-04-06 Qualcomm Incorporated Dynamic sounding reference signal (srs) resource allocation
WO2022153283A1 (fr) * 2021-01-18 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Indication d'un sous-ensemble d'antennes tx/rx pour une commutation d'antenne srs via un mac-ce
WO2022153280A1 (fr) * 2021-01-18 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Signalisation de capacité d'ue de commutation d'antenne srs

Similar Documents

Publication Publication Date Title
JP7416853B2 (ja) チャネル状態情報リポートに優先度を付けるためのシステムおよび方法
US20250081183A1 (en) Signalling for repetition
CN113287268B (zh) 用于预编码矩阵指示和信道质量指示的独立子带大小
US12279294B2 (en) Uplink resource configuration
JP2023509799A (ja) 低複雑度ユーザ機器のためのランダムアクセス
KR20200053553A (ko) 물리적 업링크 제어 채널 폴백 모드
US20240243876A1 (en) Collision handling for positioning reference signals
EP3858028B1 (fr) Procédés de signalisation de ressources réservées pour un trafic de communication à faible latence ultra-fiable (urllc)
WO2021141525A1 (fr) Hiérarchisation de canaux logiques et allocation de liaison montante correspondante
US20250192966A1 (en) CSI-RS TRANSMISSION AND RECEPTION WITH UNIFIED TCI STATES FOR MULTIPLE TRPs
WO2024241201A1 (fr) Transmissions en liaison montante dans des créneaux en duplex intégral de sous-bande (sbfd) avec des ressources de surveillance de liaison descendante
WO2024161343A1 (fr) Saut à décalage en peigne et à décalage cyclique srs combinés/séparés
US20240334376A1 (en) Configuring and indicating positioning and data traffic priorities
WO2025078972A1 (fr) Conception de ressources à trois ports de srs
WO2025079000A1 (fr) Commutation d'antenne srs pour ue à 3 tx
EP4381842B1 (fr) Procédés de mappage de ressources autour de signaux de référence de positionnement
WO2025079001A1 (fr) Correspondance de ports ptrs vers dmrs améliorée pour trois ue tx
EP4595327A1 (fr) Mappage de port ul-rs pour une opération multi-trp
WO2025027504A2 (fr) Procédés de signalisation d'agrégation de ressources de csi-rs pour grands réseaux
WO2024035292A1 (fr) Configuration de ressource adaptative de domaine fréquentiel pour attribution multi-créneau
WO2025168679A1 (fr) Rapport de paramètres pour ensembles de ressources nzp csi-rs sélectionnés
WO2024100530A1 (fr) Signalisation pour une transmission de liaison montante simultanée sur un signal de référence de sondage (srs) multiple
WO2025233912A1 (fr) Procédés d'accusé de réception de rapport de faisceau initié par un ue
WO2024033892A1 (fr) Codes de couverture orthogonaux dans le domaine temporel pour signal de référence de sondage de liaison montante

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24791109

Country of ref document: EP

Kind code of ref document: A1