WO2023208960A1 - Managing rejection of a sidelink, sl, discontinuous reception, drx, configuration - Google Patents

Abstract

The present disclosure provides a method performed by a first wireless device (RX UE). The method is performed in response to receiving, from an entity, a sidelink (SL) discontinuous reception (DRX) configuration for performing DRX of transmissions over an SL interface. The method comprises rejecting (502) the SL DRX configuration without triggering a radio link failure or radio resource control (RRC) reestablishment procedure.

Description

MANAGING DISCONTINUOUS RECEPTION OF TRANSMISSIONS TECHNICAL FIELD [0001] The present disclosure relates to methods for managing discontinuous reception of transmissions, and a wireless device and entity configured to operate in accordance with those methods. BACKGROUND [0002] Sidelink (SL) transmissions over new radio (NR) are specified for Third Generation Partnership Project (3GPP) Release 16. Four new enhancements are particularly introduced to NR sidelink transmissions as follows: (1) Not only broadcast but also unicast and groupcast are supported in sidelink transmissions. For unicast and groupcast, the physical sidelink feedback channel (PSFCH) is for a receiving user equipment (UE) to reply with a decoding status to a transmitting UE. (2) To improve the latency performance, grant-free transmissions that are adopted in NR uplink transmissions are also provided in NR sidelink transmissions. (3) To alleviate resource collisions among different sidelink transmissions launched by different UEs, an enhancement is introduced to channel sensing and resource selection procedures, which also leads to a new design of physical sidelink common control channel (PSCCH). (4) To achieve a high connection density, congestion control and thus the quality of service (QoS) management is supported in NR sidelink transmissions. [0003] To enable the above enhancements, new physical channels and reference signals are introduced in NR (available in long term evolution (LTE) before): (1) Physical Sidelink Shared Channel (PSSCH), SL version of physical downlink shared channel (PDSCH) is transmitted by a sidelink transmitting UE, which conveys sidelink transmission data, system information blocks (SIBs) for radio resource control (RRC) configuration, and a part of sidelink control information (SCI). (2) Physical sidelink feedback channel (PSFCH) (which is the Physical SL version of physical uplink control channel (PUCCH)) is transmitted by a sidelink receiving UE for unicast and groupcast, which conveys 1 bit information over 1 resource block (RB) for a hybrid automatic repeat request (HARQ) acknowledgement (ACK) and a negative ACK (NACK). In addition, channel state information (CSI) is carried in a medium access control (MAC) control element (CE) over the PSSCH instead of the PSFCH. (3) PSCCH (Physical Sidelink Common Control Channel, which is the SL version of physical downlink control channel (PDCCH)). When the traffic to be sent to a receiving UE arrives at a transmitting UE, a transmitting UE can first send the PSCCH, which conveys a part of SCI (which is the SL version of downlink control information (DCI)) to be decoded by any UE for channel sensing purposes, including reserved time-frequency resources for transmissions, demodulation reference signal (DMRS) pattern and antenna port, etc. (4) Sidelink primary synchronization signal (SPSS)/sidelink secondary synchronization signal (SSSS), which are similar to downlink transmissions in NR, in sidelink transmissions. These primary and secondary synchronization signals (called SPSS and SSSS, respectively) are supported. Through detecting the SPSS and SSSS, a UE is able to identify a sidelink synchronization identity (SSID) from a UE sending the SPSS/SSSS. Through detecting the SPSS/SSSS, a UE is therefore able to know the characteristics of the UE transmitting the SPSS/SSSS. A series process of acquiring timing and frequency synchronization together with SSIDs of UEs is called initial cell search. Note that the UE sending the SPSS/SSSS may not be necessarily involved in sidelink transmissions, and a node (UE/evolved Node B (eNB)/gNodeB (gNB)) sending the SPSS/SSSS is called a synchronization source. (5) Physical sidelink broadcast channel (PSBCH) is transmitted along with the SPSS/SSSS as a synchronization signal/PSBCH block (SSB). The SSB has the same numerology as PSCCH/PSSCH on that carrier, and an SSB should be transmitted within the bandwidth of a configured bandwidth part (BWP). The PSBCH conveys information related to synchronization, such as a direct frame number (DFN), indication of slot and symbol level time resources for sidelink transmissions, in-coverage indicator, etc. The SSB is transmitted periodically at every 160 ms. (6) DMRS, phase tracking reference signal (PT-RS), and channel state information reference signal (CSIRS) are physical reference signals supported by NR downlink/uplink transmissions and are also adopted by sidelink transmissions. Similarly, the PT-RS is only applicable for frequency range 2 (FR2) transmission. [0004] Another new feature is the two-stage sidelink control information (SCI). This is a version of the DCI for SL. Unlike the DCI, only part (first stage) of the SCI is sent on the PSCCH. This part is used for channel sensing purposes (including the reserved time-frequency resources for transmissions, demodulation reference signal (DMRS) pattern and antenna port, etc.) and can be read by all UEs while the remaining (second stage) scheduling and control information such as an 8-bits source identity (ID) and a 16-bits destination ID, new data indicator (NDI), redundancy version (RV) and HARQ process ID is sent on the PSSCH to be decoded by the receiving UE. [0005] Similar as for proximity services (PRoSE) in LTE, NR sidelink transmissions have two modes of resource allocations. In Mode 1, sidelink resources are scheduled by a gNB. In Mode 2, the UE autonomously selects sidelink resources from a (pre-)configured sidelink resource pool(s) based on the channel sensing mechanism. For the in-coverage UE, a gNB can be configured to adopt Mode 1 or Mode 2. For the out-of-coverage UE, only Mode 2 can be adopted. As in LTE, scheduling over the sidelink in NR is done in different ways for Mode 1 and Mode 2. [0006] Mode 1 supports two kinds of grants: dynamic grants and configured grants. For dynamic grant, when the traffic to be sent over sidelink arrives at a transmitting UE, this UE can launch a four-message exchange procedure to request sidelink resources from a gNB (scheduling request (SR) on uplink (UL), grant, buffer status report (BSR) on UL, grant for data on SL sent to UE). During the resource request procedure, a gNB may allocate a sidelink radio network temporary identifier (SL-RNTI) to the transmitting UE. If this sidelink resource request is granted by a gNB, then a gNB indicates the resource allocation for the PSCCH and the PSSCH in the downlink control information (DCI) conveyed by PDCCH with cyclic redundancy check (CRC) scrambled with the SL-RNTI. When a transmitting UE receives such a DCI, a transmitting UE can obtain the grant only if the scrambled CRC of DCI can be successfully solved by the assigned SL-RNTI. A transmitting UE then indicates the time-frequency resources and the transmission scheme of the allocated PSSCH in the PSCCH, and launches the PSCCH and the PSSCH on the allocated resources for sidelink transmissions. When a grant is obtained from a gNB, a transmitting UE can only transmit a single transport block (TB). As a result, this kind of grant is suitable for traffic with a loose latency requirement. [0007] For configured grant, for the traffic with a strict latency requirement, performing the four-message exchange procedure to request sidelink resources may induce unacceptable latency. In this case, prior to the traffic arrival, a transmitting UE may perform the four-message exchange procedure and request a set of resources. If a grant can be obtained from a gNB, then the requested resources are reserved in a periodic manner. Upon traffic arriving at a transmitting UE, this UE can launch the PSCCH and the PSSCH on the upcoming resource occasion. In fact, this kind of grant is also known as grant-free transmission. [0008] In both dynamic grant and configured grant, a sidelink receiving UE cannot receive the DCI (because it is addressed to the transmitting UE), and therefore a receiving UE should perform blind decoding to identify the presence of PSCCH and find the resources for the PSSCH through the SCI. [0009] The SCI has a first and second part. Among other things, the first part (sent on PSCCH) contains reserved time-frequency resources for transmissions, demodulation reference signal (DMRS) pattern and antenna port. The second part (sent on PSSCH) includes an 8-bits source identity (ID) and a 16-bits destination ID. SCI also includes a 1-bit new data indicator (NDI), 2-bit redundancy version (RV), and 4-bit HARQ process ID. When a transmitting UE launches the PSCCH, CRC is also inserted in the SCI without any scrambling. [0010] In Mode 2 resource allocation, when traffic arrives at a transmitting UE, the transmitting UE autonomously selects resources for the PSCCH and the PSSCH. To further minimize the latency of the feedback HARQ ACK/NACK transmissions and subsequent retransmissions, the transmitting UE may also reserve resources for PSCCH/PSSCH for retransmissions. To further suppress the probability to perform retransmissions, the transmitting UE may repeat the TB transmission along with the initial TB transmission. This mechanism is also known as blind retransmission. As a result, when traffic arrives at a transmitting UE, then this transmitting UE should select resources for the following transmissions: (1) the PSSCH associated with the PSCCH for initial transmission and blind retransmissions; and (2) the PSSCH associated with the PSCCH for retransmissions. [0011] Because each transmitting UE in sidelink transmissions should autonomously select resources for above transmissions, preventing different transmitting UEs from selecting the same resources is a critical issue in Mode 2. A particular resource selection procedure is therefore imposed to Mode 2 based on channel sensing. The channel sensing algorithm involves measuring reference signal received power (RSRP) on different subchannels and requires knowledge of the different UEs power levels of DMRS on the PSSCH or the DMRS on the PSCCH depending on the configuration. This information is known only after receiving SCI launched by (all) other UEs. [0012] Figure 1 illustrates a sidelink connection between two UEs, transmitting (TX) UE and receiving (RX) UE. The sidelink between the TX UE and the RX UE uses the PC5 interface, while the link between the TX UE and the network (NW) uses the Uu interface. In 3GPP Release 17, a new sidelink discontinuous reception (DRX) is going to be used over the PC5 link between two sidelink UEs. According to 3GPP Release 17, the serving cell of the TX UE is the node responsible for creating the sidelink DRX (in case of sidelink Mode 1) and this SL DRX configuration is then forwarded to the RX UE by the TX UE over PC5. In Mode 2, the SL DRX configuration is decided by the TX UE itself and sent to the RX UE. [0013] The RX UE receives an RRC configuration, which includes the SL DRX configuration. The RX UE can accept the RRC configuration (and, by that, accept the SL DRX configuration), or reject the RRC configuration by declaring radio link failure and triggering an RRC re-establishment as stated in 3GPP. SUMMARY [0014] There currently exist certain challenge(s). For example, the consequence of the RX UE needing to trigger the RRC re-establishment procedure can be long connectivity interruption and signaling overhead because the whole RRC connection over Uu and PC5 needs to be released and re-established. [0015] It is an object of the disclosure to obviate or eliminate at least some of the above- described disadvantages associated with existing techniques. [0016] According to an aspect of the disclosure, there is provided a first method. The first method is performed by a first wireless device (RX UE). The first method is performed in response to receiving, from an entity, a sidelink (SL) discontinuous reception (DRX) configuration for performing DRX of transmissions over an SL interface. The first method comprises rejecting the SL DRX configuration without triggering a radio link failure or radio resource control (RRC) reestablishment procedure. [0017] According to another aspect of the disclosure, there is provided a second method. The second method is performed by a first wireless device (RX UE). The second method comprises transmitting an indication to an entity in response to rejecting an SL DRX configuration received from the entity for performing DRX of transmissions over an SL interface. The SL DRX configuration is rejected without triggering a radio link failure or RRC reestablishment procedure and the indication is an indication that the SL DRX configuration was rejected by the RX UE without triggering the radio link failure or RRC reestablishment procedure. [0018] According to another aspect of the disclosure, there is provided a third method. The third method is performed by an entity. The third method is performed in response to transmitting an SL DRX configuration to a first wireless device (RX UE). The third method comprises receiving, from the RX UE, an indication that the SL DRX configuration was rejected by the RX UE without triggering a radio link failure or RRC reestablishment procedure. The SL DRX configuration is for performing DRX of transmissions over an SL interface. [0019] According to another aspect of the disclosure, there is provided a fourth method. The fourth method is performed by a system. The fourth method comprises the first method and/or the second method, and the third method. [0020] According to another aspect of the disclosure, there is provided a first wireless device. The first wireless device is configured to operate in accordance with the first method and/or the second method. [0021] According to another aspect of the disclosure, there is provided an entity. The entity is configured to operate in accordance with the third method. [0022] According to another aspect of the disclosure, there is provided a system comprising the first wireless device and the entity. [0023] According to another aspect of the disclosure, there is provided a computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the first method, the second method, and/or the third method. [0024] According to another aspect of the disclosure, there is provided a computer program, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform the first method, the second method, and/or the third method. [0025] Certain aspects of the disclosure and their embodiments can provide solutions to the above-mentioned problems, or other challenges, e.g. by allowing a wireless device (or UE) to not declare radio link failure or trigger the RRC reestablishment procedure when rejecting an SL DRX configuration received by a TX UE. [0026] Certain embodiments may provide one or more of the following technical advantages. The present disclosure allows a UE to not declare radio link failure and thus not trigger the RRC reestablishment procedure when rejecting an SL DRX configuration received by a TX UE, whether this SL DRX configuration is generated by the network or the TX UE. This has benefits in terms of connectivity interruption, signaling overhead, latency, and power consumption. BRIEF DESCRIPTION OF THE DRAWINGS [0027] For a better understanding of the techniques, and to show how they may be put into effect, reference will now be made, by way of example, to the accompanying drawings, in which: [0028] Figure 1 is a schematic illustration of an example system; [0029] Figures 2-4 are block diagrams illustrating methods performed according to some embodiments; [0030] Figures 5-8 are signaling diagrams illustrating an exchange of signals in a system according to some embodiments; [0031] Figure 9 is a block diagram illustrating a system according to an embodiment; [0032] Figure 10 is a block diagram illustrating a user equipment according to an embodiment; [0033] Figure 11 is a block diagram illustrating a network node according to an embodiment; [0034] Figure 12 is a block diagram illustrating a host computer according to an embodiment; [0035] Figure 13 is a block diagram illustrating a virtualization environment according to an embodiment; and [0036] Figure 14 is a block diagram illustrating a host computer communicating via a network node with a user equipment according to an embodiment. DETAILED DESCRIPTION [0037] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description. [0038] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject-matter disclosed herein, the disclosed subject-matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject-matter to those skilled in the art. [0039] As mentioned earlier, it is currently the case that the RX UE receives the RRC configuration, which includes the SL DRX configuration. The RX UE can accept the RRC configuration (and, by that, accept the SL DRX configuration), or reject the RRC configuration by declaring radio link failure and triggering an RRC re-establishment as stated in 3GPP. [0040] Thus, once the RX UE receives the SL DRX configuration, the RX UE has the choice to accept or reject the SL DRX configuration. In case the RX UE decides to reject the received SL DRX configuration, the RX UE may indicate this rejection to the TX UE. The TX UE may also inform the network about this. For example, The TX UE may inform the network about this if the network was the node responsible for generating the SL DRX configuration. [0041] However, according to 3GPP technical standard (TS) 38.331 Version (V) 17.0.0, clause 5.3.5.8.2, when a UE receives an RRC Reconfiguration message, it should trigger an RRC re-establishment procedure and declare radio link failure if is not able to comply with the configurations included in the RRC Reconfiguration message. This means that every time an RX UE decides to reject the SL DRX sent by the TX UE (whether generated by the network or the TX UE) it needs to trigger the RRC re-establishment procedure, with a consequence of long connectivity interruption and signaling overhead because the whole RRC connection over Uu and PC5 needs to be released and re-established. Moreover, 3GPP TS 38.331 V17.0.0 currently does not support that the RX UE could reject only the SL DRX configuration but apply the rest of the other configuration received without declaring a reconfiguration error or radio link failure. [0042] The present disclosure relates to methods for managing discontinuous reception of transmissions, and a wireless device and entity configured to operate in accordance with those methods. It is an object of the present disclosure to obviate or eliminate at least some of the above- described disadvantages associated with existing techniques. [0043] Figure 2 illustrates a first method according to an aspect of the disclosure. The first method is performed by a first wireless device (RX UE) in response to receiving, from an entity, a sidelink (SL) discontinuous reception (DRX) configuration for performing DRX of transmissions over an SL interface. As illustrated by block 502 of Figure 2, the first method comprises rejecting the SL DRX configuration without triggering a radio link failure or radio resource control (RRC) reestablishment procedure. [0044] In some embodiments, rejecting the SL DRX configuration may comprise not applying the SL DRX configuration. In some embodiments, the SL DRX configuration may be received in an RRCReconfiguration message and rejecting the SL DRX configuration may comprises continuing to decode the rest of the RRCReconfiguration message without triggering the radio link failure or the RRC reestablishment procedure in response to determining that the first wireless device is unable to comply with the SL DRX configuration. In some embodiments, the SL DRX configuration may be received from a second wireless device. [0045] In some embodiments, the first method may comprise transmitting a message to the second wireless device indicating that the SL DRX configuration was rejected by the first wireless device. In some embodiments, the message transmitted to the second wireless device may comprise a flag set to a value that indicates that the SL DRX configuration is rejected by the first wireless device, or a binary value that indicates that the SL DRX configuration is rejected by the first wireless device. [0046] In some embodiments, the SL DRX configuration may be received in a message that includes additional configurations, and the first method may comprise applying the additional configurations. In some embodiments, the additional configurations may comprise any configuration other than the SL DRX configuration. For example, in some embodiments, the additional configurations may comprise any one or more of an SL reset configuration (“sl- ResetConfig”), an SL measurement configuration (“sl-MeasConfig”), an SL channel state information (CSI) reference signal (RS) configuration (“sl-CSI-RS-Config”), a latency bound of an SL CSI report (“sl-LatencyBoundCSI-Report”), an SL DRX configuration for unicast communication (“sl-DRX-ConfigUC-PC5”), and a latency bound of an SL Inter-UE coordination (IUC) report (“sl-LatencyBoundIUC-Report”). In some embodiments, the message may be an RRC configuration message, such as an RRC reconfiguration SL (“RRCReconfigurationSidelink”) message. In some of these embodiments, the additional configurations may comprise any configuration that the RRC configuration message (e.g. “RRCReconfigurationSidelink” message) comprises, aside from the SL DRX configuration. [0047] In some embodiments, the first method may comprise transmitting a response message to the second wireless device indicating that the additional configurations were applied by the first wireless device. In some embodiments, the first method may comprise storing the SL DRX configuration at the first wireless device. [0048] In some embodiments, the entity may be a second wireless device. In some of these embodiments, the first method may comprise using the SL DRX configuration, transmitting a message to the second wireless device indicating that the SL DRX configuration has been used, and after transmitting the message, performing DRX on an SL interface in accordance with the SL DRX configuration. In some embodiments, the first method may comprise discarding the SL DRX configuration. [0049] In one embodiment, upon receiving an RRC message that includes an SL DRX configuration, and upon deciding that the received SL DRX configuration is rejected, the RX UE does not trigger reconfiguration failure or RRC reestablishment but may apply all the other configurations received except the received SL DRX configuration. In this case, the RX UE may or may not inform the TX UE that the SL DRX configuration has been not applied (or been rejected) and may or may not also inform the TX UE that the other configurations received in the RRC message have been applied. [0050] In another embodiment, upon receiving an RRC message that includes an SL DRX configuration, and upon deciding that the received SL DRX configuration is rejected, the RX UE may apply all the received configurations, including the SL DRX, but the RX UE does not use the received SL DRX. This means that the RX UE has the SL DRX configuration stored in its memory but is not going to use it. The entity (e.g. network/network node and/or the TX UE) may or may not be notified that the SL DRX is not used. In case the RX UE decides to use the SL DRX configuration that it has stored in its memory at a later time, the RX UE can send an indication to the TX UE or the entity (e.g. network/network node and/or the TX UE) that the SL DRX configuration is activated or enabled. [0051] Figure 3 illustrates a second method in accordance with an aspect of the disclosure. The second method is performed by a first wireless device (RX UE). As illustrated by block 602 of Figure 3, the second method comprises transmitting an indication to an entity in response to rejecting an SL DRX configuration received from the entity for performing DRX of transmissions over an SL interface. The SL DRX configuration is rejected without triggering a radio link failure or RRC reestablishment procedure and the indication is an indication that the SL DRX configuration was rejected by the RX UE without triggering the radio link failure or RRC reestablishment procedure. [0052] Figure 4 illustrates a third method in accordance with an aspect of the disclosure. The third method is performed by an entity in response to transmitting an SL DRX configuration to a first wireless device (RX UE). As illustrated by block 702 of Figure 4, the third method comprises receiving, from the RX UE, an indication that the SL DRX configuration was rejected by the RX UE without triggering a radio link failure or RRC reestablishment procedure. The SL DRX configuration is for performing DRX of transmissions over an SL interface. [0053] In some embodiments, the entity may be a second wireless device (TX UE), and the SL DRX configuration may be transmitted over the SL interface. In some embodiments, the SL DRX configuration may be transmitted to the first wireless device in an RRC configuration message. In some embodiments, the RRC configuration message may include an additional configuration for the first wireless device and the response may indicate that the additional configuration was applied by the first wireless device. [0054] In some embodiments, the third method may comprise transmitting a message to a network node indicating that the SL DRX configuration was rejected by the first wireless device. In some embodiments, the message transmitted to the network node may comprise a flag set to a value that indicates that the SL DRX configuration is rejected by the first wireless device, or a binary value that indicates that the SL DRX configuration is rejected by the first wireless device. [0055] In some embodiments, the third method may comprise receiving a message from the first wireless device indicating that the SL DRX configuration is accepted by the first wireless device. In some embodiments, the third method may comprise, in response to receiving the message from the first wireless device indicating that the SL DRX configuration is accepted by the first wireless device, transmitting communications over the SL interface in accordance with the SL DRX configuration. [0056] In some embodiments, the entity can be a network node, and the method may comprises preparing the SL DRX configuration to be applied by the RX UE over the SL interface with a second wireless device (TX UE). [0057] In some embodiments, the third method may comprise, after receiving the indication, receiving a message from the TX UE that the SL DRX configuration is being applied by the RX UE. In some embodiments, the third method may comprise, in response to receiving the indication, triggering an RRC reconfiguration of the sidelink interface. In some embodiments, the third method may comprise, in response to receiving the indication, triggering an RRC release of the RX UE. [0058] The methods described herein can be useful in a variety of use cases. For example, the methods can be for rejecting part of an RRC reconfiguration by a sidelink wireless device. Any wireless device referred to herein may be, for example, a user equipment (UE). Any references to a network herein can refer to, for example, a network node and thus these terms can be interchangeable. [0059] Some embodiments described herein refer to the NR radio access technology (RAT) but can be applied also to LTE RAT and any other RAT enabling the direct transmission between two (or more) nearby devices. [0060] The term “sidelink relay” can refer to a communication that is generated by a remote UE and is terminated at a gNB (or another destination remote UE) via the use of an intermediate node, referred to as a relay UE. [0061] In some embodiments, an SL DRX configuration (that is generated by an entity, e.g. the network or by the TX UE) is received by the RX UE within an RRC message that is received from the TX UE. In this case, the RX UE decides to reject the SL DRX configuration but in doing this it should avoid triggering a radio link failure or RRC reestablishment procedure. The TX UE is the UE that is the source of the traffic (i.e., the transmitter) and the RX UE is the UE that is the recipient of the traffic (i.e., the receiver). [0062] In a first embodiment (which is referred to herein as “Embodiment 1”), the UE may apply all the received configurations except the SL DRX configuration. [0063] In one embodiment, upon receiving an RRC message that includes an SL DRX configuration and deciding that the received SL DRX configuration is rejected, the RX UE does not trigger a radio link failure or RRC reestablishment but may apply all the other configurations received except the received SL DRX configuration. The SL DRX configuration may have been generated by the TX UE itself or by the serving cell of the TX UE. [0064] In another embodiment, if the RX UE did not apply the received SL DRX configuration but applies all other received configurations, the RX UE may decide to send, or not to send, an indication to inform the TX UE. Thus, in some embodiments, the TX UE may receive the indication from the RX UE. If the RX UE decides to inform the TX UE that the RX UE has not applied the received SL DR configuration, then the TX UE may also send an indication to inform the network that the RX UE has applied all the received configuration other than the SL DRX configuration. Thus, in some embodiments, the network may receive the indication from the TX UE. [0065] In one example, the indication may be a flag set to “true” or “false”, where “true” means that the SL DRX configuration have been correctly received and applied and “false” means that the UE did not apply the SL DRX configuration (or vice versa). In another example, the indication may be a binary value set to “1” or “0”, where “1” means that the SL DRX configuration have been correctly received and applied and “0” means that the UE did not apply the SL DRX configuration (or vice versa). In another example, the indication can just be a flag that is present/signaled only if the SL DRX configuration has been correctly received and applied. [0066] Upon receiving an indication from the RX UE (e.g. via the TX UE) that it did not apply the SL DRX configuration, the network may trigger a new RRC reconfiguration procedure (e.g., both Uu and SL transmission may be reconfigured). In some embodiments, upon receiving the indication from the RX UE that SL DRX configuration was not applied, the network may trigger an RRC release procedure to send the UE into an RRC_IDLE or RRC_INACTIVE mode. [0067] In some embodiments, upon receiving the indication from the RX UE that it did not apply the SL DRX configuration, the network may maintain the Uu RRC connection with the TX UE, but may release the SL DRX configuration that the RX UE did not apply from the UE context (TX UE). Further, in another embodiment, upon receiving the indication from the RX UE, that the RX UE did not apply the SL DRX configuration, the network may perform no actions. [0068] In another embodiment, upon receiving an RRC message that includes an SL DRX configuration and upon deciding that the received SL DRX configuration is rejected, the RX UE may trigger a radio link failure procedure only for the PC5 link between the RX UE and TX UE. This means that the RX UE may send an indication that the sidelink related part of the RRC message received has failed (i.e., because the SL DRX has been rejected) but that the Uu related part of the RRC message is still operable. Thus, in some embodiments, the TX UE may receive this indication from the RX UE. Therefore, the network may release the PC5 link between the TX UE and RX UE but still maintain the Uu link between the network and the TX UE. [0069] Some modifications of 3GPP TS 38.331 to implement the solutions of Embodiment 1 are shown in Appendix A. [0070] In a second embodiment (which is referred to herein as “Embodiment 2”), the UE may apply the SL DRX configuration but decides to not use it. [0071] In one embodiment, upon receiving an RRC message that includes an SL DRX configuration and upon deciding that the received SL DRX configuration is rejected, the RX UE may apply all the received configurations, including the SL DRX, but the RX UE does not use the received SL DRX. That is, the RX UE may store the SL DRX configuration stored in memory but does not use it. In that case, the RX UE receiver and transmitter are always “ON”. Since the RX UE applies the received RRC configurations, the network (or the TX UE) may or may not be notified by the RX UE that the SL DRX is applied but not used. [0072] In another embodiment, in case the RX UE decides to inform the TX UE or the network that the SL DRX has been stored in the memory but not used, the RX UE can send an indication to the TX UE or the network that the SL DRX configuration is “activated” or “enabled” (or “deactivated” or “disabled”). Thus, in some embodiments, the TX UE or the network may receive this indication from the RX UE. [0073] In an example, the indication may be a flag set to “true” or “false”, where “true” means that the SL DRX configuration is applied and enabled and “false” means that the SL DRX configuration is applied and disabled (or vice versa). In another example, the indication may be a binary value set to “1” or “0”, where “1” means that the SL DRX configuration is applied and enabled and “0” means that the SL DRX configuration is applied and disabled (or vice versa). In another example, the indication can just be a flag that is present/signaled only if the SL DRX configuration have been correctly applied and is enabled (or disabled). [0074] In some embodiments, if the RX UE decides to change the status of the SL DRX configuration (e.g., from “enabled” to “disabled” or vice versa), the RX UE may send a new indication to the TX UE or to the network (via the TX UE) to inform that the status of the SL DRX configuration has changed. Thus, in some embodiments, the TX UE may receive this indication from the RX UE. [0075] In another embodiment, upon receiving the indication from the RX UE that the SL DRX configuration has been applied and is disabled, the network may trigger an RRC re- establishment procedure (e.g., both Uu and SL transmission may be dropped and re-established). In further embodiments, upon receiving the indication from the RX UE that the SL DRX configuration has been applied and is disabled, the network may trigger an RRC release procedure to send the UE into an RRC_IDLE or RRC_INACTIVE mode. [0076] In some embodiments, upon receiving the indication from the RX UE that the SL DRX configuration has been applied and is disabled, the network may maintain the Uu RRC connection with the TX UE but may release the SL DRX configuration that the RX UE has applied but is disabled from the UE context (TX UE). In further embodiments, upon receiving the indication from the UE that the SL DRX configuration has been applied and is disabled, the network may perform no actions. [0077] Some modifications of 3GPP TS 38.331 to implement the solutions of Embodiment 2 are shown in Appendix B. [0078] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. [0079] Figure 5 shows one embodiment of the present disclosure. A network node 101 may send a message 107 including an SL DRX configuration to a TX UE 103. Thus, in some embodiments, the TX UE 103 may receive the message 107 including the SL DRX configuration from the network node 101. The SL DRX configuration is to be applied by an RX UE 105 that has a sidelink interface with the TX UE 103. The TX UE 103 may transmit the SL DRX configuration to the RX UE 105 in an (e.g. RRC) message 109. Thus, in some embodiments, the RX UE may receive the message 109 including the SL DRX configuration from the TX UE. Upon receiving the (e.g. RRC) message 109 that includes the SL DRX configuration, the RX UE 105 determines that the received SL DRX configuration is rejected (block 111 of Figure 5). The RX UE 105 does not trigger a radio link failure or RRC reestablishment in response to rejection of the SL DRX configuration, but may apply all the other configurations received except the received SL DRX configuration (block 113 of Figure 5). In some embodiments, the SL DRX configuration may be generated by the TX UE 103 rather than being received from the network node 101 serving the TX UE 103. [0080] Figure 6 illustrates further embodiments. As shown therein, a network node 201 may send a message 207 including an SL DRX configuration to a TX UE 203. Thus, in some embodiments, the TX UE 203 may receive the message 207 including the SL DRX configuration from the network node 201. The SL DRX configuration is to be applied by an RX UE 205 that has a sidelink interface with the TX UE 203. The TX UE 203 may transmit the SL DRX configuration to the RX UE 205 in an (e.g. RRC) message 209. Thus, in some embodiments, the RX UE 205 may receive the message 209 including the SL DRX configuration from the TX UE 203. At block 211 of Figure 6, the RX UE 205 determines that the SL DRX configuration is rejected and not applied, but may apply the other received configurations at block 213 of Figure 6. The RX UE 205 may then send an indication 215 to the TX UE 203 that the SL DRX configuration was not applied. Thus, in some embodiments, the TX UE 203 may receive the indication 215 from the RX UE 205. In addition, the TX UE 203 may also optionally send an indication 217 to the network 201 indicating that the SL DRX configuration was not applied by the RX UE 205. Thus, in some embodiments, the network 201 may receive the indication 217 from the TX UE 203. [0081] In some embodiments the indication 215 or the indication 217 may be a flag set to “true” or “false”, where “true” means that the SL DRX configuration has been correctly received and applied and “false” means that the UE did not apply the SL DRX configuration, or vice versa. In some embodiments the indication 215 or the indication 217 may be a binary value set to “1” or “0”, where “1” means that the SL DRX configuration has been correctly received and applied and “0” means that the UE did not apply the SL DRX configuration, or vice versa. In some embodiments the indication 215 or the indication 217 may be a flag that is present or signaled only if the SL DRX configuration has been correctly received and applied. [0082] In another embodiment, upon receiving the indication 217 that the RX UE 205 did not apply the SL DRX configuration, the network 201 may trigger a new RRC reconfiguration procedure (e.g., both Uu and SL transmission may be reconfigured). In another embodiment, upon receiving the indication 217 that the RX UE 205 did not apply the SL DRX configuration, the network 201 may trigger an RRC release to send the UE into an RRC_IDLE or RRC_INACTIVE. [0083] In another embodiment, upon receiving the indication 217 that the RX UE 205 did not apply the SL DRX configuration, the network 201 may maintain the Uu RRC connection with the TX UE 203, but it may release from the UE context (TX UE 203) the SL DRX configuration that the RX UE 205 did not apply. Further, in another embodiment, upon receiving the indication 217 that the RX UE 205 did not apply the SL DRX configuration, the network 201 may perform no actions. [0084] In another embodiment, upon receiving an (e.g. RRC) message that includes an SL DRX configuration 209 and upon rejecting the received SL DRX configuration 211, the RX UE 205 may trigger a failure procedure only for the PC5 link between the RX UE 205 and TX UE 203. In this embodiment, the RX UE 205 may send an indication that the sidelink related part of the (e.g. RRC) message received 209 has been rejected but that the Uu related part of the (e.g. RRC) message has been applied. Therefore, the network 201 may release the PC5 link between the TX UE 203 and RX UE 205 but still maintain the Uu link between the network 201 and the RX UE 205. [0085] Figure 7 shows another embodiment of the present disclosure. As shown therein, a network node 301 may send a message 307 including an SL DRX configuration to a TX UE 303. Thus, in some embodiments, the TX UE 303 may receive the message 307 including the SL DRX configuration from the network node 301. The SL DRX configuration is to be applied by an RX UE 305 that has a sidelink interface with the TX UE 303. The TX UE 303 may transmit the SL DRX configuration to the RX UE 305 in an (e.g. RRC) message 309. Thus, in some embodiments, the RX UE 305 may receive the message 309 including the SL DRX configuration from the TX UE 303. At block 311 of Figure 7, the RX UE 305 may determine that the SL DRX configuration is applied but not used. That is, upon receiving the (e.g. RRC) message 309 that includes an SL DRX configuration, the RX UE 305 may apply all the received configurations including the SL DRX configuration. However, the RX UE 305 may not use the received SL DRX (see block 311 of Figure 7). The RX UE 305 may store the SL DRX configuration in its memory at block 313 of Figure 7 but may not use it. In this embodiment, the RX UE 305 may not trigger a reconfiguration failure or RRC reestablishment. The SL DRX configuration may be generated by the TX UE 303, or may be received by the network serving the TX UE 303. [0086] Figure 8 shows another embodiment. As shown therein, a network node 401 may send a message 407 including an SL DRX configuration to a TX UE 403. Thus, in some embodiments, the TX UE 403 may receive the message 407 including the SL DRX configuration from the network node 401. The SL DRX configuration is to be applied by an RX UE 405 that has a sidelink interface with the TX UE 403. The TX UE 403 may transmit the SL DRX configuration to the RX UE 405 in an (e.g. RRC) message 409. Thus, in some embodiments, the RX UE 405 may receive the message 409 including the SL DRX configuration from the TX UE 403. At block 411 of Figure 8, the RX UE 405 may determine that the SL DRX configuration is applied but not used. The RX UE 405 may store the SL DRX configuration in its memory at block 413 of Figure 8 but may not use it. The RX UE 405 may then send an indication 415 to the TX UE 403 that the received SL DRX configuration is not being used. Thus, in some embodiments, the TX UE 403 may receive this indication 415 from the RX UE 405. In addition, the TX UE 403 may also optionally send an indication 417 to the network 401 that the RX UE SL DRX configuration is not being used. Thus, in some embodiments, the network 401 may receive this indication 417 from the TX UE 403. [0087] Moreover, the RX UE 405 may optionally decide at a later time to use the received SL DRX configuration (block 419 of Figure 8). In this instance, the RX UE 405 may optionally send an indication 421 to the TX UE 403 that the received SL DRX configuration is being used. Thus, in some embodiments, the TX UE 403 may receive this indication 421 from the RX UE 405. In addition, the TX UE 403 may also optionally send an indication 423 to the network 401 that the SL DRX configuration is being used by the RX UE 405. Thus, in some embodiments, the network 401 may receive this indication 423 from the TX UE 403. [0088] In some embodiments the indications 215, 217, 415, 417, 421, or 423 may be a flag set to “true” or “false”, where “true” means that the SL DRX configuration has been correctly received, applied, and is being used and “false” means that the RX UE is not using the SL DRX configuration, or vice versa. In some embodiments the indications 215, 217, 415, 417, 421, or 423 may be a binary value set to “1” or “0”, where “1” means that the SL DRX configuration has been correctly received, applied, and is being used and “0” means that the RX UE is not using the SL DRX configuration, or vice versa. In some embodiments the indications 215, 217, 415, 417, 421, or 423 may be a flag that is present or signaled only if the SL DRX configuration has been correctly received, applied, and is being used. [0089] In another embodiment, upon receiving the indication 417 that the RX UE 405 is not using the SL DRX configuration, the network 401 may trigger a new RRC reconfiguration procedure (e.g., both Uu and SL transmission may be reconfigured). In another embodiment, upon receiving the indication 417 that the RX UE 405 did not apply the SL DRX configuration, the network 401 may trigger an RRC release to send the UE into an RRC_IDLE or RRC_INACTIVE. [0090] In another embodiment, upon receiving the indication 417 that the RX UE 405 is not using the SL DRX configuration, the network 401 may maintains the Uu RRC connection with the TX UE 403, but it may release from the UE context (TX UE 403) the SL DRX configuration that the RX UE 405 is not using. Further, in another embodiment, upon receiving the indication 417 that the RX UE 405 did not apply the SL DRX configuration, the network 401 may perform no actions. [0091] There is also provided a method performed by a system. The method performed by the system can comprise any one or more of the methods described herein, such as the first method and/or the second method described earlier, and the third method described earlier. [0092] There is also provided a first wireless device. The first wireless device is configured to operate in accordance with any of the methods described herein in respect of the first wireless device (RX UE), such as the first method and/or the second method described earlier. [0093] There is also provided an entity. The entity is configured to operate in accordance with any of the methods described herein in respect of the entity (e.g. the second wireless device (TX UE) or the network node), such as the third method described earlier. [0094] There is also provided a system comprising the first wireless device described herein and the entity described herein. [0095] There is also provided a computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform any one or more of the methods described herein, such as the first method, the second method, and/or the third method described earlier. [0096] There is also provided a computer program embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform any one or more of the methods described herein, such as the first method, the second method, and/or the third method described earlier. [0097] Figure 9 shows an example of a communication system 900 in accordance with some embodiments. [0098] In the example, the communication system 900 includes a telecommunications network 902 that includes an access network 904, such as a radio access network (RAN), and a core network 906, which includes one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as network nodes 910a and 910b (one or more of which may be generally referred to as network nodes 910), or any other similar third Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 910 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 912a, 912b, 912c, and 912d (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections. [0099] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 900 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 900 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0100] The UEs 912 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 910 and other communication devices. Similarly, the network nodes 910 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 912 and/or with other network nodes or equipment in the telecommunications network 902 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunications network 902. [0101] In the depicted example, the core network 906 connects the network nodes 910 to one or more hosts, such as host 916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 906 includes one more core network nodes (e.g., core network node 908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 908. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0102] The host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and/or the telecommunications network 902, and may be operated by the service provider or on behalf of the service provider. The host 916 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0103] As a whole, the communication system 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G) standards, or any applicable future generation standard (e.g., sixth generation (6G)); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC), ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. [0104] In some examples, the telecommunications network 902 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 902. For example, the telecommunications network 902 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive internet of things (IoT) services to yet further UEs. [0105] In some examples, the UEs 912 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904. Additionally, a UE may be configured for operating in single- or multi- radio access technology (RAT) or multi- standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) New Radio - Dual Connectivity (EN-DC). [0106] In the example illustrated in Figure 9, the hub 914 can communicate with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912c and/or 912d) and network nodes (e.g., network node 910b). In some examples, the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 914 may be a broadband router enabling access to the core network 906 for the UEs. As another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 910, or by executable code, script, process, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 914 may be a content source. For example, for a UE that is a virtual reality (VR) headset, display, loudspeaker or other media delivery device, the hub 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 914 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [0107] The hub 914 may have a constant/persistent or intermittent connection to the network node 910b. The hub 914 may also allow for a different communication scheme and/or schedule between the hub 914 and UEs (e.g., UE 912c and/or 912d), and between the hub 914 and the core network 906. In other examples, the hub 914 is connected to the core network 906 and/or one or more UEs via a wired connection. Moreover, the hub 914 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 904 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection. In some embodiments, the hub 914 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 910b. In other embodiments, the hub 914 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 910b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0108] Figure 10 shows a UE 1000 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. As such, a UE can be referred to herein as a wireless device and vice-versa. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the third Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0109] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, or vehicle-to-everything (V2X) communication. In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [0110] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a power source 1008, a memory 1010, a communication interface 1012, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [0111] The processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1010. The processing circuitry 1002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1002 may include multiple central processing units (CPUs). [0112] In the example, the input/output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0113] In some embodiments, the power source 1008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1008 may further include power circuitry for delivering power from the power source 1008 itself, and/or an external power source, to the various parts of the UE 1000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1008. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied. [0114] The memory 1010 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read- only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016. The memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems. [0115] The memory 1010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a universal SIM (USIM) and/or internet protocol (IP) multimedia SIM (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1010 may allow the UE 1000 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1010, which may be or comprise a device-readable storage medium. [0116] The processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012. The communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1018 and/or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., antenna 1022) and may share circuit components, software or firmware, or alternatively be implemented separately. [0117] In the illustrated embodiment of Figure 10, communication functions of the communication interface 1012 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol (UDP) Internet Connections (QUIC), Hypertext Transfer Protocol (HTTP), and so forth. [0118] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0119] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. [0120] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television (TV), a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1000 shown in Figure 10. [0121] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0122] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [0123] Figure 11 shows a network node 1100 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). [0124] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). [0125] Other examples of network nodes include multiple transmission point (multi- TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). [0126] The network node 1100 includes a processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108. The network node 1100 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1100 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1100. [0127] The processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1100 components, such as the memory 1104, to provide network node 1100 functionality. [0128] In some embodiments, the processing circuitry 1102 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1102 includes one or more of radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, the radio frequency (RF) transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1112 and baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units. [0129] The memory 1104 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1102. The memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1102 and utilized by the network node 1100. The memory 1104 may be used to store any calculations made by the processing circuitry 1102 and/or any data received via the communication interface 1106. In some embodiments, the processing circuitry 1102 and memory 1104 is integrated. [0130] The communication interface 1106 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1106 comprises port(s)/terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection. The communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. Radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122. The radio front-end circuitry 1118 may be connected to an antenna 1110 and processing circuitry 1102. The radio front-end circuitry may be configured to condition signals communicated between antenna 1110 and processing circuitry 1102. The radio front-end circuitry 1118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1120 and/or amplifiers 1122. The radio signal may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0131] In certain alternative embodiments, the network node 1100 does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown). [0132] The antenna 1110 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port. [0133] The antenna 1110, communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and/or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [0134] The power source 1108 provides power to the various components of network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein. For example, the network node 1100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108. As a further example, the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [0135] Embodiments of the network node 1100 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100. [0136] Figure 12 is a block diagram of a host 1200, which may be an embodiment of the host 916 of Figure 9, in accordance with various aspects described herein. As used herein, the host 1200 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1200 may provide one or more services to one or more UEs. [0137] The host 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a network interface 1208, a power source 1210, and a memory 1212. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 11, such that the descriptions thereof are generally applicable to the corresponding components of host 1200. [0138] The memory 1212 may include one or more computer programs including one or more host application programs 1214 and data 1216, which may include user data, e.g., data generated by a UE for the host 1200 or data generated by the host 1200 for a UE. Embodiments of the host 1200 may utilize only a subset or all of the components shown. The host application programs 1214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), moving picture experts group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1200 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [0139] Figure 13 is a block diagram illustrating a virtualization environment 1300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1300 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. [0140] Applications 1302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1300 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [0141] Hardware 1304 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1306 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1308a and 1308b (one or more of which may be generally referred to as VMs 1308), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1306 may present a virtual operating platform that appears like networking hardware to the VMs 1308. [0142] The VMs 1308 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1306. Different embodiments of the instance of a virtual appliance 1302 may be implemented on one or more of VMs 1308, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [0143] In the context of NFV, a VM 1308 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1308, and that part of hardware 1304 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1308 on top of the hardware 1304 and corresponds to the application 1302. [0144] Hardware 1304 may be implemented in a standalone network node with generic or specific components. Hardware 1304 may implement some functions via virtualization. Alternatively, hardware 1304 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1310, which, among others, oversees lifecycle management of applications 1302. In some embodiments, hardware 1304 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1312 which may alternatively be used for communication between hardware nodes and radio units. [0145] Figure 14 shows a communication diagram of a host 1402 communicating via a network node 1404 with a UE 1406 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 912a of Figure 9 and/or UE 1000 of Figure 10), network node (such as network node 910a of Figure 9 and/or network node 1100 of Figure 11), and host (such as host 916 of Figure 9 and/or host 1200 of Figure 12) discussed in the preceding paragraphs will now be described with reference to Figure 14. [0146] Like host 1200, embodiments of host 1402 include hardware, such as a communication interface, processing circuitry, and memory. The host 1402 also includes software, which is stored in or accessible by the host 1402 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1406 connecting via an over-the-top (OTT) connection 1450 extending between the UE 1406 and host 1402. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1450. [0147] The network node 1404 includes hardware enabling it to communicate with the host 1402 and UE 1406. The connection 1460 may be direct or pass through a core network (like core network 906 of Figure 9) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0148] The UE 1406 includes hardware and software, which is stored in or accessible by UE 1406 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1406 with the support of the host 1402. In the host 1402, an executing host application may communicate with the executing client application via the OTT connection 1450 terminating at the UE 1406 and host 1402. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1450 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1450. [0149] The OTT connection 1450 may extend via a connection 1460 between the host 1402 and the network node 1404 and via a wireless connection 1470 between the network node 1404 and the UE 1406 to provide the connection between the host 1402 and the UE 1406. The connection 1460 and wireless connection 1470, over which the OTT connection 1450 may be provided, have been drawn abstractly to illustrate the communication between the host 1402 and the UE 1406 via the network node 1404, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0150] As an example of transmitting data via the OTT connection 1450, in step 1408, the host 1402 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1406. In other embodiments, the user data is associated with a UE 1406 that shares data with the host 1402 without explicit human interaction. In step 1410, the host 1402 initiates a transmission carrying the user data towards the UE 1406. The host 1402 may initiate the transmission responsive to a request transmitted by the UE 1406. The request may be caused by human interaction with the UE 1406 or by operation of the client application executing on the UE 1406. The transmission may pass via the network node 1404, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1412, the network node 1404 transmits to the UE 1406 the user data that was carried in the transmission that the host 1402 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1414, the UE 1406 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1406 associated with the host application executed by the host 1402. [0151] In some examples, the UE 1406 executes a client application which provides user data to the host 1402. The user data may be provided in reaction or response to the data received from the host 1402. Accordingly, in step 1416, the UE 1406 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1406. Regardless of the specific manner in which the user data was provided, the UE 1406 initiates, in step 1418, transmission of the user data towards the host 1402 via the network node 1404. In step 1420, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1404 receives user data from the UE 1406 and initiates transmission of the received user data towards the host 1402. In step 1422, the host 1402 receives the user data carried in the transmission initiated by the UE 1406. [0152] One or more of the various embodiments improve the performance of OTT services provided to the UE 1406 using the OTT connection 1450, in which the wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve the connectivity interruption, signaling overhead, latency, and power consumption and thereby provide benefits such as reduced user waiting time, better responsiveness, and extended battery lifetime. [0153] In an example scenario, factory status information may be collected and analyzed by the host 1402. As another example, the host 1402 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1402 may store surveillance video uploaded by a UE. As another example, the host 1402 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1402 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. [0154] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1450 between the host 1402 and UE 1406, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1402 and/or UE 1406. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1450 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1450 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1404. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1402. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1450 while monitoring propagation times, errors, etc. [0155] Other embodiments of the present disclosure are defined in the following numbered statements: Statement 1. A method performed by a wireless device (RX UE), comprising: receiving a sidelink, SL, discontinuous reception, DRX, configuration for performing DRX of transmissions over a SL interface; and rejecting the SL DRX configuration without triggering a radio link failure or radio resource control, RRC, reestablishment procedure. Statement 2. The method of Statement 1, wherein rejecting the SL DRX configuration comprises not applying the SL DRX configuration. Statement 3. The method of Statement 2, wherein the SL DRX configuration is received in a RRCReconfiguration message and rejecting the SL DRX configuration comprises continuing to decode the rest of the RRCReconfiguration message without triggering the radio link failure or the RRC reestablishment procedure in response to determining that the wireless device is unable to comply with the SL DRX configuration. Statement 4. The method of Statement 1, wherein the wireless device comprises a first wireless device and the SL DRX configuration is received from a second wireless device. Statement 5. The method of Statement 4, further comprising transmitting a message to the second wireless device indicating that the SL DRX configuration was not activated by the first wireless device. Statement 6. The method of Statement 5, wherein the message transmitted to the second wireless device comprises a flag set to value that indicates that the SL DRX configuration is not being activated by the first wireless device. Statement 7. The method of Statement 5, wherein the message transmitted to the second wireless device comprises a binary value that indicates that the SL DRX configuration is not being activated by the first wireless device. Statement 8. The method of Statement 4, wherein the SL DRX configuration is received in a message that includes additional configurations, the method further comprising applying the additional configurations. Statement 9. The method of Statement 8, wherein the message comprises an RRC configuration message. Statement 10. The method of Statement 9, further comprising transmitting a response message to the second wireless device indicating that the additional configurations were applied by the first wireless device. Statement 11. The method of Statement 1, further comprising storing the SL DRX configuration at the wireless device. Statement 12. The method of Statement 11, wherein the wireless device comprises a first wireless device and the SL DRX configuration is received from a second wireless device, the method further comprising: activating the SL DRX configuration; transmitting a message to the second wireless device indicating that the SL DRX configuration has been activated; and after transmitting the message, performing DRX on a SL interface in accordance with the SL DRX configuration. Statement 13. The method of Statement 1, further comprising discarding the SL DRX configuration. Statement 14. A method performed by a second wireless device (TX UE), comprising: transmitting, over a sidelink, SL interface, a SL discontinuous reception, DRX, configuration to a first wireless device for performing DRX of transmissions over the SL interface; and in response to transmitting the SL DRX configuration, receiving a response from the first wireless device indicating that the SL DRX configuration was rejected or not activated by the first wireless device. Statement 15. The method of Statement 14, wherein the SL DRX message is transmitted to the first wireless device in a radio resource control, RRC, configuration message. Statement 16. The method of Statement 15, wherein the wherein the RRC configuration message includes an additional configuration for the first wireless device, and wherein the response indicates that the additional configuration was applied by the first wireless device. Statement 17. The method of Statement 14, further comprising transmitting a message to a network node indicating that the SL DRX configuration was not enabled by the first wireless device. Statement 18. The method of Statement 17, wherein the message transmitted to the network node comprises a flag set to a value that indicates that the SL DRX configuration is not being activated by the first wireless device. Statement 19. The method of Statement 17, wherein the message transmitted to the network node comprises a binary value that indicates that the SL DRX configuration is not being activated by the first wireless device. Statement 20. The method of Statement 14, further comprising receiving a message from the first wireless device indicating that the SL DRX configuration is being activated by the first wireless device. Statement 21. The method of Statement 20, further comprising: in response to receiving the message from the first wireless device indicating that the SL DRX configuration is being activated by the first wireless device, transmitting communications over the SL interface in accordance with the SL DRX configuration. Statement 22. A wireless device configured to perform operations according to any of Statements 1 to 21. Statement 23. A wireless device comprising: a processing circuit; a wireless transceiver coupled to the processing circuit; and a memory coupled to the processing circuit and comprising computer readable instructions that, when executed by the processing circuit, cause the wireless device to perform operations according to any of Statements 1 to 21. Statement 24. A method of operating a network node, comprising: preparing a sidelink, SL, discontinuous reception, DRX, configuration to be applied by a first wireless device, RX UE, over a sidelink interface with a second wireless device, TX UE; transmitting the SL DRX configuration to the TX UE; and receiving an indication from the TX UE that the SL DRX configuration was not applied by the RX UE without triggering a radio link failure or radio resource control, RRC, reconfiguration. Statement 25. The method of Statement 24, further comprising, after receiving the indication, receiving a message from the TX UE that the SL DRX configuration is being applied by the RX UE. Statement 26. The method of Statement 24, further comprising: in response to receiving the indication, triggering an RRC reconfiguration of the sidelink interface. Statement 27. The method of Statement 24, further comprising: in response to receiving the indication, triggering an RRC release of the RX UE. Statement 28. A network node configured to perform operations according to any of Statements 25 to 27. Statement 29. A network node comprising: a processing circuit; a wireless transceiver coupled to the processing circuit; and a memory coupled to the processing circuit and comprising computer readable instructions that, when executed by the processing circuit, cause the network node to perform operations according to any of Statements 25 to 27. [0156] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [0157] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally. [0158] It should be noted that the above-mentioned embodiments illustrate rather than limit the idea, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.

