Patent Application
20240405941
In cellular broadband communications, a user equipment and a core network can communicate about the status of a communication channel used for data transmission.
The following presents a simplified summary of the disclosed subject matter in order to provide a basic understanding of some of the various embodiments. This summary is not an extensive overview of the various embodiments. It is intended neither to identify key or critical elements of the various embodiments nor to delineate the scope of the various embodiments. Its sole purpose is to present some concepts of the disclosure in a streamlined form as a prelude to the more detailed description that is presented later.
An example system can operate as follows. The system can communicate broadband cellular communications with a user equipment, wherein the broadband cellular communications are facilitated with carrier aggregation of a primary cell and a secondary cell. The system can send a radio resource control message to the user equipment to establish a sounding reference signal mode for the broadband cellular communications, wherein the sounding reference signal mode is a periodic mode. The system can send a second message in a second format to the user equipment, wherein the second format differs from a radio resource control format, and wherein the second message indicates changing a number of sounding reference signal positions for first communications via the primary cell. The system can send a third message in the second format to the user equipment, wherein the second message indicates the changing of the number of sounding reference signal positions for second communications via the secondary cell. The system can receive, from the user equipment, a fourth message that utilizes the number of sounding reference signal positions to convey sounding reference signal information. The system can save an indication of a channel quality that corresponds to the broadband cellular communications based on the sounding reference signal information in the fourth message.
An example method can comprise, as part of broadband cellular communications with user equipment, sending, by a system comprising a processor, a radio resource control message to the user equipment to establish a periodic sounding reference signal mode for the broadband cellular communications, wherein the broadband cellular communications are facilitated with carrier aggregation of a primary cell and a secondary cell. The method can further comprise sending, by the system, a second message in a second format to the user equipment, wherein the second format differs from a radio request control format, and wherein the second message indicates modifying a number of sounding reference signal positions for first communications via the primary cell. The method can further comprise sending, by the system, a third message in the second format to the user equipment, wherein the third message indicates the modifying of the number of sounding reference signal positions for second communications via the secondary cell. The method can further comprise receiving, by the system and from the user equipment, a fourth message that utilizes the number of sounding reference signal positions to convey sounding reference signal information. The method can further comprise saving, by the system, an indication of a channel quality that corresponds to the broadband cellular communications based on the sounding reference signal information in the fourth message.
An example non-transitory computer-readable medium can comprise instructions that, in response to execution, cause a system comprising a processor to perform operations. These operations can comprise sending, to a user equipment, a first message in a first format to establish a sounding reference signal mode for broadband cellular communications with the user equipment via a primary cell and a secondary cell. These operations can further comprise sending, to the user equipment, a second message in a second format, wherein the first format differs from the second format, and wherein the second message indicates modifying a number of sounding reference signal positions for communications via the primary cell. These operations can further comprise sending, to the user equipment, a third message in the second format, wherein the third message indicates the modifying of the number of sounding reference signal positions for communications via the secondary cell. These operations can further comprise receiving, from the user equipment, a fourth message that utilizes the number of sounding reference signal positions to convey sounding reference signal information. These operations can further comprise saving an indication of a channel quality that corresponds to the broadband cellular communications based on the sounding reference signal information in the fourth message.
Numerous embodiments, objects, and advantages of the present embodiments will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
A SRS can be sent by UE according to instructions provided by a gNB. The SRS can be used by the gNB to measure an uplink (UL) channel propagation, and can be used by the gNB for channel aware scheduling, link adaptation (LA), and downlink channel estimation when channel reciprocity exists, such as in time-division duplexing (TDD) deployments.
In some implementations of a 3rd Generation Partnership Project (3GPP) protocol, a SRS can occupy 1, 2, or 4 symbols in a time domain, and all resource blocks (RBs) in a frequency domain. A SRS can be transmitted independently of physical uplink shared channel (PUSCH) scheduling and PUSCH bandwidth.
A SRS can be triggered non-periodically using DCI messages, such as DCI_0_1 and/or DCI_1_1; in a semi-persistent manner using a MAC CE message; and/or periodically as soon as it is configured using a Layer 3 (L3) signaling (e.g., RRC signaling, and/or SRS resource set configuration).
In some examples, when a SRS is periodically triggered (which can be highly likely in some deployments), if channel conditions improve at the UE and there is a desire to reduce a number of symbols used for SRS transmissions, an approach to reducing the number of symbols can be to use RRC signaling. A problem with using RRC signaling for this purpose can be that it can be slow (being sent from a centralized unit (CU) of a radio rather than from a distributed unit (DU)), and result in more radio resource usage (both for the SRS symbols until reconfiguration, as well as for the signaling messages). Also, with this approach, to reduce or increase the symbols used for SRS, which can be indicated with 2 bits, the gNB can need to transmit a whole RRC signaling message as currently defined by 3GPP specifications. The present techniques can be implemented to facilitate a more efficient and faster approach to increasing or decreasing symbols used for SRS (as per UE conditions and other criteria) during periodic and semipersistent SRS transmission.
The present techniques can be applied in a carrier aggregation scenario, where multiple UL and/or downlink (DL) carriers (which can be referred to as component carriers) can be assigned to one UE. Carrier aggregation can generally comprise techniques to increase a data rate experienced by a UE, where multiple component carriers can be assigned to that UE.
In a periodic trigger case (e.g.,
For example, if a UE radio frequency (RF) condition changes from good to bad (or vice versa), and if a gNB attempts to adapt SRS transmission accordingly to conserve valuable radio symbols for data transmission (e.g., switching from using four symbols to using one symbol in good UE conditions, or switching from using one symbol to using four symbols in poor conditions for better channel estimation), then the prior techniques can lack an efficient and/or fast mechanism to effectuate this, leading to wasting valuable radio resources (symbols).
The present techniques can be applied to a carrier aggregation scenario, where more than one component carrier/serving cell (Scell) can be configured to carry a SRS. Additionally, a benefit of applying the present techniques to a carrier aggregation scenario can be greater than a corresponding benefit in a single-carrier scenario, because using slow, resource-and-time consuming RRC signaling to increase or decrease a number of SRS signals can be magnified in a carrier aggregation scenario where such a RRC message is issued multiple times—one for each component carrier that is configured to carry SRS information.
The present techniques can be implemented to facilitate reusing a SRS request field with DCI, even for periodic and/or semi-persistent transmission, to indicate a number of symbols to use for SRS, on a carrier on which a DCI message is carried if no cross-carrier scheduling is configured.
In a carrier aggregation scenario where no cross-carrier scheduling is configured, the SRS request field can apply to the SRS transmission on the same carrier that DCI was received on.
An associated example signal flow is illustrated in
The present techniques can be implemented to facilitate using a MAC CE
(e.g., Activation/Deactivation of SRS symbol information), including for periodic transmission and semi-persistent, to indicate a number of symbols to use for SRS for different carriers, in a carrier aggregation scenario. A MAC CE can be implemented in accordance with the table of values of a SRS request field, above, to indicate a number of SRS symbols to use during a periodic or semi-persistent SRS mode for different carriers configured for SRS transmissions. Upon receiving this MAC CE, a UE can transmit a number of symbols as specified by the MAC CE on a corresponding carrier (as indicated by the below fields), and other SRS resource configurations specified by RRC (L3) signaling can remain unchanged.
An associated example signal flow is illustrated in
This table above can represent a SRS symbol length indication for different component carriers when a highest ServCellIndex of a serving cell with configured DL/UL is less than 8.
This table above can represent a SRS symbol length indication for different component carriers when a highest ServCellIndex of a serving cell with configured DL/UL is greater than or equal to 8.
In the above tables, Ci can indicate that, if there is an Scell configured for the MAC entity with a ScellIndex I, this field can indicate a SRS symbol length change status of the Scell with ScellIndex i, and otherwise the MAC entity can ignore the Ci field. The Ci field can be set to 0 to indicate that a Scell with SCellIndex I has no SRS symbol length indication field set in the MAC CE.
In the above tables, R can indicate a reserved bit, and can be set to 0.
According to the present techniques, a IE can be used in UE capability to support dynamic switching of SRS symbols. An IE, dynamicSRSSymbolSwitchSupport, can be implemented for uplink in FeatureSetUplink. Where a UE supports this IE, it can indicate that the UE will support dynamic SRS symbol switch configuration changes in an uplink direction.
In some examples, there can be one IE for dynamic SRS symbol switching, and its use indicates support for SRS transmission optimization in both carrier aggregation and non-carrier aggregation scenarios. In other examples, there can be two respective IEs used—one for a carrier aggregation scenario (e.g., CAdynamicSRSSymbolSwitchSupport) and another for a non-carrier aggregation scenario (e.g., dynamicSRSSymbolSwitchSupport). The example of an IE for dynamic SRS symbol switching herein generally uses one IE, and it can be appreciated that these techniques can be applied where two IEs are used.
A FeatureSetUplinkIE can be used to indicate the features that the UE supports on carriers corresponding to one band entry in a band combination. An example FeatureSetUplinkIE is as follows:
In some examples, a UE is capable of handling a DCI field “SRS request” for uplink DCI format 0_1 and DCI format 1_1, as described above. This can be implemented based on a carrier indicator field (CIF) interpretation when cross carrier scheduling is configured, as well as when cross carrier scheduling is not configured. A CIF can generally comprise a field in a DCI 0_1 and/or a DCI 1_1 that indicates on which carrier resources are allocated where cross-carrier scheduling is configured. According to the present techniques, a CIF can be utilized by a base station to indicate on which carrier a number of SRS symbols is being modified, where cross-carrier scheduling is configured (e.g., a DCI can be sent on a Pcell that indicates SRS modification for Scell(s), and vice versa).
In some examples a UE is capable of handling a MAC CE (e.g., “Activation/Deactivation of SRS symbol information,” as described above.
In some examples, the present techniques can be implemented in a UE, as follows. A UE indicator can be implemented that implements the present techniques. That is, a UE can send a bit in a UE capability indicator to a centralized unit of a gNB to indicate that SRS transmission optimization with carrier aggregation is or is not supported.
Where the UE capability indicator indicates that SRS transmission optimization with carrier aggregation is supported, a UE can increase and/or decrease a number of SRS symbols transmitted (after SRS transmission has been activated by either a periodic or semi-persistent SRS mode) as instructed by a DCI message and/or a MAC CE message.
Where the UE capability indicator indicates that SRS transmission optimization with carrier aggregation is not supported, it can be that a gNB does not use DCI messages and/or MAC CE messages to increase and/or decrease a number of SRS symbols transmitted, and/or a UE ignores such DCI messages and/or MAC CE if the UE receives them.
The present techniques can be implemented to trigger an increase or decrease of SRS symbols via MAC CE and/or DCI based on changing conditions. A gNB can instruct a UE to increase or decrease a number of transmitted SRS symbols for each configured Scell in a carrier aggregation scenario based on conditions such as what follows.
An example of changing conditions can occur where a UE is in good RF conditions, and measured signal to interference and noise ratio (SINR) is higher than a certain threshold (and other indicators reported, like channel quality indicator (CQI), and block error rate (BLER), can point to good radio conditions) in certain Scells in a carrier aggregation scenario, then the gNB can instruct the UE (through DCI and/or MAC CE messaging) to decrease a number of SRS symbols for the corresponding Scells. For example, the number of SRS symbols can be reduced from four to two, from four to one, or from two to one, depending on different SINR thresholds, for the corresponding Scells.
Another example of changing conditions can occur where a UE is in bad RF conditions, and measured SINR is lower than a certain threshold (and other indicators reported, like CQI and BLER, point to poor radio conditions) in certain Scells in a carrier aggregation case, then the gNB can instruct the UE (through DCI and/or MAC CE messaging) to increase a number of SRS symbols. For example, the number of SRS symbols can be increased from one to two, from one to four, or from two to four, depending on different SINR thresholds, for the corresponding Scells.
Another example of changing conditions can occur where a UE is in fast changing radio conditions (e.g., example mobile scenarios) in certain Scells in a carrier aggregation case, then the gNB can instruct the UE (through DCI and/or MAC CE messaging) to increase or decrease a number of SRS symbols., depending on measured SINR thresholds (and/or other indicators, like CQI and BLER), for the corresponding Scells.
In cellular communications, there can be a master cell group (MCG) to which a UE initially registers. A cell that is used to initiate initial access can be referred to as a primary cell (Pcell). A Pcell can be combined with one or more secondary cells (Scells) under a MCG using carrier aggregation techniques, which can generally involve combining multiple carriers to increase bandwidth available to UEs.
The examples herein generally relate to 5G cellular communications networks, where Pcells and Scells are used. It can be appreciated that the present techniques can be applied to other types of cellular communications networks for SRS transmission optimization with carrier aggregation.
As depicted, system architecture 100 comprises gNodeB (gNB) 102, Pcell 104, Scell(s) 106, UE 108. SRS transmission optimization with carrier aggregation component 110A, and SRS transmission optimization with carrier aggregation component 110B.
gNB 102 can generally comprise a cellular fifth-generation (5G) base station, can comprise multiple antennas, and can concurrently communicate with multiple instances of UE 108. UE 108 can generally comprise a computing device that is configured to be used directly by an end-user to communicate with gNB 102. Pcell 104 can be a Pcell as described herein, and that is communicatively coupled to both gNB 102 and UE 108. Similarly, Scell(s) 106 can be one or more Scells as described herein, and that are communicatively coupled to both gNB 102 and UE 108.
SRS transmission optimization with carrier aggregation component 110A can generally comprise a component of gNB 102 that facilitates SRS transmission optimization with carrier aggregation for gNB 102 as described herein. Similarly, SRS transmission optimization with carrier aggregation component 110B can generally comprise a component of UE 108 that facilitates SRS transmission optimization with carrier aggregation for UE 108 as described herein.
In some examples, Scell(s) 106 can comprise multiple Scells, such as up to 32 carriers. With carrier aggregation, one Pcell and one or more Scells can be configured, including a SRS configuration, in a RRC message. According to the present techniques, in some examples, a number of SRS symbols can subsequently be increased or reduced in the Pcell or Scells that are configured for SRS transmission by sending a MAC CE or DCI on either the Pcell or Scell(s). This can occur in examples where cross-carrier scheduling is initially configured (e.g., in the RRC message).
In some examples where no cross-carrier scheduling is configured, then a DCI that is sent can apply SRS changes to the carrier over which it is sent (e.g., either Pcell or Scell). And a MAC CE can indicate the carrier for which the number of SRS symbols is modified.
Aperiodic SRS transmission 200 comprises DCI 202, SRS 204, time 206, and SRS transmission optimization with carrier aggregation component 210 (which can be similar to SRS transmission optimization with carrier aggregation component 110A and/or SRS transmission optimization with carrier aggregation component 110B of
DCI 202 can comprise a DCI message. Sending DCI 202 can trigger sending one aperiodic SRS at some point during time 206.
Per a 3GPP protocol, SRS triggering can be configured by a resource-Type information element (IE), a SRS-Resource IE within RRC signaling messages. A resource-Type IE can set an aperiodic (
Semi-persistent SRS transmissions 300 comprises MAC CE 302, SRS 304, time 306, and SRS transmission optimization with carrier aggregation component 310 (which can be similar to SRS transmission optimization with carrier aggregation component 110A and/or SRS transmission optimization with carrier aggregation component 110B of
MAC CE 302 can comprise a MAC CE message. Sending MAC CE 302 can trigger sending multiple semi-persistent SRS messages in SRS 304 at points during time 306.
Periodic SRS transmissions 400 comprises L3 message 402, SRS 404, time 406, and SRS transmission optimization with carrier aggregation component 410 (which can be similar to SRS transmission optimization with carrier aggregation component 110A and/or SRS transmission optimization with carrier aggregation component 110B of
L3 message 402 can comprise a RRC message. Sending MAC CE 402 can trigger sending multiple periodic SRS messages in SRS 404 at points during time 406.
In an aperiodic mode, DCI_0_1 and DCI_1_1 can be used to request a UE to transmit SRS. The SRS request filed within the DCI can be used specify the SRS resource set to use. The SRS resource set (which can range from 0 to 15, in some examples) can specify SRS resources the UE should transmit on. The SRS resources can specify the number of symbols (e.g., 1, 2, or 4) in a time domain, in addition to other parameters, like a transmission comb, a number of SRS ports, etc.
However, in a periodic trigger case (e.g.,
In a carrier aggregation scenario, a UE can be assigned more than one carrier in a downlink and an uplink (e.g., in versions of a 3GPP protocol, up to 32 component carriers (CCs) can be assigned). A UE can be configured to send SRS on any of these CCs. including on CCs that are not configured to carry any PUSCH data. In some examples, for a time-division duplexing downlink-only CC, configuring SRS symbols on the same carrier (without PUSCH data configured on the CC) can aid a gNB in making better channel estimations for link adaptation and scheduling decisions for the DL by exploiting channel reciprocity.
In a carrier aggregation scenario where a UE is assigned more than one carrier in the DL and or UL, a similar technique can be implemented where a number of SRS symbols can be increased or decreased on the carriers where SRS has been configured for periodic or semi-persistent transmission.
Signal flow 1100 begins with
The signal flow of signal flow 1100 is an example signal flow, and there can be signal flows that implement different signals, or the signals of signal flow 1100 in a different order, as part of facilitating SRS transmission optimization with carrier aggregation.
As depicted in signal flow 1100, the following occurs:
In general, a difference between signal flow 1300 and signal flow 1100 of
Signal flow 1300 begins with
The signal flow of signal flow 1300 is an example signal flow, and there can be signal flows that implement different signals, or the signals of signal flow 1300 in a different order, as part of facilitating SRS transmission optimization with carrier aggregation.
As depicted in signal flow 1300, the following occurs:
It can be appreciated that the operating procedures of process flow 1500 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1500 can be implemented in conjunction with one or more embodiments of one or more of process flow 1600 of
Process flow 1500 begins with 1502, and moves to operation 1504.
Operation 1504 depicts communicating broadband cellular communications with a user equipment, wherein the broadband cellular communications are facilitated with carrier aggregation of a primary cell and a secondary cell. That is, a gNB (e.g., gNB 102 of
After operation 1504, process flow 1500 moves to operation 1506.
Operation 1506 depicts sending a radio resource control message to the user equipment to establish a sounding reference signal mode for the broadband cellular communications, wherein the sounding reference signal mode is a periodic mode. In some examples, this RRC message can be similar to RRCReconfiguration 1146 (srs-Config with resource Type=Periodic in BWP-UplinkDedicated IE if UE supports this feature in uplink) of
After operation 1506, process flow 1500 moves to operation 1508.
Operation 1508 depicts sending a second message in a second format to the user equipment, wherein the second format differs from a radio request control format, and wherein the second message indicates changing a number of sounding reference signal positions for first communications via the primary cell. In some examples, this second message can be a DCI message like in 1188A of
In some examples, the second message indicates increasing the number of sounding reference signal positions. In some examples, the second message indicates decreasing the number of sounding reference signal positions. That is, changing the number of sounding reference signal positions can comprise increasing or decreasing the number.
In some examples, a first data size of the second message is smaller than a second data size of the radio resource control message. That is, a DCI or MAC CE message can be used to configure SRS messaging because a DCI/MAC CE message has a smaller data size than a corresponding RRC message, so bandwidth can be conserved.
In some examples, a gNB that implements process flow 1500 comprises a centralized unit and a distributed unit, the radio resource control message is sent to the user equipment from the centralized unit, the second message is sent to the user equipment from the distributed unit, and a first amount of time associated with sending the user equipment the radio resource control message from the centralized unit is greater than a second amount of time associated with sending the user equipment the second message from the distributed unit. That is, a DCI or MAC CE message for configuring SRS can be transmitted faster than a RRC message for configuring SRS because the DCI or MAC CE message is transmitted from a DU while a RRC is transmitted from a CU.
After operation 1508, process flow 1500 moves to operation 1510.
Operation 1510 depicts sending a third message in the second format to the user equipment, wherein the second message indicates the changing of the number of sounding reference signal positions for second communications via the secondary cell. In some examples, this third message can be a DCI message like in 1188B of
After operation 1510, process flow 1500 moves to operation 1512.
Operation 1512 depicts receiving, from the user equipment, a fourth message that utilizes the number of sounding reference signal positions to convey sounding reference signal information. In some examples, this fourth message can be similar to 1190 of
After operation 1512, process flow 1500 moves to operation 1514.
Operation 1514 depicts saving an indication of a channel quality that corresponds to the broadband cellular communications based on the sounding reference signal information in the fourth message. That is, a gNB can save channel quality information in a computer memory.
After operation 1514, process flow 1500 moves to 1516, where process flow 1500 ends.
It can be appreciated that the operating procedures of process flow 1600 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1600 can be implemented in conjunction with one or more embodiments of one or more of process flow 1500 of
Process flow 1600 begins with 1602, and moves to operation 1604.
Operation 1604 depicts, as part of broadband cellular communications with user equipment, sending a radio resource control message to the user equipment to establish a periodic sounding reference signal mode for the broadband cellular communications, wherein the broadband cellular communications are facilitated with carrier aggregation of a primary cell and a secondary cell. In some examples, operation 1604 can be implemented in a similar manner as operations 1504-1506 of
In some examples, operation 1604 comprises receiving, by the system and from the user equipment, a downlink control information message that comprises a first information element that indicates that the user equipment supports the modifying of the number of sounding reference signal positions during carrier aggregation communications, and wherein the first information element is separate from a second information element that indicates that the user equipment supports the modifying of the number of sounding reference signal positions during non-carrier aggregation communications. That is, using the above example, a UE capability message can indicate that the UE supports SRS transmission optimization. In some examples, separate IEs in this capability message can be used for carrier aggregation and non-carrier aggregation scenarios (e.g. CAdynamicSRSSymbolSwitchSupport and dynamicSRSSymbolSwitchSupport)
In some examples, operation 1604 comprises receiving, by the system and from the user equipment, a downlink control information message that comprises an information element that indicates that the user equipment supports the modifying of the number of sounding reference signal positions during carrier aggregation communications and non-carrier aggregation communications. That is, using the above example, a UE capability message can indicate that the UE supports SRS transmission optimization. In some examples, the same IE in this capability message can be used for carrier aggregation and non-carrier aggregation scenarios.
After operation 1604, process flow 1600 moves to operation 1606.
Operation 1606 depicts sending a second message in a second format to the user equipment, wherein the second format differs from a radio request control format, and wherein the second message indicates modifying a number of sounding reference signal positions for first communications via the primary cell. In some examples, operation 1606 can be implemented in a similar manner as operation 1508 of
In some examples, the second message (and, in some examples, the third message) comprises downlink control information message, and wherein the second message comprises a sounding reference signal request field that specifies a sounding reference signal resource set to use in the sounding reference signal transmission. In some examples, the indication is a first indication, and wherein the sounding reference signal resource set comprises a second indication of a number of symbols in a time domain. That is, DCI_0_1 and DCI_1_1 messages can be used to request the UE to transmit SRS. The SRS request filed within the DCI can be used specify the SRS resource set to use. The SRS resource set (ranging from 0 to 15) can specify SRS resources the UE should transmit on. The SRS resources can specify a number of symbols (1,2, or 4) in time domain, in addition to other parameters like a transmission comb, a number of SRS ports, etc.
In some examples, the second message (and, in some examples, the third message) comprises a medium access control control element message, wherein the medium access control control element message comprises a first format where a highest serving cell index of a serving cell is less than a threshold value, and wherein the medium access control control element message comprises a second format where the highest serving cell index of the serving cell is greater than or equal to the threshold value. Using the example described above, the first format can be used where the highest ServCellIndex of a serving cell with configured DL/UL is less than 8, and the second format can be used where the highest ServCellIndex of a serving cell with configured DL/UL is between 8 and 31.
In some examples, the second message (and, in some examples, the third message) comprises a downlink control information message that indicates scheduling a physical uplink shared channel in one cell. That is, a DCI 0_1 message can be used to request that a UE transmit a SRS message. In some examples, the second message comprises a downlink control information message that indicates scheduling a physical downlink shared channel in one cell. That is, a DCI 1_1 message can be used to request that a UE transmit a SRS message.
After operation 1606, process flow 1600 moves to operation 1608.
Operation 1608 depicts sending a third message in the second format to the user equipment, wherein the third message indicates the modifying of the number of sounding reference signal positions for second communications via the secondary cell. In some examples, operation 1608 can be implemented in a similar manner as operation 1510 of
After operation 1608, process flow 1600 moves to operation 1610.
Operation 1610 depicts receiving, from the user equipment, a fourth message that utilizes the number of sounding reference signal positions to convey sounding reference signal information. In some examples, operation 1610 can be implemented in a similar manner as operation 1512 of
After operation 1610, process flow 1600 moves to operation 1612.
Operation 1612 depicts saving an indication of a channel quality that corresponds to the broadband cellular communications based on the sounding reference signal information in the fourth message. In some examples, operation 1612 can be implemented in a similar manner as operation 1514 of
After operation 1612, process flow 1600 moves to 1614, where process flow 1600 ends.
It can be appreciated that the operating procedures of process flow 1700 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1700 can be implemented in conjunction with one or more embodiments of one or more of process flow 1500 of
Process flow 1700 begins with 1702, and moves to operation 1704.
Operation 1704 depicts sending, to a user equipment, a first message in a first format to establish a sounding reference signal mode for broadband cellular communications with the user equipment via a primary cell and a secondary cell. In some examples, operation 1704 can be implemented in a similar manner as operations 1504-1506 of
In some examples, the first message is sent via a network layer of the broadband cellular communications, and wherein the network layer differs from a physical layer, and a medium access control layer. That is, the first message can comprise a RRC/L3 message.
After operation 1704, process flow 1700 moves to operation 1706.
Operation 1706 depicts sending, to the user equipment, a second message in a second format, wherein the first format differs from the second format, and wherein the second message indicates modifying a number of sounding reference signal positions for communications via the primary cell. In some examples, operation 1706 can be implemented in a similar manner as operation 1508 of
In some examples, the second message (and in some examples, the third message) is sent via a network layer of the broadband cellular communications, and the network layer differs from a physical layer, and a medium access control layer. That is, the second message can comprise a MAC CE/L2 message.
In some examples, the second message (and in some examples, the third message) is sent via a physical layer of the broadband cellular communications, and wherein the physical layer differs from a network layer, and a medium access control layer. That is, the second message can comprise a DCI/L1 message.
In some examples, a system that implements process flow 1700 comprises a centralized unit and a distributed unit, the first message is originated in the centralized unit, and the second message (and in some examples, the third message) is originated in the distributed unit. That is, a DCI or MAC CE message for configuring SRS can be transmitted faster than a RRC message for configuring SRS because the DCI or MAC CE message is transmitted from a DU while a RRC is transmitted from a CU.
After operation 1706, process flow 1700 moves to operation 1708.
Operation 1708 depicts sending, to the user equipment, a third message in the second format, wherein the third message indicates the modifying of the number of sounding reference signal positions for communications via the secondary cell. In some examples, operation 1708 can be implemented in a similar manner as operation 1510 of
After operation 1708, process flow 1700 moves to operation 1710.
Operation 1710 depicts receiving, from the user equipment, a fourth message that utilizes the number of sounding reference signal positions to convey sounding reference signal information. In some examples, operation 1710 can be implemented in a similar manner as operation 1512 of
After operation 1710, process flow 1700 moves to operation 1712.
Operation 1712 depicts saving an indication of a channel quality that corresponds to the broadband cellular communications based on the sounding reference signal information in the fourth message. In some examples, operation 1712 can be implemented in a similar manner as operation 1514 of
After operation 1712, process flow 1700 moves to 1714, where process flow 1700 ends.
In order to provide additional context for various embodiments described herein,
For example, parts of computing environment 1800 can be used to implement one or more embodiments of gNB 102, Pcell 104, Scell(s) 106, and/or UE 108, of
In some examples, computing environment 1800 can implement one or more embodiments of the process flows of
While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the embodiments can be also implemented in combination with other program modules and/or as a combination of hardware and software.
Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the various methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.
The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.
Computing devices typically include a variety of media, which can include computer-readable storage media, machine-readable storage media, and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media or machine-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable or machine-readable instructions, program modules, structured data or unstructured data.
Computer-readable storage media can include, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD), Blu-ray disc (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid state drives or other solid state storage devices, or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.
Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.
Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
With reference again to
The system bus 1808 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 1806 includes ROM 1810 and RAM 1812. A basic input/output system (BIOS) can be stored in a nonvolatile storage such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 1802, such as during startup. The RAM 1812 can also include a high-speed RAM such as static RAM for caching data.
The computer 1802 further includes an internal hard disk drive (HDD) 1814 (e.g., EIDE, SATA), one or more external storage devices 1816 (e.g., a magnetic floppy disk drive (FDD) 1816, a memory stick or flash drive reader, a memory card reader, etc.) and an optical disk drive 1820 (e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.). While the internal HDD 1814 is illustrated as located within the computer 1802, the internal HDD 1814 can also be configured for external use in a suitable chassis (not shown). Additionally, while not shown in environment 1800, a solid state drive (SSD) could be used in addition to, or in place of, an HDD 1814. The HDD 1814, external storage device(s) 1816 and optical disk drive 1820 can be connected to the system bus 1808 by an HDD interface 1824, an external storage interface 1826 and an optical drive interface 1828, respectively. The interface 1824 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.
The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 1802, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to respective types of storage devices, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, whether presently existing or developed in the future, could also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.
A number of program modules can be stored in the drives and RAM 1812, including an operating system 1830, one or more application programs 1832, other program modules 1834 and program data 1836. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 1812. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.
Computer 1802 can optionally comprise emulation technologies. For example, a hypervisor (not shown) or other intermediary can emulate a hardware environment for operating system 1830, and the emulated hardware can optionally be different from the hardware illustrated in
Further, computer 1802 can be enabled with a security module, such as a trusted processing module (TPM). For instance, with a TPM, boot components hash next in time boot components, and wait for a match of results to secured values, before loading a next boot component. This process can take place at any layer in the code execution stack of computer 1802, e.g., applied at the application execution level or at the operating system (OS) kernel level, thereby enabling security at any level of code execution.
A user can enter commands and information into the computer 1802 through one or more wired/wireless input devices, e.g., a keyboard 1838, a touch screen 1840, and a pointing device, such as a mouse 1842. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, or other remote control, a joystick, a virtual reality controller and/or virtual reality headset, a game pad, a stylus pen, an image input device, e.g., camera(s), a gesture sensor input device, a vision movement sensor input device, an emotion or facial detection device, a biometric input device, e.g., fingerprint or iris scanner, or the like. These and other input devices are often connected to the processing unit 1804 through an input device interface 1844 that can be coupled to the system bus 1808, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, a BLUETOOTH® interface, etc.
A monitor 1846 or other type of display device can be also connected to the system bus 1808 via an interface, such as a video adapter 1848. In addition to the monitor 1846, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.
The computer 1802 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 1850. The remote computer(s) 1850 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer 1802, although, for purposes of brevity, only a memory/storage device 1852 is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN) 1854 and/or larger networks, e.g., a wide area network (WAN) 1856. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.
When used in a LAN networking environment, the computer 1802 can be connected to the local network 1854 through a wired and/or wireless communication network interface or adapter 1858. The adapter 1858 can facilitate wired or wireless communication to the LAN 1854, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter 1858 in a wireless mode.
When used in a WAN networking environment, the computer 1802 can include a modem 1860 or can be connected to a communications server on the WAN 1856 via other means for establishing communications over the WAN 1856, such as by way of the Internet. The modem 1860, which can be internal or external and a wired or wireless device, can be connected to the system bus 1808 via the input device interface 1844. In a networked environment, program modules depicted relative to the computer 1802 or portions thereof, can be stored in the remote memory/storage device 1852. It will be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers can be used.
When used in either a LAN or WAN networking environment, the computer 1802 can access cloud storage systems or other network-based storage systems in addition to, or in place of, external storage devices 1816 as described above. Generally, a connection between the computer 1802 and a cloud storage system can be established over a LAN 1854 or WAN 1856 e.g., by the adapter 1858 or modem 1860, respectively. Upon connecting the computer 1802 to an associated cloud storage system, the external storage interface 1826 can, with the aid of the adapter 1858 and/or modem 1860, manage storage provided by the cloud storage system as it would other types of external storage. For instance, the external storage interface 1826 can be configured to provide access to cloud storage sources as if those sources were physically connected to the computer 1802.
The computer 1802 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, store shelf, etc.), and telephone. This can include Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.
As it employed in the subject specification, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory in a single machine or multiple machines. Additionally, a processor can refer to an integrated circuit, a state machine, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a programmable gate array (PGA) including a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor may also be implemented as a combination of computing processing units. One or more processors can be utilized in supporting a virtualized computing environment. The virtualized computing environment may support one or more virtual machines representing computers, servers, or other computing devices. In such virtualized virtual machines, components such as processors and storage devices may be virtualized or logically represented. For instance, when a processor executes instructions to perform “operations”, this could include the processor performing the operations directly and/or facilitating, directing, or cooperating with another device or component to perform the operations.
In the subject specification, terms such as “datastore,” data storage,” “database,” “cache,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components, or computer-readable storage media, described herein can be either volatile memory or nonvolatile storage, or can include both volatile and nonvolatile storage. By way of illustration, and not limitation, nonvolatile storage can include ROM, programmable ROM (PROM), EPROM, EEPROM, or flash memory. Volatile memory can include RAM, which acts as external cache memory. By way of illustration and not limitation, RAM can be available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.
The illustrated embodiments of the disclosure can be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.
The systems and processes described above can be embodied within hardware, such as a single integrated circuit (IC) chip, multiple ICs, an ASIC, or the like. Further, the order in which some or all of the process blocks appear in each process should not be deemed limiting. Rather, it should be understood that some of the process blocks can be executed in a variety of orders that are not all of which may be explicitly illustrated herein.
As used in this application, the terms “component,” “module,” “system,” “interface,” “cluster,” “server,” “node,” or the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution or an entity related to an operational machine with one or more specific functionalities. For example, a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instruction(s), a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. As another example, an interface can include input/output (I/O) components as well as associated processor, application, and/or application programming interface (API) components.
Further, the various embodiments can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement one or more embodiments of the disclosed subject matter. An article of manufacture can encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips . . . ), optical discs (e.g., CD, DVD . . . ), smart cards, and flash memory devices (e.g., card, stick, key drive . . . ). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.
In addition, the word “example” or “exemplary” is used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
What has been described above includes examples of the present specification. It is, of course, not possible to describe every conceivable combination of components or methods for purposes of describing the present specification, but one of ordinary skill in the art may recognize that many further combinations and permutations of the present specification are possible. Accordingly, the present specification is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
The subject patent application is related by subject matter to, U.S. patent application Ser. No. ______ (docket number 133305.02/DELLP856US), filed ______, and entitled “SOUNDING REFERENCE SIGNAL TRANSMISSION OPTIMIZATION,” which claims priority to Indian Provisional Patent Application No. 20/231,1037849, filed Jun. 1, 2023, and entitled “SOUNDING REFERENCE SIGNAL TRANSMISSION OPTIMIZATION,” the entireties of which applications are hereby incorporated by reference herein. The subject patent application is related by subject matter to, U.S. patent application Ser. No. ______ (docket number 133904.01/DELLP894US), filed Jun. 1, 2023, and entitled “SOUNDING REFERENCE SIGNAL TRANSMISSION OPTIMIZATION,” the entirety of which application is hereby incorporated by reference herein.
