MOBILE STATION RELAYING VERIFICATION

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a mobile station may receive, from a first network entity, data to be relayed to a second network entity. The mobile station may transmit the data to the second network entity. The mobile station may receive, from the second network entity, a digitally signed acknowledgement of reception of the data. The mobile station may transmit the digitally signed acknowledgement to the first network entity. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for mobile station relaying verification.

BACKGROUND

SUMMARY

Some aspects described herein relate to a mobile station for wireless communication. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to, based at least in part on information stored in the memory, receive, from a first network entity, data to be relayed to a second network entity. The one or more processors may be configured to, based at least in part on information stored in the memory, transmit the data to the second network entity. The one or more processors may be configured to, based at least in part on information stored in the memory, receive, from the second network entity, a digitally signed acknowledgement of reception of the data. The one or more processors may be configured to, based at least in part on information stored in the memory, transmit the digitally signed acknowledgement to the first network entity.

Some aspects described herein relate to a mobile station for wireless communication. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to, based at least in part on information stored in the memory, receive, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station. The one or more processors may be configured to, based at least in part on information stored in the memory, transmit, to the relay mobile station, a digitally signed acknowledgement of reception of the data.

Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to, based at least in part on information stored in the memory, transmit, to a relay mobile station, data to be relayed to a remote mobile station. The one or more processors may be configured to, based at least in part on information stored in the memory, receive, from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station.

Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include receiving, by the mobile station and from a first network entity, data to be relayed to a second network entity. The method may include transmitting, by the mobile station, the data to the second network entity. The method may include receiving, by the mobile station and from the second network entity, a digitally signed acknowledgement of reception of the data. The method may include transmitting, by the mobile station, the digitally signed acknowledgement to the first network entity.

Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include receiving, by the mobile station and from a relay mobile station, data originating from a network entity and relayed by the relay mobile station. The method may include transmitting, by the mobile station and to the relay mobile station, a digitally signed acknowledgement of reception of the data.

Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include transmitting, by the network entity and to a relay mobile station, data to be relayed to a remote mobile station. The method may include receiving, by the network entity and from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a mobile station. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to receive, from a first network entity, data to be relayed to a second network entity. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to transmit the data to the second network entity. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to receive, from the second network entity, a digitally signed acknowledgement of reception of the data. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to transmit the digitally signed acknowledgement to the first network entity.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a mobile station. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to receive, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to transmit, to the relay mobile station, a digitally signed acknowledgement of reception of the data.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit, to a relay mobile station, data to be relayed to a remote mobile station. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive, from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a first network entity, data to be relayed to a second network entity. The apparatus may include means for transmitting the data to the second network entity. The apparatus may include means for receiving, from the second network entity, a digitally signed acknowledgement of reception of the data. The apparatus may include means for transmitting the digitally signed acknowledgement to the first network entity.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station. The apparatus may include means for transmitting, to the relay mobile station, a digitally signed acknowledgement of reception of the data.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a relay mobile station, data to be relayed to a remote mobile station. The apparatus may include means for receiving, from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station.

DETAILED DESCRIPTION

In some aspects, a mobile station (e.g., the UE120) may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive, from a first network entity, data to be relayed to a second network entity; transmit the data to the second network entity; receive, from the second network entity, a digitally signed acknowledgement of reception of the data; and transmit the digitally signed acknowledgement to the first network entity. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, as described in more detail elsewhere herein, the communication manager140may receive, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station; and transmit, to the relay mobile station, a digitally signed acknowledgement of reception of the data. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, a network entity (e.g., the network node110) may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit, to a relay mobile station, data to be relayed to a remote mobile station; and receive, from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

In some aspects, a mobile station (e.g., the UE120) includes means for receiving, by the mobile station and from a first network entity, data to be relayed to a second network entity; means for transmitting, by the mobile station, the data to the second network entity; means for receiving, by the mobile station and from the second network entity, a digitally signed acknowledgement of reception of the data; and/or means for transmitting, by the mobile station, the digitally signed acknowledgement to the first network entity. In some aspects, the means for the mobile station to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, a mobile station (e.g., the UE120) includes means for receiving, by the mobile station and from a relay mobile station, data originating from a network entity and relayed by the relay mobile station; and/or means for transmitting, by the mobile station and to the relay mobile station, a digitally signed acknowledgement of reception of the data. In some aspects, the means for the mobile station to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, a network entity (e.g., the network node110) includes means for transmitting, by the network entity and to a relay mobile station, data to be relayed to a remote mobile station; and/or means for receiving, by the network entity and from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station. In some aspects, the means for the network entity to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.4is a diagram illustrating an example400of a relay UE that relays communications between a UE and a network node, in accordance with the present disclosure. As shown, example400includes a UE405, a relay UE410, and a network node110. In example400, the UE405is an Rx UE, and the relay UE410is a Tx UE. In some aspects, the UE405is one UE120, and the relay UE410is another UE120. In some aspects, the UE405may be referred to as a remote UE.

As shown inFIG.4, the UE405may receive a communication (e.g., data and/or control information) directly from the network node110as a downlink communication415. Additionally, or alternatively, the UE405may receive a communication (e.g., data and/or control information) indirectly from the network node110via the relay UE410. For example, the network node110may transmit the communication to the relay UE410as a downlink communication420, and the relay UE410may relay (e.g., forward or transmit) the communication to the UE405as a sidelink communication425.