APPENDIX A 5.3.5.8.2 Inability to comply with RRCReconfiguration NOTE 00: The UE behaviour specified in this clause does not apply to the fields in ServingCellConfigCommon that are defined in release-16 and later. The UE ignores, i.e. does not take an action on and does not store, the fields that it does not support or does not comprehend. The UE shall: 1> if the UE is in (NG)EN-DC: 2> if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB3; 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> if MCG transmission is not suspended: 4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends; 3> else: 4> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7, upon which the connection reconfiguration procedure ends; 2> else, if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB1; 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7, upon which the connection reconfiguration procedure ends. 1> else if RRCReconfiguration is received via NR (i.e., NR standalone, NE-DC, or NR-DC): 2> if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB3; NOTE 0: This case does not apply in NE-DC. 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> if MCG transmission is not suspended: 4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends; 3> else: 4> initiate the connection re-establishment procedure as specified in clause 5.3.7, upon which the connection reconfiguration procedure ends; 2> else if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over the SRB1 or if the upper layers indicate that the nas-Container is invalid: NOTE 0a: The compliance also covers the SCG configuration carried within octet strings e.g. field mrdc-SecondaryCellGroupConfig. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded SCG configuration or with the combination of (parts of) the MCG and SCG configurations. NOTE 0b: The compliance also covers the V2X sidelink configuration carried within an octet string, e.g. field sl-ConfigDedicatedEUTRA. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded V2X sidelink configuration. 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else if the RRCReconfiguration message includes the field sl-DRX-Config-r17 and the UE is unable to comply with (part of) the received SL DRX configuration: 4> continue decoding the rest of RRCReconfiguration message; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> if AS security has not been activated: 4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'other' 3> else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB, SRB2, have not been setup: 4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'; 3> else: 4> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the reconfiguration procedure ends; 1> else if RRCReconfiguration is received via other RAT (Handover to NR failure): 2> if the UE is unable to comply with any part of the configuration included in the RRCReconfiguration message or if the upper layers indicate that the nas-Container is invalid: 3> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT. NOTE 1: The UE may apply above failure handling also in case the RRCReconfiguration message causes a protocol error for which the generic error handling as defined in clause 10 specifies that the UE shall ignore the message. NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/failure, except for when the UE is unable to comply with (part of) the sl-DRX-Config-r17. NOTE 3: It is up to UE implementation whether the compliance check for an RRCReconfiguration received as part of ConditionalReconfiguration is performed upon the reception of the message or upon CHO, CPA and CPC execution (when the message is required to be applied). ------------------- 5.8.9.1.3 Reception of an RRCReconfigurationSidelink by the UE The UE shall perform the following actions upon reception of the RRCReconfigurationSidelink: 1> if the RRCReconfigurationSidelink includes the sl-ResetConfig: 2> perform the sidelink reset configuration procedure as specified in 5.8.9.1.10; 1> if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList: 2> for each SLRB-PC5-ConfigIndex value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration; 3> perform the sidelink DRB release procedure, according to clause 5.8.9.1a.1; 1> if the RRCReconfigurationSidelink includes the slrb-ConfigToAddModList: 2> for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is not part of the current UE sidelink configuration: 3> if sl-MappedQoS-FlowsToAddList is included: 4> apply the SL-PQFI included in sl-MappedQoS-FlowsToAddList; 3> perform the sidelink DRB addition procedure, according to clause 5.8.9.1a.2; 2> for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is part of the current UE sidelink configuration: 3> if sl-MappedQoS-FlowsToAddList is included: 4> add the SL-PQFI included in sl-MappedQoS-FlowsToAddList to the corresponding sidelink DRB; 3> if sl-MappedQoS-FlowsToReleaseList is included: 4> remove the SL-PQFI included in sl-MappedQoS-FlowsToReleaseList from the corresponding sidelink DRB; 3> if the sidelink DRB release conditions as described in clause 5.8.9.1a.1.1 are met: 4> perform the sidelink DRB release procedure according to clause 5.8.9.1a.1.2; 3> else if the sidelink DRB modification conditions as described in clause 5.8.9.1a.2.1 are met: 4> perform the sidelink DRB modification procedure according to clause 5.8.9.1a.2.2; 1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig: 2> perform the sidelink measurement configuration procedure as specified in 5.8.10; 1> if the RRCReconfigurationSidelink message includes the sl-CSI-RS-Config: 2> apply the sidelink CSI-RS configuration; 1> if the RRCReconfigurationSidelink message includes the sl-LatencyBoundCSI-Report: 2> apply the configured sidelink CSI report latency bound; 1> if the UE is unable to comply with (part of) the configuration included in the RRCReconfigurationSidelink (i.e. sidelink RRC reconfiguration failure): 2> if the UE is not able to comply with (part of) the sl-DRX-Config-r17 (i.e., the UE reject the received SL DRX configuration); 3> continue deconding the rest of the received RRCReconfigurationSidelink message; ALTERNATIVE 1 3> set the content of the RRCReconfigurationCompleteSidelink message; 3> submit the RRCReconfigurationCompleteSidelink message to lower layer for transmission; ALTERNATIVE 1 3> set the content of the RRCReconfigurationFailureSidelink message; 3> submit the RRCReconfigurationFailureSidelink message to lower layer for transmission; NOTE X: If the UE received an RRCReconfigurationFailureSidelink due to the rejection of the SL DRX, the UE does not consider the RRC reconfiguration sidelink procedure as failed (i.e., the UE successfully applied the RRCReconfigurationSidelink message, except for the the field sl-DRX-Config-r17). 2> else 3> continue using the configuration used prior to the reception of the RRCReconfigurationSidelink message; 3> set the content of the RRCReconfigurationFailureSidelink message; 4> submit the RRCReconfigurationFailureSidelink message to lower layers for transmission; 1> else: 2> set the content of the RRCReconfigurationCompleteSidelink message; 3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission; NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure. 1> if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToReleaseList-PC5: 2> for each SL-RLC-ChannelID value included in the sl-RLC-ChannelToReleaseList-PC5 that is part of the current UE sidelink configuration; 3> perform the PC5 Relay RLC channel release procedure, according to clause 5.8.9.7.1; 1> if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToAddModList-PC5: 2> for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModList- PC5 that is not part of the current UE sidelink configuration: 3> perform the sidelink RLC channle addition procedure, according to clause 5.8.9.7.2; 2> for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModList- PC5 that is part of the current UE sidelink configuration: 3> perform the PC5 Relay RLC channel modification procedure according to clause 5.8.9.7.2;

