Method and user equipment for sidelink discontinuous reception in a wireless communication system

Abstract

Methods, systems, and devices for sidelink discontinuous reception in a wireless communication system to avoid ambiguity regarding sidelink discontinuous reception slot offset calculation. A method for a user equipment includes performing a sidelink communication associated with a destination identity; having a sidelink discontinuous reception configuration associated with the sidelink communication, where the sidelink discontinuous reception configuration includes at least an on-duration timer and a discontinuous reception cycle; deriving a first offset associated with the sidelink communication based on the destination identity and the discontinuous reception cycle; deriving a second offset associated with the sidelink communication based on the destination identity and a number of slots per subframe; starting the on-duration timer after a time period determined based on the second offset from a start of a subframe, where the subframe is determined based on at least the first offset; and monitoring for sidelink control information while the on-duration timer is running.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication networks, and more specifically, to methods and apparatus for sidelink discontinuous reception in wireless communication systems. Background Technology

[0002] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) packets. This IP packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.

[0003] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) radio technologies. Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate the evolution and completion of the 3GPP standards. Summary of the Invention

[0004] Methods, systems, and apparatus for Sidelink Discontinuous Reception (SL DRX) in wireless communication systems to avoid ambiguity in slot offset calculations for SL DRX. In various embodiments, through such and other concepts, systems, and methods of the present invention, a method for a UE in a wireless communication system includes: performing SL communication associated with a destination identifier (ID); having or being configured with an SL DRX configuration associated with the SL communication, wherein the SL DRX configuration includes at least an on-duration timer and a DRX loop; deriving a first offset associated with the SL communication based on the destination ID and the DRX loop; deriving a second offset associated with the SL communication based on the destination ID and the number of slots per subframe; starting the on-duration timer after a time period determined based on the second offset from the beginning of a subframe, wherein the subframe is determined at least based on the first offset; and monitoring Sidelink Control Information (SCI) while the on-duration timer is running. Attached Figure Description

[0005] Figure 1 A diagram illustrating a wireless communication system according to an embodiment of the present invention is shown;

[0006] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention;

[0007] Figure 3 This is a functional block diagram of a communication system according to an embodiment of the present invention;

[0008] Figure 4 This is according to an embodiment of the present invention. Figure 3 Functional block diagram of the program code;

[0009] Figure 5 This is a reproduction of Table 4.2-1 from 3GPP TS 38.211 V16.8.0: Supported basic transport parameters;

[0010] Figure 6 It comes from 3GPP TS 38.211 V16.8.0. Figure 4 3.1-1: Reproduction of uplink-downlink timing relationship;

[0011] Figure 7 This is a reproduction of Table 4.3.2-1 from 3GPP TS 38.211 V16.8.0: the number of OFDM symbols per slot, slots per frame, and slots per subframe for the normal cyclic prefix;

[0012] Figure 8 This is a reproduction of Table 4.3.2-2 from 3GPP TS 38.211 V16.8.0: the number of OFDM symbols per slot, slots per frame, and slots per subframe used for extending the cyclic prefix;

[0013] Figure 9 This is a reproduction of Table 4.3.2-3 from 3GPP TS 38.211 V16.8.0: transition times N_"Rx-Tx" and N_"Tx-Rx";

[0014] Figure 10 The accompanying drawings illustrate, according to an embodiment of the present invention, the problems of the derived time slot offset not being aligned with the time slot boundary and the derived time slot offset being greater than 1ms.

[0015] Figure 11 The accompanying drawings illustrate a solution according to an embodiment of the present invention to align the derived time slot offset with the time slot boundary and keep the derived time slot offset less than 1ms.

[0016] Figure 12 The accompanying figure illustrates an embodiment of the present invention where the number of time slots per subframe is 2, and for each destination ID, the UE can derive the time slot offset based on the remainder when the destination ID is divided by the number of time slots per subframe.

[0017] Figure 13 The accompanying figure illustrates an embodiment of the present invention where the number of time slots per subframe is 4, and for each destination ID, the UE can derive the time slot offset based on the remainder when the destination ID is divided by the number of time slots per subframe.

[0018] Figure 14 This is a flowchart illustrating how a UE derives the slot offset associated with SL multicast communication based on the destination ID and the number of slots in the subframe, according to an embodiment of the present invention.

[0019] Figure 15 This is a flowchart illustrating how a UE derives the time slot offset associated with SL multicast communication based on the destination ID and a fixed number, according to an embodiment of the present invention.

[0020] Figure 16 This is a flowchart illustrating how a UE, according to an embodiment of the present invention, derives first and second offsets associated with SL communication, starts an enable duration timer after a time period, and monitors SCI while the enable duration timer is running. Detailed Implementation

[0021] The invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is described primarily in the context of the 3GPP architecture reference model. However, it should be understood that, with the aid of the disclosed information, those skilled in the art can readily adapt and implement aspects of the invention in 3GPP2 network architectures and other network architectures.

[0022] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation techniques.

[0023] Specifically, the exemplary wireless communication systems and apparatus described below may be designed to support one or more standards, such as those provided by the consortium referred to herein as 3GPP, which is named the “3rd Generation Partnership Project”, including: [1] 3GPP TS 38.321 V16.7.0; [2] 3GPP TS 38.331 V16.7.0; [3] 3GPP RAN2#116 - Electronic Conference Report; [4] 3GPP RAN2#117 - Electronic Conference Report; [5] Draft R2-2203673 CR for TS 38.321 for sidelink enhancement; [6] Draft R2-2203672 RRC CR for NR sidelink enhancement; and [7] 3GPP TS38.211 V16.8.0. The standards and documents listed above are hereby expressly and entirely incorporated herein by reference.

[0024] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one containing antennas 104 and 106, another containing antennas 108 and 110, and yet another containing antennas 112 and 114. Figure 1 In this diagram, only two antennas are shown in each antenna group; however, each antenna group may utilize more or fewer antennas. Access Terminal (AT) 116 communicates with antennas 112 and 114, which transmit information to AT 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, which transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, forward link 120 may use a different frequency than reverse link 118.

[0025] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of the area covered by the access network 100.

[0026] In communications via forward links 120 and 126, the transmit antennas of access network 100 utilize beamforming to improve the signal-to-noise ratio of the forward links used for different access terminals 116 and 122. Furthermore, compared to access networks that transmit to all their access terminals via a single antenna, access networks that use beamforming to transmit to access terminals randomly distributed within their coverage area cause less interference to access terminals in neighboring cells.

[0027] AN can refer to a fixed station or base station used for communication with terminals, and may also be called an access point, Node B, base station, enhanced base station, eNodeB, or some other term. AT can also be called User Equipment (UE), wireless communication device, terminal, access terminal, or some other term.

[0028] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data for multiple data streams is provided from the data source 212 to the transport (TX) data processor 214.

[0029] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, decodes, and interleaves the service data of the data streams based on a specific decoding scheme selected for each data stream to provide decoded data.

[0030] OFDM technology can be used to multiplex the decoded data and pilot data of each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data for said data stream are then modulated (e.g., symbol mapping) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulated symbols. Instructions executed by processor 230 determine the data rate, decoding, and modulation for each data stream. Memory 232 is coupled to processor 230.

[0031] The modulation symbols of all data streams are then provided to a TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then provides NT modulation symbol streams to NT transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and the antennas from which the symbols are transmitted.

[0032] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and upconverts) the analog signals to provide modulated signals suitable for transmission via a MIMO channel. NT modulated signals from transmitters 222a to 222t are then transmitted from NT antennas 224a to 224t respectively.

[0033] At receiver system 250, the transmitted modulated signal is received by NR antennas 252a to 252r, and the signal received from each antenna 252 is provided to the corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide the corresponding "received" symbol stream.

[0034] The RX data processor 260 then receives and processes NR received symbol streams from NR receivers 254 based on specific receiver processing techniques to provide NT "detected" symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the service data used for the data stream. The processing performed by the RX data processor 260 complements the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0035] Processor 270 periodically determines which pre-decoding matrix to use (discussed below). Processor 270 formulates a reverse link message including the matrix index part and the rank part.

[0036] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives service data from several data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0037] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Next, processor 230 determines which pre-decoding matrix to use to determine beamforming weights and then processes the extracted message.

[0038] Memory 232 can be used to temporarily store some buffered / calculated data from 240 or 242 via processor 230, some buffered data from 212, or some specific program code. Furthermore, memory 272 can be used to temporarily store some buffered / calculated data from 260 via processor 270, some buffered data from 236, or some specific program code.

[0039] Go to Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to achieve... Figure 1 The UE (or AT) 116 and 122 are used, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306.

[0040] Figure 4 According to an embodiment of the present invention Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connections.

[0041] For LTE, LTE-A, or NR systems, layer 2, part 404, may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. Layer 3, part 402, may include a Radio Resource Control (RRC) layer.

[0042] Any two or more of the following paragraphs, (sub)bullets, points, actions, or claims described in each invention may be logically, reasonably, and appropriately combined to form a particular method.

[0043] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following invention paragraphs or sections can be implemented independently and separately to form a particular method or apparatus. The use of terms such as "based on," "more specifically," and "example" in the following disclosure is merely one possible embodiment and does not limit the specific method or apparatus.

[0044] In 3GPP specification 38.321 ([1] 3GPP TS 38.321 V16.7.0), discontinuous reception (DRX) and sidelink communication are introduced:

[0045] 5.4 UL-SCH Data Transmission

[0046] 5.4.1 UL Accepts

[0047] Uplink grants are dynamically received on the PDCCH in a random access response, configured semi-persistently via RRC, or determined to be associated with the PUSCH resource of the MSGA, as specified in Clause 5.1.2a. The MAC entity will enable the uplink grant to be transmitted on the UL-SCH. To perform the requested transmission, the MAC layer receives HARQ information from the lower layer. Uplink grants addressed to CS-RNTI with NDI=0 are considered configured uplink grants. Uplink grants addressed to CS-RNTI with NDI=1 are considered dynamic uplink grants.

[0048] If the MAC entity has a C-RNTI, a temporary C-RNTI, or a CS-RNTI, then the MAC entity will grant permission for each PDCCH timing and for each serving cell belonging to a TAG that runs a timeAlignmentTimer and for each grant received for this PDCCH timing:

[0049] 1> If the uplink for this serving cell is already permitted to be received on the PDCCH of the C-RNTI or temporary C-RNTI used for the MAC entity; or

[0050] 1> If uplink permission has already been received in the random access response:

[0051] 2> If the uplink grant is a C-RNTI for a MAC entity and if the previous uplink grant delivered to the HARQ entity for the same HARQ procedure was a CS-RNTI received uplink grant or a configured uplink grant for a MAC entity, then:

[0052] 3> Regardless of the value of NDI, NDI is considered to have been switched for use in the corresponding HARQ procedure.

[0053] 2> If uplink grant is a C-RNTI for a MAC entity, and the identified HARQ procedure is configured for configured uplink grant, then:

[0054] 3> Start or restart the configuredGrantTimer (if configured) for the corresponding HARQ procedure;

[0055] 3> Stop the cg-RetransmissionTimer used for the corresponding HARQ procedure (if it is running).

[0056] 2> Deliver the uplink grant and associated HARQ information to the HARQ entity.

[0057] 1> Otherwise, if the uplink permission for this PDCCH timing has already been received for this serving cell on the PDCCH for the CS-RNTI used for the MAC entity:

[0058] 2> If the NDI in the received HARQ message is 1:

[0059] 3> Treat the NDI used for the corresponding HARQ procedure as not yet switched;

[0060] 3> Start or restart the configuredGrantTimer (if configured) for the corresponding HARQ procedure;

[0061] 3> Stop the cg-RetransmissionTimer used for the corresponding HARQ procedure (if it is running);

[0062] 3> Deliver the uplink grant and associated HARQ information to the HARQ entity.

[0063] 2> Otherwise, if the NDI in the received HARQ message is 0:

[0064] 3> If the PDCCH content indicator is configured to be disabled for type 2, then:

[0065] 4> Trigger the configured uplink permission confirmation.

[0066] 3> Otherwise, if the PDCCH content indication is configured to be activated by type 2, then:

[0067] 4> Trigger uplink permission confirmation as configured;

[0068] 4> Store the uplink grant and associated HARQ information used for this serving cell as the configured uplink grant;

[0069] 4> Initialize or reinitialize the configured uplink permission for this serving cell, which shall begin during the associated PUSCH duration and reoccur in accordance with the rules in Clause 5.8.2;

[0070] 4> Stop the configuredGrantTimer used for the corresponding HARQ procedure (if it is running);

[0071] 4> Stop the cg-RetransmissionTimer used for the corresponding HARQ procedure (if it is running).

[0072] For each serving cell and each configured uplink permission (if configured and activated), the MAC entity will:

[0073] 1> If the MAC entity is configured with lch-based Prioritization, and the configured uplink-granted PUSCH duration does not overlap with the uplink-granted PUSCH duration received in the random access response, or with the uplink-granted PUSCH duration addressed to the temporary C-RNTI, or with the PUSCH duration of the MSGA payload for this serving cell; or

[0074] 1> If the MAC entity is not configured to have lch-based Prioritization, and the configured uplink-granted PUSCH duration does not overlap with the uplink-granted PUSCH duration received on the PDCCH or in the random access response, or the PUSCH duration for the MSGA payload of this serving cell:

[0075] 2> Set the HARQ procedure ID to the HARQ procedure ID associated with this PUSCH duration;

[0076] 2> If, for the corresponding HARQ procedure, `configuredGrantTimer` is not running and `cg-RetransmissionTimer` is not configured (i.e., new transmission), then:

[0077] 3> Treat the NDI bit used for the corresponding HARQ procedure as already switched;

[0078] 3> Deliver the configured uplink permission and associated HARQ information to the HARQ entity.

[0079] 2> Otherwise, if the cg-RetransmissionTimer used for the corresponding HARQ procedure is configured but not running, then for the corresponding HARQ procedure:

[0080] 3> If the configuredGrantTimer is not running and the HARQ procedure is not pending (i.e., a new transfer), then:

[0081] 4> Treat the NDI bit as switched;

[0082] 4> Deliver the configured uplink permission and associated HARQ information to the HARQ entity.

[0083] 3> Otherwise, if the previous uplink grant for delivery to the HARQ entity used in the same HARQ procedure was a configured uplink grant (i.e., regarding retransmissions with configured grants), then:

[0084] 4> Deliver the configured uplink permission and associated HARQ information to the HARQ entity.

[0085] For configured uplink permission that is neither configured with harq-ProcID-Offset2 nor with cg-RetransmissionTimer, the HARQ procedure ID associated with the first symbol transmitted by the UL is derived from the following equation:

[0086] HARQ procedure ID = [floor(CURRENT_symbol / periodicity)] modulus nrofHARQ-procedure

[0087] For a configured uplink grant with harq-ProcID-Offset2, the HARQ process ID associated with the first symbol transmitted by the UL is derived from the following equation:

[0088] HARQ process ID = [floor(CURRENT_symbol / periodicity)] modulus nrofHARQ-Processes+harq-ProcID-Offset2

[0089] Where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in the frame × numberOfSymbolsPerSlot + number of symbols in the slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots in each frame and the number of consecutive symbols in each slot, as specified in TS 38.211[8].

[0090] For configured uplink grants with cg-RetransmissionTimer configured, the UE implementation selects a HARQ procedure ID from the HARQ procedure IDs that can be configured for the configured grant. For HARQ procedure ID selection, the UE should prioritize retransmissions before the initial transmission. The UE will switch the NDI in the CG-UCI for the new transmission but will not switch the NDI in the CG-UCI during retransmissions.

[0091] Note 1: CURRENT_symbol refers to the symbol index of the first transmission opportunity of the bundle, which is configured for uplink permission.

[0092] Note 2: If configured uplink grant is activated and the associated HARQ procedure ID is less than nrofHARQ-Processes, then the HARQ procedure is configured for configured uplink grant, where neither harq-ProcID-Offset nor harq-ProcID-Offset2 is configured. If configured uplink grant is activated and the associated HARQ procedure ID is greater than or equal to harq-ProcID-Offset2 and less than the sum of harq-ProcID-Offset2 and nrofHARQ-Processes configured for configured grant, then the HARQ procedure is configured for configured uplink grant, where harq-ProcID-Offset2 is configured.

[0093] Note 3: If a MAC entity receives an authorization in a random access response (i.e., a MAC RAR or fallback RAR) or addressed to a temporary C-RNTI or an authorization specified for the MSGA payload as specified in Clause 5.1.2a, and if the MAC entity also receives overlapping authorization for its C-RNTI or CS-RNTI, thus requiring simultaneous transmission on the SpCell, then the MAC entity may choose to continue with the authorization for its RA-RNTI / temporary C-RNTI / MSGB-RNTI / MSGA payload transmission or the authorization for its C-RNTI or CS-RNTI.

[0094] Note 4: In the case of an unaligned SFN spanning a carrier in a cell group, the SFN of the serving cell involved is used to calculate the HARQ procedure ID for configured uplink permission.