In some aspects, the UE405may communicate directly with the network node110via a direct link430. For example, the downlink communication415may be transmitted via the direct link430. A communication transmitted via the direct link430between the UE405and the network node110(e.g., in the downlink communication415) does not pass through and is not relayed by the relay UE410. In some aspects, the UE405may communicate indirectly with the network node110via an indirect link435. For example, the downlink communication420and the sidelink communication425may be transmitted via different segments of the indirect link435. A communication transmitted via the indirect link435between the UE405and the network node110(e.g., in the downlink communication420and the sidelink communication425) passes through and is relayed by the relay UE410. Using the communication scheme shown inFIG.4may improve network performance and increase reliability by providing the UE405with link diversity for communicating with the network node110.

In some cases, the UE405may receive a communication (e.g., the same communication) from the network node110via both the direct link430and the indirect link435. In other cases, the network node110may select one of the links (e.g., either the direct link430or the indirect link435), and may transmit a communication to the UE405using only the selected link. Alternatively, the network node110may receive an indication of one of the links (e.g., either the direct link430or the indirect link435), and may transmit a communication to the UE405using only the indicated link. The indication may be transmitted by the UE405and/or the relay UE410. In some aspects, such selection and/or indication may be based at least in part on channel conditions and/or link reliability.

In some cases, the relay UE may use layer2(L2) relaying to relay communications between the network node110and the UE405. In cases in which L2relaying is used, the relay relationship between the relay UE410and the UE405may be known to network node110, and the network node110may store a context of the UE405. In some cases, the relay UE may use layer3(L3) relaying to relay communications between the network node and the UE405. In cases in which L3relaying is used, the network node is not aware of (e.g., does not store) the context of the remote UE (e.g., the UE405).

FIG.5is a diagram illustrating an example500of incentive-based relaying, in accordance with the present disclosure.

In some cases, a relay UE (or a user of the relay UE) may receive an incentive or reward for relaying data between a network node and a remote UE. For example, a network charging function (CHF) in a core network (e.g., a 5G core network) may provide a monetary payment for relaying, by a relay UE, data from a network node to a remote UE. In some examples, incentives for relaying rely on correlation of multiple reports from different entities. For example, the CHF may support reporting from the relay UE and the remote UE (e.g., via the relay UE, or directly). In this case, the CHF may correlate the reports (e.g., core network charging reports) from the relay UE and the remote UE to verify the amount of traffic relayed to the remote UE via a particular relay UE. However, in some cases, proof of relaying may not be available to verify that a relay UE relayed traffic to a remote UE. For L2relaying, the relationship between the relay UE and the remote UE is only known to the RAN node (e.g., the gNB), and the CHF may not be able to determine which relay UE relayed traffic to a remote UE. For L2relaying, if there is no transport/application ACK, the CHF may not be able to verify if a relay UE has attempted relaying, or if a remote UE is under-reporting the amount of traffic relayed to the remote UE. Additionally, RAN local traffic (e.g., traffic that does not pass through the core network), such as system information (SI) broadcast by the RAN node and relayed by a relay UE to a remote UE, cannot be corroborated by core network charging reports.

In some cases, there may be multiple possible relay UEs that can relay data between a network node and a remote UE. As shown inFIG.5, possible relay UEs for relaying data between a network node and a remote UE may include a first relay UE (relay UE1), a second relay UE (relay UE2), and a third relay (relay UE3). L2relaying and/or L3relaying may be supported for relaying the data between the network node and the remote UE. As shown inFIG.5, the network node may transmit data for the remote UE to relay UE1, relay UE2, and relay UE3. The data to be relayed to the remote UE may be unicast data (that is intended for the remote UE) and/or broadcast data. In some examples, the data to be relayed to the remote UE may include core network traffic and/or RAN local traffic, such as broadcast information link SI or broadcast traffic (e.g., from 5G multicast broadcast service (MBS)). In some examples, L3relaying may enable direct local routing of traffic to the remote UE.

As shown inFIG.5, relay UE1, relay UE2, and relay UE3 may each attempt to relay the data, received from the network node, to the remote UE. In example500, relay UE1 may successfully relay the data to the remote UE, and relay UE1 may receive acknowledgement (ACK) or negative acknowledgement (NACK) feedback (ACK/NACK feedback) (e.g., hybrid automatic repeat request (HARD) ACK/NACK feedback) from the remote UE. In this case, relay UE1 (e.g., the relay UE that successfully relayed the traffic to the remote UE) may be able to claim an incentive or reward from the network node or core network by providing proof of relaying (e.g., in a core network charging report). However, another UE (e.g., relay UE2 or relay UE3) that did not successfully relay the data to the remote UE may provide false proof of relaying for the data to attempt to claim the incentive, and the network (e.g., the CHF) may not be able to determine which relay UE relayed the traffic to the remote UE.

In some examples, in a case in which a relay UE relays data to a remote UE, a core network function (e.g., the CHF, a policy control function (PCF), or a direct discovery name management function (DDNMF)) correlates and verifies the relaying operation based on reporting by both the relay UE and the remote UE. However, in such examples, the verification requires that both the relay UE and the remote UE report the same information. This results in a higher network overhead (e.g., as compared to only one of the relay UE or the remote UE reporting the information), and the network may not know whether to trust the relay UE or the remote UE when there is a discrepancy between the information reported by the relay UE and the information reported by the remote UE. Furthermore, such reporting may incur a high overhead of radio resources for relayed uplink communications, as well as high power consumption at the remote UE. In addition, in some cases, the network may be able to verify the proof of relaying by correlating reports from the relay UE and the remote UE, as described above in connection withFIG.5.