APPENDIX B 5.3.5.3 Reception of an RRCReconfiguration by the UE The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO, CPA or CPC): 1> if the RRCReconfiguration was received neither within mrdc-SecondaryCellGroup nor within E-UTRA RRCConnectionReconfiguration nor within E-UTRA RRCConnectionResume: 2> if the RRCReconfiguration includes the scg-State: 3> perform SCG deactivation as specified in 5.3.5.13b; 2> else: 3> perform SCG activation as specified in 5.3.5.13a; Editor's note: FFS how to ensure that the notification to MAC is only processed at the time the SCG configuration is processed, if included. 1> if the RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: 2> remove all the entries within VarConditionalReconfig, if any; 1> if the RRCReconfiguration includes the daps-SourceRelease: 2> reset the source MAC and release the source MAC configuration; 2> for each DAPS bearer: 3> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell; 3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5]; 2> for each SRB: 3> release the PDCP entity for the source SpCell; 3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell; 2> release the physical channel configuration for the source SpCell; 2> discard the keys used in the source SpCell (the K_gNB key, the K_RRCenc key, the K_RRCint key, the K_UPint key and the K_UPenc key), if any; 1> if the RRCReconfiguration is received via other RAT (i.e., inter-RAT handover to NR): 2> if the RRCReconfiguration does not include the fullConfig and the UE is connected to 5GC (i.e., delta signalling during intra 5GC handover): 3> re-use the source RAT SDAP and PDCP configurations if available (i.e., current SDAP/PDCP configurations for all RBs from source E-UTRA RAT prior to the reception of the inter-RAT HO RRCReconfiguration message); 1> else: 2> if the RRCReconfiguration includes the fullConfig: 3> perform the full configuration procedure as specified in 5.3.5.11; 1> if the RRCReconfiguration includes the masterCellGroup: 2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5; 1> if the RRCReconfiguration includes the masterKeyUpdate: 2> perform AS security key update procedure as specified in 5.3.5.7; 1> if the RRCReconfiguration includes the sk-Counter: 2> perform security key update procedure as specified in 5.3.5.7; 1> if the RRCReconfiguration includes the secondaryCellGroup: 2> perform the cell group configuration for the SCG according to 5.3.5.5; 1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig: 2> if the mrdc-SecondaryCellGroupConfig is set to setup: 3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd: 4> perform MR-DC release as specified in clause 5.3.5.10; 3> if the received mrdc-SecondaryCellGroup is set to nr-SCG: 4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG; 3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG: 4> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra- SCG; 2> else (mrdc-SecondaryCellGroupConfig is set to release): 3> perform MR-DC release as specified in clause 5.3.5.10; 1> if the RRCReconfiguration message includes the radioBearerConfig: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCReconfiguration message includes the radioBearerConfig2: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCReconfiguration message includes the measConfig: 2> perform the measurement configuration procedure as specified in 5.5.2; 1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList: 2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed; 1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery: 2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2; NOTE 0: If this RRCReconfiguration is associated to the MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIB1-Delivery, the UE initiates (if needed) the request to acquire required SIBs, according to clause 5.2.2.3.5, only after the random access procedure towards the target SpCell is completed. 1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery: 2> perform the action upon reception of System Information as specified in 5.2.2.4; 1> if the RRCReconfiguration message includes the dedicatedPosSysInfoDelivery: 2> perform the action upon reception of the contained posSIB(s), as specified in clause 5.2.2.4.16; 1> if the RRCReconfiguration message includes the otherConfig: 2> perform the other configuration procedure as specified in 5.3.5.9; 1> if the RRCReconfiguration message includes the bap-Config: 2> perform the BAP configuration procedure as specified in 5.3.5.12; 1> if the RRCReconfiguration message includes the iab-IP-AddressConfigurationList: 2> if iab-IP-AddressToReleaseList is included: 3> perform release of IP address as specified in 5.3.5.12a.1.1; 2> if iab-IP-AddressToAddModList is included: 3> perform IAB IP address addition/update as specified in 5.3.5.12a.1.2; 1> if the RRCReconfiguration message includes the conditionalReconfiguration: 2> perform conditional reconfiguration as specified in 5.3.5.13; 1> if the RRCReconfiguration message includes the needForGapsConfigNR: 2> if needForGapsConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands; 1> if the RRCReconfiguration message includes the needForNCSG-ConfigNR: 2> if needForNCSG-ConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 1> if the RRCReconfiguration message includes the needForNCSG-ConfigEUTRA: 2> if needForNCSG-ConfigEUTRA is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 1> if the RRCReconfiguration message includes the sl-ConfigDedicatedNR: 2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14; NOTE 0a: If the sl-ConfigDedicatedNR was received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not build an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR. 1> if the RRCReconfiguration message includes the sl-L2RelayUEConfig: 2> perform the L2 U2N Relay UE configuration procedure as specified in 5.3.5.15; 1> if the RRCReconfiguration message includes the sl-L2RemoteUEConfig: 2> perform the L2 U2N Remote UE configuration procedure as specified in 5.3.5.16; 1> if the RRCReconfiguration message includes the dedicatedPagingDelivery: 2> if the ue-Identity included in the PagingRecord in the Paging message matches the UE identity in sl-PagingIdentity-RemoteUE in sl-PagingInfo-RemoteUE received in RemoteUEInformationSidelink message in accordance with 5.8.9.8.3: 3> inititate the Uu Message transfer in sidelink as specified in 5.8.9.9; 1> if the RRCReconfiguration message includes the sl-ConfigDedicatedEUTRA-Info: 2> perform related procedures for V2X sidelink communication in accordance with TS 36.331 [10], clause 5.3.10 and clause 5.5.2; 1> if the RRCReconfiguration message includes the ul-GapFR2-Config: 2> perform the FR2 UL gap configuration procedure as specified in 5.3.5.13c; 1> if the RRCReconfiguration message includes the musim-GapConfig: 2> for each periodic musim-GapID included in the received musim-GapToReleaseList: 3> release the MUSIM periodic gap associated to the musim-GapID from the musim- GapConfigList; 2> for each periodic musim-GapID included in the received musim-GapToAddModList: 3> if an entry with the matching musim-GapID exists in the musim-GapConfigList: 4> replace the entry with the value received for this musim-GapID; 3> else: 4> add a new entry for this musim-GapID; 1> if the RRCReconfiguration message includes the appLayerMeasConfig: 2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d; 1> set the content of the RRCReconfigurationComplete message as follows: 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each SCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each SCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG; NOTE 0b: It is expected that the reportUplinkTxDirectCurrentTwoCarrier is only received either in masterCellGroup or in secondaryCellGroup but not both. > if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG: 3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3; > if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG: 3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message; 3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution: 4> include in the selectedCondRRCReconfig the condReconfigId for the selected cell of conditional reconfiguration execution; > if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG: 3> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport: 4> if the sigLoggedMeasType in VarLogMeasReport is included: 5> include the sigLogMeasConfigAvailable in the RRCReconfigurationComplete message and set it according to the following: 6> if T330 timer is running: 7> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 6> else: 7> set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 4> include the logMeasAvailable in the RRCReconfigurationComplete message; 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: 5> include the logMeasAvailableBT in the RRCReconfigurationComplete message; 4> if WLAN measurement results are included in the logged measurements the UE has available for NR: 5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message; 3> if the sigLoggedMeasType in VarLogMeasReport is included: 4> if T330 timer is running: 5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 4> else: 5> if the UE has logged measurements available for NR: 6> set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 3> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or VarConnEstFailReportList: 4> include connEstFailInfoAvailable in the RRCReconfigurationComplete message; 3> if the UE has radio link failure or handover failure information available in VarRLF- Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report; or 3> if the UE has radio link failure or handover failure information available in VarRLF- Report of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331 [10]: 4> include rlf-InfoAvailable in the RRCReconfigurationComplete message; 3> if the UE was configured with successHO-Config when connected to the source PCell; and 3> if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: 4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG; 3> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report: 4> include successHO-InfoAvailable in the RRCReconfigurationComplete message; > if the RRCReconfiguration message was received via SRB1, but not within mrdc- SecondaryCellGroup or E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume: 3> if the UE is configured to provide the measurement gap requirement information of NR target bands: 4> if the RRCReconfiguration message includes the needForGapsConfigNR; or 4> if the NeedForGapsInfoNR information is changed compared to last time the UE reported this information: 5> include the NeedForGapsInfoNR and set the contents as follows: 6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell; 6> if requestedTargetBandFilterNR is configured, for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band; otherwise, include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band; 3> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands: 4> if the RRCReconfiguration message includes the needForNCSG-ConfigNR; or 4> if the needForNCSG-InfoNR information is changed compared to last time the UE reported this information: 5> include the NeedForNCSG-InfoNR and set the contents as follows: 6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell; 6> if requestedTargetBandFilterNCSG-NR is configured, for each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band; otherwise, include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information; 3> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands: 4> if the RRCReconfiguration message includes the needForNCSG-ConfigEUTRA; or 4> if the needForNCSG-InfoEUTRA information is changed compared to last time the UE reported this information: 5> include the NeedForNCSG-InfoEUTRA and set the contents as follows: 6> if requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG- EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information; 3> if the UE decided to reject the SL DRX configuration received within sl-DRX- Config-r17: 4> include the field sl-DRX-Reject in the RRCReconfigurationComplete message; 1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (UE in (NG)EN- DC): 2> if the RRCReconfiguration message was received via E-UTRA SRB1 as specified in TS 36.331 [10]; or 2> if the RRCReconfiguration message was received via E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (handover from NR standalone to (NG)EN-DC); 3> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr- SecondaryCellGroupConfig specified in TS 36.331 [10]: 4> submit the RRCReconfigurationComplete message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10], clause 5.6.2a. 3> else if the RRCReconfiguration message was included in E-UTRA RRCConnectionResume message: 4> submit the RRCReconfigurationComplete message via E-UTRA embedded in E- UTRA RRC message RRCConnectionResumeComplete as specified in TS 36.331 [10], clause 5.3.3.4a; 3> else: 4> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4/5.4.2.3; 3> if the scg-State is not included in the E-UTRA RRCConnectionReconfiguration message containing the RRCReconfiguration message: 4> if reconfigurationWithSync was included in spCellConfig of an SCG; or 4> if the SCG was deactivated before the reception of the E-UTRA RRC message containing the RRCReconfiguration message and lower layers consider that a Random Access procedure is needed for SCG activation: 5> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3]; 4> else: 5> the procedure ends; 3> else: 4> the procedure ends; 2> if the RRCReconfiguration message was received within nr-SecondaryCellGroupConfig in RRCConnectionReconfiguration message received via SRB3 within DLInformationTransferMRDC: 3> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4; 3> if reconfigurationWithSync was included in spCellConfig of an SCG: 4> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3]; 3> else: 4> the procedure ends; NOTE 1: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 2> else (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC: 3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; NOTE 2: In (NG)EN-DC and NR-DC, in the case RRCReconfiguration is received via SRB1 or within DLInformationTransferMRDC via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete. 1> else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1): 2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SCG within mrdc-SecondaryCellGroup: 3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3. 2> if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message: 3> if reconfigurationWithSync was included in spCellConfig in nr-SCG; or 3> if the SCG was deactivated before the reception of the NR RRC message containing the RRCReconfiguration message and lower layers consider that a Random Access procedure is needed for SCG activation: 4> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3]; 3> else: 4> the procedure ends; 2> else 3> the procedure ends; NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC): 2> if the RRCReconfiguration message was received within DLInformationTransferMRDC: 3> if the RRCReconfiguration message was received within the nr-SCG within mrdc- SecondaryCellGroup (NR SCG RRC Reconfiguration): 4> if reconfigurationWithSync was included in spCellConfig in nr-SCG: 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3]; 4> else: 5> the procedure ends; 3> else: 4> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration; 2> else: 3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; 1> else (RRCReconfiguration was received via SRB1): 2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration; 2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure: 3> resume SRB2, SRB4, and DRBs, multicast MRB, and BH RLC channels for IAB- MT, that are suspended; 1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a Random Access procedure triggered above: 2> stop timer T304 for that cell group; 2> stop timer T310 for source SpCell if running; 2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any; 2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell; 2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323 [5]; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG: 3> if T390 is running: 4> stop timer T390 for all access categories; 4> perform the actions as specified in 5.3.14.4. 3> if T350 is running: 4> stop timer T350; 3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and 3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1: 4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG; 4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG; or 2> if the reconfigurationWithSync was included in spCellConfig of an SCG and the CPA or CPC was configured 3> remove all the entries within VarConditionalReconfig, if any; 3> remove all the entries within VarConditionalReconfiguration as specified in TS 36.331 [10], clause 5.3.5.9.6, if any; 3> for each measId of the source SpCell configuration, if the associated reportConfig has a reportType set to condTriggerConfig: 4> for the associated reportConfigId: 5> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig; 4> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig: 5> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig; 4> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 2> if reconfigurationWithSync was included in masterCellGroup or secondaryCellGroup: 3> if the UE initiated transmission of a UEAssistanceInformation message for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE has initiated transmission of a UEAssistanceInformation message for the corresponding cell group since it was configured to do so in accordance with 5.7.4.2: 4> initiate transmission of a UEAssistanceInformation message for the corresponding cell group in accordance with clause 5.7.4.3 to provide the concerned UE assistance information; 4> start or restart the prohibit timer (if exists) associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration; 3> if SIB12 is provided by the target PCell; and the UE initiated transmission of a SidelinkUEInformationNR message indicating a change of NR sidelink communication related parameters relevant in target PCell (i.e. change of sl- RxInterestedFreqList or sl-TxResourceReqList) during the last 1 second preceding reception of the RRCReconfiguration message including reconfigurationWithSync in spCellConfig of an MCG; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the UE is capable of NR sidelink communication and SIB12 is provided by the target PCell, and the UE has initiated transmission of a SidelinkUEInformationNR message since it was configured to do so in accordance with 5.8.3.2: 4> initiate transmission of the SidelinkUEInformationNR message in accordance with 5.8.3.3; 2> the procedure ends. NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located. NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistanceInformation according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message might not be the same as the content of the previous UEAssistanceInformation message. ------------------- 5.8.9.1.3 Reception of an RRCReconfigurationSidelink by the UE The UE shall perform the following actions upon reception of the RRCReconfigurationSidelink: 1> if the RRCReconfigurationSidelink includes the sl-ResetConfig: 2> perform the sidelink reset configuration procedure as specified in 5.8.9.1.10; 1> if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList: 2> for each SLRB-PC5-ConfigIndex value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration; 3> perform the sidelink DRB release procedure, according to clause 5.8.9.1a.1; 1> if the RRCReconfigurationSidelink includes the slrb-ConfigToAddModList: 2> for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is not part of the current UE sidelink configuration: 3> if sl-MappedQoS-FlowsToAddList is included: 4> apply the SL-PQFI included in sl-MappedQoS-FlowsToAddList; 3> perform the sidelink DRB addition procedure, according to clause 5.8.9.1a.2; 2> for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is part of the current UE sidelink configuration: 3> if sl-MappedQoS-FlowsToAddList is included: 4> add the SL-PQFI included in sl-MappedQoS-FlowsToAddList to the corresponding sidelink DRB; 3> if sl-MappedQoS-FlowsToReleaseList is included: 4> remove the SL-PQFI included in sl-MappedQoS-FlowsToReleaseList from the corresponding sidelink DRB; 3> if the sidelink DRB release conditions as described in clause 5.8.9.1a.1.1 are met: 4> perform the sidelink DRB release procedure according to clause 5.8.9.1a.1.2; 3> else if the sidelink DRB modification conditions as described in clause 5.8.9.1a.2.1 are met: 4> perform the sidelink DRB modification procedure according to clause 5.8.9.1a.2.2; 1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig: 2> perform the sidelink measurement configuration procedure as specified in 5.8.10; 1> if the RRCReconfigurationSidelink message includes the sl-CSI-RS-Config: 2> apply the sidelink CSI-RS configuration; 1> if the RRCReconfigurationSidelink message includes the sl-LatencyBoundCSI-Report: 2> apply the configured sidelink CSI report latency bound; 1> if the UE is unable to comply with (part of) the configuration included in the RRCReconfigurationSidelink (i.e. sidelink RRC reconfiguration failure): 2> continue using the configuration used prior to the reception of the RRCReconfigurationSidelink message; 2> set the content of the RRCReconfigurationFailureSidelink message; 3> submit the RRCReconfigurationFailureSidelink message to lower layers for transmission; 1> else: 2> set the content of the RRCReconfigurationCompleteSidelink message; 3> if the UE decided to reject the SL DRX configuration received within sl-DRX- Config-r17: 4> include the field sl-DRX-Reject in the RRCReconfigurationSidelinkComplete message; 3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission; NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure. 1> if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToReleaseList-PC5: 2> for each SL-RLC-ChannelID value included in the sl-RLC-ChannelToReleaseList-PC5 that is part of the current UE sidelink configuration; 3> perform the PC5 Relay RLC channel release procedure, according to clause 5.8.9.7.1; 1> if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToAddModList-PC5: 2> for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModList- PC5 that is not part of the current UE sidelink configuration: 3> perform the sidelink RLC channle addition procedure, according to clause 5.8.9.7.2; 2> for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModList- PC5 that is part of the current UE sidelink configuration: 3> perform the PC5 Relay RLC channel modification procedure according to clause 5.8.9.7.2; ------------------- – RRCReconfigurationComplete The RRCReconfigurationComplete message is used to confirm the successful completion of an RRC connection reconfiguration. Signalling radio bearer: SRB1 or SRB3 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network RRCReconfigurationComplete message -- ASN1START -- TAG-RRCRECONFIGURATIONCOMPLETE-START RRCReconfigurationComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfigurationComplete RRCReconfigurationComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfigurationComplete-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1530-IEs OPTIONAL } RRCReconfigurationComplete-v1530-IEs ::= SEQUENCE { uplinkTxDirectCurrentList UplinkTxDirectCurrentList OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1560-IEs OPTIONAL } RRCReconfigurationComplete-v1560-IEs ::= SEQUENCE { scg-Response CHOICE { nr-SCG-Response OCTET STRING (CONTAINING RRCReconfigurationComplete), eutra-SCG-Response OCTET STRING } OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1610-IEs OPTIONAL } RRCReconfigurationComplete-v1610-IEs ::= SEQUENCE { ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1640-IEs OPTIONAL } RRCReconfigurationComplete-v1640-IEs ::= SEQUENCE { uplinkTxDirectCurrentTwoCarrierList-r16 UplinkTxDirectCurrentTwoCarrierList- r16 OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1700-IEs OPTIONAL } RRCReconfigurationComplete-v1700-IEs ::= SEQUENCE { needForNCSG-InfoNR-r17 NeedForNCSG-InfoNR-r17 OPTIONAL, needForNCSG-InfoEUTRA-r17 NeedForNCSG-InfoEUTRA-r17 OPTIONAL, selectedCondRRCReconfig-r17 CondReconfigId-r16 OPTIONAL, sl-DRX-Reject ENUMERATED {true} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRECONFIGURATIONCOMPLETE-STOP -- ASN1STOP ------------------- – RRCReconfigurationCompleteSidelink The RRCReconfigurationCompleteSidelink message is used to confirm the successful completion of a PC5 RRC AS reconfiguration. It is only applied to unicast of NR sidelink communication. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE RRCReconfigurationCompleteSidelink message -- ASN1START -- TAG-RRCRECONFIGURATIONCOMPLETESIDELINK-START RRCReconfigurationCompleteSidelink ::= SEQUENCE { rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfigurationCompleteSidelink-r16 RRCReconfigurationCompleteSidelink-IEs-r16, criticalExtensionsFuture SEQUENCE {} } } RRCReconfigurationCompleteSidelink-IEs-r16 ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfigurationCompleteSidelink-v17xy-IEs OPTIONAL } RRCReconfigurationCompleteSidelink-v17xy-IEs ::= SEQUENCE { sl-DRX-Reject ENUMERATED {true} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRECONFIGURATIONCOMPLETESIDELINK-STOP -- ASN1STOP