[0095] Note 5: If cg-RetransmissionTimer is not configured, then the HARQ procedure is not shared between different configured and permitted configurations in the same BWP.

[0096] For a MAC entity configured with lch-based Prioritization, the uplink priority is determined by the highest priority among the priorities of logical channels that are multiplexed (i.e., the MAC PDU to be transmitted is already stored in the HARQ buffer) or have multiplexable available data in the MAC PDU (i.e., the MAC PDU to be transmitted is not stored in the HARQ buffer), according to the mapping constraints described in Clause 5.4.3.1.2. No uplink priority for data multiplexed or multiplexable in the MAC PDU for any logical channel is lower than: the uplink priority for data multiplexed or multiplexable in the MAC PDU for any logical channel, or the priority of the logical channel that triggers the SR.

[0097] For a MAC entity configured with lch-based Prioritization, if the corresponding PUSCH transmission configured for uplink prioritization is cancelled by CI-RNTI as specified in Clause 11.2A of TS 38.213[6] or by a high PHY-priority PUCCH transmission as specified in Clause 9 of TS 38.213[6], then the configured uplink prioritization is considered a de-prioritized uplink prioritization. If this de-prioritized uplink prioritization is configured with autonomousTx, then the configuredGrantTimer for the corresponding HARQ procedure used for this de-prioritized uplink prioritization should be stopped if it is running.

[0098] When a MAC entity is configured with lch-based Prioritization, for each uplink granted to a HARQ entity whose associated PUSCH can be transmitted by the lower layer, the MAC entity should:

[0099] 1> If this uplink is permitted to be received in a random access response (i.e., in a MAC RAR or fallback RAR), or addressed to a temporary C-RNTI, or as determined for the transmission of the MSGA payload as specified in Clause 5.1.2a:

[0100] 2> Treat this uplink grant as a priority uplink grant.

[0101] 1> Otherwise, if this uplink is allowed to address a CS-RNTI or C-RNTI with NDI=1:

[0102] 2> If there is no un-de-prioritized configured uplink-granted overlapping PUSCH duration with a higher priority than the uplink-granted priority within the same BWP; and

[0103] 2> If there are no PUCCH resources overlapping with SR transmissions that have not yet been de-prioritized, and the logical channel that triggered the SR has a higher priority than the uplink-granted priority:

[0104] 3> Treat this uplink grant as a prioritized uplink grant;

[0105] 3> Treat other overlapping uplink grants (if they exist) as de-prioritized uplink grants;

[0106] 3> Treat other overlapping SR transfers (if they exist) as de-prioritized SR transfers.

[0107] 1> Otherwise, if this uplink is granted as configured uplink permission:

[0108] 2> If, within the same BWP, there is no other configured uplink-granted overlapping PUSCH duration with a higher priority than the uplink-granted priority that has not yet been de-prioritized; and

[0109] 2> If, within the same BWP, there is no un-de-prioritized overlapping PUSCH duration addressed to a CS-RNTI or C-RNTI with NDI=1 and addressed to an uplink-granted CS-RNTI or C-RNTI with a priority higher than or equal to the uplink-granted priority; and

[0110] 2> If there are no PUCCH resources overlapping with SR transmissions that have not yet been de-prioritized, and the logical channel that triggered the SR has a higher priority than the uplink-granted priority:

[0111] 3> Treat this uplink grant as a prioritized uplink grant;

[0112] 3> Treat other overlapping uplink grants (if they exist) as de-prioritized uplink grants;

[0113] 3> If de-prioritizing uplink granting is a configured uplink granting that has started its PUSCH and is configured with autonomousTx:

[0114] 4> Stop the configuredGrantTimer used for the corresponding HARQ process of de-prioritizing uplink grants.

[0115] 3> Treat other overlapping SR transfers (if they exist) as de-prioritized SR transfers.

[0116] Note 6: If the MAC entity is configured with lch-based Prioritization and there are at least two overlapping PUSCH durations with equal priority configured uplink grants, then the prioritized uplink grant is determined by the UE implementation scheme.

[0117] Note 7: If the MAC entity is not configured to have lch-based Prioritization and if there are at least two overlapping PUSCH durations configured uplink grant, then the UE implementation shall select one of the configured uplink grants.

[0118] Note 8: If the MAC entity is configured with lch-based Prioritization, then the MAC entity does not consider UCI multiplexing according to the procedure specified in TS 38.213[6] when determining whether the uplink granted PUSCH duration overlaps with the PUCCH resource used for SR transmission.

[0119] 5.4.2 HARQ Operation

[0120] 5.4.2.1 HARQ Entities

[0121] The MAC entity contains a HARQ entity for each serving cell with a configured uplink (including when it is configured with a supplementary uplink), which maintains a number of parallel HARQ processes.

[0122] The number of parallel UL HARQ processes per HARQ entity is specified in TS 38.214[7].

[0123] Each HARQ process supports one TB.

[0124] Each HARQ process is associated with a HARQ process identifier. For UL deliveries with UL approval in the RA response or for UL deliveries for MSGA payloads, HARQ process identifier 0 is used.

[0125] Note: When a single DCI is used to schedule multiple PUSCHs, the UE is allowed to internally map the generated TB to different HARQ procedures in the event of LBT failure. That is, the UE can transmit a new TB on any HARQ procedure with the same TBS and the same RV, and the NDI indicates the new transmission.

[0126] The maximum number of TBs that can be transmitted within a bundle, whether dynamically or configured to be granted, is given by REPETITION_NUMBER as follows:

[0127] - For dynamic grants, REPETITION_NUMBER is set to a value provided by the lower layer, as specified in Clause 6.1.2.1 of TS 38.214[7];

[0128] - For configuration permission, REPETITION_NUMBER is set to a value provided by the lower layer, as specified in Clause 6.1.2.3 of TS38.214[7].

[0129] If REPETITION_NUMBER > 1, then at most REPETITION_NUMBER-1 HARQ retransmissions follow immediately within the bundle after the first transmission within the bundle. For both dynamic grants and configured uplink grants, bundle operation relies on the HARQ entity invoking the same HARQ procedure for each transmission that is part of the same bundle. Within the bundle, HARQ retransmissions are triggered based on the REPETITION_NUMBER used for dynamic grants or configured uplink grants without waiting for feedback from previous transmissions, unless they are terminated as specified in Clause 6.1 of TS 38.214 [7]. Each transmission within the bundle is a separate uplink grant delivered to the HARQ entity.

[0130] For each transmission within a dynamically granted bundle, a sequence of redundant versions is determined according to Clause 6.1.2.1 of TS 38.214[7]. For each transmission within a configured uplink granted bundle, a sequence of redundant versions is determined according to Clause 6.1.2.3 of TS 38.214[7].

[0131] For each uplink grant, the HARQ entity will:

[0132] 1> Identify the HARQ process associated with this authorization, and for each identified HARQ process:

[0133] 2> If the received provisional C-RNTI is not addressed to the PDCCH, and the NDI provided in the associated HARQ information has been switched compared to the value in the previous transmission of this TB in this HARQ procedure; or

[0134] 2> If uplink permission is received on the PDCCH of C-RNTI, and the HARQ buffer of the identified procedure is empty; or

[0135] 2> If the uplink is permitted to receive in the random access response (i.e., in the MAC RAR or fallback RAR); or

[0136] 2> If, as specified in Clause 5.1.2a, the uplink for transmitting the MSGA payload is permitted; or

[0137] 2> If uplink permission is received on the PDCCH for the C-RNTI in the ra-ResponseWindow and the PDCCH is successfully completed, then initiate the random access procedure for beam fault recovery; or

[0138] 2> If uplink permission is part of a bundle configured with uplink permission and can be used for initial transmission in accordance with Clause 6.1.2.3 of TS38.214[7], and if a MAC PDU has not yet been obtained for this bundle:

[0139] 3> If a MAC PDU exists in the MSGA buffer and uplink permission for transmitting the MSGA payload is selected as specified in Clause 5.1.2a; or

[0140] 3> If a MAC PDU exists in the MSGA buffer and uplink permission is received in the fallbackRAR and the fallbackRAR completes successfully, then the random access procedure is as follows:

[0141] 4> Obtain the MAC PDU to transfer from the MSGA buffer.

[0142] 3> Otherwise, if a MAC PDU exists in the Msg3 buffer and uplink permission has been received in the fallbackRAR, then:

[0143] 4> Obtain the MAC PDU to transfer from the Msg3 buffer.

[0144] 3> Otherwise, if a MAC PDU exists in the Msg3 buffer and uplink permission has been received in the MAC RAR; or:

[0145] 3> If a MAC PDU exists in the Msg3 buffer and uplink permission is received on the PDCCH for the C-RNTI in the ra-ResponseWindow, and this PDCCH completes successfully, then initiate the random access procedure for beam fault recovery:

[0146] 4> Obtain the MAC PDU to transfer from the Msg3 buffer.

[0147] 4> If the uplink granted size does not match the size of the obtained MAC PDU; and

[0148] 4> If the random access procedure is successfully completed after receiving uplink permission:

[0149] 5> Indicate to the multiplexing and aggregation entity that the MAC subPDU carrying the MAC SDU from the obtained MAC PDU will be included in subsequent uplink transmissions;

[0150] 5> Obtain MAC PDU for transfer from multiplexed and aggregated entities.

[0151] 3> Otherwise, if this uplink permission is configured with autonomousTx; and

[0152] 3> If the previously configured uplink in the BWP used for this HARQ procedure is not prioritized; and

[0153] 3> If a MAC PDU has been obtained for this HARQ procedure; and

[0154] 3> If the uplink permission size matches the size of the obtained MAC PDU; and

[0155] 3> If the PUSCH transfers of the obtained MAC PDUs are not fully executed:

[0156] 4> It is believed that the MAC PDU has been obtained.

[0157] 3> Otherwise, if the MAC entity is not configured with lch-based Prioritization; or

[0158] 3> If this uplink grant is a prioritized uplink grant:

[0159] 4> Obtain the MAC PDU to transfer from the multiplexed and collection entities (if they exist);

[0160] 3> If the MAC PDU for transmission has already been obtained, then:

[0161] 4> If the uplink permission is not configured with autonomousTx; or

[0162] 4> If uplink grant is a prioritized uplink grant:

[0163] 5> Deliver the MAC PDU, uplink grant, and TB HARQ information to the identified HARQ procedure;

[0164] 5> Indicates that the identified HARQ procedure triggers a new transmission;

[0165] 5> If uplink permission is configured:

[0166] 6> If the LBT fault indication is not received from the lower layer, start or restart the configuredGrantTimer (if configured) for the corresponding HARQ procedure when the transmission is performed;

[0167] 6> If the LBT fault indication is not received from the lower layer, start or restart the cg-RetransmissionTimer for the corresponding HARQ procedure when the transmission is performed (if configured).

[0168] 5> If uplink grant is enabled via addressing to the C-RNTI, and the identified HARQ procedure is configured for configured uplink grant:

[0169] 6> If the LBT fault indication is not received from the lower layer, start or restart the configuredGrantTimer (if configured) for the corresponding HARQ procedure when the transmission is performed.

[0170] 5> If cg-RetransmissionTimer is configured for the identified HARQ procedure; and

[0171] 5> If a transmission is performed and the LBT fault indication is received from the lower layer:

[0172] 6> Treat the identified HARQ process as pending.

[0173] 3> Otherwise:

[0174] 4> Clear the HARQ buffer of the identified HARQ procedure.

[0175] 2> Otherwise (i.e., retransmit):

[0176] 3> If the uplink received on the PDCCH is allowed to be addressed to the CS-RNTI and if the HARQ buffer of the identified procedure is empty; or

[0177] 3> If the uplink is permitted as part of a cluster and if a MAC PDU has not yet been obtained for this cluster; or

[0178] 3> If the uplink grant is part of a bundle configured with uplink grants, and the PUSCH duration of the uplink grant overlaps with the uplink grant received in the random access response (i.e., MAC RAR or fallback RAR) or the uplink grant determined for the MSGA payload for this serving cell as specified in Clause 5.1.2a; or:

[0179] 3> If the MAC entity is not configured to have lch-based Prioritization and this uplink grant is part of a bundle of configured uplink grants, and the PUSCH duration of the uplink grant overlaps with the PUSCH duration of another uplink grant received on the PDCCH; or:

[0180] 3> If the MAC entity is configured with lch-based Prioritization and this uplink grant is not a prioritized uplink grant:

[0181] 4> Ignore uplink permission.

[0182] 3> Otherwise:

[0183] 4> Deliver the uplink grant and TB HARQ information (redundant version) to the identified HARQ process;

[0184] 4> Indicates that the identified HARQ procedure triggers a retransmission;

[0185] 4> If the uplink is allowed to be addressed to CS-RNTI; or

[0186] 4> If uplink grant is addressed to the C-RNTI, and the identified HARQ procedure is configured for configured uplink grant:

[0187] 5> If the LBT fault indication is not received from the lower layer, start or restart the configuredGrantTimer (if configured) for the corresponding HARQ procedure when the transmission is performed.

[0188] 4> If uplink permission is configured:

[0189] 5> If the identified HARQ procedure is pending, then:

[0190] 6> If the LBT fault indication is not received from the lower layer, start or restart the configuredGrantTimer (if configured) for the corresponding HARQ procedure when the transmission is performed;

[0191] 5> If the LBT fault indication is not received from the lower layer, start or restart the cg-RetransmissionTimer for the corresponding HARQ procedure when the transmission is performed (if configured).

[0192] 4> If the identified HARQ procedure is pending and transmission is performed, and the LBT fault indication is not received from the lower layer:

[0193] 5> Treat the identified HARQ process as non-pending.

[0194] When determining whether an NDI has been switched compared to a previously transmitted value, the MAC entity will ignore any NDI received in all uplink grants on the PDCCH for its temporary C-RNTI.

[0195] When starting or restarting configuredGrantTimer or cg-RetransmissionTimer via PUSCH transfer, it should start at the beginning of the first symbol of the PUSCH transfer.

[0196] 5.4.2.2 HARQ Procedure

[0197] Each HARQ procedure is associated with a HARQ buffer.

[0198] A new transmission is performed on the resource by indicating it on the PDCCH or in the random access response (i.e., MAC RAR or fallback RAR), or by sending it in the RRC, or as specified in Clause 5.1.2a for the MCS determined for the MSGA payload. Retransmissions are performed on the resource, and if available, by the MCS indicated on the PDCCH or on the same resource and by the same MCS as the last transmission attempt made within the bundle, or, when cg-RetransmissionTimer is configured, by the stored configured uplink granted resource and the stored MCS. If cg-RetransmissionTimer is configured, and if the configured granted configuration has the same TBS, then a retransmission with the same HARQ procedure can be performed on any configured granted configuration.

[0199] When cg-RetransmissionTimer is configured and the HARQ entity receives the MAC PDU to be transmitted and the LBT fault indication is received from the lower layer, the corresponding HARQ procedure is considered pending. For configured uplink permission with cg-RetransmissionTimer configured, each associated HARQ procedure is considered non-pending if the following conditions are met:

[0200] - The HARQ procedure is executed and the LBT fault indication is not received from the lower layer; or

[0201] - Uplink privileges are initialized as configured and this HARQ procedure is not associated with another configured uplink privilege; or

[0202] - The HARQ buffer used for this HARQ procedure is cleared.

[0203] If a HARQ entity requests a new transfer for TB, then the HARQ process will:

[0204] 1> Store the MAC PDU in the associated HARQ buffer;

[0205] 1> Store uplink permission received from the HARQ entity;

[0206] 1> The transmission is generated as described below.

[0207] If the HARQ entity request is used for the retransmission of TB, then the HARQ process will:

[0208] 1> Store uplink permission received from the HARQ entity;

[0209] 1> The transmission is generated as described below.

[0210] In order to generate a transfer for TB, the HARQ process will:

[0211] 1> If the MAC PDU is obtained from the Msg3 buffer; or

[0212] 1> If a MAC PDU is obtained from the MSGA buffer; or

[0213] 1> If there is no measurement gap during transmission and a retransmission is performed, the retransmission will not conflict with the transmission of the MAC PDU obtained from the Msg3 buffer or MSGA buffer:

[0214] 2> If there is neither NR side link communication nor V2X side link communication during transmission; or

[0215] 2> If the transmission of MAC PDU takes precedence over sidelink transmission or can be performed simultaneously with sidelink transmission:

[0216] 3> Instruct the physical layer to allow transmission based on the stored uplink.

[0217] If the HARQ procedure receives downlink feedback information, then the HARQ procedure will:

[0218] 1> Stop cg-RetransmissionTimer (if it is running);

[0219] 1> If the instruction is confirmed, then:

[0220] 2> Stop configuredGrantTimer (if it is running).

[0221] If the configuredGrantTimer of the HARQ procedure expires, then the HARQ procedure will:

[0222] 1> Stop cg-RetransmissionTimer (if it is running).

[0223] If one of the following conditions is met, then the transmission of a MAC PDU takes precedence over sidelink transmissions or can be performed concurrently with sidelink transmissions:

