Method and system for assisting information reporting for early sounding reference signal (SRS) configuration

By allowing the UE to provide channel quality information, the method facilitates effective early SRS configuration, addressing the lack of CSI during initial access and enhancing network performance.

WO2026238893A1PCT designated stage Publication Date: 2026-11-19TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/064086
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-15
Filing Date
2026-05-13
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Networks lack Channel State Information (CSI) before Radio Resource Control (RRC) configuration is completed, hindering effective early Sounding Reference Signal (SRS) configuration during initial access.

Method used

The UE provides assisting information about channel quality, such as RSRP and SINR, to the network node, enabling proper early SRS configuration with reduced overhead, including parameters like repetition factor and symbol number.

Benefits of technology

Enables efficient early SRS configuration by providing the network with necessary CSI before RRC completion, improving network performance and reducing signaling overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026064086_19112026_PF_FP_ABST
    Figure EP2026064086_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A method, system and apparatus are disclosed for sending to the network node assisting information related to a first Sounding Reference Signal (SRS) configuration, where the assisting information comprises channel quality or reference signal quality and receiving, from the network node, a second SRS configuration that is based on the assisting information, where the second SRS configuration comprises information about the channel quality before or immediately after initial access.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] METHOD AND SYSTEM FOR ASSISTING INFORMATION REPORTING FOR EARLY SOUNDING REFERENCE SIGNAL (SRS) CONFIGURATION FIELD

[0002] The present disclosure relates to wireless communications, and in particular, to assisting information for configuring a UE with early Sounding Reference Signal (SRS) configuration.

[0003] BACKGROUND

[0004] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0005] Sounding Reference Signal (SRS)

[0006] In NR, SRS is used for providing Channel State Information (CSI) to the network node (e.g., gNB) in the uplink (UL). The usage of SRS includes, e.g., deriving the appropriate transmission / reception beams and / or to perform link adaptation (i.e., setting the transmission rank and the Modulation and Coding Scheme (MCS)), and for selecting downlink (DL) (e.g., for Physical Downlink Shared Channel (PDSCH) transmissions) and UL (e.g., for Physical Uplink Shared Channel (PUSCH) transmissions) Multiple-Input Multiple-Output) MIMO precoding.

[0007] In LTE and NR, the SRS is configured via Radio Resource Control (RRC), where parts of the configuration can be updated (for reduced latency) through Medium Access Control-Control Element (MAC-CE) signaling. The configuration includes, for example, the SRS resource allocation (the time / frequency mapping and the sequence to use) as well as the time-domain behavior (aperiodic, semi-persistent, or periodic). For aperiodic SRS transmission, the RRC configuration does not activate an SRS transmission from the UE but instead a dynamic activation trigger is transmitted from the network node in the DL, via the Downlink Control Information (DCI) in the Physical Downlink Control Channel (PDCCH) which instructs the UE to transmit the SRS once, at a predetermined time.

[0008] When configuring SRS transmissions, the network node configures, through the SRS-Configuration Information Element (SRS-Config IE), a set of SRS resources and aset of SRS resource sets, where each SRS resource set contains one or more SRS resources.

[0009] Each SRS resource set can be configured with a certain usage (depending on what the SRS transmission shall be used for, see 3GPP TS 38.214), by setting the RRC parameter ‘usage’ to one of ‘antennaSwitching’, ‘codebook’, ‘nonCodebook’, and ‘beamManagement’ .

[0010] a) 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 network node can use reciprocity to set a suitable DL precoders). The UE is expected to transmit one SRS port per UE antenna port.

[0011] b) An SRS resource set that is configured with usage ‘codebook’ is used for codebook (CB)-based UL transmission (i.e., used to sound the different UE antennas, or antenna ports, and help the network node to determine / signal a suitable UL precoder, transmission rank, and MCS for PUSCH transmission). There are up to two SRS resources in an SRS resource set with usage ‘codebook’. How SRS ports are mapped to UE antenna ports is, however, up to UE implementation and not known to the network node.

[0012] c) An SRS resource set that is configured with usage ‘nonCodebook’ is used for New Channel Block (NCB)-based UL transmission. Specifically, the UE transmits one SRS resource per candidate beam (suitable candidate beams are determined by the UE based on, e.g., CSLReference Signal (RS) measurements in the DL, and in this case, some degree of beam reciprocity may need to hold). The network node then measures such SRS resources and determines which UL beam(s) that the UE should apply for PUSCH transmission. The network node then indicates to the UE which beams it should apply to the UE via indicating a subset of said SRS resources. One UL layer will be transmitted per indicated SRS resource. Note that how the UE maps SRS ports to antenna ports is up to UE implementation and is not known to the network node.

[0013] d) An SRS resource set that is configured with usage ‘beamManagement’ is used (e.g., for frequency bands above 6 GHz (i.e., for Frequency Range (FR)-2)) to evaluate different UE beams for analog beamforming arrays. The UE transmits one SRS resource per analog beam, and the network node will perform a reference signal received power (RSRP) measurement per transmitted SRS resource and, in this way, determine a suitable UE beam that is reported to the UE.SRS Configuration

[0014] Each SRS resource is configured with the following in RRC.

[0015] See ASN code in 3 GPP TS 38.331 version 16.1.0:

[0016] SRS -Re source ::= SEQUENCE {

[0017] srs-Resourceld SRS-Resourceld,

[0018] nrofSRS-Ports ENUMERATED {portl, ports2, ports4{, ptrs-Portlndex ENUMERATED {n0, nl } OPTIONAL, - Need R

[0019] transmissionComb CHOICE {

[0020] n2 SEQUENCE {

[0021] comb Off set-n2 INTEGER (0..1),

[0022] cyclicShift-n2 INTEGER (0..7)

[0023] },

[0024] n4 SEQUENCE {

[0025] comb Off set-n4 INTEGER (0 .3),

[0026] cyclicShift-n4 INTEGER (0 .11)

[0027] }

[0028] },

[0029] resourceMapping SEQUENCE {

[0030] startPosition INTEGER (0 .5),

[0031] nrofSymbols ENUMERATED {nl, n2, n4}, repetitionFactor ENUMERATED {nl, n2, n4{

[0032] },

[0033] freqDomainPosition INTEGER (0..67),

[0034] freqDomainShift INTEGER (0..268),

[0035] freqHopping SEQUENCE {

[0036] c-SRS INTEGER (0 .63),

[0037] b-SRS INTEGER (0 .3),

[0038] b-hop INTEGER (0 .3)

[0039] groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping },

[0040] resourceType CHOICE {

[0041] aperiodic SEQUENCE {},

[0042] semi-persistent SEQUENCE {

[0043] periodicity AndOffset-sp SRS-PeriodicityAndOffset,

[0044] },

[0045] periodic SEQUENCE {

[0046] periodicity AndOffset-p SRS-PeriodicityAndOffset,

[0047] }

[0048] },

[0049] sequenceld INTEGER (0 .1023),

[0050] spatialRelationlnfo SRS-SpatialRelationlnfo OPTIONAL, - Need R

[0051] resourceMapping-r 16 SEQUENCE {

[0052] startPosition-rl6 INTEGER (0 .13),

[0053] nrofSymbols-rl6 ENUMERATED {nl, n2, n4{, repetitionFactor-rl6 ENUMERATED {nl, n2, n4}

[0054] } OPTIONAL - Need R

[0055] ]]

[0056] }

[0057] An SRS resource is configurable with respect to, e.g.,

[0058] 2) The number of SRS ports (1, 2, or 4), configured by the RRC parameter nrofSRS-Ports.

[0059] 3) The transmission comb (i.e., mapping to every 2nd or 4th subcarrier), configured by the RRC parameter transmissionComb, includes:

[0060] a) The comb offset, configured by the RRC parameter combOffset, is specified (i.e., which of the combs that should be used).

[0061] b) The cyclic shift, configured by the RRC parameter cyclicShift, that configures a (port-specific, for multi-port SRS resources) cyclic shift for the Zadoff-Chusequence that is used for SRS. The use of cyclic shifts increases the number of SRS resources that can be mapped to a comb (as SRS sequences are designed to be (almost) orthogonal under cyclic shifts), but there is a limit on how many cyclic shifts can be used (8 for comb 2 and 12 for comb 4).