Claims

CLAIMS 1. A method performed by a first wireless device, RX UE (105, 205, 305, 405), the method comprising: in response to receiving (109, 209, 309, 409), from an entity (205, 207, 405, 407), a sidelink, SL, discontinuous reception, DRX, configuration for performing DRX of transmissions over an SL interface, rejecting (111, 211, 311, 411, 502) the SL DRX configuration without triggering a radio link failure or radio resource control, RRC, reestablishment procedure.

2. The method of claim 1, wherein rejecting (111, 211, 311, 411) the SL DRX configuration comprises not applying the SL DRX configuration.

3. The method of claim 2, wherein the SL DRX configuration is received (109, 209, 309, 409) in an RRCReconfiguration message and rejecting (111, 211, 311, 411) the SL DRX configuration comprises continuing to decode the rest of the RRCReconfiguration message without triggering the radio link failure or the RRC reestablishment procedure in response to determining that the first wireless device is unable to comply with the SL DRX configuration.

4. The method of any of the preceding claims, wherein the SL DRX configuration is received (109, 209, 309, 409) from a second wireless device (103, 203, 303, 403).

5. The method of claim 4, further comprising transmitting (215, 415) a message to the second wireless device (203, 403) indicating that the SL DRX configuration was rejected by the first wireless device (205, 405).