[0224] -If at the time of transmission there is a sidelink grant for transmission of NR sidelink communication and a configured grant for transmission of V2X sidelink communication on SL-SCH as described in Clause 5.14.1.2.2 of TS 36.321

[22] , and the transmission of NR sidelink communication is not prioritized as described in Clause 5.22.1.3.1a and the transmission of V2X sidelink communication is not prioritized as described in Clause 5.14.1.2.2 of TS 36.321

[22] ; or

[0225] -If at the time of transmission there is a sidelink grant for transmission of NR sidelink communication and a configured grant for transmission of V2X sidelink communication on SL-SCH as described in Clause 5.14.1.2.2 of TS 36.321

[22] , and the MACPDU contains any MAC CE or MAC PDU that prioritizes a logical channel whose highest priority value is lower than ul-PrioritizationThres (if ul-PrioritizationThres is configured); or

[0226] -If at the time of transmission there is a sidelink permission for transmission of NR sidelink communication and a configured permission for transmission of V2X sidelink communication on SL-SCH as described in Clause 5.14.1.2.2 of TS 36.321

[22] , and the MAC entity is capable of performing this UL transmission simultaneously with the transmission of NR sidelink communication and / or the transmission of V2X sidelink communication; or

[0227] -If, at the time of transmission, only the transmission of V2X sidelink communication over SL-SCH is configured to be permitted as described in Clause 5.14.1.2.2 of TS 36.321

[22] , and none of the V2X sidelink communication transmissions are prioritized as described in Clause 5.14.1.2.2 of TS 36.321

[22] , or the MAC entity is able to perform this UL transmission concurrently with the V2X sidelink communication transmission; or

[0228] - If, at the time of transmission, only a sidelink grant exists for transmissions of NR sidelink communication, and if the MAC PDU contains any MAC CE prioritized as described in Clause 5.4.3.1.3, or the NR sidelink communication transmission is not prioritized as described in Clause 5.22.1.3.1a, or the highest priority value of the logical channel in the MAC PDU is lower than ul-PrioritizationThres (ul-PrioritizationThres are configured), or at the time of transmission, a sidelink grant exists for transmissions of NR sidelink communication and the MAC entity is able to perform this UL transmission simultaneously with the NR sidelink communication transmission; or

[0229] -If at the time of transmission there is a sidelink permission for transmission of NR sidelink communication and a configured permission for transmission of V2X sidelink communication on SL-SCH as described in Clause 5.14.1.2.2 of TS 36.321

[22] , and only NR sidelink communication transmissions are prioritized as described in Clause 5.22.1.3.1a or only V2X sidelink communication transmissions are prioritized as described in Clause 5.14.1.2.2 of TS 36.321

[22] , and the MAC entity is capable of performing this UL transmission simultaneously with the priority transmission of NR sidelink communication or V2X sidelink communication:

[0230] Note 1: In the UL transmissions in which the MAC entity can simultaneously execute the transmission of the prioritized NR sidelink communication, if there is more than one UL transmission that the MAC entity cannot execute at the same time, then the UE implementation scheme shall decide whether to execute this UL transmission.

[0231] Note 2: Among all UL transmissions that the MAC entity can communicate with the prioritized V2X sidelink and execute simultaneously, if there is more than one UL transmission that the MAC entity cannot execute simultaneously, then the UE implementation scheme shall decide whether to execute this UL transmission.

[0232] Note 3: In the UL transmissions in which the MAC entity can simultaneously execute the NR sidelink transmissions that are prioritized for V2X sidelink communication, if there are more than one UL transmission that the MAC entity cannot execute at the same time, then the UE implementation scheme shall decide whether to execute this UL transmission.

[0233] Note 4: If, during transmission, there is a configured permission for transmission of V2X sidelink communication on SL-SCH as described in Clause 5.14.1.2.2 of TS 36.321

[22] , and the MAC entity cannot perform this UL transmission simultaneously with the transmission of V2X sidelink communication, and priority-related information is unavailable before the transmission time due to processing time constraints, then the UE implementation scheme shall decide whether to perform this UL transmission.

[0234] 5.7 Discontinuous Reception (DRX)

[0235] The MAC entity can be configured by an RRC with DRX functionality, which controls the UE's PDCCH monitoring activities for the MAC entity using C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and AI-RNTI. When using DRX operation, the MAC entity shall also monitor the PDCCH in accordance with the requirements present in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, the MAC entity may monitor the PDCCH discontinuously for all active serving cells using the DRX operation specified in this section; otherwise, the MAC entity will monitor the PDCCH as specified in TS 38.213[6].

[0236] Note 1: If sidelink resource allocation mode 1 is configured by RRC, then DRX functionality is not configured.

[0237] RRC controls DRX operation by configuring the following parameters:

[0238] -drx-onDurationTimer: The duration at which the DRX loop begins;

[0239] -drx-SlotOffset: The delay before drx-onDurationTimer is started;

[0240] -drx-InactivityTimer: The duration following the PDCCH timing that indicates a new UL or DL ​​transmission from the MAC entity;

[0241] -drx-RetransmissionTimerDL (per DL HARQ process, except for broadcast processes): The maximum duration until a DL retransmission is received;

[0242] -drx-RetransmissionTimerUL (per UL HARQ process): The maximum duration until permission for UL retransmission is received;

[0243] -drx-LongCycleStartOffset: The drx-StartOffset for long DRX cycles and defines the subframes at the start of long and short DRX cycles;

[0244] -drx-ShortCycle (optional): Short DRX cycle;

[0245] -drx-ShortCycleTimer (optional): The UE will follow the duration of the short DRX cycle;

[0246] -drx-HARQ-RTT-TimerDL (per DL HARQ process, except for broadcast processes): the minimum duration before the DL assignment for which the MAC entity expects a HARQ retransmission.

[0247] -drx-HARQ-RTT-TimerUL (per UL HARQ process): The minimum duration before the MAC entity expects UL HARQ retransmission permission to be granted;

[0248] -ps-Wakeup (optional): Configures the associated drx-onDurationTimer to start if DCP is monitored but not detected;

[0249] -ps-TransmitOtherPeriodicCSI (optional): Configuration to report periodic CSI on PUCCH that is not L1-RSRP during the duration indicated by drx-onDurationTimer when DCP is configured but the associated drx-onDurationTimer is not started;

[0250] -ps-TransmitPeriodicL1-RSRP (optional): Configures periodic CSI for L1-RSRP to be transmitted on PUCCH for the duration indicated by drx-onDurationTimer when DCP is configured but the associated drx-onDurationTimer is not started;

[0251] The serving cell of a MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, only one DRX group exists, and all serving cells belong to that single DRX group. When two DRX groups are configured, each serving cell is uniquely assigned to either of the two groups. The DRX parameters configured individually for each DRX group are: drx-onDurationTimer and drx-InactivityTimer. The DRX parameters common to all DRX groups are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.

[0252] When configuring DRX, the time of application for the serving cell in the DRX group includes the following times:

[0253] - The drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

[0254] -drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is active on any serving cell in the DRX group; or

[0255] -ra-ContentionResolutionTimer (as described in Clause 5.1.5) or msgB-ResponseWindow (as described in Clause 5.1.4a) is running; or

[0256] - The scheduling request is sent on the PUCCH and is pending (as described in Clause 5.4.4); or

[0257] - No PDCCH (as described in Clauses 5.1.4 and 5.1.4a) is received after successful reception of a random access response for a random access preamble that was not selected by the MAC entity in a contention-based random access preamble.

[0258] When DRX is configured, the MAC entity will:

[0259] 1> If the MAC PDU is received in a configured downlink assignment, then:

[0260] 2> After the corresponding transmission carrying the DL HARQ feedback is completed, start the corresponding HARQ process drx-HARQ-RTT-TimerDL in the first symbol;

[0261] 2> Stop the drx-RetransmissionTimerDL corresponding to the HARQ process.

[0262] 1> If the MAC PDU is transmitted in the configured uplink permission and no LBT fault indication is received from the lower layer:

[0263] 2> After the first transmission (within the bundle) of the corresponding PUSCH transmission ends, start the drx-HARQ-RTT-TimerUL of the corresponding HARQ procedure in the first symbol;

[0264] 2> Stop the drx-RetransmissionTimerUL corresponding to the HARQ process at the first transmission (within the cluster) of the corresponding PUSCH transmission.

[0265] 1> If the drx-HARQ-RTT-TimerDL expires:

[0266] 2> If the data corresponding to the HARQ procedure is not successfully decoded:

[0267] 3> After the drx-HARQ-RTT-TimerDL expires, start the corresponding HARQ procedure's drx-RetransmissionTimerDL in the first symbol.

[0268] 1> If drx-HARQ-RTT-TimerUL expires:

[0269] 2> After the drx-HARQ-RTT-TimerUL expires, start the corresponding HARQ procedure drx-RetransmissionTimerUL in the first symbol.

[0270] 1> If a DRX command MAC CE or a long DRX command MAC CE is received:

[0271] 2> Stop using drx-onDurationTimer for each DRX group;

[0272] 2> Stop using drx-InactivityTimer for each DRX group.

[0273] 1> If the drx-InactivityTimer used for the DRX group expires:

[0274] 2> If a short DRX loop is configured:

[0275] 3> After the drx-InactivityTimer expires, start or restart the drx-ShortCycleTimer for this DRX group in the first symbol;

[0276] 3> Use a short DRX cycle for this DRX group.

[0277] 2> Otherwise:

[0278] 3> Use a long DRX loop for this DRX group.

[0279] 1> If a DRX command is received via MAC CE:

[0280] 2> If a short DRX loop is configured:

[0281] 3> Start or restart the drx-ShortCycleTimer for each DRX group in the first symbol after the DRX command MAC CE is received;

[0282] 3> Use short DRX cycles for each DRX group.

[0283] 2> Otherwise:

[0284] 3> Use a long DRX loop for each DRX group.

[0285] 1> If the drx-ShortCycleTimer used for the DRX group expires:

[0286] 2> Use a long DRX loop for this DRX group.

[0287] 1> If a long DRX command is received, MAC CE:

[0288] 2> Stop the drx-ShortCycleTimer used for each DRX group;

[0289] 2> Use a long DRX loop for each DRX group.

[0290] 1> If a short DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle):

[0291] 2> Start the drx-onDurationTimer for this DRX group after the drx-SlotOffset from the beginning of the subframe.

[0292] 1> If a long DRX cycle is used for the DRX group, and [(SFN×10)+subframe number] modulo (drx-LongCycle) = drx-StartOffset:

[0293] 2> If, as specified in Clause 10.3 of TS 38.213[6], the DL BWP is configured to monitor DCP:

[0294] 3> If a DCP instruction to start drx-onDurationTimer is received from the lower layer in connection with the current DRX cycle, as specified in TS 38.213[6]; or

[0295] 3> If, as specified in TS 38.213[6], all DCP opportunities in the time domain associated with the current DRX cycle occur during the action time, consider the grant / assignment / DRX command MAC CE / long DRX command MAC CE and the dispatch request (as specified in Clause 5.1.4) received 4 ms before the start of the last DCP opportunity, or during the measurement gap, or when the MAC entity is monitoring PDCCH transmissions in the search space indicated by the recoverySearchSpaceId of the SpCell identified by C-RNTI while the ra-ResponseWindow is running; or

[0296] 3> If ps-Wakeup is configured to true and no DCP indication associated with the current DRX loop is received from the lower layer:

[0297] 4> Start drx-onDurationTimer after drx-SlotOffset from the subframe.

[0298] 2> Otherwise:

[0299] 3> Start the drx-onDurationTimer for this DRX group after the drx-SlotOffset from the beginning of the subframe.

[0300] Note 2: In the case of an unaligned SFN spanning a carrier in a cell group, the SFN of SpCell is used to calculate the DRX duration.

[0301] 1> If the DRX group is in effect:

[0302] 2> Monitor the PDCCH on the serving cell in this DRX group as specified in TS 38.213[6];

[0303] 2> If the PDCCH instructs DL to transmit:

[0304] 3> After the corresponding transmission carrying the DL HARQ feedback is completed, start the corresponding HARQ process drx-HARQ-RTT-TimerDL in the first symbol;

[0305] Note 3: When the HARQ feedback is delayed by the PDSCH indicating a non-numeric k1 value to the HARQ feedback timing, as specified in TS 38.213[6], the corresponding transmission opportunity for sending the DL HARQ feedback will be indicated in a later PDCCH requesting the HARQ-ACK feedback.

[0306] 3> Stop the drx-RetransmissionTimerDL corresponding to the HARQ process.

[0307] 3> If the PDSCH to HARQ feedback timing indication is not a numeric k1 value, as specified in TS 38.213[6]:

[0308] 4> Start drx-RetransmissionTimerDL in the first symbol after the (last) PDSCH transmission within the bundle for the corresponding HARQ process (end).

[0309] 2> If the PDCCH instructs the UL to transmit:

[0310] 3> After the first transmission (within the bundle) of the corresponding PUSCH transmission ends, start the drx-HARQ-RTT-TimerUL of the corresponding HARQ procedure in the first symbol;

[0311] 3> Stop the drx-RetransmissionTimerUL corresponding to the HARQ process.

[0312] 2> If the PDCCH indicates a new transmission (DL or UL) on the serving cell in this DRX group:

[0313] 3> Start or restart the drx-InactivityTimer for this DRX group in the first symbol after the PDCCH reception ends.

[0314] Note 3a: A PDCCH indicating SPS or configured to be active of type 2 is considered to indicate a new transmission.

[0315] 2> If the HARQ procedure receives downlink feedback information and indicates acknowledgment:

[0316] 3> Stop the drx-RetransmissionTimerUL corresponding to the HARQ process.

[0317] 1> If, as specified in Clause 10.3 of TS 38.213[6], the DL BWP is configured to monitor the DCP; and

[0318] 1> If the current symbol n occurs within the duration of drx-onDurationTimer; and

[0319] 1> If, as specified in this clause, the drx-onDurationTimer associated with the current DRX cycle is not started:

[0320] 2> If, when evaluating all the DRX action time conditions specified in this clause, the MAC entity will not be in action time, taking into account the grant / assignment / DRX command MAC CE / long DRX command MAC CE received and the scheduling request sent 4ms before symbol n, then:

[0321] 3> Do not transmit periodic SRS and semi-static SRS, as defined in TS 38.214[7];

[0322] 3> Do not report semi-persistent CSI configured on PUSCH;

[0323] 3> If ps-TransmitPeriodicL1-RSRP is not configured to have a true value:

[0324] 4> Do not report periodic CSIs as L1-RSRP on PUCCH.

[0325] 3> If ps-TransmitOtherPeriodicCSI is not configured to have a true value:

[0326] 4> Do not report periodic CSIs that are not L1-RSRP on PUCCH.

[0327] 1> Otherwise:

[0328] 2> In the current symbol n, if, when evaluating all the DRX activation time conditions specified in this clause, considering the grant / assignment and DRX command MACCE / long DRX command MAC CE received 4ms prior to symbol n on the serving cell in this DRX group and the scheduling request sent, the DRX group will not be in activation time, then:

[0329] 3> Do not transmit periodic SRS and semi-persistent SRS as defined in TS 38.214[7] in this DRX group;

[0330] 3> Do not report CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group.

[0331] 2> If the CSI mask is set by the upper layer, then:

[0332] 3> In the current symbol n, if, when evaluating all DRX action time conditions specified in this clause, the grant / assignment and DRX command MACCE / long DRX command MAC CE scheduled on the serving cell in this DRX group received 4ms prior to symbol n, the drx-onDurationTimer of the DRX group will not be running; and

[0333] 4> CSI on PUCCH is not reported in this DRX group.

[0334] Note 4: If the CSI configured on the PUCCH by the UE according to the procedure multiplexing specified in Clause 9.2.5 of TS 38.213[6] overlaps with other UCIs, and this CSI multiplexed with other UCIs will be reported on PUCCH resources outside the DRX action time of the DRX group in which this PUCCH is configured or outside the on-duration period of the DRX group in which this PUCCH is configured if the CSI masking is set by the upper layer, then the UE implementation shall decide whether to report this CSI multiplexed with other UCIs.

[0335] Regardless of whether the MAC entity is monitoring the PDCCH on the serving cell in the DRX group, the MAC entity will transmit HARQ feedback, aperiodic CSI on the PUSCH, and aperiodic SRS as defined in TS 38.214[7] on the serving cell in the DRX group when such a situation is anticipated.

[0336] If the PDCCH timing is incomplete (e.g., the activity time begins or ends in the middle of the PDCCH timing), then the MAC entity does not need to monitor the PDCCH.

[0337] 5.22 SL-SCH Data Transmission

[0338] 5.22.1 SL-SCH Data Transmission

[0339] 5.22.1.1 SL grants permission to receive and transmit SCI.

[0340] Sidelink grants are received dynamically on the PDCCH, either semi-statically configured by the RRC or autonomously selected by the MAC entity. The MAC entity determines the set of PSSCH durations for transmissions of SCI occurring on the active SL BWP, and the set of PSSCH durations for transmissions of SL-SCH associated with the SCI occurring on the active sidelink grant. Sidelink grants addressed to SLCS-RNTI with NDI=1 are considered dynamic sidelink grants.