[0062] 4) The time-domain position within a given slot, configured with the RRC parameter resourceMapping, includes:

[0063] a) The time-domain start position, which is limited to be one of the last 6 symbols (in NR Rel-15) or in any of the 14 symbols in a slot (in NR Rel-16), configured by the RRC parameter startPosition.

[0064] b) The number of symbols for the SRS resource (that can be set to 1, 2 or 4), configured by the RRC parameter nrofSymbols.

[0065] c) The repetition factor (that can be set to 1, 2 or 4), configured by the RRC 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.

[0066] 5) The sounding bandwidth, frequency-domain position and shift, and frequencyhopping pattern of an SRS resource (i.e., which part of the transmission bandwidth that is occupied by the SRS resource) is set through the RRC parameters freqDomainPo sition, freqDomainShift, and the freqH opping parameters c-SRS, b-SRS, and b-hop. The smallest possible sounding bandwidth is 4 RBs.

[0067] 6) The RRC parameter resourceType determines whether the SRS resource is transmitted as periodic, aperiodic (single transmission triggered by DCI), or semi persistent (same as periodic except for the start and stop of the periodic transmission is controlled through MAC-CE signaling instead of RRC signaling).

[0068] 7) The RRC parameter sequenceld specifies how the SRS sequence is initialized.

[0069] 8) The RRC parameter spatialRelationlnfo configures the spatial relation for the SRS beam with respect to another RS (which could be another SRS, a Synchronization Signal Block (SSB) or a CSI-RS). If an SRS resource has a spatial relation to another SRS resource, then this SRS resource should be transmitted with the same beam (i.e., virtualization) as the indicated SRS resource.

[0070] An illustration of how an SRS resource could be allocated in time and frequency within a slot (note that semi-persistent / periodic SRS resources typically span several slots), is provided in FIG. 1, where FIG. 1 is a schematic description of how an SRS resource could be allocated in time and frequency within a slot if resourceMapping-rl6 isnot signaled. In NR Rel-16, the additional (and optional) RRC parameter resourceMapping-r 16 was introduced. If resourceMapping-r 16 is signaled, the UE ignores the RRC parameter resourceMapping. The difference between resourceMapping-rl6 and esourceMapping is that the SRS resource (for which the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols and the repetition factor is still limited to 4) can start in any of the 14 OFDM symbols in a slot configured by the RRC parameter startPosition-r 16.

[0071] An SRS resource set is configured with the following in RRC. See ASN code in 3GPP TS 38.331 version 16.1.0:

[0072] SRS -Re source Set ::= SEQUENCE )

[0073] sr s-Re source S etld SRS -Re source S etld,

[0074] srs-ResourceldList SEQUENCE (SIZE(l..maxNrofSRS- ResourcesPerSet)) OF SRS-Resourceld OPTIONAL, — Cond Setup resourceType CHOICE {

[0075] aperiodic SEQUENCE {

[0076] aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),

[0077] csi-RS NZP-CSI-RS-Resourceld

[0078] OPTIONAL, — Cond NonCodebook

[0079] slotOffset INTEGER (1. 32)

[0080] OPTIONAL, - Need S

[0081] [[

[0082] aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(l..maxNrofSRS- TriggerStates-2))

[0083] OF INTEGER (L.maxNrofSRS-TriggerStates-1) OPTIONAL -Need M

[0084] ]]

[0085] },

[0086] semi-persistent SEQUENCE {

[0087] associatedCSLRS NZP-CSI-RS-Resourceld

[0088] OPTIONAL, — Cond NonCodebook},

[0089] periodic SEQUENCE {

[0090] associatedCSI-RS NZP-CSI-RS-Resourceld

[0091] OPTIONAL, — Cond NonCodebook

[0092] }

[0093] },

[0094] usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},

[0095] alpha Alpha

[0096] OPTIONAL, - Need S

[0097] pO INTEGER (-202..24)

[0098] OPTIONAL, - Cond Setup

[0099] pathlossReferenceRS PathlossReferenceRS-Config

[0100] OPTIONAL, - Need M

[0101] srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop}

[0102] OPTIONAL, - Need S

[0103] ... ,

[0104] [[

[0105] pathlossReferenceRSList-rl6 SetupRelease { PathlossReferenceRSList-rl6} OPTIONAL -Need M

[0106] ]]

[0107] }

[0108] SRS resource(s) will be transmitted as part of an SRS resource set, where all SRS resources in the same SRS resource set must share the same resource type. An SRS resource set is configurable with respect to, e.g.,

[0109] 9) For aperiodic SRS, the slot offset is configured by the RRC parameter slotOffset and sets the delay from the PDCCH trigger reception to the start of the SRS transmission.

[0110] 10) The resource usage, which is configured by the RRC parameter usage sets 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:

[0111] ‘antennaSwitching’, ‘codebook’, ‘nonCodebook’ and ‘beamManagement’.a) 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 network node can use reciprocity to set a suitable DL precoders). The UE is expected to transmit one SRS port per UE antenna port.

[0112] b) 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 network node to determine / signal a suitable UL precoder, transmission rank, and MCS for PUSCH transmission). There are up to two SRS resources in an SRS resource set with usage ‘codebook’. How SRS ports are mapped to UE antenna ports is, however, up to UE implementation and not known to the network node.

[0113] c) An SRS resource set that is configured with usage ‘nonCodebook’ is used for NCB-based UL transmission. Specifically, the UE transmits one SRS resource per candidate beam (suitable candidate beams are determined by the UE based on CSLRS measurements in the DL and, hence, reciprocity needs to hold). The network node can then, by indicating a subset of these SRS resources, determine which UL beam(s) that the UE should apply for PUSCH transmission. One UL layer will be transmitted per indicated SRS resource. Note that how the UE maps SRS ports to antenna ports is up to UE implementation and is not known to the network node.

[0114] d) An SRS resource set that is configured with usage ‘beamManagemenf is used (e.g., for frequency bands above 6 GHz (i.e., for FR2)) to evaluate different UE beams for analog beamforming arrays. The UE transmits one SRS resource per analog beam, and the network node will perform an RSRP measurement per transmitted SRS resource and, in this way, determine a suitable UE beam that is reported to the UE.

[0115] 11) The associated CSLRS (this configuration is only applicable for NCB-based UL transmission) for each of the possible resource types.

[0116] a) For an aperiodic SRS, the associated CSLRS resource is set by the RRC parameter csi-RS.

[0117] b) For semi-persistent / periodic SRS, the associated CSLRS resource is set by the RRC parameter associatedCSI-RS .

[0118] 12) The Power Class (PC) parameters, e.g., alpha and pO are used for setting the SRS transmission power. SRS has its own UL PC scheme in NR (see 3GPP TS 38.213), 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).Therefore, the SRS resource-set configuration determines, e.g., usage, power control, and slot offset for aperiodic SRS. The SRS resource configuration determines the time-and-frequency allocation, the periodicity and offset, the sequence, and the spatial-relation information.

[0119] SRS antenna switching

[0120] For reciprocity-based DL precoding, SRS is used to obtain CSI in the UL. It is desirable for the network (NW)(e.g., one or more network node) to sound all UE antennas (where sounding an antenna implies that SRS is transmitted from that antenna), but costly to equip the UE with many transmission (Tx) chains (UEs typically have more reception (Rx) chains than Tx chains). Therefore, NR supports SRS antenna switching for UEs equipped with more Rx chains than Tx chains. If a UE supports antenna switching, it will report so by means of UE-capability signaling (see, e.g., Table 1).

[0121] Table 1 SRS antenna-switching capabilities supported by the UE (see 3GPP TS 38.306).

[0122] supportedSRS- TxPortSwitch supportedSRS-TxPortSwitch-vl 610

[0123] tlr2 tlrl-tlr2

[0124] tlr4 tlrl-tlr2-tlr4

[0125] t2r4 tlrl-tlr2-t2r2-t2r4

[0126] t2r2 tlrl-t2r2

[0127] t4r4 tlrl-t2r2-t4r4

[0128] tlr4-t2r4 tlrl-tlr2-t2r2-tlr4-t2r4

[0129]