6. The method of claim 5, wherein the message transmitted (215, 415) to the second wireless device (203, 403) comprises: a flag set to a value that indicates that the SL DRX configuration is rejected by the first wireless device (205, 405); or a binary value that indicates that the SL DRX configuration is rejected by the first wireless device (205, 405).

7. The method of any of claims 4 to 6, wherein the SL DRX configuration is received (109, 209) in a message that includes additional configurations, the method further comprising: applying (113, 213) the additional configurations.

8. The method of claim 7, wherein the message is an RRC configuration message.

9. The method of claim 7 or 8, further comprising: transmitting a response message to the second wireless device indicating that the additional configurations were applied by the first wireless device.

10. The method of any of the preceding claims, further comprising storing (313, 413) the SL DRX configuration at the first wireless device (305, 405).

11. The method of claim 10, wherein the entity is a second wireless device (403), the method further comprising: using (419) the SL DRX configuration; transmitting (421) a message to the second wireless device (403) indicating that the SL DRX configuration has been used; and after transmitting the message, performing DRX on an SL interface in accordance with the SL DRX configuration.

12. The method of any of the preceding claims, further comprising discarding the SL DRX configuration.

13. A method performed by a first wireless device, RX UE (205, 405), the method comprising: transmitting (215, 217, 415, 417, 602) an indication to an entity (201, 203, 401, 403) in response to rejecting (211, 411) a sidelink, SL, discontinuous reception, DRX, configuration received from the entity (201, 203, 401, 403) for performing DRX of transmissions over an SL interface, wherein the SL DRX configuration is rejected without triggering a radio link failure or radio resource control, RRC, reestablishment procedure and the indication is an indication that the SL DRX configuration was rejected by the RX UE (205, 405) without triggering the radio link failure or RRC reestablishment procedure.