[0341] If the MAC entity is configured with sidelink resource allocation mode 1 as indicated in TS 38.331[5], then the MAC entity shall, for each PDCCH timing and for each grant received for that PDCCH timing:

[0342] 1> If SL-RNTI for the MAC entity has been granted on the receiver side of the PDCCH:

[0343] 2> If the NDI received on the PDCCH has not yet undergone a bi-state switch compared to the value in the previously received HARQ information for the HARQ procedure ID:

[0344] 3> Use the received sidelink grant to determine the PSCCH duration and PSSCH duration for one or more retransmissions of a single MAC PDU for the corresponding sidelink procedure in accordance with clause 8.1.2 of TS 38.214[7].

[0345] 2> Otherwise:

[0346] 3> Use the received sidelink permission to determine the PSCCH duration and PSSCH duration for the initial transmission and (if available) multiple retransmissions of a single MAC PDU in accordance with Clause 8.1.2 of TS 38.214[7].

[0347] 2> If the side link is permitted to be used for (multiple) retransmissions of a MAC PDU that has been positively acknowledged as specified in Clause 5.22.1.3.1a:

[0348] 3> The side link is allowed to clear the PSCCH duration and PSSCH duration corresponding to the (multiple) retransmissions of the MAC PDU.

[0349] 1> Otherwise, if the SLCS-RNTI for the MAC entity has been granted on the receiver side of the PDCCH:

[0350] 2> If the PDCCH content indicates (multiple) retransmissions for the identified HARQ procedure ID that has been set for an active, configured sidelink-granted event identified by sl-ConfigIndexCG:

[0351] 3> Use the received side link permission to determine the PSCCH duration and PSSCH duration for one or more retransmissions of a single MACPDU in accordance with Clause 8.1.2 of TS 38.214[7].

[0352] 2> Otherwise, if the PDCCH content indicates that Configurable Approval Type 2 is disabled for Configurable Sidelinks:

[0353] 3> Trigger confirmation of configured side link permission for configured side link permission.

[0354] 2> Otherwise, if the PDCCH content indicates activation for Configurable Approval Type 2 configured for the configured sidelink:

[0355] 3> Trigger confirmation for configured side-links that have been granted permission;

[0356] 3> Storage is granted via configured sidelink;

[0357] 3> Initialize or reinitialize the set of PSCCH durations and the set of PSSCH durations determined by the configured side link criteria for the transmission of multiple MAC PDUs in accordance with Clause 8.1.2 of TS 38.214[7].

[0358] If the MAC entity is configured to use sidelink resource allocation mode 2 to transmit using a resource pool in the carrier based on sensing or random selection, as indicated in TS 38.331[5] or TS 36.331

[21] , then the MAC entity will perform the following procedures for each sidelink:

[0359] Note 1: If the MAC entity is configured with sidelink resource allocation mode 2 to use a resource pool in a carrier for transmission, as indicated in TS38.331[5] or TS 36.331

[21] , then the MAC entity may generate the selected sidelink grant on the resource pool only after the release of (a plurality of) configured sidelink grants (if any) based on random selection or sensing.

[0360] Note 2: The MAC entity expects PSFCH to always be configured by RRC for at least one resource pool in sl-TxPoolSelectedNormal and for a resource pool in sl-TxPoolExceptional when at least the logical channel configured with sl-HARQ-FeedbackEnabled is set to enabled.

[0361] 1> If the MAC entity has selected the configured sidelink permission to create a transmission corresponding to multiple MAC PDUs, and SL data is available in the logical channel:

[0362] 2> If the MAC entity has not yet selected a resource pool that can be used for the logical channel:

[0363] 3> If sl-HARQ-FeedbackEnabled is set to enabled for a logical channel:

[0364] 4> Select any resource pool configured to use PSFCH resources from the resource pools;

[0365] 3> Otherwise:

[0366] 4> Select any resource pool from the resource pools;

[0367] 2> Perform a TX resource selection (reselection) check on the selected resource pool as specified in Clause 5.22.1.2;

[0368] Note 3: The MAC entity continuously performs TX resource selection (reselection) checks until the corresponding resource pool is released by RRC, or the MAC entity decides to cancel the selected sidelink permission for creating a transmission corresponding to multiple MAC PDUs.

[0369] 2> If TX resource selection (reselection) is triggered due to TX resource selection (reselection) check:

[0370] 3> Select one of the allowed values ​​configured by RRC in sl-ResourceReservePeriodList, and set the resource reservation interval Prsvp_TX with the selected value;

[0371] Note 3A: The MAC entity selects a resource reservation interval value that is greater than the remaining PDB of available SL data in the logical channel.

[0372] 3> Within an interval [5,15] of resource reservation interval greater than or equal to 100ms, or within an interval of resource reservation interval less than 100ms. Integer values ​​are randomly selected with equal probability, and SL_RESOURCE_RESELECTION_COUNTER is set to the selected value;

[0373] 3> Select the number of HARQ retransmissions, which is derived from the allowed number in sl-MaxTxTransNumPSSCH contained in sl-PSSCH-TxConfigList as configured by RRC, and the highest priority of the (multiple) logical channels allowed on the carrier if configured by RRC, and the CBR measured by the lower layer according to clause 5.1.27 of TS 38.215

[24] (if the CBR measurement result is available) or the corresponding sl-defaultTxConfigIndex configured by RRC (if the CBR measurement result is not available) from the allowed number of overlapping allowed numbers in sl-MaxTxTransNumPSSCH indicated in sl-CBR-PriorityTxConfigList;

[0374] 3> Select the amount of frequency resources, which is within the range of sl-MinSubChannelNumPSSCH and sl-MaxSubchannelNumPSSCH contained in sl-PSSCH-TxConfigList as configured by RRC, and the highest priority of the (multiple) logical channels allowed on the carrier and the CBR measured by the lower layer according to clause 5.1.27 of TS 38.215

[24] (if the CBR measurement result is available) or the corresponding sl-defaultTxConfigIndex configured by RRC (if the CBR measurement result is not available) overlapping between MinSubChannelNumPSSCH and MaxSubchannelNumPSSCH indicated in sl-CBR-PriorityTxConfigList;

[0375] 3> If the random selection of transport is configured by the upper layer, then:

[0376] 4> Based on the amount of selected frequency resources and the remaining PDB of SL data available in the allowed logical channels on the carrier, randomly select time and frequency resources from the resource pool for a transmission opportunity.

[0377] 3> Otherwise:

[0378] 4> Based on the amount of selected frequency resources available in the (multiple) logical channels allowed on the carrier and the remaining PDB of the SL data, time and frequency resources are randomly selected for a transmission opportunity from the resources indicated by the physical layer as specified in Clause 8.1.4 of TS 38.214[7].

[0379] 3> Use randomly selected resources to select a set of periodic resources separated by resource reservation intervals for transmitting PSCCH and PSSCH corresponding to the number of transmission opportunities of the MAC PDU as determined in TS 38.214[7];

[0380] 3> If you choose to retransmit one or more HARQs:

[0381] 4> If the sense-based transmission is configured by the upper layer and, in accordance with Clause 8.1.4 of TS 38.214[7], available resources are reserved in the resources indicated by the physical layer for further transmission opportunities; or

[0382] 4> If the random selection of transport is configured by the upper layer and available resources are reserved in the resource pool for more transport opportunities:

[0383] 5> Based on the amount of selected frequency resources, the number of times HARQ retransmissions are selected, and the remaining PDB of SL data available in the logical channels allowed on the carrier, the PSFCH is configured for this resource pool and the retransmission resources may be randomly selected from the available resources for one or more transmission opportunities by ensuring a minimum time gap between any two selected resources, in accordance with Clause 8.3.1.1 of TS38.212[9] by the time resource allocation indication of the previous SCI;

[0384] 5> Use randomly selected resources to select a set of periodic resources separated by resource reservation intervals for transmitting PSCCH and PSSCH corresponding to the number of retransmission opportunities for the MAC PDU as determined in TS 38.214[7];

[0385] 5> Treat the first set of teleportation opportunities as the initial teleportation opportunities, and the other set of teleportation opportunities as re-teleportation opportunities;

[0386] 5> The set of initial transmission opportunities and retransmission opportunities is considered as the selected sidelink grant.

[0387] 3> Otherwise:

[0388] 4> The set is considered as a selected side link grant.

[0389] 3> Use selected sidelink permission to determine the PSCCH duration set and PSSCH duration set according to TS 38.214[7].

[0390] 2> Otherwise, if SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER equals 1, a MAC entity is randomly selected with equal probability, the probability being in the interval [0,1] and less than or equal to the probability value configured by RRC in sl-ProbResourceKeep;

[0391] 3> Clear the selected sidelink permission (if available);

[0392] 3> Within an interval [5,15] of resource reservation interval greater than or equal to 100ms, or within an interval of resource reservation interval less than 100ms. Integer values ​​are randomly selected with equal probability, and SL_RESOURCE_RESELECTION_COUNTER is set to the selected value;

[0393] 3> Reuse the previously selected sidelink to allow the number of MAC PDUs to be transmitted for the resource reservation interval determined in TS 38.214[7] to determine the set of PSCCH durations and the set of PSSCH durations according to TS 38.214[7].

[0394] 1> If the MAC entity has already selected the chosen sidelink permission to create (multiple) transmissions corresponding to a single MAC PDU, and if SL data is available in the logical channel, or if an SL-CSI report is triggered:

[0395] 2> If SL data is available in the logical channel:

[0396] 3> If sl-HARQ-FeedbackEnabled is set to enabled for a logical channel:

[0397] 4> Select any resource pool configured to use PSFCH resources from the resource pools;

[0398] 3> Otherwise:

[0399] 4> Select any resource pool from the resource pools;

[0400] 2> Otherwise, if an SL-CSI report is triggered:

[0401] 3> Select any resource pool from the resource pools.

[0402] 2> Perform a TX resource selection (reselection) check on the selected resource pool as specified in Clause 5.22.1.2;

[0403] 2> If TX resource selection (reselection) is triggered due to TX resource selection (reselection) check:

[0404] 3> Select the number of HARQ retransmissions, which is derived from the allowed number in sl-MaxTxTransNumPSSCH contained in sl-PSSCH-TxConfigList as configured by RRC, and the highest priority of the (multiple) logical channels allowed on the carrier if configured by RRC, and the CBR measured by the lower layer according to clause 5.1.27 of TS 38.215

[24] (if the CBR measurement result is available) or the corresponding sl-defaultTxConfigIndex configured by RRC (if the CBR measurement result is not available) from the allowed number of overlapping allowed numbers in sl-MaxTxTransNumPSSCH indicated in sl-CBR-PriorityTxConfigList;

[0405] 3> Select the amount of frequency resources, which is within the range of sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH contained in sl-PSSCH-TxConfigList as configured by RRC, and the highest priority of the (multiple) logical channels allowed on the carrier and the CBR measured by the lower layer according to clause 5.1.27 of TS 38.215

[24] (if the CBR measurement result is available) or the corresponding sl-defaultTxConfigIndex configured by RRC (if the CBR measurement result is not available) overlapping between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH indicated in sl-CBR-PriorityTxConfigList;

[0406] 3> If the random selection of transport is configured by the upper layer, then:

[0407] 4> Based on the amount of selected frequency resources, the remaining PDB of SL data available in the allowed logical channels on the carrier, and the delay requirements of the triggered SL CSI report, randomly select time and frequency resources from the resource pool for a transmission opportunity.

[0408] 3> Otherwise:

[0409] 4> Based on the amount of selected frequency resources and the remaining PDB of SL data available in the logical channels allowed on the carrier and / or the delay requirements of triggered SL-CSI reports, time and frequency resources for a transmission opportunity are randomly selected from the resources indicated by the physical layer, as specified in Clause 8.1.4 of TS 38.214[7].

[0410] 3> If you choose to retransmit one or more HARQs:

[0411] 4> If the sense-based transmission is configured by the upper layer and, in accordance with Clause 8.1.4 of TS 38.214[7], available resources are reserved in the resources indicated by the physical layer for further transmission opportunities; or

[0412] 4> If the random selection of transport is configured by the upper layer and available resources are reserved in the resource pool for more transport opportunities:

[0413] 5> In the case where a PSFCH is configured for this resource pool and resources can be retransmitted by the time resource assignment of the previous SCI in accordance with Clause 8.3.1.1 of TS 38.212[9], by ensuring the minimum time gap between any two selected resources, the time and frequency resources for one or more transmission opportunities are randomly selected from the available resources based on the amount of selected frequency resources, the selected number of HARQ retransmissions, the remaining PDB of SL data available in the logical channels allowed on the carrier, and / or the delay requirements of the triggered SL-CSI;

[0414] 5> The first teleportation opportunity in time will be considered the initial teleportation opportunity, and other teleportation opportunities will be considered as re-teleportation opportunities;

[0415] 5> Treat all transmission opportunities as granted on the selected side link;

[0416] 3> Otherwise:

[0417] 4> Treat the set as the selected sidelink grant;

[0418] 3> Use selected sidelink permission to determine the PSCCH duration and PSSCH duration according to TS 38.214[7].

[0419] Note 3B: If it is not possible to select retransmission resources by ensuring that resources can be selected by the time resource allocation indication of the previous SCI, then if the PSFCH is configured for this resource pool, the UE shall determine how to select time and frequency resources from available resources for one or more transmission opportunities by ensuring the minimum time gap between any two selected resources.

[0420] 1> If the selected sidelink is permitted to be used for (multiple) retransmissions of MACPDUs that have been affirmatively acknowledged as specified in Clause 5.22.1.3.3:

[0421] 2> Allow clearing of the PSCCH duration and PSSCH duration corresponding to the (multiple) retransmissions of the MAC PDU from the selected side link.

[0422] Note 3C: The UE implementation scheme determines how the MAC entity determines the remaining PDB of the SL data.

[0423] For the selected sidelink grant, the minimum time gap between any two selected resources includes:

[0424] - The time gap between the end of the last symbol of the PSSCH transmission of the first resource and the start of the first symbol of the corresponding PSFCH reception determined by sl-MinTimeGapPSFCH and sl-PSFCH-Period for the resource pool; and - the time required for PSFCH reception and processing, plus the time required for sidelink retransmission preparation including the necessary physical channel multiplexing, and any TX-RX / RX-TX switching time.

[0425] Note 4: The UE implementation scheme determines how to determine the time required for PSFCH reception and processing, plus sidelink retransmission preparation.

[0426] The MAC entity will apply to each PSSCH duration:

[0427] 1> For each link occurring during this PSSCH duration, the following is permitted:

[0428] 2> Select the allowed MCS table in the resource pool associated with the sidelink grant;

[0429] Note 4a: If more than one MCS table is configured, the selection of the MCS table shall be determined by the UE implementation scheme.

[0430] 2> If the MAC entity is already configured with sidelink resource allocation mode 1:

[0431] 3> Select the MCS (if configured) within the range of sl-MinMCS-PSSCH and sl-MaxMCS-PSSCH configured by RRC between the selected MCS table associated with sl-ConfigDedicatedNR;

[0432] 3> Set the resource reservation interval to 0ms.

[0433] 2> Otherwise:

[0434] 3> Select an MCS (if configured by RRC) within the range of sl-MinMCS-PSSCH and sl-MaxMCS-PSSCH associated with the selected MCS table contained in sl-PSSCH-TxConfigList, and (if configured by RRC) overlap between sl-MinMCS-PSSCH and sl-MaxMCS-PSSCH associated with the selected MCS table indicated in sl-CBR-PriorityTxConfigList for the highest priority of the side link logical channel in the MAC PDU, and the CBR measured by the lower layer according to clause 5.1.27 of TS 38.215

[24] if CBR measurement results are available, or the corresponding sl-defaultTxConfigIndex configured by RRC if CBR measurement results are unavailable;

[0435] 3> If the MAC entity decides not to use the selected sidelink, it is granted the next PSSCH duration corresponding to the initial transmission opportunity:

[0436] 4> Set the resource reservation interval to 0ms.

[0437] 3> Otherwise:

[0438] 4> Set the resource reservation interval to the selected value.

[0439] Note 5: If the MCS or the corresponding range is not configured by RRC, then the MCS selection depends on the UE implementation scheme.

[0440] 2> If the configured sidelink has been activated and this PSSCH duration corresponds to the first PSSCH transmission opportunity within this sl-PeriodCG that has been configured sidelinked:

[0441] 3> Set the HARQ procedure ID to the HARQ procedure ID associated with this PSSCH duration, and if available, grant permission for all subsequent PSSCH durations occurring in this sl-PeriodCG for the configured sidelink;

[0442] 3> Determine the duration of this PSSCH for the initial transfer;

[0443] 3> Clear the HARQ buffer of the sidelink procedure associated with the HARQ procedure ID.

[0444] 2> For this PSSCH duration, the sidelink grant, selected MCS, and associated HARQ information are delivered to the sidelink HARQ entity.

[0445] For the HARQ process ID associated with the first time slot transmitted with SL, which is configured for sidelink permission, it is derived from the following equation:

[0446] HARQ process ID=[floor(CURRENT_slot / PeriodicitySL)]modulo sl-NrOfHARQ-Processes+sl-HARQ-ProcID-offset

[0447] CURRENT_slot refers to the current logical slot in the associated resource pool, and PeriodicitySL is defined in Clause 5.8.3.

[0448] 5.22.1.2 TX Resource (Re)Selection Check

[0449] If a TX resource selection (reselection) check procedure is triggered on the selected resource pool used for the sidelink procedure pursuant to Clause 5.22.1.1, then the MAC entity will target the sidelink procedure as follows:

[0450] 1> If SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER equals 1, randomly select MAC entities with equal probability, the probability being a value in the interval [0,1] higher than the probability configured by RRC in sl-ProbResourceKeep; or

[0451] 1> If the resource pool is configured or reconfigured by RRC; or

[0452] 1> If the selected sidelink is not available in the selected resource pool; or

[0453] 1> If the MAC entity does not perform a transfer or retransmission for any resource indicated in the selected sidelink grant during the last second; or

[0454] 1> If sl-ReselectAfter is configured, and the number of consecutive unused transmission opportunities on the resources indicated in the selected sidelink grant is equal to sl-ReselectAfter, the number is incremented by 1 when the resources granted by the selected sidelink within the resource reservation interval are not used; or

[0455] 1> If the selected sidelink permission cannot accommodate the RLC SDU by using the maximum allowed MCS configured in the sl-MaxMCS-PSSCH associated with the selected MCS table, and the UE selects non-fragmented RLC SDU; or

[0456] Note 1: If the selected sidelink permission cannot accommodate the RLC SDU, the UE implementation scheme shall determine whether to perform segmentation or reselect sidelink resources.

[0457] 1> If the transmission granted by the selected sidelink cannot satisfy the remaining PDB of data in the logical channel according to the associated priority, and the MAC entity chooses not to perform the transmission corresponding to a single MAC PDU:

[0458] Note 2: If the remaining PDB is not satisfied, the UE implementation scheme shall determine whether to perform a transmission corresponding to a single MAC PDU or a sidelink resource reselection.

[0459] Note 3: The UE implementation scheme determines whether TX resource selection (reselection) is triggered due to the latency requirement of MAC CE triggered under clause 5.22.1.7.

[0460] 2> Clear the selected sidelink permissions associated with the sidelink procedure (if available);

[0461] 2> Trigger TX resource (re)selection.

[0462] Note 4: Empty.

[0463] Note 5: Empty.

[0464] 5.22.1.2a Reassessment and Pre-allocation

[0465] Before the time slot in which the SCI indicating the resource is first signaled, at T3 the physical layer re-evaluates the resources granted to the selected side link for transmission from multiplexed and aggregated entities by the MACPDU, as specified in Clause 8.1.4 of TS 38.214[7].

[0466] Prior to locating a time slot with available resources, a pre-occupancy check of the physical layer MAC PDU can be performed at T3 for resources already granted by the selected side link as previously indicated by the SCI, as specified in Clause 8.1.4 of TS 38.214[7].

[0467] Note 1: The reassessment or pre-occupancy depends on the UE implementation and may occur before 'm-T3' or after 'm-T3' but before 'm'. For reassessment, m is the time slot in which the SCI indicating the resource is first signaled, as specified in Clause 8.1.4 of TS 38.214. For pre-occupancy, m is the time slot in which the resource is located, as specified in Clause 8.1.4 of TS 38.214.

[0468] If the MAC entity is configured to use sidelink resource allocation mode 2 to transmit using a resource pool in the carrier based on sensing or random selection, as indicated in TS 38.331[5] or TS 36.331

[21] , then the MAC entity will perform the following procedures for each sidelink:

[0469] 1> If the indicated resources not previously granted by the selected sidelink identified by the SCI are to be used for reassessment through the physical layer, as specified in Clause 8.1.4 of TS 38.214[7]; or

[0470] 1> If the indication has been made for any resources already granted by the selected sidelink as previously indicated by the SCI to be used for physical layer pre-allocation, as specified in Clause 8.1.4 of TS 38.214[7]:

[0471] 2> Grant permission to remove resources from the selected sidelink associated with the sidelink procedure;

[0472] 2> Based on the amount of selected frequency resources, the number of times HARQ retransmissions are selected, and the remaining PDB of any SL data available in the logical channel, the PSFCH is configured for this resource pool and the resources can be randomly selected from the resources indicated by the physical layer as specified in Clause 8.3.1.1 of TS 38.212[9], in the case of time resource allocation for retransmission of SCI, by ensuring the minimum time gap between any two selected resources permitted by the selected side link, for removing or discarding resources, time and frequency resources are randomly selected from the resources indicated by the physical layer as specified in Clause 8.1.4 of TS 38.214[7].

[0473] Note 2: If it is not possible to select retransmission resources by ensuring that resources can be selected by the time resource allocation indication of the previous SCI, then if the PSFCH is configured for this resource pool, the UE implementation determines how to select time and frequency resources from available resources for one or more transmission opportunities by ensuring the minimum time gap between any two selected resources.

[0474] 2> Replace the removed or discarded resources with selected resources (multiple) used to grant permission to the selected side link.

[0475] Note 3: The UE implementation scheme may decide to reselect any pre-selected but non-reserved resource, except for resources indicated by pre-occupancy or re-evaluation through the physical layer during reselection triggered by reassessment or pre-occupancy indicated by the physical layer.

[0476] Note 4: Whether to set a resource reservation interval in the reselected resources to replace the pre-reserved resources depends on the UE implementation plan.

[0477] Note 5: Whether resource reselection is triggered due to cancellation of priority ordering, as specified in Clause 16.2.4 of TS 38.213[6], Clause 5.14.1.2.2 and Clause 5.22.1.3.1a of TS 36.321

[22] , depends on the UE implementation scheme.

[0478] Note 6: For selected sidelink grants corresponding to multiple MAC PDUs, whether to apply a re-evaluation check to resources in non-initial reserved periods that were not sent in the immediate previous period or in the current period depends on the UE implementation scheme.

[0479] 5.22.1.3 Sidelink HARQ Operation

[0480] 5.22.1.3.1 Sidelink HARQ Entity

[0481] A MAC entity contains at most one sidelink HARQ entity for transmission on the SL-SCH, thereby maintaining multiple parallel sidelink processes.

[0482] The maximum number of transport sidelink procedures associated with a sidelink HARQ entity is 16. Sidelink procedures can be configured to transport multiple MAC PDUs. To transport multiple MAC PDUs in sidelink resource allocation mode 2, the maximum number of transport sidelink procedures associated with a sidelink HARQ entity is 4.

[0483] The sidelink grant and its associated sidelink transmission information are associated with the sidelink procedure. Each sidelink procedure supports one TB.

[0484] For each sidelink grant, the sidelink HARQ entity will:

[0485] 1> If the MAC entity determines that the sidelink is permitted for the initial transmission, as specified in Clause 5.22.1.1; or

[0486] 1> If sidelink grant is configured and no MAC PDU is obtained in the configured sidelink-granted sl-PeriodCG:

[0487] Note 1: Empty.

[0488] 2> Reassociate the sidelink procedure to this permission, and for the associated sidelink procedure:

[0489] Note 1A: The sidelink HARQ entity will enable the selected sidelink to be associated with the sidelink procedure determined by the MAC entity.

[0490] 3> Obtain the MAC PDU to transfer from the multiplexed and aggregated entity (if it exists);

[0491] 3> If the MAC PDU for transmission has already been obtained:

[0492] 4> If HARQ procedure IDs have been set for the sidelink, then:

[0493] 5> Reassociate the HARQ procedure ID corresponding to the sidelink grant with the sidelink procedure;

[0494] Note 1a: There is a one-to-one mapping between HARQ procedure IDs and sidelink procedures in MAC entities configured with sidelink resource allocation mode 1.

[0495] 4> The following determines the sidelink transmission information for the TB used in the source and destination pairs of the MAC PDU:

[0496] 5> Set the source layer 1 ID to 8 LSBs of the source layer 2 ID of the MAC PDU;

[0497] 5> Set the destination layer 1 ID to 16 LSB of the destination layer 2 ID of the MAC PDU;

[0498] 5> Reassociate the sidelink procedure with the sidelink procedure ID;

[0499] Note 1b: How the UE determines the sidelink procedure ID in the SCI depends on the UE implementation scheme for the NR sidelink.

[0500] 5> It is assumed that the NDI has undergone a bi-state switch compared to the previously transmitted values ​​of the side link identification information and side link procedure ID corresponding to the MAC PDU, and the NDI is set to the bi-state switch value;

[0501] Note 2: The initial value of NDI set for the first transmission of the associated side link procedure depends on the UE implementation scheme.

[0502] Note 3: Empty.

[0503] 5> Set the broadcast type indicator to one of broadcast, multicast, or unicast as indicated by the upper layer;

[0504] 5> If HARQ feedback has been enabled for the MAC PDU in accordance with clause 5.22.1.4.2;

[0505] 6> Set the HARQ feedback enable / disable indicator to enabled.

[0506] 5> Otherwise:

[0507] 6> Set the HARQ feedback enable / disable indicator to disabled.

[0508] 5> Set the priority to the highest priority value of the logical channel (if present) and MAC CE (if included) in the MAC PDU;

[0509] 5> If HARQ feedback is enabled for multicast:

[0510] 6> If the group size and member ID are both provided by the upper layer and the group size is no greater than the number of candidate PSFCH resources associated with this side link, then:

[0511] 7> Choose to confirm with affirmation or only with negation.

[0512] Note 4: The choice between affirmative-negative confirmation or negative confirmation only depends on the UE implementation scheme.

[0513] 5> Set the redundant version as the selected value.

[0514] 6> Otherwise:

[0515] 7> Select to only deny confirmation.

[0516] 6> If only negative confirmation is selected, the UE's location information is available, and sl-TransRange is configured for the logical channel in the MACPDU, and sl-ZoneConfig is configured as specified in TS 38.331[5], then:

[0517] 7> Set the communication range requirement to the value of the longest communication range of the logical channel in the MAC PDU;

[0518] 7> Determine the value of sl-ZoneLength corresponding to the communication range requirement, and set Zone_id to the value of Zone_id calculated using the determined value of sl-ZoneLength, as specified in TS 38.331[5].

[0519] 4> Deliver the TB's MAC PDU, sidelink grant, and sidelink transmission information to the associated sidelink process;

[0520] 4> Indicates that the associated side link process triggers a new transmission.

[0521] 3> Otherwise:

[0522] 4> Clear the HARQ buffer of the associated side link process.

[0523] 1> Otherwise (i.e., retransmit):

[0524] 2> If the HARQ procedure ID corresponding to the sidelink grant received on the PDCCH, the configured sidelink grant, or the selected sidelink grant is associated with a sidelink procedure whose HARQ buffer is empty; or

[0525] 2> If the HARQ procedure ID corresponding to the sidelink grant received on the PDCCH is not associated with any sidelink procedure, then:

[0526] 3> Ignore sidelink permission.

[0527] 2> Otherwise:

[0528] 3> Identify the sidelink procedure associated with this permission, and for the associated sidelink procedure:

[0529] 4> Grant sidelink permission to deliver the MAC PDU to the associated sidelink procedure;

[0530] 4> Indicates that the associated side link process triggers a retransmission.

[0531] 5.22.1.3.1a Side Link Process

[0532] The side link process is associated with the HARQ buffer.

[0533] New and retransmissions are performed on the resources indicated in the sidelink grant specified in Clause 5.22.1.1, using the MCS selected as specified in Clauses 8.1.3.1 and 5.22.1.1 of TS38.214[7].

[0534] If the sidelink procedure is configured to perform the transmission of multiple MAC PDUs using sidelink resource allocation mode 2, then the procedure maintenance counter SL_RESOURCE_RESELECTION_COUNTER is used. This counter is not available for other sidelink procedure configurations.

[0535] The priority of a MAC PDU is determined by the highest priority of the logical channel or the MAC CE in the MAC PDU.

[0536] If the sidelink HARQ entity requests a new transmission, then the sidelink procedure should be:

[0537] 1> Store the MAC PDU in the associated HARQ buffer;

[0538] 1> Store the sidelink grant received from the sidelink HARQ entity;

[0539] 1> The transmission is generated as described below.

[0540] If the sidelink HARQ entity requests a retransmission, then the sidelink procedure should be:

[0541] 1> Store the sidelink grant received from the sidelink HARQ entity;

[0542] 1> The transmission is generated as described below.

[0543] In order to generate a transmission, the sidelink process should:

[0544] 1> If there is no uplink transmission; or

[0545] 1> If the MAC entity can perform uplink and sidelink transmissions simultaneously during transmission; or

[0546] 1> If another MAC entity and the MAC entity are respectively capable of simultaneously performing uplink transmission and sidelink transmission during transmission; or

[0547] 1> If a MAC PDU exists in the uplink for this duration, except for MAC PDUs obtained from the Msg3 buffer, MSGA buffer, or those prioritized as specified in Clause 5.4.2.2, and sidelink transmissions take precedence over uplink transmissions:

[0548] 2> Instruct the physical layer to allow the transmission of SCI along with the associated sidelink information, based on the stored sidelink information;

[0549] 2> Instruct the physical layer to generate a transmission based on the stored side link;

[0550] 2> If HARQ feedback has been enabled for MAC PDU according to clause 5.22.1.4.2:

[0551] 3> Instruct the physical layer to monitor the PSFCH used for transmission and perform PSFCH reception as specified in Clause 5.22.1.3.2.

[0552] 2> If sl-PUCCH-Config is configured by RRC for stored sidelink permissions:

[0553] 3> Determine the confirmed transmission on the PUCCH as specified in Clause 5.22.1.3.2.

[0554] 1> If this transfer corresponds to the last transfer of the MAC PDU:

[0555] 2> Decrement SL_RESOURCE_RESELECTION_COUNTER by 1 (if available).

[0556] Note 1: If the number of HARQ retransmissions selected by the MAC entity has been reached, or if a positive acknowledgment has been received for the transmission of the MAC PDU, or if negative acknowledgment only is enabled in the SCI and no negative acknowledgment has been received for the transmission of the MAC PDU, then the MAC entity determines that this transmission corresponds to the previous transmission of the MAC PDU used for sidelink resource allocation mode 2. How the previous transmission is determined in other cases depends on the UE implementation scheme.

[0557] 1> If the highest priority sl-MaxTransNum corresponding to the logical channel in the MAC PDU has been configured by RRC in the sl-CG-MaxTransNumList for sidelink granting and the number of MAC PDU transmissions has reached sl-MaxTransNum; or

[0558] 1> If a positive acknowledgment of this transmission of the MAC PDU has been received in accordance with Clause 5.22.1.3.2; or

[0559] 1> If negative acknowledgment only is enabled in SCI and no negative acknowledgment is received for this transmission of the MAC PDU according to clause 5.22.1.3.2:

[0560] 2> Clear the HARQ buffer of the associated side link process.

[0561] If the following conditions are met, then the transmission of the MAC PDU takes precedence over the uplink transmission of the MAC entity or another MAC entity:

[0562] 1> If the MAC entity cannot simultaneously perform this-side link transmission and all uplink transmissions during transmission, and

[0563] 1> If the uplink transmission is neither prioritized as specified in Clause 5.4.2.2 nor prioritized by the upper layer according to TS23.287

[19] ; ​​and

[0564] 1> If sl-PrioritizationThres is configured, and if the highest priority value of MAC CE in the logical channel or MAC PDU is lower than sl-PrioritizationThres.

[0565] Note 2: If the MAC entity is unable to perform this sidelink transmission at the same time as all uplink transmissions as specified in Clause 5.4.2.2 of TS 36.321

[22] , and priority ordering information is unavailable before the time of this sidelink transmission due to processing time constraints, then whether to perform this sidelink transmission depends on the UE implementation scheme.

[0566] 5.22.1.3.2 PSFCH Reception

[0567] The MAC entity will transmit for each PSSCH:

[0568] 1> If an acknowledgment corresponding to the PSSCH transmission in Clause 5.22.1.3.1a is obtained from the physical layer:

[0569] 2> For the sidelink process, the acknowledgment will be passed to the corresponding sidelink HARQ entity;

[0570] 1> Otherwise:

[0571] 2> For the sidelink process, the negative acknowledgment will be passed to the corresponding sidelink HARQ entity;

[0572] 1> If a PSSCH transfer occurs for a pair of source layer 2IDs and destination layer 2IDs corresponding to a PC5-RRC connection already established by the upper layer:

[0573] 2> Perform a HARQ-based sidelink RLF detection procedure as specified in Clause 5.22.1.3.3.

[0574] If sl-PUCCH-Config is configured by RRC, then for the timing of PUCCH transmission, the MAC entity will:

[0575] 1> If the timeAlignmentTimer associated with the TAG of the serving cell that will transmit HARQ feedback stops or expires:

[0576] 2> Instruct the physical layer to confirm the data generated in this TB.