[0130] The left column of Table 1 lists UE capabilities for SRS antenna-switching that can be reported by a UE in NR Rel-15. For example, if a UE reports tlr2 it means that it has two antennas (it has two Rx chains) but can only transmit from one of those antennas at a time (it has one Tx chain). In this case, the 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 Service Capability Server (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.

[0131] In general, xTyR SRS antenna switching can be configured for a UE with x Tx chains and y Rx chains. FIG. 2 is a diagram of examples of xTyR SRS antenna switching for UE architectures with x=y / 2 Tx chains and y Rx chains, where 1T2R is shown on theleft side of FIG. 2, 2T4R in the middle of FIG. 2, and 4T8R shown on the right side of FIG. 2.

[0132] In NR Rel-16, additional UE capabilities for SRS antenna-switching were introduced, which are shown in the right column of Table 1. Here, the 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 network node. For example, the UE capability tlr 1 -tl r2 indicates that the network node can configure one single-port SRS resource (no antenna switching) or two single-port SRS resources (same as for the capability tlr2 described above) per SRS resource set with usage antennaSwitching.

[0133] In NR Rel-17, antenna switching was extended to up to 6 or 8 Rx ports, and 1, 2, or 4 Tx chains. The UE can indicate support for antenna-switching configurations beyond 4 Rx via higher-layer parameter srs-AntennaSwitchingBeyond4RX-r!7 (see 3 GPP TS 38.306), where an 11 -bit bitmap can be used to indicate which of the following antenna switching schemes are supported: {tlrl, t2r2, tlr2, t4r4, t2r4, tlr4, t2r6, tlr6, t4r8, t2r8, tlr8}.

[0134] In NR Rel-18, antenna switching was extended to 8 Tx for 8 Rx UE, by using an SRS resource with 8 SRS ports.

[0135] NR initial access

[0136] Before a UE can communicate with a network, it carries out a cell search to find, synchronize and identify a cell. Then, the UE can acquire basic system information and perform a random access procedure to establish a connection to the cell.

[0137] NR cell search and system information acquisition

[0138] In NR, the combination of synchronization signals (SS) and physical broadcast channel (PBCH) is referred to as a SS / PBCH block (SSB). Similar to LTE, a pair of SSs, primary synchronization signal (PSS) and secondary synchronization signal (SSS), is periodically transmitted on downlink from each cell to allow a UE to initially access the network. By detecting SSs, a UE can obtain the physical cell identity (PCI), achieve downlink synchronization in both time and frequency, and acquire the timing for PBCH. PBCH carries the master information block (MIB), which contains a minimum system information that a UE needs to acquire system information block 1 (SIB1). SIB1 carries the remaining minimum system information that is needed for a UE to be able to perform subsequent random-access procedures. SIB1 is transmitted in the same way as normal scheduled downlink data transmissions in NR, with the SIB1 information itself transmittedon the PDSCH physical channel and scheduling information, needed by the UE to find and decode the PDSCH, transmitted on the PDCCH physical channel within a so-called CORESET (Control Resource Set). As described below, information needed by the UE to derive the CORESET in which to find a PDCCH carrying scheduling information related to SIB1 transmission is carried within the PBCH.

[0139] The SSB periodicity can take different values (i.e., 5 ms, 10 ms, 20 ms, 40ms, 80 ms, 160 ms). For initial access, a UE assumes a SSB periodicity of 20 ms. Within one SSB period, the SSBs can be transmitted in a burst confined in one half frame (i.e., 5 ms). The maximum number (denoted as L) of SSBs in one burst is determined by the sub-carrier spacing. For a frequency range from 24.24GHz to 52.6GHz, L can be as large as 64.

[0140] As shown in FIG. 3, two types of SSBs can be transmitted in NR:

[0141] SSB that has an associated SIB1 being transmitted, referred to as celldefining (CD) SSB,

[0142] SSB that does not have an associated SIB 1 being transmitted, referred to as non-cell-defining (non-CD) SSB.

[0143] SSBs (CD-SSB as well as non-CD-SSB) can be transmitted on or outside of the synchronization raster. Transmitting the SSB on the synchronization raster means that the center frequency of the SSB is within a limited set of frequency-domain positions (the “synchronization raster”) defined in the 3GPP NR specifications. Only SSBs on the synchronization raster can be found by UEs prior to initial access. If the SSB also has an associated SIB1, a UE can then perform initial access using this SSB.

[0144] The content of the MIB which is transmitted on PBCH is specified in 3GPP specification TR 38.331:

[0145] - Extract from 3 GPP TR 38.331 - The MIB includes the system information transmitted on BCH.

[0146] Signaling radio bearer: N / A

[0147] RLC-SAP: TM

[0148] Logical channel: BCCH

[0149] Direction: Network to UE

[0150] MIB

[0151] - ASN1 START

[0152] - TAG-MIB-START

[0153] MIB ::= SEQUENCE )