14. A first wireless device (700) configured to operate in accordance with any of claims 1 to 12 and/or claim 13.

15. A method performed by an entity (201, 203, 401, 403), the method comprising: in response to transmitting (207, 209, 407, 409) a sidelink, SL, discontinuous reception, DRX, configuration to a first wireless device, RX UE (205, 405), receiving (215, 217, 415, 417, 702), from the RX UE (205, 405), an indication that the SL DRX configuration was rejected by the RX UE (205, 405) without triggering a radio link failure or radio resource control, RRC, reestablishment procedure, wherein the SL DRX configuration is for performing DRX of transmissions over an SL interface.

16. The method of claim 15, wherein: the entity is a second wireless device, TX UE (205, 405); and the SL DRX configuration is transmitted over the SL interface.

17. The method of claim 16, wherein the SL DRX configuration is transmitted to the first wireless device (205, 405) in a radio resource control, RRC, configuration message.

18. The method of claim 17, wherein the RRC configuration message includes an additional configuration for the first wireless device, and wherein the response indicates that the additional configuration was applied by the first wireless device.

19. The method of any of claims 16 to 18, further comprising: transmitting (217, 417) a message to a network node (201, 401) indicating that the SL DRX configuration was rejected by the first wireless device (205, 405).

20. The method of claim 19, wherein the message transmitted (217, 417) to the network node (201, 401) comprises: a flag set to a value that indicates that the SL DRX configuration is rejected by the first wireless device (205, 405); or a binary value that indicates that the SL DRX configuration is rejected by the first wireless device (205, 405).