Some techniques and apparatuses described herein enable UE relaying verification based at least in part on a digitally signed acknowledgement from the remote UE. A relay UE may receive, from a network node, data to be relayed to a remote UE, and the relay UE may transmit the data to the remote UE. The relay UE may receive, from the remote UE, a digitally signed acknowledgement of reception of the data. The digitally signed acknowledgment may include a message and a digital signature. The message may provide proof of the relaying of the data to the remote UE by the relay UE, and the digital signature may cryptographically protect the proof of relaying included in the message. The relay UE may transmit the digitally signed acknowledgement to the network node, and the network node (or a core network device) may verify the relaying based at least in part on the digitally signed acknowledgement. As a result, the network overhead for verifying the relaying may be reduced, as compared with verification based on reports received from the relay UE and the remote UE. Furthermore, because the proof of relaying is cryptographically protected by the digital signature generated by the remote UE, the verification prevents a UE other than the relay UE from claiming a reward or incentive for the relaying. In addition, the proof of relaying included in the digitally signed acknowledgement may be used to verify relaying in cases of L2relaying, in cases of L3relaying, in cases of relaying core network traffic, and in cases of relaying RAN local traffic.

FIGS.6A-6Bare diagrams illustrating an example600associated with UE (or mobile station) relaying verification, in accordance with the present disclosure. As shown inFIG.6A, example600includes communication between a network node110, a relay UE120-1, and a remote UE120-2. In some aspects, the network node110, the relay UE120-1, and the remote UE120-2may be included in a wireless network, such as wireless network100. The network node and the UEs120(e.g., the relay UE120-1and/or the remote UE120-2) may communicate via wireless access links, which may include uplinks and downlinks. The relay UE120-1and the remote UE120-2may communicate via a wireless access link, which may include a sidelink. In some aspects, the relay UE120-1may be a mobile station (e.g., a relay mobile station), may include a mobile station, or may be included in a mobile station. In some aspects, the remote UE120-2may be a mobile station (e.g., a remote mobile station), may include a mobile station, or may be included in a mobile station. In some aspects, the network node110may be a base station, a disaggregated base station, or one or more units of a disaggregated base station (e.g., a CU, a DU, an RU), or a combination thereof.

In some aspects, the relay UE120-2may perform operations, as described in connection withFIGS.6A and6B, relating to verification of relaying, by the relay UE120-1, of data from a first network entity to a second network entity. In some aspects, as shown in example600, the first network entity may be the network node110, and the second entity may be the remote UE120-2. In this case, the verification may relate to relaying, by the relay UE120-1, of downlink data from the network node110to the remote UE120-2. In other aspects, the first network entity may be a UE (e.g., a transmitting UE) and the second network entity may be the remote UE120-2(e.g., for verification of relaying of sidelink data by the relay UE120-1).

As shown inFIG.6A, and by reference number605, the network node110data, and the relay UE120-1may receive the data transmitted by the network node110. The data may be data to be relayed to the remote UE120-2. The relay UE120-1may receive the data (e.g., a data packet) and determine to relay the data to the remote UE120-2.

In some aspects, the determination, by the relay UE120-1, to relay the data to the remote UE120-2may be based at least in part on information, included in the data, that identifies the remote UE120-2. For example, the information that identifies the remote UE120-2may be included in a control message that accompanies the data, or the information that identifies the remote UE120-2may be included in the data packet (e.g., in a PDCP header) that includes the data. In such examples, the information may identify the remote UE120-2as a destination for the data transmitted by the network node110. For example, the data may be unicast data with a destination of the remote UE120-2.

In some aspects, the data may be broadcast data transmitted (e.g., broadcast) by the network node110, and the determination, by the relay UE120-1, to relay the data to the remote UE120-2may be based at least on a request, from the remote UE120-2, for the broadcast data. In this case, the remote UE120-2may transmit (e.g., in a unicast transmission to the relay UE120-1or in a broadcast transmission) a request for broadcast data being transmitted by the network node110. For example, the broadcast data may include SI broadcast by the network node110. The relay UE120-1may receive, from the remote UE120-2, the request for the broadcast data, and the relay UE120-1may determine to relay the broadcast data to the remote UE120-2in connection with receiving the request for the broadcast data.

As shown by reference number610, the relay UE120-1may transmit (e.g., relay) the data to the remote UE120-2. The remote UE120-2may receive the data originating from the network node110and relayed by the relay UE120-1. The relay UE120-1may transmit the data to the remote UE120-2(and the remote UE120-2may receive the data from the relay UE120-1), based at least in part on the determination by the relay UE120-1to relay the data.

As further shown by reference number615, the remote UE120-2may generate a digitally signed acknowledgement of reception of the data that is relayed from the relay UE120-1. The remote UE120-2may be configured to transmit, to the relay UE120-1, feedback including ACK/NACK feedback (e.g., HARQ ACK/NACK feedback) based at least in part on receiving the data from the relay UE120-1. The remote UE120-2may determine whether the feedback is to include an ACK (e.g., in connection with successful decoding of the data) or a NACK (e.g., in connection with unsuccessful decoding of the data). In some aspects, the remote UE120-2may generate the digitally signed acknowledgement of the reception of the data relayed from the relay UE120-1based at least in part on determining that feedback for the relayed data is to include an ACK (e.g., based at least in part on successfully decoding the relayed data).

In some aspects, the digitally signed acknowledgement may include a message and a digital signature. The message may include one or more parameters associated with the transmission of the data from the relay UE120-1to the remote UE120-2(e.g., one or more parameters associated with the relay UE120-1relaying the data to the remote UE120-2). For example, the message may include one or more parameters, such as a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a QoS flow identifier (QFI) associated with the data, a number of radio resources used for the transmission of the data from the relay UE120-1to the remote UE120-2, and/or a number of transmission attempts used for the transmission of the data from the relay UE120-1to the remote UE120-2, among other examples. In some aspects, the message may include one or more parameters that provide (e.g., to the network node110) proof of the relaying by the relay UE120-1. In some aspects, the message may include one or more parameters to be used (e.g., by the network node110or a core network device) to determine an incentive associated with relaying the data. In some aspects, the digital signature includes a message digest, associated with the message, that is encrypted based at least in part on a private security key associated with the remote UE120-2. The message digest may be a result of applying a hash function to the message (e.g., message digest=hash(message)). The digital signature may provide security for the proof of relaying information included in the message. For example, the digital signature may be used by the network node110to verify that the proof of relaying information included in the message originated from the remote UE120-2and has not been altered prior to the digitally signed acknowledgement being transmitted to the network node110.