[0154] systemFrameNumber BIT STRING (SIZE (6)),subCarrierSpacingCommon ENUMERATED {scsl5or60, scs30orl20{, ssb-SubcarrierOffset INTEGER (0..15),

[0155] dmrs-TypeA-Position ENUMERATED {pos2, pos3{,

[0156] pdcch-ConfigSIBl PDCCH-ConfigSIBl,

[0157] cellBarred ENUMERATED {barred, notBarred}, intraFreqReselection ENUMERATED {allowed, notAllowed}, spare BIT STRING (SIZE (1))

[0158] }

[0159] - TAG-MIB-STOP

[0160] — ASN1STOPMIB field descriptions

[0161] cellBarred

[0162] Value barred means that the cell is barred, as defined in TS 38.304

[0020] , This field is ignored by IAB-MT.

[0163] dmrs- TypeA-Position

[0164] Position of (first) DM-RS for downlink (see TS 38.211

[0016] , clause 7.4.1.1.2) and uplink (see TS 38.211

[0016] , clause 6.4.1.1.3).

[0165] intraFreqReselection

[0166] Controls cell selection / reselection to intra-frequency cells when the highest ranked cell is barred, or treated as barred by the UE, as specified in TS 38.304

[0020] , This field is ignored by IAB-MT.

[0167] pdcch- ConfigSIBl

[0168] Determines a common ControlResourceSet (CORESET), a common search space and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that SIB1 is absent, the field pdcch-ConfigSIB 1 indicates the frequency positions where the UE may find SS / PBCH block with SIB1 or the frequency range where the network does not provide SS / PBCH block with SIB1 (see TS 38.213

[0013] , clause 13).

[0169] ssb-SubcarrierOffset

[0170] Corresponds to kssB (see TS 38.213

[0013] ), which is the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. (See TS 38.211

[0016] , clause 7.4.3.1). For operation with shared spectrum channel access (see 37.213

[0048] ), this field corresponds to fcSSB, and kssB is obtained from fcSSB(see TS 38.211

[0016] , clause 7.4.3.1); the LSB of this field is used also for deriving the QCL relation between SS / PBCH blocks as specified in TS 38.213

[0013] , clause 4.1.

[0171] The value range of this field may be extended by an additional most significant bit encoded within PBCH as specified in TS 38.213

[0013] ,

[0172] This field may indicate that this cell does not provide SIB1 and that there is hence no CORESET#0 configured mMIB (see TS 38.213

[0013] , clause 13). In this case, the field pdcch-ConfigSIB 1 may indicate the frequency positions where the UE may (not) find a SS / PBCH with a control resource set and search space for SIB1 (see TS 38.213

[0013] , clause 13).

[0173]

[0174] subCarrierSpacingCommon

[0175] Subcarrier spacing for SI BL Msg.2 / 4 and MsgB for initial access, paging and broadcast Si-messages. If the UE acquires this MIB on an FR1 carrier frequency, the value scsl5or60 corresponds to 15 kHz and the value scs30or!20 corresponds to 30 kHz. If the UE acquires this MIB on an FR2 carrier frequency, the value scs!5or60 corresponds to 60 kHz and the value scs30or!20 corresponds to 120 kHz. For operation with shared spectrum channel access in FR1 (see 37.213

[0048] ) and for operation in FR2-2, the subcarrier spacing for SI BL Msg.2 / 4 and MsgB for initial access, paging and broadcast Si-messages is same as that for the corresponding SSB. For operation with shared spectrum channel access, this field instead is used for deriving the QCL relation between SS / PBCH blocks as specified in TS 38.213

[0013] , clause 4.1.

[0176] systemFrameNumber

[0177] The 6 most significant bits (MSB) of the 10-bit System Frame Number (SFN). The 4 LSB of the SFN are conveyed in the PBCH transport block as part of channel coding (i.e. outside the A7 / Z> encoding), as defined in clause 7.1 in TS 38.212

[0017] ,

[0178]

[0179] - End extract from TR 38.331 - Two parameters in the MIB (see above) provide information that assist UEs to find the PDCCH associated with SIB1 transmissions.

[0180] - The ssb-SubCarrierOffset provides information about the frequency offset between the detected SSB (the SSB within which the MIB is transmitted) and the Common Resource Block (CRB) grid.

[0181] The pdcch-ConfigSIB 1 provides further details of the PDCH transmission.

[0182] NR 4-step random access procedure

[0183] The 4-step random access procedure, also referred to as Type-1 random access procedure in 3GPP TS 38.213, is illustrated in FIG. 4. In the first step, a UE initiates the random-access procedure by transmitting in UL a random-access preamble (Msgl) on a physical random-access channel (PRACH). After detecting the Msgl, the gNB (network node) will respond by transmitting in DL a random-access response (RAR) on a PDSCH (Msg2). In the third step, after successfully decoding Msg2, the UE continues the procedure by transmitting in UL a PUSCH (Msg3) for terminal identification and RRC connection establishment request. In the last step of the procedure, the gNB transmits in DL a PDSCH (Msg4) for contention resolution.There can be cases that multiple UEs select the same random-access preamble and transmit the preamble on the same PRACH time / frequency resource. This preamble collision is called contention. One of the main purposes of applying Step 3 and Step 4 is to resolve such potential contention.

[0184] NR 2-step random access procedure

[0185] The 2-step random access procedure, also referred to as Type-2 random access procedure in 3GPP TS 38.213, is illustrated in FIG. 5.

[0186] In the first step, a UE sends a message A (MsgA) including random access preamble together with higher layer data such as RRC connection request possibly with some small payload on PUSCH.

[0187] After detecting the MsgA, the network sends RAR (called message B, MsgB) including UE identifier assignment, timing advance information, and contention resolution message etc.

[0188] Physical Random Access Channel (RACH) Procedure

[0189] Prior to initiation of the physical random access procedure, Layer 1 or physical layer receives from higher layers a set of SS / PBCH block indexes and provides to higher layers a corresponding set of RSRP measurements.

[0190] Physical random access procedure is triggered upon request of a PRACH transmission by higher layers or by a PDCCH order. A configuration by higher layers for a PRACH transmission includes the following:

[0191] • A configuration for PRACH transmission according to 3GPP TS 38.211 • A preamble index, a preamble SCS, PRACH target receive power, a corresponding RA-RNTI (RACH radio network temporary identifier), and a PRACH resource.

[0192] A PRACH preamble is transmitted according to the PRACH configuration with a transmission power on the indicated PRACH resource.

[0193] PRACH configuration can be cell specific or UE specific. Cell specific PRACH configuration is via a RACH-ConfigCommon information element (IE) while UE specific PRACH configuration is done via a RACH-ConfigDedicated IE. Both are described in 3GPP TS38.331.

[0194] For Type-1 random access procedure, a UE is provided with a total number, ^preamble °f PRACH preambles for both Contention-Based Random Access (CBRA) and Contention-Free Random Access (CFRA) in each PRACH occasion. The default

[0195]

[0196] is = 64 if it is not configured. The UE is also provided a number N of SS / PBCHblock indexes associated with one PRACH occasion and a number R of contention based preambles per SS / PBCH block index per valid PRACH occasion by a parameter called ssb-perRACH-OccasionAndCB-PreamblesPerSSB contained in RACH-ConfigCommon IE.

[0197] If N<1, one SS / PBCH block index is mapped to UN consecutive valid PRACH occasions and R contention based preambles with consecutive indexes associated with the SS / PBCH block index per valid PRACH occasion start from preamble index 0. An example is shown in FIG. 6, where N=l / 2, R=32, Np°emble= 64, and 4 SSBs. That is, FIG. 6 is an example of SSB to PRACH preamble mapping with N=l / 2 and R=32.

[0198] If N>1, R contention-based preambles with consecutive indexes associated with SS / PBCH block index n, 0<n<N-l, per valid PRACH occasion start from preamble indexn

[0199]

[0200] ’ ^preambie / ^- An example is shown in FIG. 7, where N=4, R=4, Np°efmble= 64, and 4 SSBs. For each PRACH occasion, PRACH preambles 0 to 3 are allocated to SSB#0 for CBRA, PRACH preambles 4 to 15 are allocated to SSB#0 for CFRA, PRACH preambles 16 to 19 are allocated to SSB#1 for CBRA and PRACH preambles 20 to 31 are allocated to SSB#1 for CFRA, and so on.

[0201] Association of CFRA preambles with SSBs can also be reconfigured via a higher parameter ssb-perRACH-Occasion in RACH-ConfigDedicated IE, in which the UE is provided with information about a number N of SS / PBCH block indexes associated with one PRACH occasion. The UE may also provide information about a mapping between a SSB or a CSI-RS index and a preamble index in a PRACH occasion.

[0202] PDCCH order initiated RACH procedure

[0203] A RACH procedure can be initiated by either the network node or the UE. It can be contention based (CB) or contention free (CF). A RACH procedure can be initiated by a PDCCH order sent from the network node to the UE for synchronizing the UL when UL time alignment may have been lost. PDCCH order is carried by DCI format 1-0 when the DCFs CRC is scrambled by a UE’s C-RNTI (Cell Radio Network Temporary Identifier) and the "Frequency domain resource assignment" field of the DCI contains all ones. The PDCCH order contains the following information:

[0204] • Random Access Preamble index: 6 bits according to a higher layer parameter “ra-Preamblelndex” in Clause 5.1.2 of 3GPP TS38.321.

[0205] • SS / PBCH index: 6 bits, If the value of the "Random Access Preamble index" is not all zeros, this field indicates the SS / PBCH that is to be used to determine a RACH (random access channel) occasion for PRACH (Physical random access channel) transmission; otherwise, this field is reserved.• PRACH Mask index. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the RACH occasion associated with the SS / PBCH indicated by "SS / PBCH index" for the PRACH transmission, according to Clause 5.1.1 of 3GPP TS38.321; otherwise, this field is reserved.

[0206] If the PRACH preamble index is non-zero, a contention free random access (CFRA) procedure is triggered, in which the PRACH preamble is allocated only for the UE in a corresponding PRACH resource.

[0207] If the PRACH preamble index is zero, and CFRA PRACH resources associated with SSBs have been provided in a UE specific RACH configuration in rach-ConfigDedicated IE, the UE first selects an SSB with SS-RSRP (SSB based Reference Signal Received Power) above a configured threshold, then selects a PRACH preamble according to the selected SSB. If the PRACH preamble index is zero, and CFRA resources associated with CSI-RSs have been provided in rach-ConfigDedicated IE, the UE first selects a CSI-RS with CSI-RSRP above a configured threshold, rsrp-ThresholdCSI-RS, then selects a PRACH preamble according to the selected CSI-RS. If the PRACH preamble index is zero and the CFRA PRACH resources associated with SSB or CSI-RS are not provided, a contention-based random access (CBRA) procedure is triggered by the PDCCH order, in which the UE selects a PRACH preamble randomly from a set of PRACH preambles configured for CBRA in the serving cell. Note that in this case, the same preamble could be selected by more than one UE in a same PRACH resource and contention could occur. PDCCH order triggered CBRA is only allowed for a SpCell, i.e., a primary cell in either a master cell group (MCG) or a secondary cell group (SCG), if cell groups are configured. The rach-ConfigDedicated IE is described in 3GPP TS38.331, the detailed procedure is described in 3GPP TS38.321 section 5.1.2.

[0208] If a UE is configured with two UL carriers for a serving cell and the UE detects a PDCCH order, the UE uses the UL / SUL indicator field value from the detected PDCCH order to determine the UL carrier for the corresponding PRACH transmission.

[0209] A RACH occasion is a time and frequency resource (i.e., a number of RBs in a number of OFDM symbols) allocated for PRACH transmission. Multiple RACH occasions may be configured in a PRACH configuration period consisting of multiple radio frames. RACH occasions may be multiplexed either in time or frequency.

[0210] From the physical layer perspective, the random access procedure triggered by a PDCCH order includes the transmission of random access preamble (Msgl) in a PRACH by a UE, the transmission of RAR (RACH response) message with a PDCCH and acorresponding PDSCH (Msg2), and when applicable, the transmission of a PUSCH scheduled by a RAR UL grant, and PDSCH for contention resolution if the RACH procedure is contention based.

[0211] One of the problems with existing networks is that the NW has no CSI before RRC configuration is completed and the UE sends a first CSI report or a first SRS transmission.

[0212] SUMMARY

[0213] During the planning discussions for NR Rel-20 and 6G, it has been suggested to specify methods for early SRS where the NW can be provided with information about the channel quality before or immediately after the initial access.

[0214] In order to provide the UE with proper early SRS configuration, it is beneficial if the NW has an estimation of the channel quality, which is currently not available at the NW during the initial access. How the UE can assist the NW for appropriate early SRS configuration is an ongoing problem. In one or more embodiments, the early SRS configuration comprises information about the channel quality before or immediately after initial access.

[0215] Some embodiments advantageously solve some problems with existing systems and / or specifications by, for example, providing methods, systems, and apparatuses for a UE to supply assisting information to a network node so that the network node can configure the UE with early SRS configuration. In one or more embodiments, the assisting information may include channel quality or reference signal quality.

[0216] In some embodiments, the UE provides the NW with assisting information so that the NW can configure the UE with proper early SRS configuration with limited overhead.

[0217] During the Msgl and / or Msg 3 transmission, the UE provides the NW with explicit or implicit information about the channel quality. The assisting information may include information about, e.g., whether the UE has performed measurement on all SSBs and / or whether the UE has selected the best SSB (with the highest RSRP), a report of the measured RSRP, Signal-to-Interference-plus-Noise Ratio (SINR), Reference Signal Received Quality (RSRQ), etc., a power headroom report or a configuration or indication associated with SRS Tx power, repetition factor, etc. Such information could be used to configure the early SRS transmission by, e.g., setting a proper repetition factor of an SRS resource, number of symbols of an SRS resource, frequency allocation etc., and / or reducing the signaling overhead for the SRS configuration where, for instance, the repetition factor may be automatically updated based on the RSRP level of the SSB. Inthis way, some embodiments described herein, improve the efficiency of early SRS configuration and addresses one of the topics of interest in NR Rel-20 and 6G.

[0218] In accordance with one aspect of the present disclosure, a method implemented in a user equipment (UE) that is configured to communicate with a network node, is provided. The method includes sending to the network node assisting information related to a first Sounding Reference Signal (SRS) configuration, the assisting information comprising channel quality or reference signal quality, and receiving from the network node, a second SRS configuration that is based on the assisting information, the second SRS configuration comprising information about the channel quality before or immediately after an initial random access procedure.

[0219] In accordance with some aspects of this aspect, the method further includes receiving, from the network node, an indication whether SRS is supported by the network node.

[0220] In some embodiments, the indication comprises one or more of one or more sets of pre-configurations for at least some parameters associated with the SRS configuration, a flag indicating whether the second SRS configuration is supported by the network node, and information about uplink resources for the UE to report the assisting information.

[0221] In some embodiments, the assisting information comprises one or more of information about channel quality associated with a selected Synchronization Signal Block (SSB) report, a flag indicating whether a selected SSB has passed a minimum Reference Signal Received Power (RSRP) threshold, information about whether the UE has performed measurements on all SSBs or not and information about one or more of suggested SRS transmission power, a repetition factor of an SRS resource, and a number of symbols of an SRS resource.

[0222] In some embodiments, wherein the assisting information is sent to the network node explicitly as a part of at least one of Message 1, Msgl, and Message 3, Msg3 or implicitly during transmission of at least one of Msgl, and Msg3.

[0223] In accordance with another aspect of the present disclosure, a method implemented in a network node that is configured to communicate with a user equipment (UE), is provided. The me4thod includes receiving, from the UE, assisting information related to a first Sounding Reference Signal (SRS) configuration, the assisting information comprising channel quality or reference signal quality, and transmitting, to the UE, a second SRS configuration that is based on the assisting information, the second SRS configurationcomprising information about the channel quality before or immediately after an initial random access procedure.

[0224] In accordance with some embodiments of this aspect, the method further includes sending an indication to the UE, the indication being related to the second SRS configuration.

[0225] In some embodiments, the method further includes, along with the SRS configuration, triggering the second SRS configuration.

[0226] In some embodiments, at least one of the second SRS configuration and the triggering is via a Message 4 (Msg4) of the random access procedure.

[0227] In some embodiments, if a reported Reference Signal Received Power (RSRP) is below a threshold, further comprising cancelling the second SRS configuration.

[0228] In accordance with another aspect of the present disclosure, a user equipment (UE) configured to communicate with a network node, is provided. The UE is configured to, send, to the network node, assisting information related to a first Sounding Reference Signal (SRS) configuration, the assisting information comprising channel quality or reference signal quality, and receive, from the network node, a second SRS configuration that is based on the assisting information, the second SRS configuration comprising information about the channel quality before or immediately after initial access.

[0229] In accordance with some embodiments of this aspect, the UE is further configured to receive, from the network node, an indication whether SRS is supported by the network node.

[0230] In some embodiments, the indication comprises one or more of one or more sets of pre-configurations for at least some parameters associated with the SRS configuration, a flag indicating whether the second SRS configuration is supported by the network node, and information about uplink resources for the UE to report the assisting information.

[0231] In some embodiments, the assisting information comprises one or more of information about channel quality associated with a selected Synchronization Signal Block (SSB) report, a flag indicating whether a selected SSB has passed a minimum Reference Signal Received Power (RSRP) threshold, information about whether the UE has performed measurements on all SSBs or not and information about one or more of suggested SRS transmission power, a repetition factor of an SRS resource, and a number of symbols of an SRS resource.In some embodiments wherein the assisting information is sent to the network node explicitly as a part of at least one of Message 1, Msgl, and Message 3, Msg3 or implicitly during transmission of at least one of Msgl, and Msg3.

[0232] In accordance with another aspect of the present disclosure, a network node configured to communicate with a user equipment (UE) is provided. The network node is configured to receive, from the UE, assisting information related to a first Sounding Reference Signal (SRS) configuration, the assisting information comprising channel quality or reference signal quality, and transmit, to the UE, a second SRS configuration that is based on the assisting information, the second SRS configuration comprising information about the channel quality before or immediately after an initial random access procdure.

[0233] In accordance with some embodiments of this aspect, the network node is further configured to send an indication to the UE, the indication being related to the second SRS configuration.

[0234] In some embodiments, the network node is further configured to, along with the SRS configuration, trigger the second SRS configuration.

[0235] In some embodiments, least one of the second SRS configuration and the triggering is via a Message 4 (Msg4) of the random access procedure.

[0236] In some embodiments, if a reported Reference Signal Received Power (RSRP) is below a threshold, the network node is further configured to cancel the second SRS configuration.

[0237] BRIEF DESCRIPTION OF THE DRAWINGS

[0238] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0239] FIG. 1 is a diagram of how an SRS resource could be allocated in time and frequency within a slot;

[0240] FIG. 2 is a diagram of example antenna switching for UE architectures;

[0241] FIG. 3 is a diagram of cell-defined and non-cell-defined SSBs;

[0242] FIG. 4 is a diagram of a four-step random access procedure for initial access; FIG. 5 is a diagram of a two-step random access procedure for initial access;

[0243] FIG. 6 is a diagram of an example of SSB to PRACH preamble mapping;FIG. 7 is a diagram of an example of SSB to PRACH preamble mapping with N=4 and R=4;

[0244] FIG. 8 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0245] FIG. 9 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0246] FIG. 10 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0247] FIG. 11 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0248] FIG. 12 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0249] FIG. 13 is a block diagram illustrating a virtualization environment according to some embodiments of the present disclosure; and