21. The method of any of claims 16 to 20, further comprising: receiving (421) a message from the first wireless device (405) indicating that the SL DRX configuration is being used by the first wireless device (405).

22. The method of claim 21, further comprising: in response to receiving (421) the message from the first wireless device indicating that the SL DRX configuration is being used by the first wireless device, transmitting communications over the SL interface in accordance with the SL DRX configuration.

23. The method of claim 15, wherein: the entity is a network node (201, 401); and the method comprises preparing the SL DRX configuration to be applied by the RX UE (205, 405) over the SL interface with a second wireless device, TX UE (203, 403).

24. The method of claim 23, further comprising: after receiving (417) the indication, receiving (423) a message from the TX UE (403) that the SL DRX configuration is being applied by the RX UE (405); in response to receiving the indication, triggering an RRC reconfiguration of the sidelink interface; or in response to receiving the indication, triggering an RRC release of the RX UE.

25. An entity (700, 800) configured to operate in accordance with any of claims 15 to 24.

26. A method performed by a system, the method comprising: the method as claimed in any of claims 1 to 12 and/or claim 13; and the method as claimed in any of claims 15 to 24.

27. A system comprising: a first wireless device as claimed in claim 14; and an entity as claimed in claim 25.

28. A computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the method according to any of claims 1 to 12, claim 13, and/or any of claims 15 to 24.

29. A computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform the method according to any of claims 1 to 12, claim 13, and/or any of claims 15 to 24.