FIG.6Bshows an example650of generating the digitally signed acknowledgement by the remote UE120-2. As shown by reference number652, in example650ofFIG.6B, the message may include an indication of the size of the data relayed to the remote UE120-2(e.g., shown as dataSize inFIG.6B), the priority associated with the data, the QoS parameter or QFI associated with the data, and the number of transmission attempts used for the transmission of the data from the relay UE120-1to the remote UE120-2. As shown by reference654, the remote UE120-2may compute/determine the message digest corresponding to the message by applying a hash function to the message. For example, the remote UE120-2may determine the message digest using the secure hash algorithm 1 (SHA-1) hash function, or another hash function. The message digest results from applying the hash function to the message. As shown by reference number656, the remote UE120-2may then encrypt the message digest using the private key of the remote UE120-2to generate the digital signature. For example, the remote UE120-2may use the Rivest-Shamir-Adelman (RSA) encryption algorithm, or another encryption algorithm, to encrypt the message digest based at least in part on the private key of the remote UE120-2. The digital signature may be an encrypted signature that results from encrypting the message digest. As shown by reference number658, the remote UE120-2may then attach the digital signature to the message, resulting in the digitally signed acknowledgement.

Returning toFIG.6A, as shown by reference number625, the remote UE120-2may transmit, to the relay UE120-1, the digitally signed acknowledgement of reception of the data. For example, the remote UE120-2may transmit the digitally signed acknowledgement to the relay UE120-1in a case in which the remote UE120-2determined that the feedback for the data relayed to the remote UE120-2is an ACK (e.g., in a case in which the remote UE120-2successfully decodes the relayed data). The relay UE120-1may receive, from the remote UE120-2, the digitally signed acknowledgement of reception of the data by the remote UE120-2.

As shown by reference number630, the relay UE120-1may transmit, to the network node110, the digitally signed acknowledgement of reception of the data by the remote UE120-2. The network node110may receive, from the remote UE120-2, the digitally signed acknowledgement of reception of the data by the remote UE120-2. In some aspects, the relay UE120-1may verify that the message is consistent with the data relayed to the remote UE120-2prior to transmitting the digitally signed acknowledgement to the network node110. For example, the relay UE120-1may verify that the one or more parameters included in the message (e.g., the one or more parameters associated with the transmission of the data from the relay UE120-1to the remote UE120-2) are consistent with the relaying of the data from the relay UE120-1to the remote UE120-2. In this case, the relay UE120-1may transmit the digitally signed acknowledgement to the network node110based at least in part on the verification of the one or more parameters included in the message. In this way, the relay UE120-1may verify the accuracy of the one or more parameters that provide the proof of relaying prior to transmitting the digitally signed acknowledgement, including the message and the digital signature, to the network node110.

In some aspects, the relay UE120-1may report the digitally signed acknowledgement for the relayed data to the network node110using real-time (or near real-time) reporting. For example, once the relay UE120-1receives the digitally signed acknowledgment from the remote UE120-2, the relay UE120-1may transmit the digitally signed acknowledgement to the network node110. In this case, if the relay UE120-1relays multiple data packets to the remote UE120-2and/or one or more other remote UEs, the relay UE120-1may separately transmit, to the network node110, the respective digitally signed acknowledgement for each relayed data packet. In some aspects, the relay UE120-1may report the digitally signed acknowledgement for the relayed data to the network node110using non-real-time reporting. For example, the relay UE120-1may aggregate all of the digitally signed acknowledgments for relaying to one or more remote UEs (the remote UE120-2and/or one or more other remote UEs) over a time period (e.g., in one day), and the relay UE120-1may transmit the aggregated digitally signed acknowledgments together in a communication (e.g., an uplink communication) to the network node110. In this case, the relay UE120-1may transmit the digitally signed acknowledgement for reception of the relayed data to the remote UE120-2to the network node110in a communication that includes the digitally signed acknowledgement and one or more other digitally signed acknowledgements associated with relaying other data.

As further shown inFIG.6A, and by reference number635, the network node110may verify the relaying of the data to the remote UE120-2by the relay UE120-1. The network node110, to verify the relaying of the data, may decrypt the message digest based at least in part on a public security key associated with the remote UE120-2. In some aspects, the remote UE120-2may provide the public security key associated with the remote UE120-2to the network node110. For example, the remote UE120-2may provide the public security key associated with the remote UE120-2to the network node110when an initial registration is formed or an initial connection is established between the remote UE120-2and the network node110. In some aspects, the remote UE120-2may transmit the public security key associated with the remote UE120-2directly to the network node110. In some aspects, the remote UE120-2may transmit the public security key to the network node110via one or more relay UEs (e.g., the relay UE120-1and or one or more other relay UEs). The network node110may receive public security key associated with the remote UE120-2. The network node110may perform decryption on the digital signature (e.g., using a decryption algorithm) based at least in part on the public security key associated with the remote UE120-2, resulting in the message digest.