[0250] FIG. 14 is a flowchart of another example process from the perspective of the network node according to some embodiments of the present disclosure.

[0251] DETAILED DESCRIPTION

[0252] The present disclosure solves the problem of how the UE can provide the NW with assisting information about the channel quality and / or reference signal quality so that the NW can configure the UE with early SRS configuration with limited signaling overhead. In some embodiments of the present disclosure, the UE will provide the NW in Msgl and / or Msg3 of initial access with information about, e.g., the RSRP / SINR / RSRQ of the measured SSB, and / or indication / determination about the SRS configurations. In this way, the NW is provided with information about the channel quality which, in turn, enables the NW to configure the UE. In addition, the signaling overhead is reduced where, for instance, the repetition factor is automatically updated based on the RSRP level of the selected SSB. Alternatively, the assisting information enables the NW to decide whether to trigger the early SRS or not. In this way, the present disclosure improves the efficiency of the early SRS and addresses one of the topics of interest in NR Rel-20 and 6G.

[0253] Some embodiments of the present disclosure enable the NW to configure the UE with early SRS configuration and / or decide whether to trigger the early SRS or not. In one or more embodiments, the early SRS configuration comprises information about thechannel quality before or immediately after initial access. In addition, such methods can reduce the signaling overhead associated with early SRS configuration where some configurations can be automatically updated based on the reported assisting information. If the NW has limited information about the channel quality, it may consider conservative SRS configurations, e.g., high SRS Tx power, repetition factor, etc., which are not efficient. With the embodiments disclosed herein, such problems are avoided. In this way, the present disclosure addresses one of the topics of interest in 3GPP NR Rel-20 and 6G.