[0577] 1> Otherwise, if a MAC PDU has already been granted for the sidelink associated with the PUCCH transmission timing in Clause 5.22.1.3.1, then the MAC entity will:

[0578] 2> If the most recent transmission of the MAC PDU was not prioritized as specified in Clause 5.22.1.3.1a:

[0579] 3> According to Clause 16.5 of TS 38.213[6], the physical layer is instructed to transmit a negative acknowledgment on the PUCCH.

[0580] 2> Otherwise, if HARQ feedback is disabled for the MAC PDU and a next retransmission of the MAC PDU is not required:

[0581] 3> According to Clause 16.5 of TS 38.213[6], the physical layer is instructed to send a positive acknowledgment on the PUCCH corresponding to the transmission.

[0582] 2> Otherwise, if HARQ feedback is disabled for the MAC PDU and no sidelink permission is available for the next retransmission of the MAC PDU (including if HARQ feedback is disabled for the MAC PDU and the sl-MaxTransNum corresponding to the highest priority logical channel in the MAC PDU has been configured by RRC in the sl-CG-MaxTransNumList for sidelink permission, and the number of transmissions of the MAC PDU has not reached sl-MaxTransNum after all PSSCH durations in the sl-PeriodCG for sidelink permission), (if present):

[0583] 3> According to Clause 16.5 of TS 38.213[6], the physical layer is instructed to send a negative acknowledgment on the PUCCH corresponding to the transmission.

[0584] 2> Otherwise:

[0585] 3> According to Clause 16.5 of TS 38.213[6], the physical layer is instructed to send an acknowledgment corresponding to the transmission on the PUCCH.

[0586] 1> Otherwise:

[0587] 2> According to Clause 16.5 of TS 38.213[6], the physical layer is instructed to send an affirmative acknowledgment on the PUCCH.

[0588] 5.22.1.3.3 HARQ-based sidelink RLF detection

[0589] The HARQ-based sidelink RLF detection procedure is used to detect sidelink RLF based on the number of consecutive DTXs during PSFCH reception for PC5-RRC connections.

[0590] The RRC configuration uses the following parameters to control HARQ-based sidelink RLF detection:

[0591] -sl-maxNumConsecutiveDTX.

[0592] The following UE variables are used for HARQ-based sidelink RLF detection.

[0593] -NumConsecutiveDTX is maintained for each PC5-RRC connection.

[0594] The sidelink HARQ entity should (re)initialize numConsecutiveDTX to zero immediately after the establishment of the PC5-RRC connection or the (re)configuration of sl-maxNumConsecutiveDTX for each PC5-RRC connection established by the upper layer (if it exists).

[0595] The sidelink HARQ entity should, for each PSFCH reception timing associated with the PSSCH transmission,:

[0596] 1> If PSFCH reception is not available at the PSFCH reception time:

[0597] 2> Increment numConsecutiveDTX by 1;

[0598] 2> If numConsecutiveDTX reaches sl-maxNumConsecutiveDTX:

[0599] 3> Instruct the RRC to perform HARQ-based sidelink RLF detection.

[0600] 1> Otherwise:

[0601] 2> Reinitialize numConsecutiveDTX to zero.

[0602] 5.22.1.4 Multiplexing and Combining

[0603] For a PDU associated with an SCI, the MAC will consider only the logical channel with the same source tier 2 ID - destination tier 2 ID pair among unicast, multicast, and broadcast. This allows multiple transmissions for different sidelink procedures to be executed independently during different PSSCH durations.

[0604] 5.22.1.4.1 Logical Channel Prioritization

[0605] 5.22.1.4.1.1 General Provisions

[0606] Whenever a new transmission is executed, the sidelink logical channel prioritization procedure is applied.

[0607] The RRC control side schedules link data through signaling for each logical channel:

[0608] -sl-Priority, where the increased priority value indicates a lower priority;

[0609] -sl-PrioritisedBitRate sets the sidelink priority bit rate (sPBR);

[0610] -sl-BucketSizeDuration sets the duration of the sidelink bucket size (sBSD).

[0611] RRC further controls the LCP procedure by configuring mapping limits for each logical channel:

[0612] -sl-configuredGrantType1Allowed specifies whether type 1 is allowed for sidelink transmission;

[0613] -sl-AllowedCG-List, which sets the allowed configured permissions for sidelink transmissions;

[0614] -sl-HARQ-FeedbackEnabled sets whether logical channels are allowed to be multiplexed when sl-HARQ-FeedbackEnabled is enabled or disabled.

[0615] The following UE variables are used in the logical channel prioritization procedure:

[0616] -SBj, which is maintained for each logical channel j.

[0617] When establishing a logical channel, the MAC entity should initialize the logical channel's SBj to zero.

[0618] For each logical channel j, the MAC entity should:

[0619] 1> Before each instance of the LCP program, increment the product sPBR×T of SBj, where T is the time elapsed since the last increment of SBj;

[0620] 1> If the value of SBj is greater than the sidelink bucket size (i.e., sPBR × sBSD):

[0621] 2> Set SBj to the size of the sidelink bucket.

[0622] Note: The exact timing of the UE updating SBj during the LCP procedure depends on the UE implementation scheme, as long as SBj is up-to-date when it is approved by the LCP.

[0623] 5.22.1.4.1.2 Selection of Logical Channel

[0624] For each SCI corresponding to a new transmission, the MAC entity should:

[0625] 1> Select a destination associated with one of unicast, multicast, and broadcast, which has at least one of the following logical channels and logical channels with the highest priority among those satisfying all of the following conditions:

[0626] 2>SL data can be used for transmission; and

[0627] 2> In the case of any logical channel having SBj>0, SBj>0; and

[0628] 2> When configured, sl-configuredGrantType1Allowed is set to true if the SL grant is configured as grant type 1; and

[0629] 2> When configured, sl-AllowedCG-List contains a configured permission index associated with SL permission; and

[0630] 2> If PSFCH is not configured for SL associated with SCI, then sl-HARQ-FeedbackEnabled is set to disabled.

[0631] Note 1: If multiple destinations have the same highest priority logical channel that satisfies all of the above conditions, or if multiple destinations have MAC CE and / or logical channels with the same priority as MAC CE that satisfy all of the above conditions, then the choice of which destination to select depends on the UE implementation scheme.

[0632] 1> Select a logical channel from the logical channels belonging to the selected destination that meets all of the following conditions:

[0633] 2>SL data can be used for transmission; and

[0634] 2> When configured, sl-configuredGrantType1Allowed is set to true if SL grant is configured as grant type 1; and

[0635] 2> If configured, sl-AllowedCG-List contains a configured grant index associated with SL grants; and 3> If PSFCH is configured to be used for sidelink grants associated with SCI:

[0636] 4> If sl-HARQ-FeedbackEnabled is enabled for the highest priority logical channel that meets the above conditions, then sl-HARQ-FeedbackEnabled is enabled; or

[0637] 4> If sl-HARQ-FeedbackEnabled is set to disabled for the highest priority logical channel that meets the above conditions, then sl-HARQ-FeedbackEnabled is set to disabled.

[0638] 3> Otherwise:

[0639] 4> sl-HARQ-FeedbackEnabled is set to disabled.

[0640] Note 2: For the transmission of MAC PDUs that only carry CSI report MAC CE, sl-HARQ-FeedbackEnabled is set to disabled.

[0641] 5.22.1.4.1.3 Allocation of Sidelink Resources

[0642] For each SCI corresponding to a new transmission, the MAC entity should:

[0643] 1> Allocate resources to logical channels as follows:

[0644] 2> In Clause 5.22.1.4.1.2, for SL, selected logical channels where SBj>0 are permitted to be allocated resources in descending priority order. If the sPBR of a logical channel is set to infinity, the MAC entity shall allocate resources for all data available for transmission on the logical channel before satisfying the sPBR of the lower priority logical channel;

[0645] 2> Decrement SBj by the total size of the MAC SDU serving the above logical channel j;

[0646] 2. If any resources are reserved, all logical channels selected in Clause 5.22.1.4.1.2 shall be served in strictly decreasing priority order (regardless of the value of SBj) until the data or SL permitted for said logical channel is exhausted, whichever comes first. Logical channels configured with the same priority shall be provided equally.

[0647] Note: The value of SBj can be negative.

[0648] The UE will also follow the following rules during the above SL scheduling procedure:

[0649] - If the entire SDU (or a partially transmitted SDU or a retransmitted RLC PDU) is fitted into the remaining resources of the associated MAC entity, then the UE should not segment the RLC SDU (or a partially transmitted SDU or a retransmitted RLC PDU).

[0650] - If the UE segments the RLC SDU from the logical channel, it will maximize the size of the segment to fill the authorization of the associated MAC entity as much as possible;

[0651] - The UE should maximize data transmission;

[0652] - If a MAC entity is given a sidelink permission size of 12 bytes or more, and there is available data and it is allowed to be transmitted (in accordance with Clause 5.22.1.4.1), the MAC entity should not transmit padding alone.

[0653] - Logical channels configured with sl-HARQ-FeedbackEnabled that are set to enabled and logical channels configured with sl-HARQ-FeedbackEnabled that are set to disabled cannot be multiplexed into the same MAC PDU.

[0654] A MAC entity should not generate a MAC PDU for a HARQ entity if the following conditions are met:

[0655] - There is no sidelink CSI report MACCE generated for this PSSCH transmission as specified in Clause 5.22.1.7; and

[0656] - A MAC PDU contains zero MAC SDUs.

[0657] Logical channels should be prioritized according to the following order (highest priority listed first):

[0658] -Data from SCCH;

[0659] - Side link CSI report MAC CE;

[0660] - Data from any STCH.

[0661] 5.22.1.4.2 Multiplexing of MAC Control Elements and MAC SDUs

[0662] The MAC entity shall, in accordance with Clauses 5.22.1.4.1 and 6.1.6, multiplex the MAC CE and MAC SDU in the MAC PDU.

[0663] 5.22.2 SL-SCH Data Reception

[0664] 5.22.2.1 SCI Reception

[0665] The SCI indicates whether a transmission exists on the SL-SCH and provides relevant HARQ information. The SCI consists of two parts: the Level 1 SCI on the PSCCH and the Level 2 SCI on the PSSCH, as specified in Clause 8.1 of TS 38.214[7].

[0666] MAC entities will:

[0667] 1> Duration of each PSCCH monitored by the MAC entity during the period:

[0668] 2> If Level 1 SCI has already been received on PSCCH:

[0669] 3> Determine the set of PSSCH durations for the portion of the received data that uses SCI to receive the second-level SCI and transport blocks;

[0670] 3> If a Level 2 SCI for this PSSCH duration has already been received on the PSSCH:

[0671] 4> Store the SCI as an SCI valid for the duration of the PSSCH corresponding to the transmission of the transport block and the associated HARQ and QoS information;

[0672] 1> For a MAC entity, for each PSSCH duration with a valid SCI:

[0673] 2> Deliver the SCI and associated sidelink transmission information to the sidelink HARQ entity.

[0674] 5.22.2.2 Sidelink HARQ Operation

[0675] 5.22.2.2.1 Sidelink HARQ Entity

[0676] At most one sidelink HARQ entity exists at the MAC entity for SL-SCH reception, thereby maintaining multiple parallel sidelink processes.

[0677] Each sidelink procedure is associated with an SCI of interest to the MAC entity. This interest is determined by the SCI's sidelink identification information. The sidelink HARQ entity will direct the sidelink transmission information received on the SL-SCH and the associated TB to the corresponding sidelink procedure.

[0678] The number of receive sidelink procedures associated with the sidelink HARQ entity is defined in TS 38.306[5].

[0679] For each PSSCH duration, the sidelink HARQ entity will:

[0680] 1> For each SCI that is valid during this PSSCH duration:

[0681] 2> If the NDI has undergone a bi-state switch compared to the previously received transmission of the sidelink identification information and sidelink procedure ID corresponding to the SCI, or if this is the first transmission received for the pair of sidelink identification information and sidelink procedure ID for the SCI:

[0682] 3> If a sidelink procedure exists that is associated with the SCI's sidelink identification information and sidelink procedure ID:

[0683] 4> It is assumed that the side link process is not occupied;

[0684] 4> Clear the soft buffer of the side link process.

[0685] 3> The TB received from the physical layer, along with the associated sidelink identification information and sidelink procedure ID, will be allocated to an unused sidelink procedure;

[0686] 3> Associate the sidelink procedure with the sidelink identification information and sidelink procedure ID of this SCI, and treat this transmission as a new transmission.

[0687] Note 1: When a new TB arrives, the sidelink HARQ entity will assign the TB to any unoccupied sidelink procedure. If there are no unoccupied sidelink procedures in the sidelink HARQ entity, then how to manage the receive sidelink procedure depends on the UE implementation scheme.

[0688] Note 1a: If the NDI has not yet undergone a dual-state switch compared to the previously received value of the sidelink procedure ID corresponding to the sidelink identification information and SCI, and if there is no sidelink procedure associated with the sidelink identification information and SCI sidelink procedure ID, then the handling of the corresponding TB depends on the UE implementation scheme.

[0689] 1> For each side of the link process:

[0690] 2> If it is a sidelink procedure, based on its associated SCI, the NDI has not yet undergone a bi-state switch compared to the previously received transmitted values ​​of the sidelink identification information and sidelink procedure ID corresponding to the SCI:

[0691] 3> The TB received from the physical layer will be allocated to the side link process, and this transmission will be treated as a retransmission.

[0692] Note 2: A single sidelink procedure can be (re)associated with only a single combination of sidelink identification information and sidelink procedure ID at any given time, and a single combination of sidelink identification information and sidelink procedure ID can be (re)associated with only a single sidelink procedure at any given time.

[0693] 5.22.2.2.2 Side Link Process

[0694] For each PSSCH duration during which a transmission occurs in the sidelink process, a TB and associated HARQ information are received from the sidelink HARQ entity.

[0695] For each received TB and associated sidelink transmission information, the sidelink process will be:

[0696] 1> If this is a new teleport:

[0697] 2> Attempt to decode the received data.

[0698] 1> Otherwise, if this is a retransmission:

[0699] 2> If this TB of data has not yet been successfully decoded, then:

[0700] 3> Instruct the physical layer to combine the received data with the data currently in the soft buffer for this TB, and attempt to decode the combined data.

[0701] 1> If the MAC entity successfully decodes the data it attempted to decode for this TB; or

[0702] 1> If the data used for this TB was previously successfully decoded:

[0703] 2> If this is the first successful decoding of this TB of data:

[0704] 3> If this TB is associated with unicast, the DST field of the decoded MAC PDU sub-header is equal to 8MSB of any source layer 2 ID of the UE, where 16LSB is equal to the destination ID in the corresponding SCI, and the SRC field of the decoded MAC PDU sub-header is equal to 16MSB of any destination layer 2 ID of the UE, where 8LSB is equal to the source ID in the corresponding SCI; or

[0705] 3> If this TB is associated with multicast or broadcast, and the DST field of the decoded MAC PDU subheader is equal to 8MSB of any destination layer 2ID of the UE, where 16LSB is equal to the destination ID in the corresponding SCI:

[0706] 4> Pass the decoded MAC PDU to the demultiplexing and multiplexing entity;

[0707] 2> It is assumed that the side link process is not occupied.

[0708] 1> Otherwise:

[0709] 2> Instruct the physical layer to replace the data in the soft buffer used for this TB with the data that the MAC entity attempts to decode.

[0710] 1> If HARQ feedback is enabled via SCI:

[0711] 2> If only the negative confirmation is indicated by SCI according to Clause 8.4.1 of TS 38.212[9]:

[0712] 3> If the UE's location information is available, and the distance between the UE's location and the center location of the nearest zone calculated based on the Zone_id in the SCI and the value of sl-ZoneLength corresponding to the communication range requirement in the SCI as specified in TS 38.331[5] is less than or equal to the communication range requirement in the SCI; or

[0713] 3> If neither Zone_id nor communication range requirements are indicated by SCI; or

[0714] 3> If the UE's location information is unavailable:

[0715] 4> If the data that the MAC entity attempted to decode for this TB was not successfully decoded, or if the data for this TB was not successfully decoded previously:

[0716] 5> Instruct the physical layer to generate a negative acknowledgment of the data in this TB.

[0717] 2> If the negative-positive acknowledgment or unicast is directed by SCI according to Clause 8.4.1 of TS 38.212[9]:

[0718] 3> If the data that the MAC entity attempted to decode for this TB was successfully decoded, or if the data for this TB was previously successfully decoded:

[0719] 4> Indicates that the physical layer has generated a positive confirmation of the data in this TB.

[0720] 3> Otherwise:

[0721] 4> Instruct the physical layer to generate a negative acknowledgment of the data in this TB.

[0722] In 3GPP 38.331 ([2] 3GPP TS 38.331 V16.7.0), the slot offset for Uu DRX is described.

[0723] -DRX-Config

[0724] IE DRX-Config is used to configure DRX-related parameters.

[0725] DRX-Config information element

[0726]

[0727]

[0728]

[0729]

[0730] The calculations for slot offset and start-up offset are discussed in the 3GPP RAN2#116 meeting ([3] 3GPP RAN2#116 - Electronic Conference Report):