The network node110, to verify the relaying of the data, may then verify the one or more parameters included in the message in the digitally signed acknowledgment based at least in part on the decrypted message digest. For example, the network node110may apply the hash function (e.g., the SHA-1 hash function) to the message, and compare the result of applying the hash function to the message (e.g., another message digest generated by the network node110) to the decrypted message digest to verify whether the message digest generated by the network node110by applying the hash function to the message is the same as the decrypted message digest. The one or more parameters provide proof of relaying of the data to the remote UE120-2by the relay UE120-1. Because the message digest included in the digitally signed acknowledgement is decrypted based at least in part on the private key associated with the remote UE120-2, the relay UE120-1cannot alter the message digest included in the digitally signed acknowledgement. Accordingly, by verifying the message based at least in part on the decrypted message digest, the network node110may verify that the one or more parameters (e.g., the proof of relaying) included in the message by the remote UE120-2have not been altered prior to the digitally signed acknowledgement being transmitted to the network node110.

In some aspects, one or more network devices (e.g., network entities) other than (or in addition to) the network node110may perform the verification of the relaying based at least in part on the digitally signed acknowledgement. For example, in some aspects, the network node110may transmit the digitally signed acknowledgement of reception of the data by the remote UE120-2to a core network device, such as a device associated with a CHF, a PCF, a DDNMF, or another core network function, and the core network device may perform the verification of the relaying of the data from the relay UE120-1to the remote UE120-2based at least in part on the digitally signed acknowledgment.

As further shown inFIG.6A, and by reference number640, the network node110may transmit an incentive (or an indication of an incentive) to the relay UE120-1. The relay UE120-1may receive the incentive (or the indication of the incentive). In some aspects, the network node110may transmit the incentive (or the indication of the incentive) to the relay UE120-1based at least in part on verifying the relaying of the data to the remote UE120-2by the relay UE120-1. For example, the network node110may transmit the incentive (or the indication of the incentive) to the relay UE120-1based at least in part on the verification of the one or more parameters in the message included in the message. In some aspects, the incentive for relaying the data to the remote UE120-2by the relay UE120-1may include at least one of a monetary incentive, a QoS incentive, or digital tokens that may be redeemed for monetary or QoS rewards, among other examples.

In some aspects, a device other than the network node110may provide the incentive to the relay UE120-1or the user of the relay UE120-1based at least in part on the verification of the relaying of the data. For example, a core network device associated with a CHF may provide a monetary incentive for relaying the data to an account of the user of the relay UE120-1. In such examples, the network node110may transmit an indication of the incentive to the relay UE120-1, and the relay UE120-1may receive the indication of the incentive.

As indicated above,FIGS.6A-6Bare provided as an example. Other examples may differ from what is described with respect toFIGS.6A-6B.

FIG.7is a diagram illustrating an example700associated with L2relay enhancements for UE (or mobile station) relaying verification, in accordance with the present disclosure. As shown inFIG.7, example700includes communication between core network702, a network node110, a relay UE120-1, and a remote UE120-2. In some aspects, the network node110may communicate with the relay UE120-1and/or the remote UE120-2via wireless access links, which may include uplinks and downlinks. The relay UE120-1and the remote UE120-2may communication via a sidelink. The core network (e.g., a 5G core network) may include an access and mobility function (AMF) and a CHF, as well as other core network functions. The AMF and the CHF may be performed on one or more core network devices.

As shown inFIG.7, and by reference number705, the network node110, the relay UE120-1, and the remote UE120-2may establish an L2relay relationship, in which the relay UE120-1relays communications between the network node110and the remote UE120-2. In some aspects, the network node110may be, may include, or may be included in a RAN node associated with the relay UE120-1(e.g., a RAN node with which the relay UE120-1has established a connection). In this case, the network node110may store a context of the remote UE120-2associated with the L2relay relationship.

As shown by reference number710, the network node110may transmit, to the core network702, an indication of a remote UE ID associated with the remote UE120-2. For example, the network node110may transmit the indication of the remote UE ID to report the L2relay relationship to the core network. In some aspects, the network node110may transmit the indication of the remote UE ID of the remote UE120-2to the AMF such that the remote UE ID of the remote UE120-2may be associated with a context of the remote UE120-2. For example, the network node110may be triggered to report the remote UE ID of the remote UE120-2, to be associated with the context of the relay UE120-1, to the AMF in connection with the L2relay relationship being established. In some aspects, the remote UE ID may be a general public subscription ID (GPSI), as the remote UE120-2and the relay UE120-1may not be served by the same public land mobile network (PLMN) in some cases.

As shown by reference number715, the AMF may transmit/report the remote UE ID of the remote UE120-2to the CHF. In some aspects, the AMF may associate the remote UE ID with the context of the relay UE120-1as an L2remote UE ID. In some aspects, the AMF may be triggered to report the L2remote UE ID to the CHF for correlation creation when the AMF receives the remote UE ID from the network node110.

As shown by reference number720, the CHF may create a correlation between the relay UE120-1(e.g., a UE ID of the relay UE120-1) and the remote UE ID (e.g., the GPSI) of the remote UE120-2based at least in part on receiving the remote UE ID from the AMF. The CHF may store the correlation between the relay UE120-1and the remote UE ID of the remote UE120-2. In some aspects, the CHF may correlate reports, from the relay UE120-1and the remote UE120-2, of relaying data to the remote UE120-2by the relay UE120-1based at least in part on the correlation between the relay UE120-1and the remote UE ID of the remote UE120-2, and the CHF may determine and/or provide an incentive (e.g., to the relay UE120-1) for the relaying based at least in part on correlating the reports of the relaying. In this way, verification, by the CHF, of the relaying to the remote UE120-2by the relay UE120-1may be based at least in part on the reporting, by the network node110, of the L2relay relationship to the core network.