[0254] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to a UE supplying assisting information so that the network can configure the UE with early SRS configuration. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0255] Throughout this disclosure, the term SRS is used. However, another term might be used in 6G. In either event, the term refers to a UL reference signal for sounding the channel from the UE to the network node.

[0256] The terminologies used in this disclosure are for the NR initial access. However, in 6G, different terminologies or signalings may be used during the initial access.

[0257] The present disclosure discusses the 4-step initial access procedure when an idle UE connects to the NW which is expected to be a case of interest for early SRS. However, the same approaches are also applicable in, e.g., the 2-step random access procedure where, e.g., the UE may send the assisting information via Msg-A (as discussed above.

[0258] The present disclosure is also applicable in the cases with SCell activation or switching out of SCell dormancy in connected mode.

[0259] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or“including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0260] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0261] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0262] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0263] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” usedherein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0264] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0265] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0266] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0267] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0268] Some embodiments are directed to a UE supplying assisting information to the network node so that the network node can configure the UE with early SRS configuration.

[0269] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 8 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more network nodes 15. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0270] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of related communication standards (e.g., 4G, 5G and 6G 3GPP communication standards) and, as aresult, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.

[0271] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTEZE-UTRAN, a gNB for NR / NG-RAN (i.e., being configured for multiradio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC) and / or Wi-Fi.

[0272] A network node 16 (eNB or gNB) is configured to include an SRS configuration unit 24 which is configured to perform one or more network node 16 functions that are described herein such as, for example, determining a SRS configuration for the UE 22. A user equipment 22 is configured to include an assisting information unit 26 which is configured to perform one or more UE 22 functions that are described herein such as, for example, assisting the network node 16 in determining early SRS configuration.

[0273] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 9.

[0274] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a communication interface 29 comprising a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0275] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application SpecificIntegrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0276] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16.

[0277] Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include SRS configuration unit 24 which is configured to perform one or more network node 16 functions that are described herein such as, for example, determining a SRS configuration for the UE 22.

[0278] The network node 16 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeB s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 16 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 40 or portions of memory 40 for different RATs) and some components may be reused (e.g., a same antenna may be shared by different RATs). The network node 16 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 16, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN,Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 16.

[0279] In certain alternative embodiments, network node 16 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, the processing circuitry 36 includes radio front-end circuitry and is connected to the antenna 34. Similarly, in some embodiments, all or some of the RF receivers, transmitters and / or transceivers are part of the radio interface 30. In still other embodiments, the communication interface 29 includes one or more ports or terminals, the radio interface 30, and the RF receiver, transmitter and / or transceiver, and the communication interface 31 communicates with baseband processing circuitry, which is part of a digital unit (not shown).

[0280] The antenna 34 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 34 may be coupled to the radio front-end circuitry in radio interface 30 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 34 is separate from the network node 16 and connectable to the network node 16 through one or more interfaces or ports.

[0281] Network node 15 can include one or more components described above with respect to network node 16, e.g., communication interface 29, radio interface 30, antenna 34, ports, processing circuitry 36, processor 38, memory 40 and software 42. These elements of network node 15 can be arranged such that network node 15 can perform various core network functions. Network node 15 can communicate wirelessly or via a wired connection with network nodes 16 via communication link 59.

[0282] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0283] Communication functions of the radio interface 46 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication,multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0284] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0285] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0286] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causesthe processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include assisting information unit 26 which is configured to perform one or more UE 22 functions that are described herein such as, for example, assisting the network node 16 in determining early SRS configuration.

[0287] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 9 and independently, the surrounding network topology may be that of FIG. 8.

[0288] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, 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.

[0289] Although FIGS. 8 and 9 show various “units” such as SRS configuration unit 24 and assisting information unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0290] FIG. 10 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 10 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG.

[0291] 10 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 62b and STA 62c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), orthe like, including UEs 22 that are shown and described with respect to FIGS. 8 and 9. In other words, in some embodiment, STA 62 is a UE 22. Further, stations 62 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0292] Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0293] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like.

[0294] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 10 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.

[0295] FIG. 11 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the SRS configuration unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to receive (Block S100) from the UE 22, assisting information related to a first SRS configuration, where the assisting information comprises channel quality or reference signal quality, as described herein. Network node 16 is further configured to transmit (Block SI 02) to the UE 22, a second SRS configuration (e.g., early SRS configuration) that is based on the assistinginformation, where the second SRS configuration comprises information about the channel quality before or immediately after initial access, as described herein.

[0296] In some embodiments, network node 16 is further configured to send an indication to the UE 22, the indication being related to the second SRS configuration.

[0297] In some embodiments, network node 16 is further configured to, along with the SRS configuration, trigger the second SRS configuration.

[0298] In some embodiments, the second SRS configuration and / or the triggering is via a Message 4 (Msg4) of a random access procedure.

[0299] In some embodiments, network node 16 is further configured to, based on the received assisting information, determine whether to trigger the second SRS configuration.

[0300] In some embodiments, if a reported RSRP is below a threshold, network node 16 is further configured to cancel the second SRS configuration.

[0301] In some embodiments, network node 16 is further configured to use the assisting information in determining different parameters, including at least one of a repetition factor of an SRS resource, a number of symbols of an SRS resource, a UL power of SRS transmission, and SRS bandwidth.

[0302] FIG. 12 is a flowchart of an example process in a UE 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of UE 22 such as by one or more of processing circuitry 50 (including the assisting information unit 26), processor 52, and / or radio interface 46. UE 22 is configured to send (Block SI 04) to the network node 16 assisting information related to a first SRS configuration, where the assisting information comprises channel quality or reference signal quality, as described herein. UE 22 is further configured to receive (Block SI 06) from the network node 16, a second SRS configuration that is based on the assisting information, where the second SRS configuration comprises information about the channel quality before or immediately after initial access, as described herein.

[0303] In some embodiments, UE 22 is further configured to receive, from network node 16, an indication whether SRS is supported by network node 16.

[0304] In some embodiments, the indication contains one or more sets of preconfigurations for at least some parameters associated with the SRS configuration.

[0305] In some embodiments, the indication is a flag indicating whether the early SRS configuration is supported by network node 16.In some embodiments, the indication comprises information about uplink resources for the UE 22 to report the assisting information.

[0306] In some embodiments, the assisting information comprises information about channel quality associated with a selected SSB report.

[0307] In some embodiments, the assisting information comprises a flag indicating whether a selected SSB has passed a minimum RSRP threshold.

[0308] In some embodiments, the assisting information comprises one or more of information about suggested SRS transmission power, a repetition factor of an SRS resource, and a number of symbols of an SRS resource.

[0309] In some embodiments, the assisting information is sent to network node 16 as a new signaling before Message 4 (Msg4) of a random access procedure.

[0310] In some embodiments, the assisting information comprises a power headroom report, where the power headroom report includes information about how much additional transmission power UE 22 has available beyond what is currently being used.