[0731]

[0732] In the RAN2#117 electronic meeting ([4] 3GPP RAN2#117 electronic meeting report), it was agreed to initiate offset calculation:

[0733]

[0734] In the MAC CR (Draft R2-2203673CR of TS 38.321 for sidelink enhancement) used to introduce SL DRX, the slot offset and start-up offset for broadcast and multicast are calculated:

[0735] 5.x.1 UE behavior in receiving SL-SCH data

[0736] When the SL DRX loop is configured, the duration includes the time for the following cases:

[0737] -sl-drx-onDurationTimer or sl-drx-InactivityTimer is running; or

[0738] -sl-drx-RetransmissionTimer is running; or

[0739] - In the absence of a reported MAC CE SL-CSI, the sl-LatencyBoundCSI-Report configured by RRC; or

[0740] - The time between the transmission of the SL-CSI report request and the receipt of the SL-SCI report for the MAC CE, in the case of receiving the SL-CSI report for the MAC CE; or

[0741] - The time slot associated with the notified periodic transmission of SL-SCH data transmitted through the UE.

[0742] When configuring one or more SL DRXs, the MAC entity should:

[0743] 1> If multiple SL-QoS-Profiles mapped to the destination layer 2 ID and multiple SL DRXs are cyclically associated with multicast and broadcast:

[0744] 2> Among the multiple SL DRX cycles mapped to multiple SL-QoS-Profiles associated with the destination layer 2 ID, select the sl-drx-cycle with the shortest length. 2> Among the multiple SL DRX onDurationTimer mapped to multiple SL-QoS-Profiles associated with the destination layer 2 ID, select the sl-drx-onDurationTimer with the longest length.

[0745] 1> If sl-drx-HARQ-RTT-Timer expires:

[0746] 2> If the data in the corresponding side link procedure is not successfully decoded or if HARQ feedback (i.e., negative acknowledgment) is not transmitted for unicast due to UL / SL prioritization:

[0747] 3> Start the sl-drx-RetransmissionTimer for the corresponding side link procedure in the first time slot after the expiration of sl-drx-HARQ-RTT-Timer.

[0748] When the broadcast type is multicast or broadcast as indicated by the upper layer, sl-drx-StartOffset and sl-drx-SlotOffset are derived from the following equations:

[0749] sl-drx-StartOffset(ms) = destination layer - 2ID modulo sl-drx-Cycle(ms).

[0750] sl-drx-SlotOffset(ms) = destination layer - 2ID modulo sl-drx-onDurationTimer(ms).

[0751] 1> If using SL DRX loop, and [(DFN×10)+number of subframes]modulo(sl-drx-Cycle)=sl-drx-StartOffset:

[0752] 2> Start sl-drx-onDurationTimer after sl-drx-SlotOffset at the beginning of the subframe.

[0753] 1> If SL DRX is in effect:

[0754] 2> Monitor the SCIs (i.e., Level 1 SCIs and Level 2 SCIs) in this SL DRX.

[0755] 2> If SCI instructs a new SL to be transmitted:

[0756] 3> If the source layer -1 ID of the SCI is equal to 8 LSBs of the predetermined destination layer 2 ID, and the destination layer 1 ID of the SCI is equal to 8 LSBs of the predetermined source layer 2 ID, and the broadcast type indicator in the SCI is set to unicast:

[0757] 4> Start or restart the sl-drx-InactivityTimer for the corresponding source layer 1 ID and destination layer 1 ID pair after the first time slot of SCI reception.

[0758] 3> If the destination layer 1 ID of the SCI (i.e., the level 2 SCI) is equal to the given destination layer 1 ID and the broadcast type indicator in the SCI is set to multicast: 4> Among the multiple SL-QoS-Profiles of multiple SL DRX inactivity timers mapped to the destination layer 2 ID associated with the destination layer 1 ID of the SCI, select the sl-drx-InactivityTimer with the largest sl-drx-InactivityTimer length; and

[0759] 4> Start or restart the sl-drx-InactivityTimer for the corresponding destination layer 1 ID after the first time slot of SCI reception.

[0760] 2> If SCI instructs SL to transmit:

[0761] 3> If SL associated with SCI is allowed to not configure PSFCH resources:

[0762] 4> Start the sl-drx-HARQ-RTT-Timer for the corresponding side link procedure in the time slot after the PSSCH transmission (i.e., the currently received PSSCH) ends.

[0763] 3> If PSFCH resources are permitted for SLs associated with SCI:

[0764] 4> If HARQ feedback is enabled via SCI and the broadcast type indicator in SCI is set to unicast or multicast;

[0765] 5> Start the sl-drx-HARQ-RTT-Timer for the corresponding sidelink procedure in the first time slot after the end of the corresponding PSFCH transmission for SL HARQ feedback; or

[0766] 5> When SL HARQ feedback is not transmitted due to UL / SL priority, start the sl-drx-HARQ-RTT-Timer for the corresponding side link procedure in the first time slot after the corresponding PSFCH resource carrying SL HARQ feedback ends.

[0767] 4> If HARQ feedback is disabled via SCI and resources intended for one or more retransmission opportunities are not scheduled in SCI:

[0768] 5> Start the sl-drx-HARQ-RTT-Timer for the corresponding side link procedure in the time slot after the PSFCH resource ends.

[0769] 4> If HARQ feedback is disabled via SCI and resources for one or more retransmission opportunities are scheduled in SCI:

[0770] 5> Start the sl-drx-HARQ-RTT-Timer for the corresponding side link procedure in the time slot after the PSSCH transmission (i.e., the currently received PSSCH) ends.

[0771] Note: When the SCI indicates a retransmission of resources, the sl-drx-HARQ-RTT-Timer is derived from the retransmission resource timing (i.e., the retransmission resource immediately following the one indicated in the SCI). When the SCI does not indicate a retransmission of resources, the UE uses the sl-drx-HARQ-RTT-Timer configured as specified in TS38.331[5].

[0772] 3> Stop using sl-drx-RetransmissionTimer for the corresponding side link process.

[0773] 1> If the source layer 2ID and destination layer 2ID pair for unicast receive the SL DRX command MAC CE:

[0774] 2> Stop using sl-drx-onDurationTimer for source layer 2ID and destination layer 2ID pairs for unicast;

[0775] 2> Stop using sl-drx-InactivityTimer for source layer 2ID and destination layer 2ID pairs used for unicast.

[0776] The sidelink DRX configuration is described in the RRC CR (Draft R2-2203672RRC CR for NR sidelink enhancement) of SL DRX:

[0777] -SL-DRX-Config-GC-BC

[0778] The IE SL-DRX-Config-GC-BC is used to configure DRX-related parameters for multicast and broadcast communications on the NR sidelink. (SL-DRX-Config-GC-BC information element)

[0779]

[0780]

[0781]

[0782]

[0783] In [7] 3GPP TS 38.211 V16.8.0, the following paragraph relates to the number of slots in a subframe or 1 millisecond.

[0784] 4-frame structure and physical resources

[0785] 4.1 General Provisions

[0786] Throughout this specification, unless otherwise stated, the sizes of all fields in the time domain are expressed in time units T. c =1 / (Δf) max ·N f The expression is given by ) where Δfmax = 480·103Hz and N f =4096. Constant κ = T s / T c =64, where T s =1 / (Δf) re f·N f,ref ), Δf ref =15·10 3 Hz and N f,ref =2048.

[0787] Throughout this specification, unless otherwise indicated, statements using the term “UE” in Clauses 4, 5, 6, or 7 shall apply equally to the IAB-MT portion of the IAB node.

[0788] 4.2 Basic Parameters

[0789] Table 4.2-1 shows the basic OFDM parameters that support multiple parameters, where μ and cyclic prefix used for downlink or uplink bandwidth are obtained from the higher-layer parameters subcarrierSpacing and cyclicPrefix, respectively.

[0790] Figure 5 This is a reproduction of Table 4.2-1 from 3GPP TS 38.211 V16.8.0: Supported Transport Basic Parameters.

[0791] 4.3 Frame Structure

[0792] 4.3.1 Frames and Subframes

[0793] Downlink, uplink, and sidelink transmissions are organized into a T f =(Δf max N f / 100)·T c A frame with a duration of 10ms has T. sf =(Δf max N f / 1000)·T c It consists of ten subframes with a duration of 1 ms. The number of consecutive OFDM symbols in each subframe is... Each frame is divided into two equal half-frames consisting of five subframes, each having half-frame 0 composed of subframes 0-4 and half-frame 1 composed of subframes 5-9.

[0794] On a carrier, there is one set of frames in the uplink and one set of frames in the downlink.

[0795] The uplink frame number i used for transmission from the UE should begin T before the start of the corresponding downlink frame at the UE. TA =(N TA +N TA,offset )T c , where N TA,offset As given in [5,TS 38.213], except for the msgA transmission on PUSCH when NTA=0 should be used.

[0796] Figure 6 It comes from 3GPP TS 38.211 V16.8.0. Figure 4 3.1-1: Reproduction of the uplink-downlink timing relationship.

[0797] 4.3.2 Time Slot

[0798] For the subcarrier spacing configuration μ, the time slots are numbered in ascending order within the subframe. And numbered in ascending order within the frame. Existing in a time slot 10 consecutive OFDM symbols, of which Depends on the cyclic prefix as given in Tables 4.3.2-1 and 4.3.2-2. Time slots in subframes. The start of OFDM symbols in the same subframe The beginnings are aligned in time.

[0799] OFDM symbols in time slots within downlink or uplink frames can be classified as 'downlink', 'flexible', or 'uplink'. The signaling for time slot formats is described in Clause 11.1 of [5, TS 38.213].

[0800] In the time slots of a downlink frame, the UE will assume that downlink transmissions occur only in the 'downlink' or 'flexible' symbols.

[0801] In the time slots of this uplink frame, the UE will only transmit in the 'uplink' or 'flexible' symbols.

[0802] A UE that cannot perform full-duplex communication across all cells within a group of cells and does not support simultaneous transmission and reception as defined by parameters such as simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL [10, TS 38.306] expects to transmit in the uplink in one cell within the group of cells no earlier than the end of the last received downlink symbol in the same or different cells within the group of cells. Rx-Tx T c M Rx-Tx As given in Table 4.3.2-3.

[0803] A UE that cannot perform full-duplex communication in all cells within a group of cells and does not support simultaneous transmission and reception as defined by parameters simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL[10,TS 38.306] expects to receive in the downlink in one cell within the group of cells no earlier than the end of the last transmitted uplink symbol in the same or different cells within the group of cells after NTx-RxTc, where NTx-Rx is given in Table 4.3.2-3.

[0804] For DAPS handover operations, UEs that are not capable of full-duplex communication are expected to transmit NTx-RxTc to the cell in the uplink no earlier than the end of the last received downlink symbol in the different cells, where NTx-Rx is given in Table 4.3.2-3.

[0805] For DAPS handover operations, UEs that are not capable of full-duplex communication are expected to receive from the cell in the downlink no earlier than the end of the last transmitted uplink symbol in the different cells after NTx-RxTc, where NTx-Rx is given in Table 4.3.2-3.

[0806] UEs that are unable to perform full-duplex communication are expected to transmit NTx-RxTc in the uplink no earlier than the end of the last received downlink symbol in the same cell, where NTx-Rx is given in Table 4.3.2-3.

[0807] A UE that is unable to perform full-duplex communication is expected to receive NTx-RxTc in the downlink no earlier than the end of the last transmitted uplink symbol in the same cell, where NTx-Rx is given in Table 4.3.2-3.

[0808] Figure 7 This is a reproduction of Table 4.3.2-1 from 3GPP TS 38.211 V16.8.0: the number of OFDM symbols per slot, slots per frame, and slots per subframe for the normal cyclic prefix.

[0809] Figure 8 This is a reproduction of Table 4.3.2-2 from 3GPP TS 38.211 V16.8.0: the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe used for extending the cyclic prefix.

[0810] Figure 9 This is a reproduction of Table 4.3.2-3 from 3GPP TS 38.211 V16.8.0: transition times N_"Rx-Tx" and N_"Tx-Rx".

[0811] In the new radio (NR), a sidelink (SL) user equipment (UE) can perform SL communications (e.g., unicast, multicast, and / or broadcast) with one or more other UEs. In version 17NR, discontinuous reception (DRX) of SL is introduced. A receiver (Rx) UE can intermittently monitor the Physical Sidelink Control Channel (PSCCH) and / or Sidelink Control Information (SCI) based on a sidelink DRX configuration. The sidelink DRX configuration can be configured by the network or provided / configured by the transmitter (Tx) UE. In multicast and broadcast, the drx start offset and drx slot offset are calculated by the Rx UE at least via the destination identifier (ID) (e.g., the destination layer 2 ID associated with a multicast group or broadcast / multicast delivery). The start offset is calculated via the following formula according to the MAC CR (e.g., draft R2-2203673CR of TS 38.321 for sidelink enhancements):

[0812] sl-drx-StartOffset(ms) = Destination Layer 2ID modulo sl-drx-Cycle(ms).

[0813] The time slot offset is calculated using the following formula:

[0814] sl-drx-SlotOffset(ms) = Destination Layer 2ID modulo sl-drx-onDurationTimer(ms).

[0815] The slot offset (e.g., sl-drx-SlotOffset) is derived (in milliseconds) from the modulus of the destination ID divided by the start duration timer (length). Based on this calculation, a problem arises when the slot offset derived from the modulus of the destination ID divided by the start duration timer (length) may not be aligned to the slot boundaries. Figure 10 An example is shown below. For a sidelink bandwidth portion (BWP) or carrier configured with 4 slots in one millisecond / subframe (e.g., subcarrier spacing configured u=2, or subcarrier spacing configured to 60kHz), when sl-drx-onDurationTimer is 31 (in 1 / 32ms) and destination layer 2 ID is 10, the derived slot offset is 10 (in 1 / 32ms) and not aligned with the slot boundaries, which can lead to ambiguity regarding UE behavior regarding in which slot the DRX timer is started. For a sidelink BWP or carrier configured with 4 slots in one millisecond / subframe, the slot offset that will be aligned with the slot boundaries can be 0, 8, 16, or 24 (in 1 / 32ms). Another problem occurs when the derived slot offset is greater than 1ms. For example, when sl-drx-onDurationTimer is 80ms and destination layer 2 ID is 10, the derived time slot offset is 10ms, which exceeds the millisecond boundary and affects the time slot offset function. The UE cannot start the DRX timer without waiting for a long period of time, which can lead to poor performance of DRX operation on the sidelink.

[0816] One concept of this invention is that the UE can determine or derive the slot offset for SL communication based on the destination ID (e.g., destination layer 2 ID) and the number of slots per millisecond / subframe. For example, the slot offset can be the modulus of the destination ID divided by one millisecond / subframe or the number of slots per frame (e.g., numberOfSlotsPerFrame). The number of slots can be the number of consecutive slots per frame / subframe.

[0817] sl-drx-SlotOffset (slot) = Number of slots in one millisecond of destination layer 2ID modulo.

[0818] sl-drx-SlotOffset(slot) = destination layer 2ID modulo numberOfSlotsPerFrame(slot).

[0819] sl-drx-SlotOffset(slot) = destination layer 2ID modulo numberOfSlotsPerSubframe(slot).

[0820] Preferably, in various embodiments, the number of time slots in one millisecond / subframe can be determined or derived based on the following table in TS 38.211, where u is based on the subcarrier spacing configuration.

[0821] The number of OFDM symbols per slot, per frame slot, and per subframe slot used for the standard cyclic prefix:

[0822]

[0823] Alternatively and / or as an alternative, the time slot offset can be derived by dividing the modulus of the destination ID by a predefined number (e.g., 2, 4, 8, 16, 32, ...). This predefined number can be specified, (pre-)configured, or provided by the network or Tx UE.

[0824] sl-drx-SlotOffset (slot) = destination layer 2ID modulo fixed or predefined number (slots).

[0825] Alternatively and / or as an alternative, the slot offset can be derived by dividing the modulus of the destination ID by a predefined number (e.g., 32) or by enabling a duration timer (length). The slot offset can be a modulus rounded up or down to the (nearest) slot boundary or a specific slot boundary. Figure 11 An example is shown. A carrier or bandwidth portion is configured with four time slots in one millisecond. When the on-duration timer (length) is 31 (1 / 32ms) and the destination layer 2 ID is 10, the modulus of the destination layer 2 ID divided by the on-duration timer is 10 (1 / 32ms). The UE can derive the time slot offset by rounding down (e.g., using a floor function) to the nearest time slot boundary less than or equal to the modulus, where in this example, the boundary is the start boundary of the second time slot (e.g., 8 / 32ms). Alternatively, the UE can derive the time slot offset by rounding up (e.g., using a floor function) to the nearest time slot boundary greater than or equal to the modulus, where in this example, the boundary is the start boundary of the third time slot (e.g., 16 / 32ms). Alternatively, if the modulus of the time slot offset is not aligned to the time slot boundary, then the UE can derive the time slot offset as the first time slot after the modulus of the time slot offset, where in this example, it is the third time slot boundary.