In some aspects, the L2relay enhancements described above in connection withFIG.7may be combined with the operations described above in connection withFIGS.6A and6Bor may be performed independently with respect to the operations described above in connection withFIGS.6A and6B.

FIG.8is a diagram illustrating an example process800performed, for example, by a mobile station, in accordance with the present disclosure. Example process800is an example where the mobile station (e.g., relay UE120-1) performs operations associated with mobile station relaying verification.

As shown inFIG.8, in some aspects, process800may include receiving, from a first network entity, data to be relayed to a second network entity (block810). For example, the mobile station (e.g., using communication manager1108and/or reception component1102, depicted inFIG.11) may receive, from a first network entity, data to be relayed to a second network entity, as described above.

As further shown inFIG.8, in some aspects, process800may include transmitting the data to the second network entity (block820). For example, the mobile station (e.g., using communication manager1108and/or transmission component1104, depicted inFIG.11) may transmit the data to the second network entity, as described above.

As further shown inFIG.8, in some aspects, process800may include receiving, from the second network entity, a digitally signed acknowledgement of reception of the data (block830). For example, the mobile station (e.g., using communication manager1108and/or reception component1102, depicted inFIG.11) may receive, from the second network entity, a digitally signed acknowledgement of reception of the data, as described above.

As further shown inFIG.8, in some aspects, process800may include transmitting the digitally signed acknowledgement to the first network entity (block840). For example, the mobile station (e.g., using communication manager1108and/or transmission component1104, depicted inFIG.11) may transmit the digitally signed acknowledgement to the first network entity, as described above.

In a first aspect, the data comprises information that identifies the second network entity, and transmitting the data to the second network entity comprises transmitting the data to the second network entity based at least in part on the information that identifies the second network entity.

In a second aspect, alone or in combination with the first aspect, the data comprises broadcast data transmitted by the first network entity, and process800includes receiving, from the second network entity, a request for the broadcast data, wherein transmitting the data to the second network entity comprises transmitting the data to the second network entity based at least in part on receiving the request for the broadcast data.

In a third aspect, alone or in combination with one or more of the first and second aspects, the digitally signed acknowledgement comprises a message comprising indications of one or more parameters associated with transmission of the data from the mobile station to the second network entity, and a digital signature associated with the second network entity.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the one or more parameters comprise at least one of a size of the data, a priority associated with the data, a QoS parameter associated with the data, a number of radio resources used for the transmission of the data from the mobile station to the second network entity, or a number of transmission attempts used for the transmission of the data from the mobile station to the second network entity.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the digital signature comprises a message digest, associated with the message, that is encrypted based at least in part on a private security key associated with the second network entity.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the message digest is a result of applying a hash function to the message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, transmitting the digitally signed acknowledgement to the first network entity comprises transmitting the digitally signed acknowledgement to the first network entity based at least in part on a verification of the one or more parameters included in the message.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process800includes receiving an incentive based at least in part on transmitting the digitally signed acknowledgement to the first network entity.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, transmitting the digitally signed acknowledgement to the first network entity comprises transmitting, to the first network entity, a communication that includes the digitally signed acknowledgement and one or more other digitally signed acknowledgements associated with relaying other data.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the first network entity is a network node.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the second network entity is a remote mobile station.

FIG.9is a diagram illustrating an example process900performed, for example, by a mobile station, in accordance with the present disclosure. Example process900is an example where the mobile station (e.g., remote UE120-2) performs operations associated with mobile sttion relaying verification.

As shown inFIG.9, in some aspects, process900may include receiving, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station (block910). For example, the mobile station (e.g., using communication manager1208and/or reception component1202, depicted inFIG.12) may receive, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station, as described above.

As further shown inFIG.9, in some aspects, process900may include transmitting, to the relay mobile station, a digitally signed acknowledgement of reception of the data (block920). For example, the mobile station (e.g., using communication manager1208and/or transmission component1204, depicted inFIG.12) may transmit, to the relay mobile station, a digitally signed acknowledgement of reception of the data, as described above.

In a first aspect, the data comprises information that identifies the mobile station.

In a second aspect, alone or in combination with the first aspect, the data comprises broadcast data transmitted by the network entity, and process900includes transmitting, to the relay mobile station, a request for the broadcast data, wherein receiving the data comprises receiving the data from the relay mobile station based at least in part on transmitting the request for the broadcast data.

In a third aspect, alone or in combination with one or more of the first and second aspects, the digitally signed acknowledgement comprises a message comprising indications of one or more parameters associated with transmission of the data from the relay mobile station to the mobile station, and a digital signature associated with the mobile station.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the one or more parameters comprise at least one of a size of the data, a priority associated with the data, a QoS parameter associated with the data, a number of radio resources used for the transmission of the data from the relay mobile station to the mobile station, or a number of transmission attempts used for the transmission of the data from the relay mobile station to the mobile station.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the digital signature comprises a message digest, associated with the message, that is encrypted based at least in part on a private security key associated with the mobile station.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process900includes applying a hash function to the message, resulting in the message digest, encrypting the message digest based at least in part on a private security key associated with the mobile station, resulting in the digital signature, and attaching the digital signature to the message, resulting in the digitally signed acknowledgement.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process900includes transmitting, by the mobile station and to the network entity, a public security key associated with the mobile station.

FIG.10is a diagram illustrating an example process1000performed, for example, by a network entity, in accordance with the present disclosure. Example process1000is an example where the network entity (e.g., network node110) performs operations associated with mobile station relaying verification.

As shown inFIG.10, in some aspects, process1000may include transmitting, to a relay mobile station, data to be relayed to a remote mobile station (block1010). For example, the network entity (e.g., using communication manager1308and/or transmission component1304, depicted inFIG.13) may transmit, to a relay mobile station, data to be relayed to a remote mobile station, as described above.