[0311] In some embodiments, either before, with, or after the sending of the assisting information, UE 22 is further configured to report to network node 16 a capability report associated with the second SRS configuration.

[0312] In some embodiments, UE 22 is further configured to transmit SRSs based on the second SRS configuration received from network node 16.

[0313] In some embodiments, the assisting information is sent to the network node as a part of at least one of Message 1 (Msgl) and Message 3 (Msg3).

[0314] O-RAN Implementation

[0315] For example, in some embodiments, the telecommunication system 10 includes one or more Open-RAN (ORAN) network nodes 16. An ORAN network node 16 is a node in the telecommunication system 10 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 system 10, including one or more network nodes 16 in the access network 12 and / or core network nodes 14.

[0316] Examples of an ORAN network node 16 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 anycombination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 16 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 22a, 22b, 22c, and 22d (one or more of which may be generally referred to as UEs 22) to the core network 14 over one or more wireless connections.

[0317] FIG. 13 is a block diagram illustrating a virtualization environment 108 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, 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 108 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. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 108 includes components defined by the 0-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0318] Applications 110 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 108 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0319] Hardware 112 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices asdescribed herein, such as a network interface, input / output interface, and so forth.

[0320] Software may be executed by the processing circuitry to instantiate one or more virtualization layers 114 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 116a and 116b (one or more of which may be generally referred to as VMs 103), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 101 may present a virtual operating platform that appears like networking hardware to the VMs 103.

[0321] The VMs 116 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 114. Different embodiments of the instance of an application / virtual appliance 110 may be implemented on one or more of VMs 116, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0322] In the context of NFV, a VM 116 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 116, and that part of hardware 112 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 116 on top of the hardware 112 and corresponds to the application / virtual appliance 110.

[0323] Hardware 112 may be implemented in a standalone network node 16 with generic or specific components. Hardware 112 may implement some functions via virtualization. Alternatively, hardware 112 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 118, which, among others, oversees lifecycle management of application / virtual appliance 96. In some embodiments, hardware 98 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities,such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 120 which may alternatively be used for communication between hardware nodes and radio units.

[0324] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for a UE 22 supplying assisting information associated with early SRS configuration.

[0325] Some embodiments address how the UE 22 can provide the network node 16 with assisting information about the channel quality so that the network node 16 can configure the UE 22 with early SRS configuration with limited signaling overhead. One or more network node 16 functions described below may be performed by one or more of processing circuitry 36, processor 38, SRS configuration unit 24, communication interface 29, etc. One or more UE 22 functions described below may be performed by one or more of processing circuitry 50, processor 52, assisting information unit 26, radio interface 46, etc.

[0326] In some embodiments, in the 4-step random access procedure, upon receiving Synchronization Signals (SS) / PBCH block, including SIB1, the UE 22 initiates the random-access procedure by transmitting in UL a random-access preamble (Msgl) on a physical random-access channel (PRACH). Detecting the Msgl, the network node 16 will respond by transmitting in DL a random-access response (RAR) on a PDSCH (Msg2). After successfully decoding Msg2, the UE 22 continues the procedure by transmitting in UL a PUSCH (Msg3) for terminal identification and RRC connection establishment request. Finally, in Msg4, the network node 16 transmits in DL a PDSCH for contention resolution.

[0327] In order to configure the UE 22 with early SRS configurations, it is beneficial if the network node 16 is provided with an estimation of the channel quality, otherwise it may configure all UEs 22 with conservative configurations (e.g., too high Tx power, SRS repetition, etc.) which are not efficient. Such assisting information can also help the network node 16 to decide whether early SRS should be triggered for a UE 22 or not. The present disclosure discloses methods for the UE 22 to provide the network node 16 with assisting information enabling proper early SRS configuration.FIG. 14 shows a flowchart of another example process performed by the network node 16. Aspects of the present disclosure are included in Step 124 of FIG. 14. In the following discussion, it is assumed that the UE 22 supports the early SRS.

[0328] In FIG. 14, the network node 16 optionally sends (Block SI 22) to UE 22 an indication related to early SRS. This indication indicates whether early SRS is supported by the network node 16 or not. Here, the indication may contain one or more sets of preconfigurations for at least some parameters associated with SRS configuration. In the context of one or more embodiments, “pre-configuration” means that when the network node 16 indicates to UE 22 the support for early SRS configuration, the network node 16 may also inform UE 22 with some pre-configurations of early SMS configurations such as set of possible bandwidths, comb offsets, repetition factors, etc.

[0329] In some embodiments, the indication may be a flag (e.g., an indication flag) indicating whether the early SRS is supported by the network node 16 or not.

[0330] In some embodiments, the indication comprises information about the UL resources for the UE 22 to report the assisting information.

[0331] The network node 16 receives (Block S124) from the assisting information. As a part of SS / PBCH block transmission, the UE 22 receives one or multiple SSBs (as discussed above). In general, the UE 22 is not expected to necessarily perform measurements on all SSBs. The network node 16 provides the UE 22 with a minimum RSRP threshold, and the UE 22 can select one SSB which satisfies the minimum RSRP threshold. Also, if the UE 22 finds no SSB satisfying the minimum RSRP threshold, UE 22 selects one of them (e.g., the one with the highest RSRP). Whether the UE 22 performs measurements on all SSBs or not may depend on, e.g., the UE 22 capabilities, UE 22 implementation (it is different for different UE manufacturers), delay constraints, etc.

[0332] In some embodiments, the assisting information may comprise information about the channel quality associated with the selected SSB, e.g., RSRP, SINR, RSRQ measurement report.

[0333] In some embodiments, the assisting information may comprise a flag indicating whether the selected SSB has passed the minimum RSRP threshold or not.

[0334] In some embodiments, the indication may comprise information about whether the reported measurement is reliable or not. There are different methods for the UE 22 to understand whether a measurement is reliable or not, e.g., based on the UE’s mobility, whether the reported RSRP is above the minimum RSRP threshold or not, or whether the UE 22 has checked all SSBs or not. Also, the UE 22 may perform channel estimationbased on received SSB and if the estimation error is high, the UE 22 understands that the measurement is not reliable.

[0335] In some embodiments, the assisting information may comprise information about the suggested SRS Tx power, repetition factor of an SRS resource, the number of symbols of an SRS resource, etc.

[0336] In some embodiments, the assisting information may comprise the power headroom report, i.e., an information about how much additional transmission power the UE 22 has available beyond what is currently used (where the power headroom report, e.g., could be related to Msgl or Msg3 transmission).

[0337] In some embodiments, the assisting information is sent to the network node 16 as a part of Msgl and / or Msg3.

[0338] In some embodiments, the assisting information is transmitted to the network node 16 as a new signaling before Msg4.

[0339] In some embodiments, the assisting information may be indicated explicitly or implicitly. Here, in some embodiments, the implicit indication can be via, e.g., sending a specific preamble associated with the selected SSB if the SSB is selected based on measurement on all SSBs. In general, the mapping between SSBs and PRACH resources is defined by the network node 16 and can follow different SSB-to-random access resource mappings (e.g., 1-to-l, many-to-one, one-to-many). Then, with implicit indication, for a selected SSB, the UE 22 may consider a specific preamble so that the network node 16 understands that the UE 22 has checked all SSBs. Such specific preambles may be defined in 3 GPP specification.

[0340] In some embodiments, before, after, or along with the assisting information, the UE 22 may report the network node 16 a capability report associated with early SRS.

[0341] The network node 16 determines the early SRS configuration and indicates the configuration to the UE 22 by providing (Block SI 12) the UE 22 with early SRS configuration based on the received assisting information.

[0342] In some embodiments, along with the configuration, the network node 16 triggers the early SRS transmission.

[0343] In some embodiments, the early SRS configuration and / or triggering may be via Msg4.

[0344] In some embodiments, based on the received assisting information, the network node 16 decides whether early SRS should be triggered or not. For example, if the reported RSRP / SINR / RSRQ is quite low (e.g., below a threshold), the network node 16may cancel the early SRS transmission. For example, the early SRS may be canceled if the reported RSRP is below a threshold X dBm, e.g., X=-100 dBm (since channel estimation based on SRS might be too un-reliable in poor channel conditions).