[0826] sl-drx-SlotOffset(1 / 32ms) = destination layer 2ID modulo 32(1 / 32ms) round up / down to the slot boundary.

[0827] sl-drx-SlotOffset(1 / 32ms) = destination layer 2ID modulo sl-drx-ondurationtimer(1 / 32ms) rounds up / down to the slot boundary.

[0828] Alternatively, the UE may not round the modulus up / down to the nearest slot boundary for deriving the slot offset. If it is not a complete PSCCH timing, the UE may not monitor the Sidelink Control Information / Physical Sidelink Control Channel (SCI / PSCCH). For example, if or when the slot offset is in the middle of a (sidelink) slot, the UE may not monitor the PSCCH timing within that (sidelink) slot. If a sidelink slot is not entirely within the sidelink active time (e.g., the sidelink active time begins or ends in the middle of the sidelink slot), the UE may not monitor the SCI / PSCCH within that sidelink slot.

[0829] Alternatively, and / or as an alternative, the slot offset can be derived by dividing the modulus of the destination ID by the start duration timer (length) and also by a predefined number (e.g., 32). This yields a slot offset of less than 1 millisecond. Furthermore, the slot offset can be a modulus rounded up or down to the (nearest) slot or subframe boundary or a specific slot boundary. Alternatively, the UE may not round the modulus up / down to the nearest slot boundary for deriving the slot offset.

[0830] sl-drx-SlotOffset (unit: 1 / 32ms) = [destination layer 2 ID modulo sl-drx-onDurationTimer] modulo32 (unit: 1 / 32ms).

[0831] Figure 11 An example is shown. The sl-drx-onDurationTimer is 100ms and the destination ID is 130. The modulus of the destination ID divided by the sl-drx-onDurationTimer is 30ms, which exceeds the subframe boundary. The UE can derive the slot offset based on a second modulus divided by 32, which gives 30 / 32 in 1 / 32ms units.

[0832] Preferably, in various embodiments, the transformation from "time slot" to "millisecond" can be as follows:

[0833]

[0834]

[0835]

[0836] Preferably, in various embodiments, the number of slots per millisecond, or numberOfSlotsPerSubframe, can be determined or derived based on the subcarrier spacing or basic parameters of the SL BWP.

[0837] Figure 12 An example is shown below. The number of slots per subframe (for SL BWP) is 2. For each destination ID (used for multicast or broadcast), the UE can derive sl-drx-SlotOffset based on the remainder of the destination ID divided by the number of slots per subframe (2 in this example), where the slot offset is the remainder divided by the number of slots per subframe (e.g., remainder = 0, slot offset = 0 / 2; remainder = 1, slot offset = 1 / 2).

[0838] Figure 13 Another example is shown below. The number of slots per subframe (for SL BWP) is 4. For each destination ID (used for multicast or broadcast), the UE can derive sl-drx-SlotOffset based on the remainder of the destination ID divided by the number of slots per subframe (4 in this example), where the slot offset is the remainder divided by the number of slots per subframe (e.g., remainder = 0, slot offset = 0 / 4; remainder = 1, slot offset = 1 / 4; remainder = 2, slot offset = 2 / 4; remainder = 3, slot offset = 3 / 4).

[0839] Preferably, in various embodiments, for a subcarrier spacing of 15*2μkHz, the number of time slots in one millisecond is 2μ.

[0840] Preferably, in various embodiments, μ = 0, 1, 2, 3, 4, 5, depending on the basic parameters or subcarrier spacing of the SL BWP.

[0841] Preferably, in various embodiments, the time slot boundary is based on Where i = 0, 1, ..., 2μ-1.

[0842] Preferably, in various embodiments,

[0843] Preferably, in various embodiments,

[0844] For example, given SCS = 60kHz and 4 time slots within a subframe, if destination layer 2ID = 26 (in decimal), then In this example,

[0845] Preferably, in various embodiments, for sidelink groups, the UE determines the start timing of the start duration timer based on the derived sl-drx-SlotOffset.

[0846] Preferably, in various embodiments, the UE starts an on-duration timer for monitoring (multicast) sidelink transmissions for at least the group, based at least on the derived sl-drx-SlotOffset.

[0847] Preferably, in various embodiments, for unicast sidelink DRX configurations, the start timing of the duration timer is based on higher-layer configuration (rather than based on destination ID derivation).

[0848] Preferably, in various embodiments, the sl-drx-SlotOffset (ms) derived from the startup timing for enabling the duration timer should be aligned with the slot boundary (in ms).

[0849] Preferably, in various embodiments, the sl-drx-SlotOffset (1 / 32ms) derived for the startup timing of the start duration timer should be aligned with the slot boundary (1 / 32ms).

[0850] Preferably, in various embodiments, for a unicast sidelink DRX configuration, the candidate value of sl-drx-SlotOffset in a higher-layer configuration (e.g., via the vehicle-to-everything (V2X) layer, network, or Tx UE configuration) can be 0, 1, 2, 3, ... 31 (in units of 1 / 32 ms).

[0851] Preferably, in various embodiments, for multicast sidelink DRX, the candidate value of sl-drx-SlotOffset should be Where i = 0, 1, ... (2μ-1) ​​(in units of 1 / 32ms).

[0852] Preferably, in various embodiments, for multicast sidelink DRX, the value set {0,1,…31} excluding Values ​​other than i = 0, 1, ... (2μ-1) ​​are not allowed to be used or applied to sl-drx-SlotOffset.

[0853] For all the concepts, embodiments, and examples above and in this document:

[0854] SL communication can be multicast or broadcast communication.

[0855] SL communication cannot be unicast communication.

[0856] Time slot offset can be measured in time slots or milliseconds.

[0857] The UE can be an Rx UE in SL communication.

[0858] The UE can start the enable duration timer after the time indicated in the slot offset, starting from the beginning of the subframe.

[0859] All of the above concepts, embodiments, and examples can be combined into new concepts and / or combinations of new concepts.

[0860] See Figure 14 According to such and other concepts, systems and methods of the present invention, method 1000 for a UE in a wireless communication system includes performing SL communication associated with a destination ID (step 1002) and deriving a slot offset associated with SL multicast communication based on the destination ID and the number of slots in the subframe (step 1004).

[0861] In various embodiments, the slot offset is derived by dividing the modulus of the destination ID by the number of slots in the subframe.

[0862] In various embodiments, the number of time slots in a subframe is configured by the network.

[0863] In various embodiments, the number of time slots in a subframe is associated with the SL BWP.

[0864] In various embodiments, the slot offset is sl-drx-slotoffset.

[0865] Return to reference Figure 3 and Figure 4 In one or more embodiments from the UE's perspective, apparatus 300 includes program code 312 stored in the transmitter's memory 310. CPU 308 can execute program code 312 to: (i) perform SL communication associated with a destination ID; and (ii) derive a slot offset associated with SL multicast communication based on the destination ID and the number of slots in the subframe. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0866] See Figure 15 Through such and other concepts, systems and methods of the present invention, method 1010 for a UE in a wireless communication system includes performing SL communication associated with a destination ID (step 1012) and deriving a time slot offset associated with SL multicast communication based on the destination ID and a fixed number (step 1014).

[0867] In various embodiments, the time slot offset is derived by dividing the modulus of the destination ID by a fixed number.

[0868] In various embodiments, the fixed number is configured by the network.

[0869] In various embodiments, the fixed number is 2, 4, 8, 16 or 32.

[0870] In various embodiments, SL communication is either multicast or broadcast.

[0871] Return to reference Figure 3 and Figure 4 In one or more embodiments from the UE's perspective, device 300 includes program code 312 stored in the transmitter's memory 310. CPU 308 can execute program code 312 to: (i) perform SL communication associated with a destination ID; and (ii) derive a timeslot offset associated with SL multicast communication based on the destination ID and a fixed number. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0872] See Figure 16 According to this invention, a method 1020 for a UE in a wireless communication system includes performing SL communication associated with a destination ID (step 1022), having or being configured with an SL DRX configuration associated with the SL communication, wherein the SL DRX configuration includes at least an on-duration timer and a DRX loop (step 1024), deriving a first offset associated with the SL communication based on the destination ID and the DRX loop (step 1026), deriving a second offset associated with the SL communication based on the destination ID and the time slot number per subframe (step 1028), starting an on-duration timer after a time period determined based on the second offset from the beginning of the subframe, wherein the subframe is determined at least based on the first offset (step 1030), and monitoring the SCI while the on-duration timer is running (step 1032).

[0873] In various embodiments, the second offset is derived by dividing a first value by the number of slots per subframe, wherein the first value is the remainder of the destination ID divided by the number of slots per subframe.

[0874] In various embodiments, the first offset is the start offset or sl-drx-StartOffset.

[0875] In various embodiments, the second offset is a slot offset or sl-drx-SlotOffset.

[0876] In various embodiments, the SL DRX configuration including at least an enabled duration timer means that the SL DRX configuration includes the duration length of the enabled duration timer, and / or the SL DRX configuration including at least a DRX loop means that the SL DRX configuration includes the duration length of the DRX loop.

[0877] In various embodiments, SL communication is multicast or broadcast communication.

[0878] In various embodiments, the second offset is measured in milliseconds.

[0879] In various embodiments, the subframe satisfies the condition that the remainder of the number associated with the subframe divided by the DRX cycle is equal to the first offset, and / or the number associated with the subframe is equal to ((the number of subframes × 10) + (the number of subframes of the subframe)).

[0880] In various embodiments, the second offset is set to (destination ID modulo the number of slots per subframe) / (number of slots per subframe).

[0881] In various embodiments, the number of slots per subframe is the number of slots per subframe in the SL BWP, wherein the UE performs SL communication in the SL BWP, and / or the number of slots per subframe is associated with the basic parameters or subcarrier spacing of the SL BWP, and / or the number of slots per subframe is based on the basic parameters or subcarrier spacing of the SL BWP being one of 1, 2, 4, 8, 16 or 32.

[0882] Return to reference Figure 3 and Figure 4 In one or more embodiments from the UE's perspective, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) perform SL communication associated with a destination ID; (ii) be configured with or have an SL DRX configuration associated with the SL communication, wherein the SL DRX configuration includes at least an on-duration timer and a DRX loop; (iii) derive a first offset associated with the SL communication based on the destination ID and the DRX loop; (iv) derive a second offset associated with the SL communication based on the destination ID and the number of slots per subframe; (v) start an on-duration timer after a time period determined based on the second offset from the start of the subframe, wherein the subframe is determined at least based on the first offset; and (vi) monitor the SCI while the on-duration timer is running. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0883] Any combination of the concepts or teachings above may be combined together or formed into new embodiments. The disclosed details and embodiments may be used to solve at least (but not limited to) the problems mentioned above and herein.

[0884] It should be noted that any of the methods, alternatives, steps, examples, and embodiments presented herein may be used independently, individually, and / or in combination with multiple methods, alternatives, steps, examples, and embodiments.

[0885] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented or practiced by using other structures, functions, or structures and functions other than or different from one or more aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on a pulse repetition frequency. In some aspects, a parallel channel can be established based on a pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on a pulse repetition frequency, a pulse position or offset, and a time-hopping sequence.

[0886] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0887] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of both, which may be designed using source decoding or some other technique) and various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination thereof, with instructions. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as a departure from the scope of this disclosure.

[0888] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0889] It should be understood that any particular order or hierarchy of steps in any disclosed process is an instance of an example method. It should be understood that the specific order or hierarchy of steps in the process may be rearranged based on design preferences, while remaining within the scope of this disclosure. The appended method claims present the elements of the various steps in a sample order and are not intended to be limited to any particular order or hierarchy presented.

[0890] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, this machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. Example storage media can be integrated with a processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside as discrete components in a user equipment. Furthermore, in some aspects, any suitable computer program product can include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some respects, computer program products may include packaging materials.

[0891] While the invention has been described in conjunction with various aspects and examples, it should be understood that further modifications are possible. This application is intended to cover any changes, uses, or adaptations to the invention that generally follow the principles of the invention and include such deviations from this disclosure that fall within the scope of known and customary practice in the art to which this invention pertains.

Claims

1. A method for discontinuous sidelink reception in a user equipment, characterized in that, include: Perform sidelink communication associated with the destination identifier; Having or being configured with a sidelink discontinuous reception configuration associated with the sidelink communication, wherein the sidelink discontinuous reception configuration includes at least an enable duration timer and a discontinuous reception loop; A first offset associated with the sidelink communication is derived based on the destination identifier and the discontinuous reception cycle; A second offset associated with the sidelink communication is derived based on the destination identifier and the number of time slots per subframe, wherein the second offset is derived according to one of the following: The second offset is derived by dividing a first value by the number of time slots per subframe, wherein the first value is the remainder of the destination identifier divided by the number of time slots per subframe; or The second offset is set to (the number of time slots per subframe as the destination identifier) ​​ / (the number of time slots per subframe); The on-duration timer is started from the beginning of a subframe after a time period determined based on the second offset, wherein the subframe is determined at least based on the first offset; and Monitor side link control information while the start duration timer is running.

2. The method according to claim 1, characterized in that, The first offset is the start offset or sl-drx-StartOffset.

3. The method according to claim 1, characterized in that, The second offset is a slot offset or sl-drx-SlotOffset.

4. The method according to claim 1, characterized in that: The sidelink discontinuous reception configuration including at least the enable duration timer means that the sidelink discontinuous reception configuration includes the duration length of the enable duration timer; and / or The fact that the sidelink discontinuous reception configuration includes at least the discontinuous reception cycle means that the sidelink discontinuous reception configuration includes the duration of the discontinuous reception cycle.

5. The method according to claim 1, characterized in that, The sidelink communication is either multicast or broadcast communication.

6. The method according to claim 1, characterized in that, The second offset is in milliseconds.

7. The method according to claim 1, characterized in that: The subframes satisfy the condition that the remainder of the number associated with the subframes divided by the discontinuous reception cycle is equal to the first offset; and / or The number associated with the subframe is equal to ((the number of frames of the subframe × 10) + (the number of subframes of the subframe)).

8. The method according to claim 1, characterized in that: The number of time slots per subframe is the number of time slots per subframe in the sidelink bandwidth portion, wherein the user equipment performs the sidelink communication in the sidelink bandwidth portion; and / or The number of time slots per subframe is associated with the basic parameters or subcarrier spacing of the sidelink bandwidth portion; and / or Based on the basic parameters of the sidelink bandwidth portion or the subcarrier spacing, the number of time slots per subframe is one of 1, 2, 4, 8, 16 or 32.

9. A user equipment, characterized in that, include: Memory; as well as A processor, operatively coupled to the memory, wherein the processor is configured to execute program code to: Perform sidelink communication associated with the destination identifier; Having or being configured with a sidelink discontinuous reception configuration associated with the sidelink communication, wherein the sidelink discontinuous reception configuration includes at least an enable duration timer and a discontinuous reception loop; A first offset associated with the sidelink communication is derived based on the destination identifier and the discontinuous reception cycle; A second offset associated with the sidelink communication is derived based on the destination identifier and the number of time slots per subframe, wherein the second offset is derived according to one of the following: The second offset is derived by dividing a first value by the number of time slots per subframe, wherein the first value is the remainder of the destination identifier divided by the number of time slots per subframe; or The second offset is set to (the number of time slots per subframe as the destination identifier) ​​ / (the number of time slots per subframe); The on-duration timer is started from the beginning of a subframe after a time period determined based on the second offset, wherein the subframe is determined at least based on the first offset; and Monitor side link control information while the start duration timer is running.

10. The user equipment according to claim 9, characterized in that, The first offset is the start offset or sl-drx-StartOffset.

11. The user equipment according to claim 9, characterized in that, The second offset is a slot offset or sl-drx-SlotOffset.

12. The user equipment according to claim 9, characterized in that: The sidelink discontinuous reception configuration including at least the enable duration timer means that the sidelink discontinuous reception configuration includes the duration length of the enable duration timer; and / or The fact that the sidelink discontinuous reception configuration includes at least the discontinuous reception cycle means that the sidelink discontinuous reception configuration includes the duration of the discontinuous reception cycle.

13. The user equipment according to claim 9, characterized in that, The sidelink communication is either multicast or broadcast communication.

14. The user equipment according to claim 9, characterized in that, The second offset is in milliseconds.

15. The user equipment according to claim 9, characterized in that: The subframe satisfies that the remainder of the number associated with the subframe divided by the discontinuous reception cycle is equal to the first offset; and / or The number associated with the subframe is equal to ((the number of frames of the subframe × 10) + (the number of subframes of the subframe)).

16. The user equipment according to claim 9, characterized in that: The number of time slots per subframe is the number of time slots per subframe in the sidelink bandwidth portion, wherein the user equipment performs the sidelink communication in the sidelink bandwidth portion; and / or The number of time slots per subframe is associated with the basic parameters or subcarrier spacing of the sidelink bandwidth portion; and / or Based on the basic parameters of the sidelink bandwidth portion or the subcarrier spacing, the number of time slots per subframe is one of 1, 2, 4, 8, 16 or 32.

Images