As further shown inFIG.10, in some aspects, process1000may include receiving, from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station (block1020). For example, the network entity (e.g., using communication manager1308and/or reception component1302, depicted inFIG.13) may receive, from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station, as described above.

In a first aspect, process1000includes transmitting, by the network entity and to the relay mobile station, an incentive or an indication of an incentive based at least in part on receiving the digitally signed acknowledgement.

In a second aspect, alone or in combination with the first aspect, the data comprises information that identifies the remote mobile station.

In a third aspect, alone or in combination with one or more of the first and second aspects, the data comprises broadcast data.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the digitally signed acknowledgement comprises a message comprising indications of one or more parameters associated with transmission of the data from the relay mobile station to the remote mobile station, and a digital signature associated with the remote mobile station.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the one or more parameters comprise at least one of a size of the data, a priority associated with the data, a QoS parameter associated with the data, a number of radio resources used for the transmission of the data from the relay mobile station to the remote mobile station, or a number of transmission attempts used for the transmission of the data from the relay mobile station to the remote mobile station.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the digital signature comprises a message digest, associated with the message, that is encrypted based at least in part on a private security key associated with the second network entity.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the message digest is a result of applying a hash function to the message.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process1000includes decrypting the message digest based at least in part on a public security key associated with the relay mobile station, and verifying the one or more parameters in the message based at least in part on the message digest.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process1000includes transmitting, by the network entity and to the relay mobile station, an incentive or an indication of an incentive based at least in part on verifying the one or more parameters in the message.

FIG.11is a diagram of an example apparatus1100for wireless communication, in accordance with the present disclosure. The apparatus1100may be a mobile station, or a mobile station may include the apparatus1100. In some aspects, the apparatus1100includes a reception component1102and a transmission component1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1100may communicate with another apparatus1106(such as a UE, a base station, or another wireless communication device) using the reception component1102and the transmission component1104. As further shown, the apparatus1100may include the communication manager1108. The communication manager1108may perform operations similar to communication manager140described elsewhere herein. The communication manager1108may include a determination component1110, among other examples.

The reception component1102may receive, from a first network entity, data to be relayed to a second network entity. The transmission component1104may transmit the data to the second network entity. The reception component1102may receive, from the second network entity, a digitally signed acknowledgement of reception of the data. The transmission component1104may transmit the digitally signed acknowledgement to the first network entity.

The determination component1110may determine that the data received from the first network entity is to be relayed to the second network entity.

The reception component1102may receive an incentive based at least in part on transmitting the digitally signed acknowledgement to the first network entity.

FIG.12is a diagram of an example apparatus1200for wireless communication, in accordance with the present disclosure. The apparatus1200may be a mobile station, or a mobile station may include the apparatus1200. In some aspects, the apparatus1200includes a reception component1202and a transmission component1204, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1200may communicate with another apparatus1206(such as a UE, a base station, or another wireless communication device) using the reception component1202and the transmission component1204. As further shown, the apparatus1200may include the communication manager1208. The communication manager1208may perform operations similar to the communication manager140described elsewhere herein. The communication manager1208may include one or more of a hashing component1210, an encryption component1212, and/or an attachment component1214, among other examples.

The reception component1202may receive, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station. The transmission component1204may transmit, to the relay mobile station, a digitally signed acknowledgement of reception of the data.

The hashing component1210may apply a hash function to the message, resulting in the message digest.

The encryption component1212may encrypt the message digest based at least in part on a private security key associated with the mobile station, resulting in the digital signature.

The attachment component1214may attach the digital signature to the message, resulting in the digitally signed acknowledgement.

The transmission component1204may transmit, to the network entity, a public security key associated with the mobile station.

FIG.13is a diagram of an example apparatus1300for wireless communication, in accordance with the present disclosure. The apparatus1300may be a network entity, or a network entity may include the apparatus1300. In some aspects, the apparatus1300includes a reception component1302and a transmission component1304, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1300may communicate with another apparatus1306(such as a UE, a base station, or another wireless communication device) using the reception component1302and the transmission component1304. As further shown, the apparatus1300may include the communication manager1308. The communication manager1308may perform operations similar to the communication manager150described elsewhere herein. The communication manager1308may include one or more of a decryption component1310and/or a verification component1312, among other examples.

The transmission component1304may transmit, to a relay mobile station, data to be relayed to a remote mobile station. The reception component1302may receive, from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station.

The transmission component1304may transmit, to the relay mobile station, an incentive or an indication of an incentive based at least in part on receiving the digitally signed acknowledgement.

The decryption component1310may decrypt the message digest based at least in part on a public security key associated with the relay mobile station.

The verification component1312may verify the one or more parameters in the message based at least in part on the message digest.

The transmission component1304may transmit, to the relay mobile station, an incentive or an indication of an incentive based at least in part on verifying the one or more parameters in the message.