[0345] In some embodiments, the assisting information may enable the reduction of the configuration overhead. For example, the repetition factor can be automatically updated based on the reported RSRP level of the SSB. Here, for low RSRP, a higher order SRS repetition factor may be automatically used, to reduce signaling overhead of number of SRS repetitions to be used.

[0346] In some embodiments, based on the reported RSRP, the number of symbols for an SRS resource, the comb size or the SRS periodicity may be automatically updated. For example, for an RSRP below a threshold Y dBm (e.g., Y=-90 dBm), the SRS may be configured with N symbols (e.g., N=4 instead of N=l). Lower comb size may be considered for better resolution and / or the SRS periodicity may be increased for faster tracking. The present disclosure includes such automatic updates of the SRS configurations based on the reported channel (e.g., by some tables).

[0347] In some embodiments, the bandwidth of the SRS is automatically adapted based on the indicated RSRP. For example, if the RSRP is low, a smaller SRS bandwidth is used in order to maintain a reasonable power spectral density of the SRS, which would enable reliable channel estimation.

[0348] In some embodiments, multiple different RSRP ranges are defined (e.g., -110 dBm to -100 dBm, -lOOdBm to -90 dBm, and so on), and the RSRP range -110 dBm to -100 dBm might be associated with a repetition factor 4 and / or SRS bandwidth of 50 PRBs, and the RSRP range -lOOdBm to -90 dBm might be associated with a repetition factor 1 and / or an SRS bandwidth of 100 PRBs, etc.

[0349] In some embodiments, instead of using RSRP, the UE 22 is provided with the Total Radiated Power (TRP) output power of the SSBs (e.g., in broadcasted system information), and together with the TRP output power of the SSBs and the measured RSRP of the SSBs the UE 22 determines the path loss between the TRP and UE 22, and the UE 22 uses the path loss to determine one or more SRS parameters like repetition factor, SRS bandwidth, etc. (this could be beneficial since SRS link budget is more dependent on the path loss between the TRP and UE 22 than the RSRP).

[0350] In some embodiments, this estimated path loss is also used for determining the output power of the early SRS.In some embodiments, the assisting information may help the network node 16 to determine different parameters such as the repetition factor of an SRS resource, the number of symbols of an SRS resource, the UL power for SRS transmission, SRS bandwidth etc.

[0351] The UE 22 will transmit the early SRSs based on the configurations received from the network node 16.

[0352] As described herein, the present disclosure enables the network node 16 to understand the channel quality associated with UE 22 before the early SRS transmission. This enables the network node 16 to configure the UE 22 with early SRS transmission configurations which, in turn, results in an early understanding about the channel quality and an improved throughput. Moreover, the configuration overhead can be reduced based on the received assisting information and early SRS is used only in the cases where it is expected to be useful. In this way, the present disclosure addresses one of the topics of interest in NR Rel-20 and 6G.

[0353] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0354] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processingapparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0355] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0356] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0357] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0358] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0359] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

44Claims:

1. A method implemented in a user equipment, UE, (22) that is configured to communicate with a network node (16), the method comprising:sending to the network node (16) assisting information related to a first Sounding Reference Signal, SRS, configuration, the assisting information comprising channel quality or reference signal quality (SI 04); andreceiving from the network node (16), a second SRS configuration that is based on the assisting information, the second SRS configuration comprising information about the channel quality before or immediately after initial access (SI 06).

2. The method of claim 1, wherein the second SRS configuration received comprises updated channel quality information based on the channel quality or reference signal quality in the assisting information.

3. The method of Claim 1 or 2, further comprising receiving, from the network node (16), an indication whether SRS is supported by the network node (16).

4. The method of Claim 3, wherein the indication comprises one or more of: one or more sets of pre-configurations for at least some parameters associated with the SRS configuration;a flag indicating whether the second SRS configuration is supported by the network node (16); andinformation about uplink resources for the UE (22) to report the assisting information.

5. The method of any one of Claim 1-4, wherein the assisting information comprises one or more of:information about channel quality associated with a selected Synchronization Signal Block, SSB, report;a flag indicating whether a selected SSB has passed a minimum Reference Signal Received Power, RSRP, threshold;information about whether the UE has performed measurements on all SSBs or not; and information about one or more of suggested SRS transmission power, a repetition factor of an SRS resource, and a number of symbols of an SRS resource.

456. The method of any one of Claims 1-5, wherein the assisting information is sent to the network node (16) explicitly as a part of at least one of Message 1, Msgl, and Message 3, Msg3 or implicitly during transmission of at least one of Msgl, and Msg3.

7. A method implemented in a network node (16) that is configured to communicate with a user equipment, UE, (22) the method comprising:receiving, from the UE (22), assisting information related to a first Sounding Reference Signal, SRS, configuration, the assisting information comprising channel quality or reference signal quality (SI 00); andtransmitting, to the UE (22), a second SRS configuration that is based on the assisting information, the second SRS configuration comprising information about the channel quality before or immediately after initial access (SI 02).

8. The method of claim 7, wherein the channel quality information in the second SRS configuration is updated based on the channel quality or reference signal quality in the assisting information.

9. The method of Claim 7 or 8, further comprising sending an indication to the UE (22), the indication being related to the second SRS configuration.

10. The method of any one of Claims 7-9, further comprising, along with the SRS configuration, triggering the second SRS configuration.

11. The method of Claim 10, wherein at least one of the second SRS configuration and the triggering is via a Message 4, Msg4, of a random access procedure.

12. The method of any one of Claims 7-11, wherein if a reported Reference Signal Received Power, RSRP, is below a threshold, further comprising cancelling the second SRS configuration.

13. A user equipment, UE (2), configured to communicate with a network node (16), the UE (22) configured to:46send, to the network node (16), assisting information related to a first Sounding Reference Signal, SRS, configuration, the assisting information comprising channel quality or reference signal quality; andreceive, from the network node (16), a second SRS configuration that is based on the assisting information, the second SRS configuration comprising information about the channel quality before or immediately after initial access.

14. The UE(22) of claim 13, wherein the second SRS configuration received comprises updated channel quality information based on the channel quality or reference signal quality in the assisting information.

15. The UE (22) of Claim 13 or 14, wherein the UE (22) is further configured to receive, from the network node, (16) an indication whether SRS is supported by the network node (16).

16. The UE (22) of Claim 15, wherein the indication comprises one or more of: one or more sets of pre-configurations for at least some parameters associated with the SRS configuration;a flag indicating whether the second SRS configuration is supported by the network node (16);information about whether the UE has performed measurements on all SSBs or not; and information about uplink resources for the UE (22) to report the assisting information.

17. The UE (22) of any one of Claims 13-16, wherein the assisting information comprises one or more of:information about channel quality associated with a selected Synchronization Signal Block, SSB, report;a flag indicating whether a selected SSB has passed a minimum Reference Signal Received Power, RSRP, threshold; andinformation about one or more of suggested SRS transmission power, a repetition factor of an SRS resource, and a number of symbols of an SRS resource.

18. The UE (22) of any one of Claims 12-15, wherein the assisting information is sent to the network node (16) explicitly as a part of at least one of Message 1, Msgl, and Message 3,Msg3 or implicitly during transmission of at least one of Msgl, and Msg3.

19. A network node (16) configured to communicate with a user equipment, UE, (22) the network node (16) configured to:receive, from the UE (22), assisting information related to a first Sounding Reference Signal, SRS, configuration, the assisting information comprising channel quality or reference signal quality; andtransmit, to the UE (22), a second SRS configuration that is based on the assisting information, the second SRS configuration comprising information about the channel quality before or immediately after initial access.

20. The network node of claim 19, wherein the network node (16) is configured to update the channel quality information in the second SRS configuration based on the channel quality of reference signal quality in the assisting information21. The network node (16) of Claim 20, wherein the network node (16) is further configured to send an indication to the UE (22), the indication being related to the second SRS configuration.

22. The network node (16) of any one of Claims 20 and 21, wherein the network node (16) is further configured to, along with the SRS configuration, trigger the second SRS configuration.

23. The network node (16) of any one of Claims 19-22, wherein at least one of the second SRS configuration and the triggering is via a Message 4, Msg4, of a random access procedure.

24. The network node (16) of any of Claims 19-23, wherein if a reported Reference Signal Received Power, RSRP, is below a threshold, the network node (16) is further configured to cancel the second SRS configuration.