Methods and nodes for scheduling the early SRS capability report
By allowing UEs to request resources for early SRS capability reports during initial access, the network can efficiently configure SRS transmissions, addressing the lack of CSI during initial access and improving throughput.
Patent Information
- Application Number
- PCT/IB2026/054781
- 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
Existing networks lack Channel State Information (CSI) during initial access procedures, as the UE cannot send a first CSI report or SRS transmission until RRC configuration is completed, which is challenging given limited resources in initial access messages and the need for early SRS capability reports from UEs supporting early SRS.
Methods for scheduling early SRS capability reports during initial access by allowing UEs to request resources explicitly or implicitly in Msg1, with the network allocating resources in Msg2 for the report in Msg3, enabling the network to understand UE capabilities and configure SRS efficiently.
Enables early SRS capability reporting with reduced signaling overhead, allowing the network to properly configure UEs based on their capabilities, improving channel quality understanding and throughput.
Smart Images

Figure IB2026054781_19112026_PF_FP_ABST
Abstract
Description
P113716W01Methods and nodes for scheduling the early SRS capability report RELATED APPLICATIONS
[0001] This application claims the benefits of priority of US 63 / 806,213, entitled “Methods for scheduling the early SRS capability report” and filed at the USPTO on May 15, 2025, which is hereby incorporated by reference in its entirety.TECHNICAL FIELD
[0002] This application relates to communication networks and particularly to methods and nodes for scheduling an early SRS capability report during an initial access procedure.BACKGROUND
[0003] Sounding Reference Signal (SRS)
[0004] In New Radio (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 transmi ssion / recepti on 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 DL Shared Channel (PDSCH) transmissions) and UL (e.g., for Physical UL Shared Channel (PUSCH) transmissions) Multiple Input Multiple Output (MIMO) precoding.
[0005] In Long Term Evolution (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 (MAC)-Control Element (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 User Equipment (UE) but instead a dynamic activation trigger is transmitted from the gNB in the DL, via the DL Control Information (DCI) in the Physical DL Control Channel (PDCCH), which instructs the UE to transmit the SRS once, at a predetermined time.
[0006] When configuring SRS transmissions, the gNB configures, through the SRS-Config Information Element (IE), a set of SRS resources and a set of SRS resource sets, where each SRS resource set contains one or more SRS resources.
[0007] 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 for further details), by setting the RRC parameter "usage’ to one of ‘antennaSwitching’, ‘codebook’, ‘nonCodebook’, and ‘beamManagemenf .
[0008] SRS configuration
[0009] Each SRS resource is configured according to 3GPP TS 38.331 (e.g. version 16.1.0).P113716W01
[0010] An SRS resource is configurable with respect to, e.g.,
[0011] 2) The number of SRS ports (1, 2, or 4), configured by the RRC parameter nrofSRS- Ports.
[0012] 3) The transmission comb (i.e., mapping to every 2nd or 4th subcarrier), configured by the RRC parameter IransmissionComb. which includes: a. the comb offset, configured by the RRC parameter combOffset, and b. the cyclic shift, configured by the RRC parameter cyclicShift.
[0013] 4) The time-domain position within a given slot, configured with the RRC parameter resourceMapping, which includes: a. the time-domain start position, b. the number of symbols for the SRS resource (that can be set to 1, 2 or 4), configured by the RRC parameter nrofSymbols and c. the repetition factor (that can be set to 1, 2 or 4), configured by the RRC parameter repetitionFactor .
[0014] 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 freqDomainPosition, freqDomainShift, and the freqHopping parameters c-SRS, b-SRS, and b-hop. The smallest possible sounding bandwidth is 4 RBs.
[0015] 6) The RRC parameter resourceType determines whether the SRS resource is transmitted as periodic, aperiodic (single transmission triggered by DCI), or semi persistent.
[0016] 7) The RRC parameter sequenceld specifies how the SRS sequence is initialized.
[0017] 8) The RRC parameter spatialRelationlnfo configures the spatial relation for the SRS beam with respect to another References Signal (RS) (which could be another SRS, an 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.
[0018] An SRS resource set is configured according to 3GPP TS 38.331 (e.g. version 16.1.0).
[0019] SRS resource(s) will be transmitted as part of an SRS resource set, where all SRS resources in the same SRS resource set share the same resource type. An SRS resource set is configurable with respect to, e.g.,
[0020] 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.
[0021] 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: ‘antennaSwitching’, ‘codebook’, ‘nonCodebook’ and ‘beamManagemenf .P113716W01
[0022] 11) The associated CSI-RS (this configuration is only applicable for NCB-based UL transmission) for each of the possible resource types. For an aperiodic SRS, the associated CSI-RS resource is set by the RRC parameter csi-RS. For semi-persistent / periodic SRS, the associated CSI-RS resource is set by the RRC parameter associatedCSI-RS .
[0023] 12) The power control (PC) parameters, e.g., alpha and pO are used for setting the SRS transmission power (see 3GPP TS 38.213 for further details).
[0024] To summarize, 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.
[0025] SRS antenna switching
[0026] For reciprocity-based DL precoding, SRS is used to obtain CSI in the UL. It is desirable for the network (NW) 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 Transmit (Tx) chains (UEs typically have more Receive (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).Table 1 SRS antenna-switching capabilities supported by the UE (copied from 3GPP TS 38.306).supportedSRS-TxPortSwitch supportedSRS-TxPortSwitch-v1610t1r2 Hr1-t1r2t1r4 Hr1-t1r2-t1r4t2r4 Hr1-t1r2-t2r2-t2r4t2r2 Hr1-t2r2t4r4 Hr1-t2r2-t4r4Hr4-t2r4 Hr1-t1r2-t2r2-t1r4-t2r4
[0027] 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 are configured in different Orthogonal Frequency Division Multiplexing (OFDM) symbols and separated, at least, by a guard period that depends on the subcarrier spacing (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.P113716W01
[0028] In general, xTyR SRS antenna switching can be configured for a UE with x Tx chains and y Rx chains. Fig. 1 shows examples of xTyR SRS antenna switching for UE architectures with x = y / 2 Tx chains and y Rx chains.
[0029] 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 gNB. For example, the UE capability tlrl-tlr2 indicates that the gNB can configure one single-port SRS resource (no antenna switching) or two singleport SRS resources (same as for the capability tlr2 described above) per SRS resource set with usage antennaSwitching.
[0030] In NR Rel-17, antenna switching was extended to up to 6 or 8 Rx ports, and 1, 2, or 4 Tx chains. In NR Rel-18, antenna switching was extended to 8 Tx for 8 Rx UE, by using an SRS resource with 8 SRS ports.
[0031] NR initial access
[0032] Before a UE can properly communicate with a network, it must carry out cell search to find, synchronize and identify a cell. Then, it can acquire basic system information (SI) and perform a random access (RA) procedure to establish a connection with the cell.
[0033] NR cell search and system information acquisition
[0034] 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 signals (PSS) and secondary SS (SSS), is periodically transmitted on DL 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 DL synchronization in both time and frequency, and acquire the timing for PBCH. PBCH carries the master information block (MIB), which contains a minimum SI that a UE needs to acquire system information block 1 (SIB 1). SIB 1 carries the remaining minimum SI that is needed for a UE to be able to perform the subsequent RA procedure. SIB 1 is transmitted in the same way as normal scheduled DL data transmissions in NR, with the SIB 1 information itself transmitted on the PDSCH and scheduling information, needed by the UE to find and decode the PDSCH.
[0035] NR 4-step random access (RA) procedure
[0036] The 4-step RA procedure, also referred to as Type-1 RA procedure in 3GPP TS 38.213, is illustrated in Fig. 2. This procedure is considered when an idle UE connects to the NW. In the first step, a UE initiates the RA procedure by transmitting in UL a RA preamble (Msgl) on a physical RA channel (PRACH), e.g. upon receiving a SS / PBCH block and SIBl. After detecting the Msgl, the gNB will respond by transmitting in DL a RA response (RAR) on a PDSCH (Msg2).P113716W01In 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.
[0037] There can be cases where multiple UEs select the same RA 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.
[0038] NR 2-step random access (RA) procedure
[0039] The 2-step RA procedure, also referred to as Type-2 RA procedure in TS 38.213, is illustrated in Fig. 3.
[0040] In the first step, a UE sends a message A (MsgA) including RA preamble together with higher layer data such as RRC connection request possibly with some small payload on PUSCH.
[0041] After detecting the MsgA, the network sends RAR (called MsgB) including UE identifier assignment, timing advance information, and contention resolution message, etc.SUMMARY
[0042] There currently exist certain challenge(s). One of the problems with existing networks for the initial access is that the NW has no CSI before the RRC configuration is completed. Once the RRC Configuration is completed, then the UE can send a first CSI report or a first SRS transmission. With this motivation, during the planning discussions for Rel20 / 6G, it has been suggested to specify methods for early SRS transmissions where the NW can be provided with information about the channel quality before or immediately after the initial access.
[0043] Specifically, a preliminary NR Rel-20 WID states the following:
[0044] On enhancing DL CSI acquisition, targeting FR1 , specify the following enhancements:
[0045] Early SRS / CSI / CSI-RS triggering for UE transitioning from IDLE / INACTIVE to CONNECTED mode viaMSG4 of 4-step RACH, as well as for SCell activation and switching out of SCell dormancy in CONNECTED mode via the legacy signaling mechanisms (based on legacy SCell activation MAC CE, and legacy switching DCI out of SCell dormancy, respectively) .
[0046] In order to provide the UE with a suitable early SRS configuration during or in conjunction with a 4-step RACH procedure, the NW may need to receive associated capability reports from the UEs which support early SRS. This, however, can be challenging given the limited resources in the initial access messages and the fact that probably only some UEs may be capable of early SRS. Furthermore, the existing UE capability signaling framework (i.e., via dedicated RRC signaling) cannot be used in this case, as the UEs are not in the connected mode. Therefore, how to schedule the early SRS capability report is an open problem.P113716W01
[0047] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
[0048] There are provided methods for scheduling the UE for early SRS capability report. With the proposed schemes / methods, upon receiving possible initial indications that the NW supports early SRS, the UE supporting early SRS may explicitly or implicitly request in Msgl for resources. Accordingly, in Msg2, the UE may receive explicitly or implicitly resources so that it can send the early SRS capability report in Msg3. As a result, the NW is provided with information about which UEs support early SRS and their capabilities, with limited overhead. In this way, the proposed schemes address one of the topics of interest in NR Rel-20 and 6G. Please note that different or similar messages during the initial access might be used in 6G.
[0049] In other words, the problem this disclosure solves is how the UE supporting early SRS can be scheduled with resources so that the UE can send the early SRS capability report / message to the NW. The scheduling request can be either explicit via an enhancement of Msgl or implicit via, e.g., sending a specific preamble of the selected SSB. Upon receiving the scheduling request, in Msg2 the NW may or may not allocate resources for the UE’s capability report to be sent in Msg3. The resources may be indicated to the UE either explicitly or implicitly. In this way, the NW is provided with information about which UEs support early SRS and their specific capabilities with limited overhead which, in turn, enables the NW to properly configure the UEs.
[0050] There is provided a method in the wireless device. The method comprises: sending, to a network node, a first indication related to capability for early SRS transmission; receiving, from the network node, an indication of resources for transmitting a capability report for early SRS transmission; and sending, to the network node, the capability report on the resources. A wireless device implementing this method is also provided.
[0051] There is provided a method in a network node. The method comprises: receiving, from a wireless device, a first indication related to capability for early SRS transmission; sending, to the wireless device, an indication of resources for transmitting a capability report for early SRS transmission; and receiving the capability report from the wireless device. A network node for implementing this method is also provided.
[0052] Certain embodiments may provide one or more of the following technical advantage(s). The proposed schemes / methods enable the UE to send the early SRS capability reports during the initial access / RA procedure. Such methods reduce the signaling overhead associated with early SRS configuration and also provide the NW with UE-specific information, which enables proper early SRS configurations. If the NW has limited information about the UE Tx and Rx chain architecture, it may consider, e.g., too few SRS resources / SRS ports or too manyP113716W01SRS resources / SRS ports for the early SRS transmission, which is not efficient. With the proposed schemes, such problems are avoided.BRIEF DESCRIPTION OF THE DRAWINGS
[0053] Exemplary embodiments will be described in more detail with reference to the following figures, in which:Fig. 1 illustrates an example of SRS antenna switching, with 1T2R (left), 2T4R (middle), and 4T8R (right) SRS antenna switching.
[0054] Fig. 1 illustrates an example of 1T2R (left), 2T4R (middle), and 4T8R (right) SRS antenna switching.
[0055] Fig. 2 illustrates an example of a four-step RA procedure for the initial access.
[0056] Fig. 3 illustrates an example of a two-step RA procedure for the initial access.
[0057] Fig. 4 illustrates an example of a signaling diagram between a UE and a network node for early SRS transmission, according to an embodiment.
[0058] Fig. 5 illustrates an example of a flow chart of a method in a wireless device, according to an embodiment.
[0059] Fig. 6 illustrates an example of a flow chart of a method in a network node, according to an embodiment.
[0060] Fig. 7 shows an example of a communication system, according to an embodiment.
[0061] Fig. 8 is another example of a communication system according to some embodiments.
[0062] Fig. 9 shows a schematic diagram of a UE, according to an embodiment.
[0063] Fig. 10 shows a schematic diagram of a network node, according to an embodiment.DETAILED DESCRIPTION
[0064] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0065] It should be noted that the term SRS is used in this disclosure. However, another term might be used in 6G. The purpose of the SRS is to use an UL reference signal for sounding the channel from the UE to the gNB. Therefore, this disclosure applies to any UL reference signals.
[0066] The terminologies of the NR initial access / RA are used herein. However, in 6G, different terminologies or signaling may be used during the initial access. Therefore, the disclosure applies to any such signaling involved during the initial access (procedure).
[0067] The term “early SRS” refers to the early SRS transmission. The terms “SRS capability report”, “capability report” and “capability assumption report” can be used interchangeably.P113716W01
[0068] Examples are described in the context of the 4-step initial access procedure when an idle UE connects to the NW, which is expected to be the main 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 perform explicit or implicit scheduling request via Msg-A.
[0069] In order to configure the UE with “suitable” (i.e., matching the UE’s capabilities) SRS configurations, the network may require information about the UE’s capabilities, otherwise it may configure all UEs with “non-suitable” (i.e., not matching the UE’ s capabilities) SRS configurations (e.g., too few or too many SRS resources / SRS ports, etc.), which is not efficient. Thus, the NW benefits from receiving the UE capability report before Msg4, where it configures the UE with SRS configurations. This, however, can be challenging given that Msg 1-3 of the 4-step RA procedure have limited resources and only a subset of UEs may support the early SRS feature. Moreover, it may be beneficial for the NW to have prior information about which UEs are going to send the early SRS capability report. Hence, there is a need for efficient methods so that, during Msg 1-2, the UE receives proper resources to send the UE capability report in Msg3. One alternative would be that all UEs receive the resources associated with the early SRS capability report. However, this is obviously an inefficient method given that in practice only some UEs might support early SRS. This is the motivation for this disclosure, in which methods for scheduling the early SRS capability report are provided.
[0070] Fig. 4 illustrates a high-level signaling diagram 90 between the UE / wireless device and the network node for early SRS during the initial access procedure, according to an embodiment. For example, it is assumed that the UE supports early SRS transmission.
[0071] In step 100 (optional), the UE receives an indication from the NW indicating whether early SRS is supported by the NW or not. The indication may contain one or more preconfigurations for at least some parameters associated with the SRS configuration. In an alternative, the indication may be only a flag indicating whether the early SRS is supported by the NW or not.
[0072] In Step 110, the UE sends to the NW an indication about its early SRS capabilities. In one example, the UE performs a scheduling request and requests for UL resources so that it can send the UE capability report. The scheduling request can be performed in different ways as explained in the following.
[0073] In one example, in Msgl, the UE explicitly requests for UL resources to send the UE’s capability report. For instance, the request may be via an indication flag (e.g., if the specification considers the UE capability report to be of fixed length), where the UE only indicates to the NWP113716W01whether it supports early SRS or not. Then, the NW will schedule the UL resources for the UE to send the capability report.
[0074] In one example, the UE may send detailed information about the required size of the UL resources to send the UE capability report. For instance, a pre-defined set of sizes for the early SRS capability report may be defined in the specification, e.g., {LI, L2} with L1<L2, and in Msgl the UE indicates to the NW whether it requires UL resources of size LI or L2. In another alternative, the set of pre-defined sizes for early SRS capability report may be indicated to the UE in Step 100, and in Msgl the UE may indicate to the NW one of the pre-defined sizes.
[0075] In one example, the explicit scheduling request for the early SRS capability report may be based on a new signaling defined before or after Msgl. For instance, the UE may send a 1 -bit scheduling request (SR) in PUCCH.
[0076] In another example, the UE may indicate to the NW that it supports early SRS and requests for UL resources implicitly. For instance, the implicit indication can be via, e.g., sending a specific preamble associated with the selected SSB. It should be noted that, in general, the mapping between SSBs and PRACH resources is defined by the NW and can follow different SSB-to-random access resource mappings (e.g., 1-to-l, many-to-one, one-to-many). Then, with the implicit indication, for a selected SSB, the UE may consider a specific preamble so that the NW understands that the UE supports early SRS and requires UL resources to send the associated capability report. Such specific preambles need to be captured in the specification.
[0077] In one example, in Step 110, the UE does not request for UL resources. Instead, the UL resources are pre-allocated (either as pre-defined rules / hard-coded resources captured in specification or to be indicated to the UE as a part of indication in Step 100). Then, in Step 110, the UE only informs the NW that in Msg3 it will perform a UE capability report in the pre-allocated resources. Compared to the previous examples, where the UE explicitly or implicitly requests for UL resources, in this example / case, some pre-allocated resources need to be considered in Msg3 (which will be used or not used by the UE).
[0078] In (an optional) Step 120, the UE receives an indication from the NW regarding the UL resources granted for the UE capability report. Such an indication may be via Msg2 or a new signaling before Msg3.
[0079] In one example, in Msg2, the NW sends an ACK / NACK whether it has received the UE’s request / indication of Step 110, and whether the NW grants the resources or not. Then, the UE is allowed to send the capability report in pre-allocated resources. In another example, the NW may explicitly provide the UE with UL resources to send the capability report. It should be noted that, once the NW receives the scheduling request, it may or may not grant the request (i.e. ULP113716W01resources) depending on the channel conditions, number of UEs, etc. However, how the NW decides whether to grant the request or not is an internal procedure of the NW and is out of the scope of this disclosure.
[0080] Step 120 may be optional. For instance, if there are pre-allocated resources for the UE capability report and in Step 110 the UE indicates to the NW that it will use them, the UE may send the UE capability report in Msg3 with no need for acknowledgement from the NW in Step 120.
[0081] In Step 130, the UE sends the early SRS capability report in Msg3. The capability report may comprise different information about, e.g., the supported antenna switching modes, number of Tx ports, number of Rx ports, number of SRS resources, number of SRS per SRS resource, etc.
[0082] In Step 140, the UE receives the early SRS configuration from the NW according to the UE capability report and, in Step 150, the UE transmits the SRS according to the SRS configuration. With the proposed procedure 90, the received SRS configuration matches well with the UEs capabilities.
[0083] Furthermore, the proposed schemes herein enable the NW to understand the UE’s capabilities associated with early SRS with limited resource overhead. This enables the NW to properly configure the UE with early SRS transmission configurations which, in turn, results in an early understanding about the channel quality and an improved throughput.
[0084] Now turning to Fig. 5, a flow chart of a method 200 for (enabling) early SRS transmission during an initial access procedure, will be described, according to an embodiment. The method 200 is performed by a wireless device, such as UE 712 of Fig. 7 and / or UE 900 of Fig. 9. Method 200 comprises:
[0085] Step 210: sending, to a network node, a first indication related to capability for early SRS transmission;
[0086] Step 220: receiving, from the network node, an indication of resources for transmitting a capability report for early SRS transmission;
[0087] Step 230: sending, to the network node, the capability report on the resources.
[0088] In some examples, the wireless device receives a SRS configuration based at least on the capability report. In some examples, the wireless device sends a SRS based at least on the SRS configuration. In some examples, the wireless device receives a second indication indicating that the network node supports early SRS transmission. In some examples, the second indication further contains one or more pre-configurations for at least one parameter associated with a SRS configuration. In some examples, the first indication comprises a request for resources for sendingP113716W01the capability report. In some examples, the first indication is sent in Msgl or in a signaling defined before or after Msgl. In some examples, the signaling is a 1 -bit scheduling request in PUCCH. In some examples, the first indication comprises information about a size of the resources for sending the capability report. In some examples, the first indication is sent via a specific preamble associated with a selected SSB. In some examples, the second indication further comprises an indication of the resources allocated for the transmission of the capability report. In some examples, the second indication is received in Msg2. In some examples, the indication of the resources is received via Msg2 or a signaling before Msg3. In some examples, the capability report is sent in Msg3. In some examples, the wireless device receives an ACK or NACK in response to sending the first indication related to the capability. In some examples, the capability report comprises one or more of supported antenna switching modes, a number of transmit antenna ports, a number of receive antenna ports, a number of SRS resources, a number of SRS resource per SRS resource set, etc.
[0089] Fig. 6 illustrates a flow chart of a method 300 for enabling early SRS transmission during an initial access procedure, according to an embodiment. The method 300 is performed by a network node, such as network node 710 of Fig. 7 and / or network node 1000 of Fig. 10. Method 300 comprises:
[0090] Step 310: receiving, from a wireless device, a first indication related to capability for early SRS transmission;
[0091] Step 320: sending, to the wireless device, an indication of resources for transmitting a capability report for early SRS transmission;
[0092] Step 330: receiving the capability report from the wireless device.
[0093] In some examples, the network node sends a SRS configuration based at least on the capability report. In some examples, the network node receives a SRS based at least on the SRS configuration. In some examples, the network node sends a second indication indicating that the network node supports early SRS transmission. In some examples, the second indication further contains one or more pre-configurations for at least some parameters associated with a SRS configuration. In some examples, the first indication comprises a request for resources for the wireless device to send the capability report. In some examples, the first indication is received in Msgl or in a signaling defined before or after Msgl. In some examples, the signaling is a 1 -bit scheduling request in PUCCH. In some examples, the first indication comprises information about a size of the resources for sending the capability report. In some examples, the first indication is received via a specific preamble associated with a selected SSB. In some examples, the second indication further comprises an indication of the resources allocated for the capability report. InP113716W01some examples, the second indication is sent in Msg2. In some examples, the indication of the resources is sent via Msg2 or a signaling before Msg3. In some examples, the capability report is received in Msg3. In some examples, the network node sends an ACK or NACK in response to receiving the first indication related to the capability. In some examples, the capability report comprises one or more of supported antenna switching modes, a number of transmit antenna ports, a number of receive antenna ports, a number of SRS resources, a number of SRS resource per SRS resource set, etc.
[0094] Fig. 7 shows an example of a communication system 700 in accordance with some embodiments.
[0095] In the example, the communication system 700 includes a telecommunications network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes or base stations of various types, access network nodes 710A and 710B are depicted (which may be collectively referred to as network nodes 710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 704 may include more than one access network technology. The network nodes 710 of access network 704 facilitate direct or indirect connection of wireless devices, also referred to as UEs, such as by connecting UEs 712A, 712B, 712C, and 712D (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.
[0096] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 702 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 network nodes to implement one or more functionalities of any network node in the telecommunications network 702, including one or more access network nodes 710 and / or core network nodes 708.
[0097] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g.,P113716W01xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN 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 network 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 0-RAN Alliance or comparable technologies.
[0098] The network nodes 710 facilitate direct or indirect connection of one or more UEs 712 to the core network 706 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0099] The UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 710 and other communication devices. Similarly, the network nodes 708, 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 702) with the UEs 712 and / or with other network nodes or equipment in the telecommunications network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 702. More specifically, UEs 712 may send messages, data, and / or other signals to network nodes 708, 710 or other elements of the telecommunications network 702 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 708, 710 may send messages, data, and other signals toP113716W01UEs 712, other network nodes 708, 710, and other devices in telecommunications network 702 directly or indirectly. As one specific example, a core network node 708 may transmit a particular message to a UE 712 by transmitting the message to an access network node 710 that will then transmit the message to the intended UE 712. Similarly, a core network node 708 may receive a particular message from a UE 712 by receiving the message from an access network node 710 that itself received the message from the UE 712.
[0100] In the depicted example, the core network 706 connects elements of the access network 704 (e.g., one or more of the network nodes 710) to one or more host computing systems, such as host 716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 706 includes one or more core network nodes (e.g., core network node 708) of various types, one or more of which may be generally referred to as network nodes 708. Network nodes 708 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0101] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and / or the telecommunications network 702. The host 716 may be operated by the service provider or on behalf of the service provider. The host 716 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0102] As a whole, the communication system 700 of Fig. 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 700 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal MobileP113716W01Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 700 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 700 supporting different standards, protocols, or rule sets.
[0103] As one example, in certain embodiments, access network 704 may contain some access network nodes 710 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 710 support (or the same access network nodes 710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 706 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 706 with individual networks 704, 706 supporting different standard generations.
[0104] Telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 702. For example, the telecommunications network 702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0105] In some examples, one or more of the UEs 712 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) NR - Dual Connectivity (EN-DC).P113716W01
[0106] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712C and / or 712D) and network nodes (e.g., network node 71 OB). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 710, or by executable code, script, process, or other instructions in the hub 714.
[0107] As another example, the hub 714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0108] The hub 714 may have a constant / persistent or intermittent connection to the network node 710B. The hub 714 may also allow for a different communication scheme and / or schedule between the hub 714 and UEs (e.g., UE 712C and / or 712D), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 710B. In other embodiments, the hub 714 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0109] Fig. 8 is another example of a communication system 800 according to some embodiments. As used herein, the communication system 800 includes multiple access points (APs) 810 (with four exemplary APs 810A, 810B, 810C, and 810D being depicted) and multiple wireless devices, referred to in the context of communication system 800 as stations (STAs) 812P113716W01(referred to individually as STA 812A, STA 812B, STA 812C, STA 812D, and STA 812E). STA 812A is served by AP 810Ain a first basic service set (BSS) 820A. STA 810B and STA 810C are served by AP 810B in a second BSS, BSS 820B. STA 812D is served by AP 810C in a third BSS, BSS 820C. STA 812E is served by AP 810D in a fourth BSS, BSS 820D. Stations 812 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), or the like. Further, stations 812 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0110] Each of STAs 812 may connect through a radio link to one of APs 810. For example, depending on location or channel conditions experienced by a given STA 812, 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.[OHl] Each AP 810 may provide data connectivity to STAs 812 connected to a particular AP 810. As illustrated, APs 810 may be connected to a data network 830. In this way, APs 810 may also provide data connectivity between STAs 812 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 812 and its serving AP 810 may be used for providing various kinds of services to STA 812, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 812 and / or on a device linked to STA 812. By way of example, Fig. 8 illustrates an application service platform 832 provided in data network 830. The application(s) executed on STA 812 and / or on one or more other devices linked to STA 812 may use the radio link for data communication with one or more other STA 812 and / or the application service platform 832, thereby enabling utilization of the corresponding service(s) at STA 812.
[0112] Fig. 9 shows a wireless device 900, which may be configured to operate in communication system 700 of Fig. 7 or in communication system 800 of Fig. 8. The wireless device 900 may be alternatively referred to as a UE 900, like a UE 712 within the context of communication system 700, or as a station (STA) 900 or as a non-access-point station (non-AP STA) 900, like a STA 812 within the context of the communication system 800, in accordanceP113716W01with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3GPP, including a narrow band loT (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0113] A wireless device 900 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 900 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
[0114] In particular embodiments, wireless device 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 900 may include all or a subset of the components shown in Fig. 9. The level of integration between the components may vary from one embodiment of wireless device 900 to another. In general, in a particular embodiment of wireless device 900, processing circuitry 902, input / output interface 906, power source 908, memory 910, and communication interface 912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 900. Further, certain embodiments of wireless devices 900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0115] The processing circuitry 902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 910. The processing circuitry 902 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs,P113716W01general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 902 may include multiple central processing units (CPUs). Furthermore, the processing circuitry 902 is configured to perform any steps of method 200 of Fig. 5.
[0116] In the example, the input / output interface 906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 900. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0117] In some embodiments, the power source 908 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of wireless device 900 via input circuitry or an interface such as an electrical power cable. Power source 908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 900 to which power is supplied.
[0118] The memory 910 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), and related ROM, magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by wireless device 900, any of a variety of various operating systems or combinations of operating systems.
[0119] The memory 910 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hardP113716W01disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow wireless device 900 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 910, which may be or comprise a device-readable storage medium.
[0120] The processing circuitry 902 may be configured to communicate with an access network or other network via or using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0121] In the illustrated embodiment, communication functions of the communication interface 912 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 / internet protocol (TCP / IP), synchronous opticalP113716W01networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0122] In particular embodiments, wireless device 900 may provide an output of data captured via a sensor, through its communication interface 912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 900 can be communicated through a wireless connection to a network node via another wireless device 900. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0123] As another example, wireless device 900 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 900 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0124] Wireless device 900, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 900 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 900 shown in Fig. 9.
[0125] As yet another specific example, in an loT scenario, wireless device 900 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 900 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 900 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 900 may represent a vehicle, such as a car, aP113716W01bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0126] In practice, any number of wireless devices 900 may be used together with respect to a single use case. For example, a first wireless device 900 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 900 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 900 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 900 can also include more than one of the functionalities described above. For example, wireless device 900 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0127] Fig. 10 shows a network node 1000 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1000 may be configured to operate in communication system 700 of Fig. 7, like network nodes 708 or 710, or in communication system 800 of Fig. 8, like an AP 810 or a station 812. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs (NBs), evolved NBs (eNBs) and NR NBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).
[0128] Network nodes 1000 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0129] Other examples of network nodes 1000 include multiple transmission point (multi -TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicastP113716W01coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0130] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in a particular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1000.
[0131] The network node 1000 may be composed of multiple distinct network entities (e.g., a NB 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 1000 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 NBs. In such a scenario, each unique NB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, 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 1000.
[0132] The processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1004, to provide network node 1000 functionality. Furthermore, the processing circuitry 1002 is configured to perform any steps of method 300 of Fig. 6.
[0133] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radioP113716W01frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
[0134] The memory 1004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.
[0135] The communication interface 1006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 900 may be capable of wireless communication and communication interface 1006 may also include radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, an antenna 1010. Particular embodiments of radio front-end circuitry 1018 include filter(s) 1020 and amplifier(s) 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal (s) may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed toP113716W01the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0136] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
[0137] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through one or more interfaces or ports.
[0138] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1000. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1000. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0139] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, orP113716W01integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0140] Embodiments of the network node 1000 may include additional components beyond those shown in Fig. 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.
[0141] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
[0142] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality.
[0143] 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.
Claims
P113716W01CLAIMS1. A method (200) performed by a wireless device during an initial access procedure, the method comprising:sending (210), to a network node, a first indication related to capability for early SRS transmission;receiving (220), from the network node, an indication of resources for transmitting a capability report for early SRS transmission; andsending (230), to the network node, the capability report on the resources.
2. The method of claim 1, further comprising receiving a SRS configuration based at least on the capability report.
3. The method of claim 2, further comprising sending a SRS based at least on the SRS configuration.
4. The method of any one of claims 1 to 3, further comprising receiving a second indication indicating that the network node supports early SRS transmission.
5. The method of claim 4, wherein the second indication further contains one or more preconfigurations for at least one parameter associated with a SRS configuration.
6. The method of any one of claims 1 to 5, wherein the first indication comprises a request for resources for sending the capability report.
7. The method of any one of claims 1 to 6, wherein the first indication is sent in Msgl or in a signaling defined before or after Msgl.
8. The method of claim 7, wherein the signaling is a 1 -bit scheduling request in Physical Uplink Control Channel (PUCCH).
9. The method of any one of claims 1 to 8, wherein the first indication comprises information about a size of the resources for sending the capability report.
10. The method of claim 6, wherein the first indication is sent via a specific preamble associated with a selected Synchronization Signal block (SSB).
11. The method of any one of claims 4 to 10, wherein the second indication further comprises an indication of the resources allocated for the transmission of the capability report.
12. The method of any one of claims 4 to 11, wherein the second indication is received in Msg2.
13. The method of any one of claims 1 to 12, wherein the indication of the resources is received via Msg2 or a signaling before Msg3.
14. The method of any one of claims 1 to 13, wherein the capability report is sent in Msg3.
15. The method of any one of claims 1 to 14, further comprising receiving an acknowledgement (ACK) or negative ACK in response to sending the first indication related to the capability.P113716W0116. The method of any one of claims 1 to 15, wherein the capability report comprises one or more of supported antenna switching modes, a number of transmit antenna ports, a number of receive antenna ports, a number of SRS resources, and a number of SRS resource per SRS resource set.
17. A method (300) performed by a network node during an initial access procedure, the method comprising:receiving (310), from a wireless device, a first indication related to capability for early SRS transmission;sending (320), to the wireless device, an indication of resources for transmitting a capability report for early SRS transmission; andreceiving (330) the capability report from the wireless device.
18. The method of claim 17, further comprising sending a SRS configuration based at least on the capability report.
19. The method of claim 18, further comprising receiving a SRS based at least on the SRS configuration.
20. The method of any one of claims 17 to 19, further comprising sending a second indication indicating that the network node supports early SRS transmission.
21. The method of claim 20, wherein the second indication further contains one or more preconfigurations for at least some parameters associated with a SRS configuration.
22. The method of any one of claims 17 to 21, wherein the first indication comprises a request for resources for the wireless device to send the capability report.
23. The method of any one of claims 17 to 22, wherein the first indication is received in Msgl or in a signaling defined before or after Msgl.
24. The method of claim 23, wherein the signaling is a 1-bit scheduling request in Physical Uplink Control Channel (PUCCH).
25. The method of any one of claims 17 to 24, wherein the first indication comprises information about a size of the resources for sending the capability report.
26. The method of claim 25, wherein the first indication is received via a specific preamble associated with a selected Synchronization Signal block (SSB).
27. The method of any one of claims 20 to 26, wherein the second indication further comprises an indication of the resources allocated for the capability report.
28. The method of any one of claims 20 to 27, wherein the second indication is sent in Msg2.
29. The method of any one of claims 17 to 28, wherein the indication of the resources is sent via Msg2 or a signaling before Msg3.P113716W0130. The method of any one of claims 17 to 29, wherein the capability report is received in Msg3.
31. The method of any one of claims 17 to 30, further comprising sending an acknowledgement (ACK) or negative ACK in response to receiving the first indication related to the capability.
32. The method of any one of claims 17 to 31, wherein the capability report comprises one or more of supported antenna switching modes, a number of transmit antenna ports, a number of receive antenna ports, a number of SRS resources, and a number of SRS resource per SRS resource set.
33. A wireless device (712, 900) for enabling an early SRS transmission during an initial access procedure, the wireless device (712, 900) comprising:a communication interface (912);processing circuitry (902) configured to perform the method of any one of claims 1 to 16; anda power source (908) configured to supply power to the processing circuitry (902).
34. A network node (710, 1000) for enabling an early SRS transmission during an initial access procedure, the network node comprising:a communication interface (1006);processing circuitry (1002) configured to perform the method of any one of claims 17 to 32;a power source (1008) configured to supply power to the processing circuitry.
35. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods according to any one of claims 1 to 32.