The following provides an overview of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by a mobile station, comprising: receiving, by the mobile station and from a first network entity, data to be relayed to a second network entity; transmitting, by the mobile station, the data to the second network entity; receiving, by the mobile station and from the second network entity, a digitally signed acknowledgement of reception of the data; and transmitting, by the mobile station, the digitally signed acknowledgement to the first network entity.Aspect 2: The method of Aspect 1, wherein the data comprises information that identifies the second network entity, and wherein transmitting the data to the second network entity comprises: transmitting the data to the second network entity based at least in part on the information that identifies the second network entity.Aspect 3: The method of Aspect 1, wherein the data comprises broadcast data transmitted by the first network entity, and further comprising: receiving, by the mobile station and from the second network entity, a request for the broadcast data, wherein transmitting the data to the second network entity comprises transmitting the data to the second network entity based at least in part on receiving the request for the broadcast data.Aspect 4: The method of any of Aspects 1-3, wherein the digitally signed acknowledgement comprises: a message comprising indications of one or more parameters associated with transmission of the data from the mobile station to the second network entity; and a digital signature associated with the second network entity.Aspect 5: The method of Aspect 4, wherein the one or more parameters comprise at least one of a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a number of radio resources used for the transmission of the data from the mobile station to the second network entity, or a number of transmission attempts used for the transmission of the data from the mobile station to the second network entity.Aspect 6: The method of any of Aspects 4-5, wherein the digital signature comprises a message digest, associated with the message, that is encrypted based at least in part on a private security key associated with the second network entity.Aspect 7: The method of Aspect 6, wherein the message digest is a result of applying a hash function to the message.Aspect 8: The method of any of Aspects 4-7, wherein transmitting the digitally signed acknowledgement to the first network entity comprises: transmitting the digitally signed acknowledgement to the first network entity based at least in part on a verification of the one or more parameters included in the message.Aspect 9: The method of any of Aspects 1-8, further comprising: receiving, by the mobile station, an incentive based at least in part on transmitting the digitally signed acknowledgement to the first network entity.Aspect 10: The method of any of Aspects 1-9, wherein transmitting the digitally signed acknowledgement to the first network entity comprises: transmitting, to the first network entity, a communication that includes the digitally signed acknowledgement and one or more other digitally signed acknowledgements associated with relaying other data.Aspect 11: The method of any of Aspects 1-10, wherein the first network entity is a network node.Aspect 12: The method of any of Aspects 1-11, wherein the second network entity is a remote mobile station.Aspect 13: A method of wireless communication performed by a mobile station, comprising: receiving, by the mobile station and from a relay mobile station, data originating from a network entity and relayed by the relay mobile station; and transmitting, by the mobile station and to the relay mobile station, a digitally signed acknowledgement of reception of the data.Aspect 14: The method of Aspect 13, wherein the data comprises information that identifies the mobile station.Aspect 15: The method of Aspect 13, wherein the data comprises broadcast data transmitted by the network entity, and further comprising: transmitting, by the mobile station and to the relay mobile station, a request for the broadcast data, wherein receiving the data comprises receiving the data from the relay mobile station based at least in part on transmitting the request for the broadcast data.Aspect 16: The method of any of Aspects 13-15, wherein the digitally signed acknowledgement comprises: a message comprising indications of one or more parameters associated with transmission of the data from the relay mobile station to the mobile station; and a digital signature associated with the mobile station.Aspect 17: The method of Aspect 16, wherein the one or more parameters comprise at least one of a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a number of radio resources used for the transmission of the data from the relay mobile station to the mobile station, or a number of transmission attempts used for the transmission of the data from the relay mobile station to the mobile station.Aspect 18: The method of any of Aspects 16-17, wherein the digital signature comprises a message digest, associated with the message, that is encrypted based at least in part on a private security key associated with the mobile station.Aspect 19: The method of Aspect 18, further comprising: applying a hash function to the message, resulting in the message digest; encrypting the message digest based at least in part on a private security key associated with the mobile station, resulting in the digital signature; and attaching the digital signature to the message, resulting in the digitally signed acknowledgement.Aspect 20: The method of any of Aspects 18-19, further comprising: transmitting, by the mobile station and to the network entity, a public security key associated with the mobile station.Aspect 21: A method of wireless communication performed by a network entity, comprising: transmitting, by the network entity and to a relay mobile station, data to be relayed to a remote mobile station; and receiving, by the network entity and from the relay mobile station, a digitally signed acknowledgement of reception of the data by the remote mobile station.Aspect 22: The method of Aspect 21, further comprising: transmitting, by the network entity and to the relay mobile station, an incentive or an indication of an incentive based at least in part on receiving the digitally signed acknowledgement.Aspect 23: The method of any of Aspects 21-22, wherein the data comprises information that identifies the remote mobile station.Aspect 24: The method of any of Aspects 21-22, wherein the data comprises broadcast data.Aspect 25: The method of any of Aspects 21-24, wherein the digitally signed acknowledgement comprises: a message comprising indications of one or more parameters associated with transmission of the data from the relay mobile station to the remote mobile station; and a digital signature associated with the remote mobile station.Aspect 26: The method of Aspect 25, wherein the one or more parameters comprise at least one of a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a number of radio resources used for the transmission of the data from the relay mobile station to the remote mobile station, or a number of transmission attempts used for the transmission of the data from the relay mobile station to the remote mobile station.Aspect 27: The method of any of Aspects 25-26, wherein the digital signature comprises a message digest, associated with the message, that is encrypted based at least in part on a private security key associated with the second network entity.Aspect 28: The method of Aspect 27, wherein the message digest is a result of applying a hash function to the message.Aspect 29: The method of any of Aspects 27-28, further comprising: decrypting the message digest based at least in part on a public security key associated with the relay mobile station; and verifying the one or more parameters in the message based at least in part on the message digest.Aspect 30: The method of Aspect 29, further comprising: transmitting, by the network entity and to the relay mobile station, an incentive or an indication of an incentive based at least in part on verifying the one or more parameters in the message.Aspect 31: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-12.Aspect 32: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-12.Aspect 33: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-12.Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-12.Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-12.Aspect 36: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 13-20.Aspect 37: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 13-20.Aspect 38: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 13-20.Aspect 39: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 13-20.Aspect 40: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 13-20.Aspect 41: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 21-30.Aspect 42: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 21-30.Aspect 43: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 21-30.Aspect 44: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 21-30.Aspect 45: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 21-30.