Channel access listening and frequency interleaving for sidelink communications

By optimizing channel access and handover gap management, as well as frequency interleaving design, the efficiency and reliability issues of sidelink communication in unlicensed spectrum have been resolved, achieving more efficient spectrum utilization.

CN119032624APending Publication Date: 2024-11-26INTEL CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028283.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-02-16
Filing Date
2023-04-17
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

When conducting sidelink communication in unlicensed spectrum, existing technologies face challenges such as complex channel access monitoring processes, difficulties in managing TX/RX and RX/TX handover gaps, mutual blocking issues between UEs, and challenges in frequency interleaving structure design, resulting in low communication efficiency.

Method used

By optimizing the channel access monitoring mechanism, adjusting the TX/RX and RX/TX handover interval lengths, and employing cyclic prefix extension and suffix extension techniques, flexible channel access is achieved. A frequency interleaving physical structure design is adopted to reduce inter-UE blocking and improve spectrum efficiency through the interleaved channel structure.

Benefits of technology

It improves the efficiency and reliability of sidelink communication in unlicensed spectrum, reduces LBT overhead, reduces mutual interference between UEs, and improves spectrum utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032624A_ABST
    Figure CN119032624A_ABST
Patent Text Reader

Abstract

Various embodiments herein provide techniques for sidelink communication, e.g., in an unlicensed band. For example, embodiments may relate to, for example, a channel access listening procedure associated with a listen before talk (LBT) procedure for unlicensed spectrum. Embodiments may also relate to frequency interleaved physical structures for sidelink communications. Other embodiments may be described and claimed.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the following applications: U.S. Provisional Patent Application No. 63 / 332,178 filed on April 18, 2022; U.S. Provisional Patent Application No. 63 / 332,109 filed on April 18, 2022; U.S. Provisional Patent Application No. 63 / 407,408 filed on September 16, 2022; U.S. Provisional Patent Application No. 63 / 408,344 filed on September 20, 2022; and U.S. Provisional Patent Application No. 63 / 485,382 filed on February 16, 2023. Technical Field

[0003] Various embodiments may generally relate to the field of wireless communications.For example, some embodiments may relate to techniques for sidelink communications, such as in an unlicensed spectrum. Background Art

[0004] Mobile communications have evolved significantly from early voice systems to today's highly complex integrated communications platforms. The next generation of wireless communications systems, fifth generation (5G), which may additionally or alternatively be referred to as new radio (NR), can enable a variety of users and applications to access information and share data anytime, anywhere. NR can be a unified network / system that is designed to meet very different and sometimes conflicting performance dimensions and services. Such diverse and multi-dimensional requirements can be driven by different services and applications.

[0005] For example, in the 3rd Generation Partnership Project (3GPP) Release 16 (Rel.16) specification, sidelink (SL) communications were developed in the radio access network (RAN) to support advanced vehicle-to-everything (V2X) applications. In Release 17 (Rel.17), SA2 studied proximity services, including public safety and business-related services, and standardized them as part of Rel.17, developing power saving solutions (e.g., partial listening, discontinuous reception (DRX), etc.) and user equipment (UE) coordination to improve power consumption and reliability of SL transmissions for battery-constrained terminals. Although NR SL was originally developed for V2X applications, there is a growing interest in extending the applicability of NR SL to commercial use cases, such as sharing sensor information (e.g., video) between highly automated vehicles. For commercial SL applications, desired features may include increased SL data rates and support for new carrier frequencies for SL. To achieve these elements, one goal of Release 18 (Rel.18) is to extend SL operations in unlicensed spectrum (e.g., referred to as NR-U SL). BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The embodiments will be easily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, similar reference numerals represent similar structural elements. The embodiments are illustrated in the figures of the accompanying drawings by way of example and not by way of limitation.

[0007] Figure 1 The New Radio – Unlicensed (NR-U) side link (SL) communication mode is schematically shown.

[0008] Figure 2A Switching times within a SL slot without a physical sidelink feedback channel (PSFCH) are shown according to various embodiments.

[0009] Figure 2B The switching time within the SL slot with PSFCH according to various embodiments is shown.

[0010] Figure 3 Examples of transmit (Tx) / receive (Rx) and Rx / Tx gaps (guard periods) in a sidelink physical structure according to various embodiments are shown.

[0011] Figure 4 An example of applying a cyclic prefix extension (CPE) to a synchronization signal block (SSB) transmission when a previous SL transmission of a sidelink SSB (S-SSB) transmission ends one symbol earlier is shown according to various embodiments.

[0012] Figure 5 Examples of the effects of SL synchronization errors according to various embodiments are shown.

[0013] Figure 6 Examples of the impact of UE-UE propagation delay according to various embodiments are shown.

[0014] Figure 7 An example is shown in which two UEs contend for the same channel and perform LBT simultaneously according to various embodiments.

[0015] Figure 8 An example is shown in which two UEs select the same starting position for their transmissions and pre-apply different CPEs and Listen Before Talk (LBT) procedures to avoid collisions between their transmissions according to various embodiments.

[0016] Fig. 9 An example of a general ON / OFF time mask for shared spectrum channel access according to various embodiments is shown.

[0017] Fig.10 An example of implementing a Type 2B LBT is shown with an LBT window and an ON / OFF (OFF / ON) transient cycle according to various embodiments.

[0018] Fig.11 An example of a Type 2B LBT for SL communication in an unlicensed spectrum according to various embodiments is shown.

[0019] Fig.12 An example of a physical channel structure with 20 MHz bandwidth (BW) and 30 kHz subcarrier spacing (SCS) (number of resource blocks (NRB) = 51) according to various embodiments is shown, where M = 5; for int. #0, N = 11, and for int. #1-4, N = 10.

[0020] Fig.13A and Fig. 13B An example of a physical channel structure with two single RB interleaving options with K=51 RBs and M=5 according to various embodiments is shown.

[0021] Fig.14 An example of a physical channel structure with band group RB interleaving with K=51 RBs and M=5 according to various embodiments is shown.

[0022] Fig.15 An example of comb-5 subcarrier (SC) interleaving according to various embodiments is shown.

[0023] Fig.16 A wireless network according to various embodiments is schematically illustrated.

[0024] Fig.17 Components of a wireless network according to various embodiments are schematically illustrated.

[0025] Fig.18 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments.

[0026] Fig.19 Depicted are example procedures for practicing the various embodiments discussed herein.

[0027] Fig. 20 Another example process for practicing the various embodiments discussed herein is depicted.

[0028] Fig.21 Another example process for practicing the various embodiments discussed herein is depicted. DETAILED DESCRIPTION

[0029] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are described for the purpose of explanation rather than limitation, so as to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments can be practiced in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted to avoid unnecessary details obscuring the description of various embodiments. For the purpose of this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0030] Embodiments herein provide techniques for sidelink communications, for example, in unlicensed frequency bands. For example, embodiments may relate to a channel access listening process. Embodiments may also relate to a physical structure of frequency interleaving for sidelink communications.

[0031] As mentioned above, one goal of Release 18 (Rel. 18) is to extend SL operation in unlicensed spectrum, referred to herein as NR unlicensed (NR-U) SL spectrum. However, it is important to note that different regional regulatory requirements are enforced globally to allow fair use of spectrum and fair coexistence between different technologies. Therefore, it may be sufficient to implement a solution for all regions that complies with the most stringent regulations published in EN301893 from ETSI BRAN. In fact, for the development of NR-U during Rel. 16, 3GPP NR-based systems that comply with these regulations have already been developed.

[0032] That being said, in order to implement a SL communication system in an unlicensed band, consideration of the SL communication system may need to be combined with the regulatory requirements required to operate in the unlicensed band. Specifically, it is noted that NR SL can operate in two modes of operation: 1) Mode 1, in which the gNB schedules the SL transmission resources to be used by the UE, and Uu operation is limited to the licensed spectrum; 2) Mode 2, in which the UE determines (e.g., the gNB does not schedule) the SL transmission resources within the gNB / network configured or pre-configured SL resources. Figure 1 Two modes of operation are shown.

[0033] In this context, there are several specific challenges for implementing NR-U SL.

[0034] Channel access listening process

[0035] In SL, the concept of SL slots is introduced together with transmit / receive (TX / RX) and RX / TX switching gaps, where the switching slot is defined as a guard interval for proper RF retuning at the UE when switching from RX mode to TX mode (or vice versa). Figure 2A-2B An example of SL time slot is shown in FIG. Figure 2A depicts the case of a SL slot without a physical sidelink feedback channel (PSFCH), while Figure 2B An example of a SL slot with PSFCH is provided.

[0036] like Figure 2A-2B As shown, there will be at least one symbol gap (which is synonymous with LBT overhead in the unlicensed band) in the SL system, because in FR-1, when there is a gap greater than 16us between bursts within the channel occupation time (COT), whether the system is operating in semi-static channel access mode or dynamic channel access mode, an LBT mechanism is required at the initiating device and / or the responding device to resume transmission or start transmission after the gap. Various embodiments of this document provide techniques for alleviating this problem.

[0037] Another issue to consider about SL timeslots is that in SL, all transmissions start at predefined symbol positions within the timeslot, and the first symbol of each SL transmission is a copy of the second symbol, where this physical structure is defined to support automatic gain control (AGC) convergence time. However, due to the fact that LBT may be required in unlicensed spectrum and potential LBT failures may occur, additional flexibility is needed regarding when SL transmissions can be initiated. In this regard, various options are discussed in this disclosure.

[0038] Therefore, embodiments of the present invention provide mechanisms for handling gaps left in the SL for RX / TX and TX / RX switching gaps when operating in unlicensed spectrum. In addition, embodiments of the present invention provide mechanisms for mitigating mutual blocking between UEs when operating in TDM or FDM mode.

[0039] TX / RX&RX / TX switching gap

[0040] As mentioned above, the SL physical structure defines one symbol for TX / RX and RX / TX switching gaps (also called guard periods). The actual duration required for these TX / RX and RX / TX switching gaps has been determined by RAN4, and they can be less than 13us. However, the duration allocated for TX / RX and RX / TX switching gaps depends on the subcarrier spacing (SCS) setting (e.g., the CP-free OFDM symbol duration is equal to 66.6 / 33.3 and 16.6us for 15 / 30 / 60kHz SCS, respectively), and is greater than the actual time required.

[0041] When operating in unlicensed spectrum, for efficient LBT operation and to reduce LBT overhead within the SL COT shared interval, the gap between transmission bursts within the COT should be less than or equal to 16us, so that LBT may not be required for both dynamic channel access mode and semi-static channel access mode. If the gap is greater than 16us, a type 2A or 2B LBT process may be required within the shared COT.

[0042] To reduce the TX / RX and RX / TX switching gaps defined in the SL physical structure when operating in unlicensed spectrum, in one embodiment, one of the following options may be employed:

[0043] ○ Option 1: SL transmission can start earlier than the symbol / slot boundary (e.g., using cyclic prefix extension, or adding any other reference signal or data signal);

[0044] ○ Option 2: SL transmission ends at a time later than a symbol boundary (eg, using cyclic suffix extension, or adding any other reference signal or data signal).

[0045] (Option 1: Cyclic Prefix Extension and Option 2: Cyclic Suffix Extension)

[0046] In one embodiment, if option 1 or option 2 above is adopted, the determination of the length of the cyclic prefix or suffix to be applied is left to the UE implementation. In another option, in SL mode 1, the cyclic prefix extension to be applied so as to reduce the gap length is indicated in the scheduling DCI 3_x. In another option, the cyclic suffix applied by the UE is indicated in the SL control indication (SCI) (in the first level or the second level or both).

[0047] Whether reducing TX / RX and RX / TX switching times, or using one of the above options, it may be important to define the UE's behavior with respect to the LBT procedure in the presence of such gaps. In this sense, these features may be decoupled based on whether the SL slot may or may not include a PSFCH transmission.

[0048] Case without PSFCH

[0049] In one embodiment, when the SL timeslot may not include the PSFCH, one of the following options may be used:

[0050] ○ Option 1: If the gap originating from the TX-RX time along with subsequent transmissions (e.g., other bursts from the gNB or the same UE, or other bursts from other UEs transmitted over PSFCH) is occurring within the COT, it is left to the implementation to ensure that there is always enough gap between the UL burst and the subsequent burst to perform LBT if LBT may be needed.

[0051] ○ Option 2: For 60kHz, adjust the TX-RX switching time to at least 2 symbols to guarantee a minimum gap of 25us so that LBT is always required regardless of the SCS and scenario, and there is no need to handle the gap length via cyclic prefix or post-prefix from the UE perspective.

[0052] ○ Option 3: The TX-RX switching time is left as defined in Rel-16, and the UE performing transmission after the gap determines the specific length of the gap by decoding the SCI from the previous burst and specifically by knowing the time domain resources used for the previous burst and the time domain resources used for the subsequent expected transmission. After knowing the specific length of the gap, the UE can select the LBT type to be used according to one or more of the following rules:

[0053] ◆If the UE operates in dynamic channel access mode, and if the gap is greater than 16us but less than 25us, LBT Type 2B is used.

[0054] ◆If the UE operates in dynamic channel access mode and if the gap is greater than 25us, LBT Type 2A is used.

[0055] ◆If the UE operates in semi-static channel access mode, and if the gap is greater than X us, the UE can perform the LBT process using an observation window of Xus, where X = 9 us, or can be equal to 16 us (in China or other regions where this length of observation window is required).

[0056] Case with PSFCH

[0057] When the SL slot may include PSFCH, different considerations may be made separately depending on whether the slot may be related to TX / RX and RX / TX switching.

[0058] In one embodiment, when the SL timeslot may include a PSFCH, one of the following options may be used for the TX / RX switching time:

[0059] Alt 1: Leave the switching time as it is and do not apply enhancement

[0060] Alt-2: For 60kHz, the switching time is adjusted to at least X symbols to guarantee a minimum gap of 25us, so that LBT is always required regardless of the SCS and scenario, and there is no need to handle the gap length via CP extension from the UE's perspective. In one embodiment, X is fixed and is equal to X=2, for example. In another embodiment, X is configured by a higher layer.

[0061] □Also note:

[0062] ■For semi-static channel access mode, if the UE sending PSFCH is a responding device or an initiating device, one symbol may be sufficient for 60kHz because the listening should be 9us long. In this case, in one embodiment, different switching time lengths may be used based on whether the semi-static channel access mode and the dynamic channel access mode are used.

[0063] ■Special considerations may also be required in China where the minimum listening is 16us. In this case, in one embodiment, cell-specific RRC signaling may be required to distinguish between regional deployments, and additional differentiation for RX / TX and TX / RX switching times may also be made based on whether this parameter is configured. As an example, if the system is operating in semi-static channel access mode and it is operating in China or any other country that requires a minimum listening of 16us, then X=2 may be configured or used, otherwise X=1 may be configured or used.

[0064] ○RX-TX switching time

[0065] In one embodiment, when the SL timeslot may include PSFCH, one of the following options may be used for the RX / TX switching time:

[0066] Alt 1: Leave the switching time as it is and do not apply enhancement

[0067] Alt-2: For 60kHz, the switching time is adjusted to at least X symbols to guarantee a minimum gap of 25us, so that LBT is always required regardless of the SCS and scenario, and there is no need to handle the gap length via CP extension from the UE's perspective. In one embodiment, X is fixed and is equal to X=2, for example. In another embodiment, X is configured by a higher layer.

[0068] □Other aspects may include:

[0069] ■For semi-static channel access mode, if the UE sending PSFCH is a responding device or an initiating device, one symbol may be sufficient for 60kHz because the listening should be 9us long. In this case, in one embodiment, different switching time lengths may be used based on whether the semi-static channel access mode and the dynamic channel access mode are used.

[0070] ■Special considerations may also be required in China where the minimum listening is 16us. In this case, in one embodiment, cell-specific RRC signaling may be required to distinguish between regional deployments, and additional differentiation for RX / TX and TX / RX switching times may also be made based on whether this parameter is configured. As an example, if the system is operating in semi-static channel access mode and it is operating in China or any other country that requires a minimum listening of 16us, then X=2 may be configured or used, otherwise X=1 may be configured or used.

[0071] In one embodiment, regardless of the SCS, PSFCH is defined as short control signaling and one of the following options may be used:

[0072] ○ Option 1: No LBT is required for PSFCH and a 5% duty cycle is applied for the device, which means that the UE sending PSFCH will be responsible for meeting the 5%, otherwise LBT will be required for any additional PSFCH transmission.

[0073] ○ Option 2: No LBT is required for PSFCH and a 5% duty cycle is applied per “initiating” device, meaning that the UE that is initiating COT is responsible for (counting) 5%, regardless of the UE sending PSFCH, and it is left to the gNB or initiating UE to indicate whether LBT is required.

[0074] ○ Option 3: No LBT is required for PSFCH and a 5% duty cycle is applied per “cell”, which means that the serving gNB is responsible for the 5% regardless of the UE sending PSFCH and it is left to the gNB to indicate whether LBT is required.

[0075] ○ Option 4: If the UE operates in dynamic channel access mode, then use Type 2A LBT before sending PSFCH when the gap between the previous burst within the shared COT and the transmission of PSFCH is greater than 25us, or when PSFCH falls outside the COT of any other UE or this UE.

[0076] Another possible consideration is when the PSFCH is sent if the UE is the initiating device, and the start point of the COT is aligned with the PSFCH transmission. In this case, in many scenarios, the UE will not be able to perform any LBT (Type 1 or Type 2A / 2B) because the previous burst of PSFCH transmission may block the LBT process. In this regard, in one embodiment, one of the following options can be used:

[0077] ○ Option 1: No special processing is supported, and the UE is avoided as an initiating device at the boundary of PSFCH transmission as much as possible through appropriate scheduling.

[0078] ○ Option 2: PSFCH transmission is allowed only when one or more of the following are met:

[0079] ◆PSFCH transmission occurs within a shared COT from another device (COT of gNB or other UE).

[0080] ◆If COT has been initiated before PSFCH transmission, PSFCH occurs within the COT of the transmitting UE.

[0081] In one embodiment, immediately before a PSFCH transmission may occur (e.g., immediately before the start of resources allocated for the PSFCH), the UE may apply a cyclic prefix extension of the following length:

[0082] T_(symb,(l-1)mod 7·2^μ)^μ-Y

[0083] Wherein, l is an OFDM symbol to which cyclic prefix extension may be applied, μ identifies the subcarrier spacing (e.g., μ=0 corresponds to 15 kHz, μ=1 corresponds to 30 kHz, and μ=2 corresponds to 60 kHz), and Y may be fixed and equal to 13 us as an example, or may be some other value in other embodiments (e.g., less than or equal to approximately 16 us (if the UE transmitting the PSFCH is capable of operating as a responding device within its own or another UE's COT)). This option may be applied, for example, when a UE detects that its PSFCH transmission may occur within a shared COT, and additionally, another UE may perform a PSSCH / PSCCH transmission within the SL time slot where the PSFCH transmission will occur, at the end of one symbol prior to the PSFCH transmission, as shown in the right figure of FIG. 2 . In one embodiment, as an alternative, the value of Y is (pre-)configured, or may be decided by the UE based on the UE's implementation. In one embodiment, even though Y may be provided by (pre) configuration, its value may be predefined or fixed under the following conditions: the UE assesses that its S-SSB transmission may occur within the shared COT and determines that the previous SL transmission (PSSCH / PSCCH or PSFCH) from itself or another UE may end one symbol before the start of the S-SSB transmission, such as Figure 4 shown.

[0084] In one embodiment, when the UE performs a PSFCH transmission outside of the shared COT, no cyclic prefix extension is applied before the transmission. In this case, whether the UE can perform Type 2A or Type 1 LBT, this can end immediately before the first symbol of the PSFCH transmission (e.g., performing Type 2A and Type 1 LBT so that the assessment of whether the channel is idle or occupied will occur immediately before the PSFCH transmission).

[0085] In one embodiment, when a UE performs a PSFCH transmission within a shared COT, and when the previous transmission may end more than one symbol earlier, a cyclic prefix extension is applied before the PSFCH transmission. In this case, the length of the cyclic prefix extension may be left to the UE implementation or based on (a pre-configured value).

[0086] Note that some of the options / embodiments provided above are not mutually exclusive but can be adopted in combination.

[0087] Cyclic prefix extension for S-SSB within a shared COT:

[0088] In one embodiment, S-SSB may be transmitted inside or outside the COT, and if its transmission occurs outside the COT, Type 2A LBT may be used when one or more of the following conditions are met:

[0089] ●S-SSB transmission is at most 1ms long

[0090] ●The duty cycle is at most 1 / 20

[0091] ●The duty cycle is calculated over a 50ms observation period

[0092] When a UE evaluates that its S-SSB transmission may occur within the shared COT, in one embodiment, if it also determines that a previous SL transmission (PSSCH / PSCCH or PSFCH) from itself or another UE may end one symbol before the start of the S-SSB transmission, such as Figure 4 As shown, the UE may append a cyclic prefix extension before the start of the S-SSB transmission in symbols preceding the following length:

[0093]

[0094] In one embodiment, l is an OFDM symbol to which cyclic prefix extension may be applied, μ identifies the subcarrier spacing (e.g., μ=0 corresponds to 15 kHz, μ=1 corresponds to 30 kHz, and μ=2 corresponds to 60 kHz), and Y may be fixed and equal to 13 us as an example, or may generally be less than or equal to 16 us if the UE transmitting the S-SSB is capable of operating within its own or another UE's COT. In one embodiment, as an alternative, the value of Y is (pre-)configured within each resource pool, or may be determined by the UE based on the UE's implementation. In one embodiment, even though Y may be provided by (pre-)configuration, its value may be predefined or fixed under the following conditions: the UE assesses that its S-SSB transmission may occur within the shared COT, and determines that a previous SL transmission (PSSCH / PSCCH or PSFCH) from itself or another UE may end one symbol before the start of the S-SSB transmission, such as Figure 4 shown.

[0095] In one embodiment, when the UE performs an S-SSB transmission outside of a shared COT, cyclic prefix extension is not applied prior to the S-SSB transmission. In this case, whether the UE may perform Type 2A or Type 1 LBT, this may end immediately prior to the first symbol of the S-SSB transmission (e.g., performing Type 2A and Type 1 LBT such that the assessment of whether the channel is idle or occupied occurs immediately prior to the S-SSB transmission).

[0096] In one embodiment, when the UE performs S-SSB transmission within the shared COT, and when the previous transmission may end more than one symbol earlier, a cyclic prefix extension is applied before the S-SSB transmission. In this case, the length of the cyclic prefix extension may be left to the UE implementation or based on a (pre-)configured value.

[0097] In one embodiment, for SL-U, the conditions under which Type 2C can be applied can be relaxed. For example, Type 2C can be applied within a shared COT regardless of the length of the transmission (which does not need to be shorter than 584us).

[0098] Sidelink AGC considerations for unlicensed spectrum operation

[0099] In the NR design, all SL transmissions start at predefined symbol positions within the slot. In addition, the first symbol of each SL transmission is a copy of the second symbol, where this physical structure is defined to support AGC at each slot as per RAN4 input on AGC convergence time. However, operating channel access at fixed / predefined positions in time is not suitable for operating in unlicensed spectrum with preemptive technologies, as these technologies access the channel at arbitrary times and across slot boundaries.

[0100] In one embodiment, channel access at any time with sub-symbol granularity is supported, where AGC can be invoked at any time within a time slot when a significant received signal power change is observed. In another option, such behavior can be avoided if no preemptive technology is deployed (e.g., indicating absenceOfAnyOtherTechnology).

[0101] In one embodiment, the following options may be used:

[0102] ● Option 1: All SL transmissions start at predefined symbol positions within the time slot;

[0103] ● Option 2: SL transmission can start at any symbol or a predefined or configurable set of symbols within a slot;

[0104] • Option 3: SL transmission can be configured to start at a given predefined symbol position or within a predefined set of starting positions (or can start at any symbol within a slot).

[0105] In one embodiment, the UE may apply CP extension prior to SL transmission, and this is used to enable additional time for preparing the actual waveform for PSCCH and / or PSSCH transmission.

[0106] In one embodiment, the AGC symbol may be lengthened and may be adapted to ensure that an immediate transmission occurs shortly after LBT is successfully performed by assessing that the channel is clear.

[0107] In one embodiment, different options and different embodiments among those described above may apply depending on whether the SL transmission may occur inside or outside the shared COT.

[0108] In one embodiment, the start of the OFDM symbol in a slot is offset to adjust the TX / RX gap and use the extended CP in conjunction with AGC adaptation.

[0109] In one embodiment, AGC adaptation is omitted since transmission only starts with PSCCH and AGC is adjusted during reception of PSCCH.

[0110] In one embodiment, the AGC is adjusted during transmission which does not imply anything that is demodulated.

[0111] Note that some of the options / embodiments provided above are not mutually exclusive but can be adopted in combination.

[0112] Potential impact of SL synchronization on LBT operations

[0113] As mentioned above, according to RAN4, the upper bound for TX / RX and RX / TX switching time is 13us in FR1 and 7us in FR2. The UE typically also has ON / OFF and OFF / ON transition periods on the order of 10us. In addition, the UE may also introduce SL synchronization errors (e.g., GNSS synchronization errors or gNB synchronization errors), and gNB SL synchronization additionally includes propagation delays, which for macro cell deployments can be on the order of several us (e.g., 2us or 4us for gNB-UE distances of 600m and 1200m, respectively). In addition, the gNB synchronization error can be on the order of up to 3us.

[0114] For SLs operating in unlicensed bands, the LBT procedure may be required and the UEs are expected to perform energy measurements within specific time instances. However, due to the above errors, the UEs may end up blocking each other based on the following two situations: Figure 5 As shown in the example:

[0115] ● Case 1: Depends on the location of UE2’s LBT type, the propagation delay between UE2 and UE1, Δ prop As well as the location of the energy measurement interval (observation window) within the LBT window of UE2, UE2 may be blocked by the transmission of UE1. In this case, the propagation delay from UE1 to UE2 is beneficial to UE2 and plays a positive role.

[0116] ● Case 2: Depends on the LBT type, propagation delay between UE2 and UE1, Δ prop As well as the location of the energy measurement interval (observation window) within the LBT window of UE1, UE1 may be blocked by UE2 in any subsequent transmission. In this case, the propagation delay from UE2 to UE1 is unfavorable to UE1 and plays a negative role.

[0117] Furthermore, even though two or more UEs may attempt to align their start transition times and the synchronization error may be negligible, blocking between them may still occur due to propagation delays, such as Figure 6 shown.

[0118] In one embodiment, when operating in unlicensed spectrum and operating the SL in TDM mode only, FDM between SL UEs is not supported.

[0119] In one embodiment, to alleviate the above problems, FDM between SL UEs is supported, and the LBT window and the energy measurement interval (observation window) within the LBT window are aligned between UEs to avoid mutual blocking.

[0120] In particular, when perfect alignment between UEs becomes impossible due to the above problems, in one embodiment, one or more of the following may be used to alleviate mutual blocking between UEs:

[0121] ○ Option 1: Use subchannel-based LBT or interlace-based LBT when OCB must be met. In this case, during the LBT procedure at the UE, energy measurements are evaluated / performed only within the subchannels or interlaces used by the UE for SL transmission.

[0122] ○ Option 2: Still perform LBT on the 20MHz LBT BW block, but adjust the ED threshold so that in the case of FDM, even if the header of a transmission performed by a UE may overlap with the LBT window of another UE, mutual blocking can be minimized. For example, in the case of FDM, the ED threshold can be further reduced, either by a fixed value or by simply using the effective bandwidth that the UE may be transmitting in the EDT threshold calculation.

[0123] ○ Option 3: In FDM, the LBT process or structure can be modified so that mutual blocking is alleviated:

[0124] ● Option 3a: UE pre-executes LBT window by considering the possible worst case scenario (the disadvantage is that transmission cannot happen immediately). For example, assuming a 3us error case, all LBT windows should be initiated 3us+LBT window before transmission.

[0125] ■ By way of implementation, this can be easily applied to both dynamic channel access mode and semi-static channel access mode.

[0126] ● Option 3b: For semi-static channel access mode, always force 4us measurements in the first 4us of the 9us measurement window. This will allow the device to ignore any energy measurements towards the end of the LBT window that may be caused by transmission misalignment. A similar approach can be applied to Type 1, Type 2a, and 2b in dynamic channel access mode, but the results may not be as efficient and deterministic as for semi-static channel access mode.

[0127] In one embodiment, to ensure that UEs can operate in FDM mode within a carrier (e.g., 20 MHz channel bandwidth) or across carriers, they are forced to terminate their LBT procedures at the same time and initiate transmission at the same time if LBT is successful. To ensure this type of operation, a cyclic prefix extension (CPE) may be appended before each transmission within a carrier or across carriers of each UE so that the UEs may not block each other during the LBT procedure and are able to transmit at the termination of LBT. In one option, the CPE length is equal to

[0128] T_(symb,(l-1)mod 7·2^μ)^μ-Y

[0129] Where l is an OFDM symbol to which cyclic prefix extension can be applied, and μ identifies the subcarrier spacing (e.g., μ=0 corresponds to 15 kHz, μ=1 corresponds to 30 kHz, and μ=2 corresponds to 60 kHz). As for the value of Y, one or more of the following options may be used:

[0130] Y is (pre)configured based on a predefined or (pre)configurable set of values ​​(as an example, it can be {16us, 25us, 34us, 43us, 52us, 61us or T_(symb,(l-1)mod 7·2^μ)^μ}).

[0131] Y is selected by the UE implementation over a set of predefined or (pre-)configurable values ​​(as an example, it may be {16us, 25us, 34us, 43us, 52us, 61us or T_(symb,(l-1)mod7·2^μ)^μ}).

[0132] Y is selected by the UE implementation.

[0133] Y is (pre-)configured based on a predefined or (pre-)configurable set of values ​​depending on the priority of the transmission (as an example, it can be {16us, 25us, 34us, 43us, 52us, 61us or T_(symb, (l-1) mod 7·2^μ)^μ}). In other words, based on the priority of the transmission, there may be different (pre-)configured cyclic prefix extensions, and the UE may apply the cyclic prefix extension based on the priority of the current transmission.

[0134] Y is selected by the UE implementation on a set of predefined or (pre-) configurable values ​​depending on the priority of the transmission (as an example, it can be {16us, 25us, 34us, 43us, 52us, 61us or T_(symb, (l-1) mod 7·2^μ)^μ}). In other words, based on the priority of the transmission, there may be different (pre-) configured cyclic prefix extensions, and the UE may apply the cyclic prefix extension based on the priority of the current transmission.

[0135] In one embodiment, the cyclic shift prefix is ​​appended only for UEs operating in RA mode 2. Alternatively, the cyclic shift prefix is ​​appended regardless of the RA mode the UE is operating in. In one embodiment, the cyclic shift prefix is ​​appended only for UEs operating outside a shared COT. Alternatively, the cyclic shift prefix is ​​appended regardless of whether the UE may operate outside or within a shared COT that may belong to itself or another UE.

[0136] Randomize or pseudo-randomize LBT window

[0137] When operating in TDM mode, it may happen that two UEs select the same set of resources from a resource pool or a set of resources, which results in the same start time for their transmissions. In this case, by performing LBT simultaneously, the two UEs may not be able to hear each other and, while being able to successfully assess that the channel is idle and transmit (by potentially even obtaining overlapping COTs), their transmissions may collide with each other, e.g. Figure 7 shown.

[0138] To mitigate mutual interference, in one embodiment, CP extension may be applied before the actual transmission burst begins, and each UE may randomly pick the length of the CP extension (e.g., from a predefined set of values) so that the start position of each transmission is randomized, ensuring that one UE will not block another UE during the LBT process and their transmissions will never collide. Figure 8 This mechanism is shown in .

[0139] In general, in one embodiment, UEs may use an LBT measurement bandwidth aligned with the structure of their transmission bandwidth or frequency subchannels to determine whether they can access a channel on any frequency resource.

[0140] In one embodiment, the mechanism defined above may be implemented by using the same principle as the starting position within the Rel-16 CG symbol, and the CP extension to be used may be defined as follows:

[0141]

[0142] where μ identifies the subcarrier spacing (e.g., μ=0 corresponds to 15 kHz, μ=1 corresponds to 30 kHz, and μ=2 corresponds to 60 kHz), and Δ i Links to a set of predefined values, which, as an example, may be defined in the following table:

[0143]

[0144]

[0145] In one embodiment, the cyclic shift prefix is ​​appended only for UEs operating in RA mode 2. Alternatively, the cyclic shift prefix is ​​appended regardless of the RA mode the UE is operating in. In one embodiment, the cyclic shift prefix is ​​appended only for UEs operating outside a shared COT. Alternatively, the cyclic shift prefix is ​​appended regardless of whether the UE may operate outside or within a shared COT that may belong to itself or another UE.

[0146] In one embodiment, when the UE performs a SL transmission outside of a shared COT, cyclic prefix extension is not applied. In this case, independent of the type of LBT performed by the UE, this may end just before the first symbol of the SL transmission (e.g., performing LBT such that the assessment of whether the channel is idle or occupied will occur just before the actual SL transmission).

[0147] In one embodiment, the UE may apply one or more of the following criteria to select a cyclic prefix extension to append prior to its transmission:

[0148] • The UE randomly selects a cyclic prefix extension to apply before its transmission, either by randomly picking among a fixed / predefined set of values ​​or on a subset of values ​​that are (pre-)configured and selected from a predefined set of values.

[0149] • The UE may select the cyclic prefix extension to apply based on the priority of the transmission. For example, define a set of predefined cyclic prefix extension values ​​and associate each of them or a set of them with a specific priority.

[0150] • Different sets of values ​​may be defined based on whether the transmission occurs within or outside the COT.

[0151] In one embodiment, the above method may only be applied to one or more of the following types of SL transmissions:

[0152] PSSCH / PSCCH

[0153] PSFCH

[0154] S-SSB

[0155] ON / OFF and OFF / ON transition time considerations for unlicensed spectrum operation

[0156] As discussed herein, when operating in unlicensed spectrum, the LBT procedure can be enforced. Specifically, if the time gap between subsequent SL transmissions is greater than or equal to 16us, energy measurements must be performed within the LBT window. In addition, according to RAN4 requirements, NR transmissions have ON / OFF and OFF / ON transition periods, which are limited to T for operation in unlicensed spectrum. ONOFF = 10us as the boundary, and it has been defined Figure 8 The mask shown:

[0157] That being said, in order to avoid Fig.10 The measurement of transition effects within the LBT window depicted in Figure 2 requires some special considerations.

[0158] In one embodiment, the minimum gap between consecutive SL transmissions requiring LBT should be readjusted to account for ON / OFF and OFF / ON transition periods. For example, for dynamic channel access mode, the minimum gap should be at least T ONOFF / 2(5us)+T LBT (16us)+T OFFON / 2(5) = 26us (or 21us if the implementation in the LBT process includes a 5us OFF-ON by performing a 4us measurement 5us before the end of the observation period). For the semi-static channel access mode, the minimum gap should be at least T ONOFF / 2(5us)+T LBT (Xus)+T OFFON / 2(5)=X=10us (or X+5us if the implementation in the LBT process includes a 5us OFF-ON by performing a 4us measurement 5us before the end of the observation period), where X=9us except in China or any other region where a minimum observation window of X=16us is required.

[0159] In one embodiment, the position of the measurement window within the observation window of the LBT process is modified so that the ON / OFF and OFF / ON transition periods are taken into account, and the position of the measurement window is pre-configured by the specification or by the gNB / network, or appropriately selected by the UE implementation. As an example of this method, modify according to one of the following options Fig.11 A Type 2B LBT depicted in:

[0160] ○ Option 1: The values ​​of parameters Δ1, Δ2, Δ3, Δ4 are left to the UE implementation

[0161] ○ Option 2: The values ​​of Δ1, Δ2, Δ3, Δ4 are pre-configured by the gNB / network

[0162] ○ Option 3: Boundaries for values ​​of Δ1, Δ2, Δ3, Δ4 are predefined by the specification

[0163] Note that the above example can be applied to any other LBT type in a straightforward manner.

[0164] The above problem may not be critical for UL to UL transmission switching between different devices, because there may always be enough gaps between SL transmissions from different UEs so that the ON / OFF and OFF / ON transition times will not affect the LBT process. In NR-U SL, UL to UL transmission switching from exactly the same device is actually very common due to PSFCH transmissions, and depending on the gaps between bursts, the device can indeed block itself. For example, for 60kHz SCS, one symbol gap is equal to ~16us, but when performing 16us LBT due to the 5us transition time from the end of the first burst and the beginning of the subsequent burst, the second burst may be blocked and cannot be sent. To alleviate this additional problem, in one embodiment, one or more of the following options can be adopted:

[0165] Option 1: Gaps smaller than a certain duration should be avoided by the UE and should be filled by the UE with additional transmissions (e.g., CP extension, reference signals, data signals, or any other options that may include dummy / junk transmissions) to form continuous transmissions. For example, 1 and 2 symbol gaps for 60kHz SCS and 1 symbol gap for 30kHz SCS are not allowed and are always filled by the UE.

[0166] • Option 2: Gaps smaller than a certain duration are not allowed and the UE shall drop subsequent transmissions. For example, 1 and 2 symbol gaps for 60 kHz SCS and 1 symbol gap for 30 kHz SCS are not allowed.

[0167] Option 3: The gap defined by ETSI BRAN is adjusted by 10us (or 5us), and specifically, one or more of the following may be adopted:

[0168] ○ No LBT can be extended to 16+10us or 16+5us (where the OFF / ON transition time can be accounted for by implementation and by performing 4us measurement at the head of the 9us observation window), which means no LBT for 1 symbol slot for 60kHz SCS.

[0169] ○ If the gap is greater than 16+10us (or 16+5us) and less than 25+10us (or 25+5us), apply 16us LBT

[0170] ○If the gap is greater than 25+10us (or 25+5us), apply 25us LBT

[0171] • Option 4: The transition period is absorbed within the start time interval of the transmission, and / or the transition period is absorbed within the end time interval of the transmission.

[0172] o In this case, a small gap equal to the duration of the LBT window can be supported

[0173] ○ A UE receiving a transmission may be allowed to skip processing of symbols affected by the transition period

[0174] ● Option 5: Reduce the transition period to 5us (e.g., impose new requirements on the transition period)

[0175] • Option 6: Modify the RAN4 masking so that the transition period within the SL transmission is captured, so no transmission will overflow and potentially overlap within the LBT window.

[0176] ● Option 7: The position of the measurement window is fixed to a specific time instance within the measurement window. For example

[0177] ○ For Type 2B LBT, a 1us measurement window is performed in the last 3us of the first 7us observation window, and / or a 4us measurement window is performed in the first 4us of the last 9us observation window.

[0178] o For the 9us observation time for the semi-static channel access mode, a 4us sensing window is performed in the first or last 4us of the observation time.

[0179] The physical structure of frequency interleaving

[0180] The regulations on power spectral density (PSD) limits of 10dBm / MHz for ETSI and MIIT and 11dBm / MHz for FCC, as well as a minimum percentage of occupied channel bandwidth (OCB) of 80%-100% (see ETSI EN 301 893), imply the need to use bandwidth extension at the expense of spectral efficiency, or to support an interleaved channel structure that improves coverage with maximum spectral efficiency.

[0181] In Rel.16 NR-U uplink, interleaved waveforms are introduced and supported for both PUCCH transmission and PUSCH transmission. The frequency domain allocation for PUCCH and PUSCH is controlled by the higher-layer parameter useInterlacePUCCH-PUSCH. As an example, in Fig.12 FIG. 4 shows how different RBs are interleaved in a 30kHz subcarrier spacing (SCS).

[0182] When the use of interleaved PUCCH-PUSCH is configured, for 15kHz and 30kHz SCS, the interlaces are formed based on the following table, where M is the number of interlaces per carrier and N is the number of RBs per interlace:

[0183] SCS(kHz) NRB (for 20MHz) M N 15 106 10 10 / 11 30 51 5 10 / 11

[0184] For 60kHz SCS or higher, interleaving is not supported.

[0185] In this context, there are several specific challenges for implementing NR-U SL. The embodiments of this document provide techniques for implementing an interleaving structure for a physical layer channel of SL. The interleaving structure can be a general solution applicable to any physical channel (e.g., a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), a physical sidelink feedback channel (PSFCH), a sidelink synchronization signal block (S-SSB), and / or a physical sidelink broadcast channel (PSBCH)).

[0186] For SL communication, support for an interleaved structure may be considered for several UL physical channels (e.g., PSCCH / PSSCH / PSFCH / S-SSB and PSBCH). However, note that even in the SL Rel.16 / 17 design, when the UE sends feedback for multiple SL transmissions, the PSFCH transmissions may already be spread across the SL resource pool bandwidth. When considering an interleaved structure for SL, the following solutions may be considered:

[0187] ● Interleaving solutions based on interleaving a single RB. Rel.16 NR-U solution is an example of this category.

[0188] • Interleaving solutions based on interleaving a set of RBs. These solutions have the advantage over single RB solutions that they are more robust with respect to frequency offsets between different UEs transmitting simultaneously.

[0189] ● Interleaving solutions based on interleaving subcarriers Note that interleaving a subcarrier group can be considered the same as interleaving a RB or a RB group.

[0190] All interleaving solutions divide the number of available frequency resources into M parts. Since the concept of subchannels is introduced for SL, one of these parts can be considered as a subchannel. Therefore, in the description of various embodiments of this document, a subchannel can generally refer to a group of frequency resources, but not in the NR SL definition of several adjacent RBs. Note that for some options, it can be assumed that the NR SL resource pool configuration is extended to accommodate additional information required for NR-U SL operation.

[0191] Single RB interleaving

[0192] For the single RB solution, a compromise between the NR SL and NR-U solutions can be taken. In this regard, in one embodiment, one of the following options can be used:

[0193] ● Option 1: In this option, the number K RBs configured per resource pool are divided into M subchannels, each subchannel comprising N RBs. Note that the remaining K–M*N RBs are not used for transmission, in the same way as in NR SL. The N logical RBs of each subchannel are mapped to the physical RBs in an interleaved manner. This means that the resource pools are configured in the same way as in Rel.16 NR SL, but with an additional RRC bit signaling the use of interleaved subchannel logical to physical RB mapping. Fig.13A An example is shown. In one example, M is configurable or fixed and is equal to 10 for 15 kHz and 5 for 30 kHz.

[0194] ● Option 2: In this option, the configuration of the resource pool is changed. In this case, an additional field needs to be introduced to indicate the interleaving mapping. Based on this field, the Rel.16NR SL field indicating the number of subchannels needs to be reinterpreted, or a new field for the number of interleaved frequency parts (also called subchannels) needs to be introduced. The current Rel.16 field indicating the number of RBs per subchannel is redundant in this case, so it can be reinterpreted. Based on this signaling, the number K of available RBs is divided into M subchannels. Note that in this case, these subchannels may have different sizes compared to Rel.16NR SL, as some subchannels will have size, while some have The remaining RBs can be mapped to any subchannel. Fig. 13B An example is shown in . In one example, M is configurable or fixed and is equal to 10 for 15kHz and 5 for 30kHz. Note that by choosing M=10 and M=5 for 15kHz and 30kHz SCS respectively, this fully mimics the interleaving structure defined in NR-U, where some interleavings will be formed by K=10 PRBs and some interleavings will be formed by K=11 PRBs in the same way as Rel.16 NR-U.

[0195] In one embodiment, whether option 1 or option 2 is supported, the UE may be configured to transmit on one or more interlaces.

[0196] In one embodiment, the interleaving structure provided by the above embodiment may be applied to one or more of the following physical channels:

[0197] -PSCCH;

[0198] -PSSCH;

[0199] -PSFCH;

[0200] -PSBCH;

[0201] -S-SSB.

[0202] In one embodiment, for PSCCH and PSSCH transmission, one subchannel for PSSCH is equal to an N RB-based interleaving over all RB sets within the resource pool, where N is fixed (eg, N=1) or may be (pre-)configured.

[0203] Group RB interleaving

[0204] From the receiver's point of view, it cannot always be guaranteed that the frequency synchronization of different UEs is perfect. For interleaved transmission, this means that the SCs at the edges of a group of subcarriers (SCs) will experience inter-carrier interference (ICI) because the SCs from other UEs will not be completely orthogonal. Depending on how large the expected frequency offset between different UEs is, this may be motivated to use a group of SCs larger than one RB for each UE. This also has the benefit of improved channel estimation, because in this case all RSs in the group can be considered to perform it instead of just a single RB. As in the case of single RB interleaving, the remaining RBs can either be included in the transmission or not considered. In this regard, in one embodiment, one of the following options can be used:

[0205] ● Option 1: After all available PBs are distributed to M subchannels, all remaining additional RBs are not used. Afterwards, the N RBs per subchannel are divided into L RB groups. The RB groups for each subchannel are then mapped to interleaved RB groups. Note that depending on the number of RBs, not every group must have the same size. The signaling for resource pool configuration will consist of an additional PRG group size field. In addition, mapping rules for groups need to be established. In one example, M, N, and L are configurable, or can be fixed.

[0206] ● Option 2: In the second case, all RBs are used. This means that compared to option 1, the remaining RBs are added to the first (last or any other mapping) subchannel. Again, the RBs in each subchannel are divided into L RB groups. Fig.14 As shown in the example in . Note that in this case, the RB groups within a subchannel do not necessarily have the same size either. The resource pool signaling will be the same as option 2 for the single RB interleaving case, with only an additional field added for the number of RB groups per subchannel or the minimum number of RBs per RB group. In one example, M, N, and L are configurable or can be fixed.

[0207] In one embodiment, whether option 1 or option 2 is supported, the UE may be configured to transmit on one or more interlaces.

[0208] In one embodiment, the interleaving structure provided by the above embodiment may be applied to one or more of the following physical channels:

[0209] -PSCCH;

[0210] -PSSCH;

[0211] -PSFCH;

[0212] -PSBCH;

[0213] -S-SSB.

[0214] Subcarrier-based interleaving

[0215] The third interleaving category is to interleave a single subcarrier. Note that the subcarrier groups are not treated separately, as this would be the case if a group of SCs were treated as RBs (potentially of different sizes). In this case, the signaling would also consist of only one additional information field indicating that subcarrier-based interleaving is used. Fig.15 As shown, a comb-x SC structure may be used. In the example shown, 5 different frequency resources are available.

[0216] In one embodiment, whether option 1 or option 2 is supported, the UE may be configured to transmit on one or more interlaces.

[0217] In one embodiment, the interleaving structure provided by the above embodiment may be applied to one or more of the following physical channels:

[0218] -PSCCH;

[0219] -PSSCH;

[0220] -PSFCH;

[0221] -PSBCH;

[0222] -S-SSB.

[0223] Configuration parameters

[0224] In one embodiment, the interleaving structure may be enabled or disabled based on regional compliance, and a cell-specific high-layer parameter may be introduced to enable the interleaving physical structure. In this regard, one of the following options may be adopted:

[0225] • Option 1: A new RRC parameter (e.g., useInterlacePSCCH-PSSCH or useInterlacePSCCH-PSSCH-PSFCH) may be defined to enable and disable the waveform based on whether regional requirements would require this waveform for SL in unlicensed spectrum.

[0226] • Option 2: The same RRC parameter as defined in Rel.16 (eg, useInterlacePUCCH-PUSCH) may be used, as this is only an indication that interleaving is required due to regional compliance.

[0227] In separate options, these configurations can be made part of the resource pool configuration. In fact, as mentioned above, when listing the interleaving options for some of these options, additional signaling fields are required.

[0228] Note that enabling an interleaving structure does make the interleaving structure mandatory for transmissions on the physical channels to which this structure is applied. Other options include the interleaving structure depending on other system conditions, such as one or more of the following:

[0229] COT sharing

[0230] System load

[0231] LBT status

[0232] ●Unicast / multicast connection status

[0233] Network configuration

[0234] As an example, the interleaving structure may be used by a UE initiating a COT, but may not be required in a shared COT.

[0235] Note that some of the options / embodiments provided above are not mutually exclusive but can be adopted in combination.

[0236] Indication of interleaved mapping

[0237] Embodiments herein may also relate to indication of interleaving mapping. In Rel.16 NR-U, the X bit from the FDRA field (DCI or RRC) is used to indicate one or more interleavings that the UE should use for PUSCH or PUCCH transmission at a given time, where:

[0238] - X = 5 bits for 30kHz SCS, where 5 bits form a bitmap for 5 interleavings;

[0239] - X = 6 bits for 15kHz SCS, where the interlace indication is based on the RIV-based approach for 10 interlaces, where:

[0240] o RIV values ​​0..54 indicate the starting interleaving index and the number of consecutive interleaving indices.

[0241] ○ RIV values ​​55..63 indicate the following interleaving combinations:

[0242] RIV Interleaved Index 55 0,5 56 0,1,5,6 57 1,6 58 1,2,3,4,6,7,8,9 59 2,7 60 2,3,4,7,8,9 61 3,8 62 4,9 63 reserve

[0243] Moving forward to Rel.18 SL, a few methods may be used to appropriately indicate the interleaving set to be used via sl-TxPoolScheduling, and in one embodiment, one or more of the following options may be used:

[0244] ●Option 1: When the resource pool configuration parameters that are defined / used to indicate that an interleaved waveform is required are configured, sl-SubchannelSize-r16 is released, sl-StartRB-Subchannel-r16 is reinterpreted to indicate the lowest or highest RB for a specific interleave, and sl-NumSubchannel-r16 can be reinterpreted to indicate the number of consecutive interleaves (in the frequency domain) to be used.

[0245] In case additional interleaving signaling is required, new fields may be introduced and these fields may be one or more of the following:

[0246] ○ Interleaving PRB group size;

[0247] ○ Allowed frequency resource allocation per LBT type.

[0248] Option 2: When a resource pool configuration parameter is configured that is defined / used to indicate that an interleaved waveform is required, an additional dedicated parameter may be added within the SL-ResourcePool IE to specify the interleaving set to be used. For example, one or more of the following may be introduced:

[0249] ○ Indication of the lowest or highest PRB for a particular interlace or interlace set;

[0250] ○The number of consecutive PRBs;

[0251] ○ A bitmap indicating the interleaving to be used.

[0252] ● Option 3: Where the use of an interleaved physical structure is optional or conditional on system state. This means that wideband, interleaved, and subchannel based channel access potentially need to coexist. This means that configurations for all channel access methods need to exist in the resource pool configuration. In this regard, there are two sub-options that can be considered:

[0253] ○ Option 3A: For any combination of the current frequency allocation methods, there is a single configuration of frequency resources.

[0254] ○ Option 3B: This configuration is based on the reinterpretation of the already existing sub-channel based resource pool configuration fields. Additional functionality for other frequency allocation methods is based on the reinterpretation of these fields or the addition of new fields.

[0255] In one embodiment, SL Control Indication (SCI) 1-x (level 1 or level 2 or both) or DCI 3_x or both may be enhanced to carry additional information related to one or more interlaces that the UE may be using for transmission. Specifically, with respect to FDRA signaling in SCI 1-x and DCI 3_x, one or more of the following options may be considered:

[0256] Option 1: The concept of reusing the FDRA field design from SCI 1-x in DCI 3_x can be reused. At the same time, the frequency offset used for the initial transmission scheduled by DCI 3_x needs to be modified to accommodate the interleaved resource allocation. In this case, the lowest index of the subchannel allocation for the initial transmission can be signaled as an interleaving index from 0 to M-1.

[0257] ● Option 2: When RRC parameters defined / used to indicate that an interleaved waveform is required are configured, the FDRA field within DCI 3_x and SCI 1-x is reinterpreted and the X bit is used to indicate the interleaving or interleaving set to be used as in Rel.16NR-U. In one option, if wideband operation is supported in SL, the Y bit is additionally used to indicate which RB sets (corresponding to the LBT BW) are allocated to the UE, where Y is determined by the number N of RB sets contained in the BWP, as follows:

[0258] ○ Option 2a: In one sub-option, the field "First transmission sub-channel index" is not carried in DCI 3_x, or the field is reorganized for other purposes, and the transmission spans across the entire configured interlace or interlace set.

[0259] ○ Option 2b: In one sub-option, the field "First transmission sub-channel index" is carried within DCI 3_x, and it is used to signal the lowest index of the RBs belonging to the selected interlace set that the initial transmission can span.

[0260] ● Option 3: For SCI 1-x and DCI 3_x signaling, keep the structure from Rel.16SL. This means that the PSCCH only exists in one subchannel, because the starting subchannel of the transmission needs to be connected to the PSCCH location.

[0261] - Option 4: To indicate the used / reserved subchannel, the indicated subchannel index is determined by the interleaving index within the RB set and the RB set index within the resource pool. In this case, the index follows the interleaving index first and then the RB set index.

[0262] - Option 5: To indicate the used / reserved subchannels, the UE may indicate the interlace index or subchannel index within the RB set and the RB set index within the resource pool in an independent manner.

[0263] In terms of UE capabilities, in one embodiment, one of the following options may be adopted and relevant considerations may be made:

[0264] ●Alt.1: Interleaving is mandatory for NR-U SL from both RX and TX perspective.

[0265] ●Alt.2: Interleaving is optional for NR-U SL from TX perspective, but it is mandatory from RX perspective.

[0266] ●Alt.3: Interleaving is optional for NR-U SL from both TX and RX perspective.

[0267] In one embodiment, the PRBs of the intra-cell guard band belonging to two adjacent RB sets can be used for SL transmission. In one option, this is limited to the case when the UE can successfully perform LBT on these two RB sets and the UE performs simultaneous transmission on these two RB sets.

[0268] In one embodiment, PRBs in the intra-cell guard band belonging to two adjacent RB groups are never used for SL transmission.

[0269] Note that some of the options / embodiments provided above are not mutually exclusive but can be adopted in combination.

[0270] Systems and implementation

[0271] Figure 16-18 Various systems, devices, and components are shown in which aspects of the disclosed embodiments may be implemented.

[0272] Fig.16 A network 1600 according to various embodiments is shown. The network 1600 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, example embodiments are not limited thereto, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0273] The network 1600 may include a UE 1602, which may include any mobile or non-mobile computing device designed to communicate with the RAN 1604 via an air connection. The UE 1602 may be communicatively coupled to the RAN 1604 via a Uu interface. The UE 1602 may be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-mounted display device, an in-vehicle diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0274] In some embodiments, the network 1600 may include multiple UEs directly coupled to each other via a sidelink interface. The UE may be an M2M / D2D device that communicates using a physical sidelink channel (e.g., but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

[0275] In some embodiments, UE 1602 may additionally communicate with AP 1606 via an over-the-air connection. AP 1606 may manage WLAN connections, which may be used to offload some / all network traffic from RAN 1604. The connection between UE 1602 and AP 1606 may conform to any IEEE 802.11 protocol, wherein AP 1606 may be a Wireless Fidelity Router. In some embodiments, UE 1602, RAN 1604 and AP 1606 may utilize cellular-WLAN aggregation (eg, LWA / LWIP). Cellular-WLAN aggregation may involve UE 1602 being configured by RAN 1604 to utilize both cellular radio resources and WLAN resources.

[0276] RAN 1604 may include one or more access nodes, such as AN 1608. AN 1608 may terminate the air interface protocol for UE 1602 by providing access layer protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 1608 may implement data / voice connections between CN 1620 and UE 1602. In some embodiments, AN 1608 may be implemented in a discrete device, or as one or more software entities running on a server computer as part of a virtual network (which may be referred to as a CRAN or a virtual baseband unit pool), for example. AN 1608 is referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 1608 may be a macro cell base station, or a low power base station for providing a femto cell, a pico cell, or other similar cells with a smaller coverage area, a smaller user capacity, or a higher bandwidth than a macro cell.

[0277] In an embodiment where the RAN 1604 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 1604 is an LTE RAN) or an Xn interface (if the RAN 1604 is a 5G RAN). The X2 / Xn interface (which may be separated into a control / user plane interface in some embodiments) may allow the ANs to transfer information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0278] The ANs of the RAN 1604 may each manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to the UE 1602. The UE 1602 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 1604. For example, the UE 1602 and the RAN 1604 may use carrier aggregation to allow the UE 1602 to connect to multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a primary node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second AN may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0279] RAN 1604 may provide an air interface on a licensed spectrum or an unlicensed spectrum. To operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms with PCell / Scell ​​based on CA technology. Before accessing the unlicensed spectrum, a node may perform a medium / carrier sensing operation based on, for example, a listen-before-talk (LBT) protocol.

[0280] In the V2X scenario, UE 1602 or AN 1608 may be or act as an RSU, which may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by the following items: for a UE, it may be referred to as a "UE-type RSU"; for an eNB, it may be referred to as an "eNB-type RSU"; for a gNB, it may be referred to as a "gNB-type RSU"; etc. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the roadside that provides connection support to passing vehicle UEs. The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high-speed events (e.g., collision avoidance, traffic warnings, etc.). Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be housed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0281] In some embodiments, the RAN 1604 may be an LTE RAN 1610 with an eNB (e.g., eNB 1612). The LTE RAN 1610 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; Turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on a sub-6 GHz frequency band.

[0282] In some embodiments, the RAN 1604 may be a NG-RAN 1614 having a gNB (e.g., gNB 1616) or an ng-eNB (e.g., ng-eNB 1618). The gNB 1616 may be connected to a 5G-enabled UE using a 5G NR interface. The gNB 1616 may be connected to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1618 may also be connected to the 5G core via an NG interface, but may be connected to the UE via an LTE air interface. The gNB 1616 and the ng-eNB 1618 may be connected to each other via an Xn interface.

[0283] In some embodiments, the NG interface can be divided into two parts: an NG user plane (NG-U) interface, which carries service data between the nodes of NG-RAN 1614 and UPF 1648 (e.g., N3 interface); and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of NG-RAN 1614 and AMF 1644 (e.g., N2 interface).

[0284] NG-RAN 1614 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarization codes, Repetition codes, Simplex codes and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use PBCHDMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate on a FR1 band including a sub-6 GHz band or a FR2 band including a band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB, which is an area of ​​a downlink resource grid including PSS / SSS / PBCH.

[0285] In some embodiments, the 5G-NR air interface may utilize BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, UE 1602 may be configured with multiple BWPs, each of which is configured with a different SCS. When a BWP change is indicated to UE 1602, the transmitted SCS also changes. Another use case example of BWP is related to power saving. Specifically, UE 1602 may be configured with multiple BWPs with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs may be used for data transmission with a small traffic load while allowing power saving at UE 1602 and in some cases at gNB 1616. A BWP containing a larger number of PRBs may be used in scenarios with higher traffic loads.

[0286] RAN 1604 is communicatively coupled to CN 1620, which includes network elements to provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UE 1602). The components of CN 1620 may be implemented in one physical node or in separate physical nodes. In some embodiments, NFV may be used to virtualize any or all functions provided by the network elements of CN 1620 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN 1620 may be referred to as a network slice, and a logical instantiation of a portion of CN 1620 may be referred to as a network sub-slice.

[0287] In some embodiments, CN 1620 may be LTE CN 1622 (which may also be referred to as EPC). LTE CN 1622 may include MME 1624, SGW 1626, SGSN 1628, HSS 1630, PGW 1632, and PCRF 1634, which are coupled to each other via interfaces (or "reference points") as shown. The functions of the elements of LTE CN 1622 may be briefly described as follows.

[0288] The MME 1624 may implement mobility management functions to track the current location of the UE 1602 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0289] The SGW 1626 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 1622. The SGW 1626 may be the local mobility anchor for handovers between RAN nodes and may also provide anchoring for inter-3GPP mobility. Other responsibilities may include legal interception, charging, and some policy enforcement.

[0290] SGSN 1628 can track the location of UE 1602 and perform security functions and access control. In addition, SGSN 1628 can perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1624; MME selection for handover; etc. The S3 reference point between MME 1624 and SGSN 1628 can realize user and bearer information exchange for 3GPP indirect access mobility in idle / active state.

[0291] The HSS 1630 may include a database for network users, including subscription related information, to support the handling of communication sessions by network entities. The HSS 1630 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. The S6a reference point between the HSS 1630 and the MME 1624 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access the LTE CN 1620.

[0292] The PGW 1632 may terminate the SGi interface towards a data network (DN) 1636, which may include an application / content server 1638. The PGW 1632 may route data packets between the LTE CN 1622 and the data network 1636. The PGW 1632 may be coupled to the SGW 1626 via an S5 reference point to facilitate user plane tunnels and tunnel management. The PGW 1632 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 1632 and the data network 1636 may be an operator external public, private PDN, or an operator internal packet data network (e.g., for provisioning IMS services). The PGW 1632 may be coupled to the PCRF 1634 via a Gx reference point.

[0293] PCRF 1634 is the policy and charging control element of LTE CN 1622. PCRF 1634 can be communicatively coupled to app / content server 1638 to determine appropriate QoS and charging parameters for service flows. PCRF 1632 can distribute the associated rules to PCEF with appropriate TFT and QCI (via Gx reference point).

[0294] In some embodiments, CN 1620 may be 5GC 1640. 5GC 1640 may include AUSF 1642, AMF 1644, SMF 1646, UPF 1648, NSSF 1650, NEF 1652, NRF 1654, PCF 1656, UDM 1658, and AF 1660, which are coupled to each other through interfaces (or "reference points") as shown. The functions of the elements of 5GC 1640 may be briefly described as follows.

[0295] AUSF 1642 can store data for authentication of UE 1602 and handle authentication related functions. AUSF 1642 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 1640 through reference points as shown, AUSF 1642 can also expose interfaces based on Nausf services.

[0296] AMF 1644 may allow other functions of 5GC 1640 to communicate with UE 1602 and RAN 1604 and subscribe to notifications about mobility events for UE 1602. AMF 1644 may be responsible for registration management (e.g., for registering UE 1602), connection management, reachability management, mobility management, legal interception of AMF-related events, and access authentication and authorization. AMF 1644 may provide transport for SM messages between UE 1602 and SMF 1646 and act as a transparent proxy for routing SM messages. AMF 1644 may also provide transport for SMS messages between UE 1602 and SMSF. AMF 1644 may interact with AUSF 1642 and UE 1602 to perform various security anchoring and context management functions. In addition, AMF 1644 can be the termination point of the RANCP interface, which can include or be the N2 reference point between RAN 1604 and AMF 1644; and AMF 1644 can be the termination point of NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 1644 can also support NAS signaling with UE 1602 through the N3IWF interface.

[0297] SMF 1646 may be responsible for SM (e.g., session establishment, tunnel management between UPF 1648 and AN 1608); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring service steering at UPF 1648 to route services to the correct destination; terminating interfaces toward policy control functions; controlling a portion of policy enforcement, billing, and QoS; legal interception (for SM events and interfaces to LI systems); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN 1608 via N2 via AMF 1644; and determining the SSC mode for a session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between UE 1602 and data network 1636.

[0298] The UPF 1648 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 1636, and a branch point to support multi-homed PDU sessions. The UPF 1648 may also perform packet routing and forwarding, perform packet inspection, implement the user plane portion of policy rules, legal intercept packets (UP collection), perform service usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink service verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1648 may include an uplink classifier to support routing of service flows to the data network.

[0299] NSSF 1650 may select a set of network slice instances to serve UE 1602. NSSF 1650 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI (if necessary). NSSF 1650 may also determine the AMF set or list of candidate AMFs to be used to serve UE 1602 based on appropriate configuration and possibly by querying NRF 1654. The selection of a set of network slice instances for UE 1602 may be triggered by the AMF 1644 registered by UE 1602 through interaction with NSSF 1650, which may result in a change in AMF. NSSF 1650 may interact with AMF 1644 via the N22 reference point; and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, NSSF 1650 may expose an interface based on Nnssf services.

[0300] NEF 1652 can securely open services and capabilities provided by 3GPP network functions to third parties, internal opening / reopening, AF (e.g., AF1660), edge computing or fog computing systems, etc. In such an embodiment, NEF 1652 can authenticate, authorize or restrict AF. NEF 1652 can also convert information exchanged with AF 1660 and information exchanged with internal network functions. For example, NEF 1652 can convert between AF service identifiers and internal 5GC information. NEF 1652 can also receive information from other NFs based on the capabilities opened by other NFs. The information can be stored at NEF 1652 as structured data, or stored at a data storage NF using a standardized interface. The stored information can then be reopened by NEF 1652 to other NFs and AFs, or used for other purposes (e.g., analysis). In addition, NEF 1652 can display interfaces based on Nnef services.

[0301] NRF 1654 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 1654 also maintains information of available NF instances and the services they support. As used herein, the terms "instantiate", "instantiation", etc. may refer to the creation of an instance, while "instance" may refer to the specific appearance of an object, which may occur, for example, during program code execution. In addition, NRF 1654 may expose an interface based on Nnrf services.

[0302] PCF 1656 can provide policy rules to the control plane functions to implement them, and can also support the unified policy framework to manage network behavior. PCF 1656 can also implement a front end to access subscription information related to policy decisions in the UDR of UDM 1658. In addition to communicating with functions through reference points as shown in the figure, PCF 1656 also exposes an interface based on Npcf services.

[0303] UDM 1658 can process subscription-related information to support the processing of communication sessions by network entities, and can store subscription data of UE 1602. For example, subscription data can be transferred via the N8 reference point between UDM 1658 and AMF 1644. UDM 1658 can include two parts: application front end and UDR. UDR can store subscription data and policy data for UDM 1658 and PCF 1656, and / or structured data for openness and application data for NEF 1652 (including PFD for application detection, application request information for multiple UE 1602). Nudr service-based interfaces can be displayed by UDR to allow UDM 1658, PCF 1656 and NEF 1652 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of changes in relevant data in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 1658 can also expose Nudm service-based interfaces.

[0304] AF 1660 may provide application influence on service routing, provide access to NEF, and interact with the policy framework for policy control.

[0305] In some embodiments, 5GC 1640 can enable edge computing by selecting an operator / third-party service to be geographically close to the point where UE 1602 attaches to the network. This can reduce latency and load on the network. In order to provide edge computing implementation, 5GC 1640 can select UPF 1648 close to UE 1602 and perform service guidance from UPF 1648 to data network 1636 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 1660. In this way, AF 1660 can affect UPF (re)selection and service routing. Based on operator deployment, when AF 1660 is considered a trusted entity, the network operator can allow AF 1660 to interact directly with relevant NFs. In addition, AF 1660 can expose an interface based on Naf services.

[0306] The data network 1636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers (including, for example, an application / content server 1638).

[0307] Fig.17 Schematically illustrated is a wireless network 1700 in accordance with various embodiments. The wireless network 1700 may include a UE 1702 in wireless communication with an AN 1704. The UE 1702 and the AN 1704 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.

[0308] UE 1702 may be communicatively coupled to AN 1704 via connection 1706. Connection 1706 is shown as an air interface to implement the communicatively coupling and may conform to a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

[0309] The UE 1702 may include a host platform 1708 coupled to a modem platform 1710. The host platform 1708 may include an application processing circuit 1712, which may be coupled to a protocol processing circuit 1714 of the modem platform 1710. The application processing circuit 1712 may run various applications for outgoing / incoming application data of the UE 1702. The application processing circuit 1712 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0310] The protocol processing circuitry 1714 may implement one or more layer operations to facilitate sending or receiving data over the connection 1706. The layer operations implemented by the protocol processing circuitry 1714 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0311] The modem platform 1710 may also include digital baseband circuitry 1716, which may implement one or more layer operations that are "lower" layer operations in the network protocol stack that are performed by the protocol processing circuitry 1714. These operations may include, for example, PHY operations, including one or more of the following: HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0312] The modem platform 1710 may also include a transmit circuit 1718, a receive circuit 1720, an RF circuit 1722, and an RF front end (RFFE) 1724, which may include or be connected to one or more antenna panels 1726. In short, the transmit circuit 1718 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit 1720 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 1722 may include a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 1724 may include a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming component (e.g., a phased array antenna component), etc. The selection and arrangement of the components of the transmit circuit 1718, the receive circuit 1720, the RF circuit 1722, the RFFE 1724, and the antenna panel 1726 (generally referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be provided in the same or different chips / modules, etc.

[0313] In some embodiments, the protocol processing circuit 1714 may include one or more instances of control circuitry (not shown) for providing control functionality for the transmit / receive components.

[0314] UE reception may be established by and via antenna panel 1726, RFFE 1724, RF circuitry 1722, receive circuitry 1720, digital baseband circuitry 1716, and protocol processing circuitry 1714. In some embodiments, antenna panel 1726 may receive transmissions from AN 1704 via receive beamformed signals received by multiple antennas / antenna elements of one or more antenna panels 1726.

[0315] UE transmission may be established by and via protocol processing circuitry 1714, digital baseband circuitry 1716, transmit circuitry 1718, RF circuitry 1722, RFFE 1724, and antenna panel 1726. In some embodiments, the transmit component of UE 1704 may apply spatial filtering to the data to be transmitted to form transmit beams emitted by antenna elements of antenna panel 1726.

[0316] Similar to UE 1702, AN 1704 may include a host platform 1728 coupled to a modem platform 1730. Host platform 1728 may include application processing circuitry 1732 coupled to protocol processing circuitry 1734 of modem platform 1730. The modem platform may also include digital baseband circuitry 1736, transmit circuitry 1738, receive circuitry 1740, RF circuitry 1742, RFFE circuitry 1744, and antenna panel 1746. The components of AN 1704 may be similar to and substantially interchangeable with similarly named components of UE 1702. In addition to performing data transmission / reception as described above, the components of AN 1708 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0317] Fig.18 is a block diagram illustrating components according to some example embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein. Specifically, Fig.18 A graphical representation of hardware resources 1800 is shown, including one or more processors (or processor cores) 1810, one or more memory / storage devices 1820, and one or more communication resources 1830, each of which may be communicatively coupled via a bus 1840 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1802 may be executed to provide an execution environment for one or more network slices / subslices to utilize the hardware resources 1800.

[0318] Processor 1810 may include, for example, processor 1812 and processor 1814. Processor 1810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP (e.g., a baseband processor), an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0319] The memory / storage device 1820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1820 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, etc.

[0320] The communication resources 1830 may include interconnect or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1804 or one or more databases 1806 or other network elements via the network 1808. For example, the communication resources 1830 may include a wired communication component (e.g., for coupling via USB, Ethernet, etc.), a cellular communication component, an NFC component, (or low power consumption ) components, components and other communication components.

[0321] The instructions 1850 may include software, programs, applications, applet, apps, or other executable code for causing at least any processor 1810 to perform any one or more of the methods discussed herein. The instructions 1850 may reside in whole or in part in at least one of the processor 1810 (e.g., in a cache memory of the processor), the memory / storage device 1820, or any suitable combination thereof. In addition, any portion of the instructions 1850 may be transmitted to the hardware resources 1800 from any combination of the peripheral device 1804 or the database 1806. Therefore, the memory of the processor 1810, the memory / storage device 1820, the peripheral device 1804, and the database 1806 are examples of computer-readable and machine-readable media.

[0322] Example Process

[0323] In some embodiments, Figure 16-18 The electronic device, network, system, chip or component or part or implementation thereof of or some other figures herein may be configured to perform one or more processes, techniques or methods or parts thereof as described herein. Fig.19One such process 1900 is depicted in . Process 1900 may be performed by a user equipment (UE), one or more elements of a UE, or an electronic device including a UE. At 1902, process 1900 may include: identifying a set of sidelink resources for transmission of a sidelink message, wherein the set of sidelink resources is in an unlicensed spectrum, and wherein the set of sidelink resources includes individual resource blocks (RBs) interleaved in the frequency domain. At 1904, process 1900 may also include: sending or receiving a sidelink message on the set of sidelink resources.

[0324] Fig. 20 Another process 2000 is shown according to various embodiments. Process 2000 may be performed by a user equipment (UE), one or more elements of a UE, or an electronic device including a UE. At 2002, process 2000 may include: identifying a resource allocation for a physical sidelink feedback channel (PSFCH) or a sidelink synchronization signal block (S-SSB). At 2004, process 2000 may also include: applying a cyclic prefix extension immediately before the resource allocation.

[0325] Fig.21 Another process 2100 according to various embodiments is shown. The process 2100 may be performed by a user equipment (UE), one or more elements of a UE, or an electronic device including a UE. At 2102, the process 2100 may include receiving configuration information indicating one or more start symbols allowed for sidelink transmissions of the UE. At 2104, the process 2100 may also include sending a sidelink transmission based on the configuration information.

[0326] For one or more embodiments, at least one component described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the preceding figures may be configured to operate according to one or more examples described below. As another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the preceding figures may be configured to operate according to one or more examples described below in the example section.

[0327] Example

[0328] Example A1 may include one or more non-transitory computer readable media (NTCRMs) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE), configure the UE to:

[0329] identifying a set of sidelink resources for transmission of a sidelink message, wherein the set of sidelink resources are in an unlicensed spectrum, and wherein the set of sidelink resources comprises individual resource blocks (RBs) interleaved in a frequency domain; and

[0330] The sidelink message is sent or received on the set of sidelink resources.

[0331] Example A2 may include one or more NTCRMs as described in Example A1, wherein the resource pool of K RBs is divided into M subchannels of N RBs, wherein the group of side link resources is one of the M subchannels, and wherein the remaining K–M*N RBs are not used for sidelink transmissions.

[0332] Example A3 may include one or more NTCRMs as described in Example A1, wherein the instruction, when executed, further configures the UE to: receive a radio resource control (RRC) message indicating a resource pool for sidelink communication, wherein the RRC message includes an indication that an interleaved RB mapping is used for the resource pool, and wherein the group of side link resources is identified based on the indication.

[0333] Example A4 may include one or more NTCRMs as described in Example A3, wherein the indication is a cell-specific indication based on regional requirements for sidelink communications in an unlicensed spectrum.

[0334] Example A5 may include one or more NTCRMs as described in Example A3, wherein the instructions, when executed, further configure the UE to: receive configuration information indicating a set of interlaces included in the set of side link resources in the resource pool, wherein the configuration information includes one or more of the following:

[0335] an indication of the lowest or highest RB of the set of interlaces or a corresponding interlace in the set of interlaces;

[0336] a number of consecutive interlaces to use in the frequency domain;

[0337] The size of the interleaved physical resource blocks (PRBs);

[0338] Allocation of allowed frequency resources according to a Listen Before Talk (LBT) type; or

[0339] A bitmap used to indicate the set of interlaces.

[0340] Example A6 may include one or more NTCRMs as described in Example A1, wherein the instructions, when executed, further configure the UE to receive a message for configuring the number of interlaces to which the subchannels in the set of side link resources are mapped.

[0341] Example A7 may include one or more NTCRMs as described in any of Examples A1-A6, wherein the set of side link resources is a first set of side link resources, and wherein the instructions, when executed, further configure the UE to:

[0342] identifying a second set of sidelink resources including RBs adjacent to corresponding RBs of the first set of sidelink resources; and

[0343] Simultaneously with sending or receiving the sidelink message on the first set of sidelink resources, sending or receiving the sidelink message or another sidelink message on the second set of sidelink resources and an intra-cell guard band between the first set of sidelink resources and the second set of sidelink resources.

[0344] Example A8 may include one or more non-transitory computer readable media (NTCRMs) having instructions stored thereon that, when executed by one or more processors of a user equipment (UE), configure the UE to:

[0345] identifying resource allocations for a physical sidelink feedback channel (PSFCH) or a sidelink synchronization signal block (S-SSB); and

[0346] A cyclic prefix extension is applied immediately before the resource allocation.

[0347] Example A9 may include the one or more NTCRMs of Example A8, wherein the cyclic prefix extension has a length of:

[0348]

[0349] Wherein, l is the symbol to which the cyclic prefix extension is applied, μ is a value based on the subcarrier spacing, and Y is the time period.

[0350] Example A10 may include one or more NTCRMs as described in Example A9, wherein Y is less than or equal to 16 microseconds.

[0351] Example A11 may include one or more NTCRMs as described in Example A8, wherein the cyclic prefix extension is applied before the PSFCH or the S-SSB if a previous sidelink transmission by the UE or another UE is about to end one symbol before the start of the PSFCH or the S-SSB.

[0352] Example A12 may include one or more NTCRMs as described in Example A8, wherein the S-SSB is sent outside of a channel occupancy time of the UE, and wherein a listen-before-talk type 2A is used for the SSB if one or more of the following is true:

[0353] The S-SSB transmission is at most 1 millisecond long; or

[0354] The duty cycle of the S-SSB is at most 1 / 20 over the observation period.

[0355] Example A13 may include one or more NTCRMs as described in any of Examples A8-A12, wherein the instruction, when executed, further configures the UE to: perform a listen-before-talk (LBT) process before transmission of the PSFCH, wherein the LBT process stops at a specified time, and the specified time is the same for all UEs communicating on the same side link carrier.

[0356] Example A14 may include one or more non-transitory computer readable media (NTCRMs) having instructions stored thereon that, when executed by one or more processors of a user equipment (UE), configure the UE to:

[0357] receiving configuration information indicating two starting symbols allowed for sidelink transmission of the UE; and

[0358] Based on the configuration information, the sidelink transmission is sent.

[0359] Example A15 may include one or more NTCRMs as described in Example A14, wherein the two start symbols correspond to corresponding starting positions within a time slot.

[0360] Example A16 may include one or more NTCRMs as described in Example A14, wherein the two starting symbols correspond to any symbol within a preconfigured set of values.

[0361] Example A17 may include one or more NTCRMs as described in Example A14, wherein the instructions, when executed, also configure the UE to apply a pre-configured cyclic prefix extension before the sidelink transmission.

[0362] Example A18 may include one or more NTCRMs as described in Example A14, wherein the instructions, when executed, further configure the UE to perform a listen-before-talk process prior to the sidelink transmission.

[0363] Example A19 may include one or more NTCRMs as described in Example A14, wherein the LBT process stops at a specified time, and the specified time is the same for all UEs communicating on the same sidelink carrier.

[0364] Example A20 may include one or more NTCRMs as described in any of Examples A14-A19, wherein the sidelink transmission is a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH).

[0365] Example B1 may include a method for adjusting the TX / RX switching gap for a SL system operating in an unlicensed spectrum to meet LBT requirements when the PSFCH is not carried within the SL.

[0366] Example B2 may include a method for adjusting the TX / RX switching gap for a SL system operating in unlicensed spectrum to meet LBT requirements when carrying PSFCH within the SL.

[0367] Example B3 may include a method for supporting a SL system operating in an unlicensed spectrum and mitigating mutual interference between UEs when it operates in FDM mode.

[0368] Example B4 may include a method for supporting a SL system operating in an unlicensed spectrum and mitigating mutual interference between UEs when operating in TDM mode.

[0369] Example B5 may include a method for adapting AGC for a UE in case of LBT operation.

[0370] Example B6 may include a method for accounting for ON / OFF transitions of a transmitter for LBT operation.

[0371] Example B7 includes a method to be performed by a user equipment (UE), one or more elements of a UE, or an electronic device including a UE, wherein the method includes:

[0372] It is identified that the switching protection period is greater than 16 μs;

[0373] shortening the switching protection period to less than or equal to 16 μs; and

[0374] Sidelink (SL) transmissions are sent using a shortened switching protection period.

[0375] Example B8 includes a method as described in Example B7 and / or some other examples herein, wherein the switching protection period is a TX / RX or RX / TX switching gap.

[0376] Example B9 includes a method as described in any of Examples B7-B8 and / or some other examples herein, wherein shortening the switching protection period includes shortening the switching protection period to less than or equal to 13 μs.

[0377] Example B10 includes a method as described in any of Examples B7-B9 and / or some other examples herein, further including: sending the SL transmission without using LBT.

[0378] Example B11 includes a method as described in any of Examples B7-B10 and / or some other examples herein, wherein shortening the switching protection period includes: identifying resources on which the SL transmission is to be sent and aligned with a symbol or time slot boundary of a frame or subframe in which the SL transmission is to be sent.

[0379] Example B12 includes a method as described in any of Examples B7-B11 and / or some other examples herein, wherein the SL transmission is a physical SL feedback channel (PSFCH) transmission.

[0380] Example B13 includes a method as described in Example B12 and / or some other examples herein, further comprising: before transmission of the PSFCH, adding a cyclic prefix extension of length based on whether the UE sending the PSFCH is capable of operating as a responding device within its own or another UE's COT.

[0381] Example C1 may include providing a method for satisfying channel occupancy regulatory requirements to enable a SL system to operate in an unlicensed spectrum.

[0382] Example C2 may include a method as described in Example C1 or some other examples herein, wherein a single interleaving method is introduced.

[0383] Example C3 may include a method as described in Example C1 or some other examples herein, wherein a group interleaving method is introduced.

[0384] Example C4 may include a method as described in Example C1 or some other examples herein, wherein a subcarrier-based interleaving method is introduced.

[0385] Example C5 may include a method as described in Examples C1-C4 or some other examples herein, wherein different options are provided on how to configure the above method.

[0386] Example C6 may include a method of a UE, the method comprising:

[0387] determining a set of sidelink resources for transmission of a sidelink message, wherein the set of sidelink resources are interleaved in the time domain and / or the frequency domain; and

[0388] The sidelink message is sent on the set of sidelink resources.

[0389] Example C7 may include a method as described in Example C6 or some other examples herein, wherein the set of side link resources is in an unlicensed spectrum.

[0390] Example C8 may include a method as described in Examples C6-C7 or some other examples herein, wherein the set of side link resources is interleaved using a single resource block interleaving.

[0391] Example C9 may include a method as described in Examples C6-C7 or some other examples herein, wherein, in the set of side link resources, respective groups of multiple resource blocks are interleaved with each other.

[0392] Example C10 may include a method as described in Examples C6-C9 or some other examples herein, wherein the subcarriers of the set of side link resources are interleaved.

[0393] Example C11 may include a method as described in Examples C6-C10 or some other examples herein, further comprising: receiving an indication for activating interleaving.

[0394] Example C12 may include a method as described in Examples C6-C11 or some other examples herein, wherein the sidelink message is PSCCH, PSSCH, PSFCH, PSBCH and / or S-SSB.

[0395] Example Z01 may include an apparatus comprising components for performing one or more elements of a method described in or related to any of Examples A1-A20, B1-B13, C1-C12, or any other method or process described herein.

[0396] Example Z02 may include one or more non-transitory computer-readable media, including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples A1-A20, B1-B13, C1-C12, or any other method or process described herein.

[0397] Example Z03 may include a device comprising logic, modules, or circuits for performing one or more elements of a method described in or related to any of Examples A1-A20, B1-B13, C1-C12, or any other method or process described herein.

[0398] Example Z04 may include methods, techniques, or processes as described in or related to any of Examples A1-A20, B1-B13, C1-C12, or portions or sections thereof.

[0399] Example Z05 may include a device comprising: one or more processors and one or more computer-readable media, the media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes described in or related to any one of Examples A1-A20, B1-B13, C1-C12, or portions thereof.

[0400] Example Z06 may include signals as described in or related to any of Examples A1-A20, B1-B13, C1-C12, or portions or sections thereof.

[0401] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of Examples A1-A20, B1-B13, C1-C12, or parts or segments thereof, or otherwise described in the present disclosure.

[0402] Example Z08 may include a signal encoded with data as described in or related to any of Examples A1-A20, B1-B13, C1-C12, or portions or sections thereof, or otherwise described in this disclosure.

[0403] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of Examples A1-A20, B1-B13, C1-C12, or parts or segments thereof, or otherwise described in the present disclosure.

[0404] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein one or more processors execute the computer-readable instructions to cause the one or more processors to perform a method, technique, or process described in or related to any one of Examples A1-A20, B1-B13, C1-C12, or a portion thereof.

[0405] Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Examples A1-A20, B1-B13, C1-C12, or a portion thereof.

[0406] Example Z12 may include a signal in a wireless network as shown and described herein.

[0407] Example Z13 may include a method of communicating in a wireless network as shown and described herein.

[0408] Example Z14 may include a system for providing wireless communications as shown and described herein.

[0409] Example Z15 may include an apparatus for providing wireless communications as shown and described herein.

[0410] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be obtained from the practice of the various embodiments.

[0411] abbreviation

[0412] Unless otherwise used herein, the terms, definitions and abbreviations may be consistent with those defined in 3GPP TR 21.905v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

[0413] 3GPP Third Generation Partnership Project

[0414] 4G Fourth Generation

[0415] 5G Fifth Generation

[0416] 5GC 5G Core Network

[0417] AC Application Client

[0418] ACR Application Context Relocation

[0419] ACK

[0420] ACID Application Client Identity

[0421] AF Application Function

[0422] AM Confirmation Mode

[0423] AMBR Aggregate Maximum Bit Rate

[0424] AMF Access and Mobility Management Function

[0425] AN Access Network

[0426] ANR Automatic Neighbor Relation

[0427] AOA Angle of Arrival

[0428] AP application protocol, antenna port, access point

[0429] API Application Programming Interface

[0430] APN Access Point Name

[0431] ARP Allocation and Retention Priority

[0432] ARQ Automatic Repeat Request

[0433] AS Access Layer

[0434] ASP Application Service Provider

[0435] ASN.1 Abstract Syntax Notation 1

[0436] AUSF authentication server function

[0437] AWGN Additive White Gaussian Noise

[0438] BAP Backhaul Adaptation Protocol

[0439] BCH Broadcast Channel

[0440] BER Bit Error Rate

[0441] BFD Beam Fault Detection

[0442] BLER Block Error Rate

[0443] BPSK Binary Phase Shift Keying

[0444] BRAS Broadband Remote Access Server

[0445] BSS Business Support System

[0446] BS Base Station

[0447] BSR Buffer Status Report

[0448] BW Bandwidth

[0449] BWP Fractional Bandwidth

[0450] C-RNTI Cell Radio Network Temporary Identity

[0451] CA Carrier Aggregation, Certification Authority

[0452] CAPEX Capital Expenditure

[0453] CBD Candidate Beam Detection

[0454] CBRA Contention-based random access

[0455] CC component carrier, country code, secret checksum

[0456] CCA Clear Channel Assessment

[0457] CCE Control Channel Element

[0458] CCCH Common Control Channel

[0459] CE Coverage Enhancement

[0460] CDM Content Distribution Network

[0461] CDMA Code Division Multiple Access

[0462] CDR Charging Data Request

[0463] CDR charging data response

[0464] CFRA Contention-free random access

[0465] CG Cell Group

[0466] CGF Billing Gateway Function

[0467] CHF billing function

[0468] CI Community Identity

[0469] CID Cell ID (eg, positioning method)

[0470] CIM Common Information Model

[0471] CIR Carrier to Interference Ratio

[0472] CK Key

[0473] CM connection management, conditional enforcement

[0474] CMAS Commercial Mobile Alert Service

[0475] CMD command

[0476] CMS Cloud Management System

[0477] CO Conditional Options

[0478] CoMP Coordinated Multipoint

[0479] CORESET Control Resource Set

[0480] COTS Commercial Off-the-Shelf

[0481] CP Control Plane, Cyclic Prefix, Attachment Point

[0482] CPD Connection Point Descriptor

[0483] CPE Customer Premises Equipment

[0484] CPICH Common Pilot Channel

[0485] CQI Channel Quality Indicator

[0486] CPU CSI processing unit, central processing unit

[0487] C / R Command / Response field, bit

[0488] CRAN Cloud Radio Access Network, Cloud RAN

[0489] CRB Common Resource Block

[0490] CRC Cyclic Redundancy Check

[0491] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator

[0492] C-RNTI Cell RNTI

[0493] CS Circuit Switched

[0494] CSCF Call Session Control Function

[0495] CSAR Cloud Service Archive

[0496] CSI Channel State Information

[0497] CSI-IM CSI interference measurement

[0498] CSI-RS CSI reference signal

[0499] CSI-RSRP CSI reference signal received power

[0500] CSI-RSRQ CSI reference signal reception quality

[0501] CSI-SINR CSI signal to interference and noise ratio

[0502] CSMA Carrier Sense Multiple Access

[0503] CSMA / CA CSMA with Collision Avoidance

[0504] CSS Common Search Space, Cell Specific Search Space

[0505] CTF Billing Trigger Function

[0506] CTS Clear to Send

[0507] CW codeword

[0508] CWS Contention Window Size

[0509] D2D Device to Device

[0510] DC dual connection, direct current

[0511] DCI Downlink Control Information

[0512] DF deployment style

[0513] DL Downlink

[0514] DMTF Distributed Management Task Force

[0515] DPDK Data Plane Development Kit

[0516] DM-RS DMRS demodulation reference signal

[0517] DN Data Network

[0518] DNN data network name

[0519] DNAI Data Network Access Identifier

[0520] DRB Data Radio Bearer

[0521] DRS Discovery Reference Signal

[0522] DRX Discontinuous Reception

[0523] DSL Domain Specific Language, Digital Subscriber Line

[0524] DSLAM DSL Access Multiplexer

[0525] DwPTS Downlink Pilot Time Slot

[0526] E-LAN ​​Ethernet Local Area Network

[0527] E2E End to End

[0528] EAS Edge Application Server

[0529] ECCA Extended Clear Channel Assessment, Extended CCA

[0530] ECCE Enhanced Control Channel Element, Enhanced CCE

[0531] ED Energy Detection

[0532] EDGE Enhanced Data Rates for GSM Evolution (GSM Evolution)

[0533] EAS Edge Application Server

[0534] EASID Edge Application Server Identifier

[0535] ECS Edge Configuration Server

[0536] ECSP Edge Computing Service Provider

[0537] EDN Edge Data Network

[0538] EEC Edge Enabler Client

[0539] EECID Edge Enabler Client Identifier

[0540] EES Edge Enabler Server

[0541] EESID Edge Enabler Server ID

[0542] EHE Edge Hosting Environment

[0543] EGMF Open Control Management Function

[0544] EGPRS Enhanced GPRS

[0545] EIR Equipment Identity Register

[0546] eLAA Enhanced Authorization Assisted Access, Enhanced LAA

[0547] EM Component Manager

[0548] eMBB Enhanced Mobile Broadband

[0549] EMS Component Management System

[0550] eNB Evolved NodeB, E-UTRAN Node B

[0551] EN-DC E-UTRA-NR Dual Connectivity

[0552] EPC Evolved Packet Core

[0553] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0554] EPRE Energy Element per Resource

[0555] EPS Evolved Packet System

[0556] EREG Enhanced REG, Enhanced Resource Element Group

[0557] ETSI European Telecommunications Standards Institute

[0558] ETWS Earthquake and Tsunami Early Warning System

[0559] eUICC embedded UICC, embedded universal integrated circuit card

[0560] E-UTRA Evolved UTRA

[0561] E-UTRAN Evolved UTRAN

[0562] EV2X Enhanced V2X

[0563] F1AP F1 Application Protocol

[0564] F1-C F1 control plane interface

[0565] F1-U F1 User Plane Interface

[0566] FACCH Fast Associated Control Channel

[0567] FACCH / F Fast Associated Control Channel / Full Rate

[0568] FACCH / H Fast Associated Control Channel / Half Rate

[0569] FACH Forward Access Channel

[0570] FAUSCH Fast Uplink Signalling Channel

[0571] FB Function Block

[0572] FBI Feedback

[0573] FCC Federal Communications Commission

[0574] FCCH Frequency Correction Channel

[0575] FDD Frequency Division Duplex

[0576] FDM Frequency Division Multiplexing

[0577] FDMA Frequency Division Multiple Access

[0578] FE Front End

[0579] FEC Forward Error Correction

[0580] FFS Further Research

[0581] FFT Fast Fourier Transform

[0582] feLAA further enhances authorized assisted access and LAA

[0583] FN Frame Number

[0584] FPGA Field Programmable Gate Array

[0585] FR Frequency Range

[0586] FQDN Fully Qualified Domain Name

[0587] G-RNTI GERAN Radio Network Temporary Identity

[0588] GERAN GSM EDGE RAN, GSM EDGE radio access network

[0589] GGSN Gateway GPRS Support Node

[0590] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System)

[0591] gNB Next Generation NodeB

[0592] gNB-CU gNB centralized unit, next generation NodeB centralized unit

[0593] gNB-DU gNB distributed unit, next generation NodeB distributed unit

[0594] GNSS Global Navigation Satellite System

[0595] GPRS General Packet Radio Service

[0596] GPSI General Public Subscription Identifier

[0597] GSM Global System for Mobile Communications, Groupe Special Mobile

[0598] GTP GPRS Tunneling Protocol

[0599] GTP-U GPRS User Plane Tunneling Protocol

[0600] GTS (related to WUS) sleep entry signal

[0601] GUMMEI Globally Unique MME Identifier

[0602] GUTI Globally Unique Temporary UE Identity

[0603] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0604] HANDO switch

[0605] HFN Superframe Number

[0606] HHO Hard Handover

[0607] HLR Home Location Register

[0608] HN Home Network

[0609] HO Switchover

[0610] HPLMN Home Public Land Mobile Network

[0611] HSDPA High Speed ​​Downlink Packet Access

[0612] HSN Hopping Sequence Number

[0613] HSPA High Speed ​​Packet Access

[0614] HSS Home Subscriber Server

[0615] HSUPA High Speed ​​Uplink Packet Access

[0616] HTTP Hypertext Transfer Protocol

[0617] HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443)

[0618] I-Block Information Block

[0619] ICCID Integrated Circuit Card Identifier

[0620] IAB Integration Access and Postbacks

[0621] ICIC Inter-cell Interference Coordination

[0622] ID Identity, identifier

[0623] IDFT Inverse Discrete Fourier Transform

[0624] IE Cell

[0625] IBE In-Band Emission

[0626] IEEE Institute of Electrical and Electronics Engineers

[0627] IEI Information Element Identifier

[0628] IEIDL Information element identifier data length

[0629] IETF Internet Engineering Task Force

[0630] IF Infrastructure

[0631] IIOT Industrial Internet of Things

[0632] IM Interference Measurement, Intermodulation, IP Multimedia

[0633] IMC IMS credentials

[0634] IMEI International Mobile Equipment Identity

[0635] IMGI International Mobile Group Identity

[0636] IMPI IP Multimedia Private Identity

[0637] IMPU IP Multimedia Public Identity

[0638] IMS IP Multimedia Subsystem

[0639] IMSI International Mobile Subscriber Identity

[0640] IoT

[0641] IP Internet Protocol

[0642] Ipsec IP security, Internet Protocol security

[0643] IP-CAN IP-Connect Access Network

[0644] IP-M IP Multicast

[0645] IPv4 Internet Protocol version 4

[0646] IPv6 Internet Protocol version 6

[0647] IR Infrared

[0648] IS Synchronization

[0649] IRP Integration Reference Point

[0650] ISDN Integrated Services Digital Network

[0651] ISIM IM Service Identity Module

[0652] ISO International Organization for Standardization

[0653] ISP Internet Service Provider

[0654] IWF interworking function

[0655] I-WLAN Intercommunication WLAN

[0656] Convolutional code constraint length, USIM individual key

[0657] kB kilobyte (1000 bytes)

[0658] kbps kilobits per second

[0659] Kc key

[0660] Ki Individual subscriber authentication key

[0661] KPI Key Performance Indicator

[0662] KQI Key Quality Indicator

[0663] KSI Key Set Identifier

[0664] ksps kilosymbols per second

[0665] KVM Kernel Virtual Machine

[0666] L1 Layer 1 (physical layer)

[0667] L1-RSRP Layer 1 reference signal received power

[0668] L2 Layer 2 (Data Link Layer)

[0669] L3 Layer 3 (Network Layer)

[0670] LAA Authorized Assisted Access

[0671] LAN Local Area Network

[0672] LADN Local Area Data Network

[0673] LBT Listen before you speak

[0674] LCM Lifecycle Management

[0675] LCR Low Chip Rate

[0676] LCS Location Services

[0677] LCID Logical Channel ID

[0678] LI layer indicator

[0679] LLC Logical Link Control, Lower Layer Compatibility

[0680] LMF Location Management Function

[0681] LOS Line of Sight

[0682] LPLMN Local PLMN

[0683] LPP LTE Positioning Protocol

[0684] LSB Least Significant Bit

[0685] LTE Long Term Evolution

[0686] LWA LTE-WLAN Aggregation

[0687] LWIP LTE / WLAN wireless level integration with IPsec tunneling

[0688] LTE Long Term Evolution

[0689] M2M Machine to Machine

[0690] MAC Medium Access Control (Protocol Layer Context)

[0691] MAC Message Authentication Code (Security / Cryptography Context)

[0692] MAC-A MAC for authentication and key agreement (TSG T WG3 context)

[0693] MAC-I MAC for data integrity of signalling messages (TSG T WG3 context)

[0694] MANO Management and Orchestration

[0695] MBMS Multimedia Broadcast and Multicast Service

[0696] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0697] MCC Mobile Country Code

[0698] MCG Master Cell Group

[0699] MCOT Maximum Channel Occupancy Time

[0700] MCS Modulation Coding Scheme

[0701] MDAF Management Data Analysis Function

[0702] MDAS Management Data Analysis Service

[0703] MDT Minimized Drive Test

[0704] ME Mobile Devices

[0705] MeNB Master eNB

[0706] MER False Message Rate

[0707] MGL Measurement Gap Length

[0708] MGRP measurement gap repetition period

[0709] MIB Master Information Block, Management Information Base

[0710] MIMO Multiple Input Multiple Output

[0711] MLC Mobile Location Center

[0712] MM Mobility Management

[0713] MME Mobility Management Entity

[0714] MN Master Node

[0715] MNO Mobile Network Operator

[0716] MO Measurement object, mobile calling

[0717] MPBCH MTC Physical Broadcast Channel

[0718] MPDCCH MTC Physical Downlink Control Channel

[0719] MPDSCH MTC Physical Downlink Shared Channel

[0720] MPRACH MTC Physical Random Access Channel

[0721] MPUSCH MTC Physical Uplink Shared Channel

[0722] MPLS Multiprotocol Label Switching

[0723] MS Mobile Station

[0724] MSB Most Significant Bit

[0725] MSC Mobile Switching Center

[0726] MSI minimum system information, MCH scheduling information

[0727] MSID Mobile Station Identifier

[0728] MSIN Mobile Station Identification Number

[0729] MSISDN Mobile Subscriber ISDN Number

[0730] MT mobile called, mobile terminal

[0731] MTC Machine Type Communication

[0732] mMTC Massive MTC, Massive Machine Type Communication

[0733] MU-MIMO Multi-User MIMO

[0734] MWUS MTC wake-up signal, MTC WUS

[0735] NACK Negative Acknowledgement

[0736] NAI Network Access Identifier

[0737] NAS Non-Access Stratum, Non-Access Layer

[0738] NCT Network Connection Topology

[0739] NC-JT Non-coherent joint transmission

[0740] NEC Network Capability Openness

[0741] NE-DC NR-E-UTRA dual connectivity

[0742] NEF Network Exposure Function

[0743] NF Network Function

[0744] NFP Network Forwarding Path

[0745] NFPD Network Forwarding Path Descriptor

[0746] NFV Network Function Virtualization

[0747] NFVI NFV Infrastructure

[0748] NFVO NFV Orchestrator

[0749] NG Next generation, next generation

[0750] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

[0751] NM Network Manager

[0752] NMS Network Management System

[0753] N-PoP Network Point of Presence

[0754] NMIB, N-MIB Narrowband MIB

[0755] NPBCH Narrowband Physical Broadcast Channel

[0756] NPDCCH Narrowband Physical Downlink Control Channel

[0757] NPDSCH Narrowband Physical Downlink Shared Channel

[0758] NPRACH Narrowband Physical Random Access Channel

[0759] NPUSCH Narrowband Physical Uplink Shared Channel

[0760] NPSS Narrowband Primary Synchronization Signal

[0761] NSSS Narrowband Secondary Synchronization Signal

[0762] NR New air interface, neighbor relationship

[0763] NRF NF Repository Functionality

[0764] NRS Narrowband Reference Signal

[0765] NS Network Services

[0766] NSA Non-standalone operation mode

[0767] NSD Network Service Descriptor

[0768] NSR Network Service Record

[0769] NSSAI Network Slice Selection Assistance Information

[0770] S-NNSAI Single NSSAI

[0771] NSSF network slice selection function

[0772] NW Network

[0773] NWUS Narrowband wake-up signal, narrowband WUS

[0774] NZP Non Zero Power

[0775] O&M

[0776] ODU2 Optical Channel Data Unit - Type 2

[0777] OFDM Orthogonal Frequency Division Multiplexing

[0778] OFDMA Orthogonal Frequency Division Multiple Access

[0779] OOB Out of Band

[0780] OOS Out of Sync

[0781] OPEX Operating Expenses

[0782] OSI Other System Information

[0783] OSS Operation Support System

[0784] OTA (Over the Air)

[0785] PAPR Peak to Average Power Ratio

[0786] PAR Peak to Average Ratio

[0787] PBCH Physical Broadcast Channel

[0788] PC Power Control, Personal Computer

[0789] PCC primary component carrier, primary CC

[0790] P-CSCF Proxy CSCF

[0791] PCell Primary Cell

[0792] PCI Physical Cell ID, Physical Cell Identity

[0793] PCEF Policy and Charging Enforcement Function

[0794] PCF Policy Control Function

[0795] PCRF Policy Control and Charging Rules Function

[0796] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer

[0797] PDCCH Physical Downlink Control Channel

[0798] PDCP Packet Data Convergence Protocol

[0799] PDN Packet Data Network, Public Data Network

[0800] PDSCH Physical Downlink Shared Channel

[0801] PDU Protocol Data Unit

[0802] PEI Persistent Equipment Identifier

[0803] PFD Packet Flow Description

[0804] P-GW PDN Gateway

[0805] PHICH Physical Hybrid ARQ Indicator Channel

[0806] PHY Physical Layer

[0807] PLMN Public Land Mobile Network

[0808] PIN Personal Identification Number

[0809] PM performance measurement

[0810] PMI Precoding matrix indicator

[0811] PNF Physical Network Function

[0812] PNFD Physical Network Functional Descriptor

[0813] PNFR Physical Network Function Record

[0814] POC PTT over Cellular

[0815] PP, PTP point to point

[0816] PPP Point-to-Point Protocol

[0817] PRACH Physical RACH

[0818] PRB Physical Resource Block

[0819] PRG Physical Resource Group

[0820] ProSe Proximity Services, Proximity-Based Services

[0821] PRS Positioning Reference Signal

[0822] PRR Packet Receive Radio

[0823] PS Packet Service

[0824] PSBCH Physical Sidelink Broadcast Channel

[0825] PSDCH Physical Sidelink Downlink Channel

[0826] PSCCH Physical Sidelink Control Channel

[0827] PSSCH Physical Sidelink Shared Channel

[0828] PSFCH Physical Sidelink Feedback Channel

[0829] PSCell Primary SCell

[0830] PSS Primary Synchronization Signal

[0831] PSTN Public Switched Telephone Network

[0832] PT-RS Phase Tracking Reference Signal

[0833] PTT Push to Talk

[0834] PUCCH Physical Uplink Control Channel

[0835] PUSCH Physical Uplink Shared Channel

[0836] QAM Quadrature Amplitude Modulation

[0837] QCI QoS Class Identifier

[0838] QCL Quasi-Co-location

[0839] QFI QoS flow ID, QoS flow identifier

[0840] QoS Quality of Service

[0841] QPSK Quadrature (Quaternary) Phase Shift Keying

[0842] QZSS Quasi-Zenith Satellite System

[0843] RA-RNTI Random Access RNTI

[0844] RAB Radio Access Bearer, Random Access Burst

[0845] RACH Random Access Channel

[0846] RADIUS Remote Authentication Dial-In User Service

[0847] RAN Radio Access Network

[0848] RAND Random number (for authentication)

[0849] RAR Random Access Response

[0850] RAT Radio Access Technology

[0851] RAU Routing Area Update

[0852] RB Resource Block, Radio Bearer

[0853] RBG Resource Block Group

[0854] REG Resource Element Group

[0855] Rel version

[0856] REQ Request

[0857] RF

[0858] RI Rank Indicator

[0859] RIV Resource Indicator Value

[0860] RL Wireless Link

[0861] RLC Radio Link Control, Radio Link Control Layer

[0862] RLC AM RLC Acknowledgement Mode

[0863] RLC UM RLC Unacknowledged Mode

[0864] RLF Radio Link Failure

[0865] RLM Radio Link Monitoring

[0866] RLM-RS Reference signal for RLM

[0867] RM Registration Management

[0868] RMC Reference Measurement Channel

[0869] RMSI Remaining MSI, Remaining Minimum System Information

[0870] RN Relay Node

[0871] RNC Radio Network Controller

[0872] RNL Radio Network Layer

[0873] RNTI Radio Network Temporary Identifier

[0874] ROHC Robust Header Compression

[0875] RRC Radio Resource Control, Radio Resource Control Layer

[0876] RRM Radio Resource Management

[0877] RS reference signal

[0878] RSRP Reference Signal Received Power

[0879] RSRQ Reference Signal Received Quality

[0880] RSSI Received Signal Strength Indicator

[0881] RSU Roadside Unit

[0882] RSTD Reference Signal Time Difference

[0883] RTP Real Time Protocol

[0884] RTS Ready to send

[0885] RTT Round Trip Time

[0886] Rx receive, receive, receiver

[0887] S1AP S1 Application Protocol

[0888] S1-MME is used for S1 control plane

[0889] S1-U S1 for user plane

[0890] S-CSCF Serving CSCF

[0891] S-GW Service Gateway

[0892] S-RNTI SRNC Radio Network Temporary Identity

[0893] S-TMSI SAE temporary mobile station identifier

[0894] SA Standalone Operation Mode

[0895] SAE system architecture evolution

[0896] SAP Service Access Point

[0897] SAPD Service Access Point Descriptor

[0898] SAPI Service Access Point Identifier

[0899] SCC Secondary Component Carrier, Secondary CC

[0900] SCell Secondary Cell

[0901] SCEF service capability exposure function

[0902] SC-FDMA Single Carrier Frequency Division Multiple Access

[0903] SCG Secondary Cell Group

[0904] SCM Security Context Management

[0905] SCS subcarrier spacing

[0906] SCTP Stream Control Transmission Protocol

[0907] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[0908] SDL Supplemental Downlink

[0909] SDNF Structured Data Storage Network Function

[0910] SDP Session Description Protocol

[0911] SDSF structured data storage function

[0912] SDT Small Data Transfer

[0913] SDU Service Data Unit

[0914] SEAF Security Anchoring Function

[0915] SeNB Secondary eNB

[0916] SEPP Security Edge Protection Proxy

[0917] SFI Slot Format Indicator

[0918] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference

[0919] SFN System Frame Number

[0920] SgNB

[0921] SGSN Serving GPRS Support Node

[0922] S-GW Service Gateway

[0923] SI System Information

[0924] SI-RNTI System Information RNTI

[0925] SIB System Information Block

[0926] SIM Subscriber Identity Module

[0927] SIP Session Initiation Protocol

[0928] SiP System in Package

[0929] SL Side Link

[0930] SLA Service Level Agreement

[0931] SM Session Management

[0932] SMF session management functions

[0933] SMS Short Message Service

[0934] SMSF SMS Function

[0935] SMTC SSB-based measurement timing configuration

[0936] SN Secondary Node, Serial Number

[0937] SoC System on Chip

[0938] SON Self-Organizing Network

[0939] SpCell Special Cell

[0940] SP-CSI-RNTI Semi-persistent CSI RNTI

[0941] SPS Semi-Persistent Scheduling

[0942] SQN Serial Number

[0943] SR Scheduling Request

[0944] SRB Signalling Radio Bearer

[0945] SRS Sounding Reference Signal

[0946] SS Sync Signal

[0947] SSB Synchronous Signal Block

[0948] SSID Service Set Identifier

[0949] SS / PBCH block

[0950] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator

[0951] SSC Session and Service Continuity

[0952] SS-RSRP Reference signal received power based on synchronization signal

[0953] SS-RSRQ Reference signal reception quality based on synchronization signal

[0954] SS-SINR Signal-to-interference-noise ratio based on synchronization signal

[0955] SSS Secondary synchronization signal

[0956] SSSG Search Space Group

[0957] SSSIF Search Space Set Indicator

[0958] SST Slice / Service Type

[0959] SU-MIMO Single User MIMO

[0960] SUL Supplementary Uplink

[0961] TA Timing Advance, Tracking Area

[0962] TAC Tracking Area Code

[0963] TAG Timing Advance Group

[0964] TAI Tracking Area Identity

[0965] TAU Tracking Area Updates

[0966] TB Transfer Block

[0967] TBS Transport Block Size

[0968] TBD

[0969] TCI Transmission Configuration Indicator

[0970] TCP transport communication protocol

[0971] TDD Time Division Duplex

[0972] TDM Time Division Multiplexing

[0973] TDMA Time Division Multiple Access

[0974] TE Terminal Equipment

[0975] TEID Tunnel Endpoint Identifier

[0976] TFT Business Flow Template

[0977] TMSI Temporary Mobile Subscriber Identity

[0978] TNL Transport Network Layer

[0979] TPC Transmit Power Control

[0980] TPMI Transmit Precoding Matrix Indicator

[0981] TR Technical Report

[0982] TRP, TRxP transmit and receive points

[0983] TRS Tracking Reference Signal

[0984] TRx Transceiver

[0985] TS Technical Specifications, Technical Standards

[0986] TTI Transmission Time Interval

[0987] Tx transmission, sending, transmitter

[0988] U-RNTI UTRAN Radio Network Temporary Identity

[0989] UART Universal Asynchronous Receiver and Transmitter

[0990] UCI Uplink Control Information

[0991] UE User Equipment

[0992] UDM Unified Data Management

[0993] UDP User Datagram Protocol

[0994] UDSF Unstructured Data Storage Network Function

[0995] UICC Universal Integrated Circuit Card

[0996] UL Uplink

[0997] UM Unconfirmed Mode

[0998] UML Unified Modeling Language

[0999] UMTS Universal Mobile Telecommunications System

[1000] UP User Plane

[1001] UPF User Plane Function

[1002] URI Uniform Resource Identifier

[1003] URL Uniform Resource Locator

[1004] URLLC Ultra-Reliable and Low Latency

[1005] USB Universal Serial Bus

[1006] USIM Universal Subscriber Identity Module

[1007] USS UE-specific search space

[1008] UTRA UMTS Terrestrial Radio Access

[1009] UTRAN Universal Terrestrial Radio Access Network

[1010] UwPTS Uplink Pilot Time Slot

[1011] V2I Vehicle to Infrastructure

[1012] V2P Vehicle to Pedestrian

[1013] V2V Vehicle to Vehicle

[1014] V2X Vehicle to Everything

[1015] VIM Virtualization Infrastructure Manager

[1016] VL Virtual Link

[1017] VLAN Virtual LAN, Virtual Local Area Network

[1018] VM Virtual Machine

[1019] VNF Virtualized Network Function

[1020] VNFFG VNF forwarding graph

[1021] VNFFGD VNF Forwarding Graph Descriptor

[1022] VNFM VNF Manager

[1023] VoIP Voice over IP, Voice over Internet Protocol

[1024] VPLMN Visited Public Land Mobile Network

[1025] VPN Virtual Private Network

[1026] VRB Virtual Resource Block

[1027] WiMAX Worldwide Interoperability for Microwave Access

[1028] WLAN Wireless Local Area Network

[1029] WMAN Wireless Metropolitan Area Network

[1030] WPAN Wireless Personal Area Network

[1031] X2-C X2-Control Plane

[1032] X2-U X2-User Plane

[1033] XML Extensible Markup Language

[1034] XRES Expected User Response

[1035] XOR

[1036] ZC Zadoff-Chu

[1037] ZP Zero Power

[1038] the term

[1039] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.

[1040] The term "application" may refer to a complete and deployable package or environment for implementing a certain function in an operating environment. The term "AI / ML application" may refer to an application that contains some AI / ML models and application-level descriptions.

[1041] The term "circuit" as used herein refers to, is part of, or includes the following hardware components that are configured to provide the described functions: for example, electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code (or a combination of circuits and program code used in an electrical or electronic system), the hardware elements being used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[1042] The term "processor circuit" used herein refers to a circuit that can sequentially and automatically perform a series of arithmetic or logical operations, or record, store and / or transmit digital data, is a part of it, or includes them. The processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer executable instructions (e.g., program code, software module and / or functional process). The processing circuit may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

[1043] As used herein, the term "interface circuit" refers to, is a part of, or includes circuitry that enables information to be exchanged between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[1044] The term "user equipment" or "UE" as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with, and may be referred to as, a client, a mobile station, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio device, a reconfigurable radio device, a reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[1045] The term "network element" as used herein refers to a physical or virtualized device and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered a synonym for and / or referred to as: networked computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[1046] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[1047] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[1048] The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, power, input / output operations, a port or network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a workload unit, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources accessible to a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing and / or network resources. System resources may be viewed as a set of coherent functions, network data objects, or services that may be accessed through a server, wherein these system resources reside on a single host or multiple hosts and may be clearly identifiable.

[1049] The term "channel" as used herein refers to any transmission medium, whether tangible or intangible, for transmitting data or data streams. The term "channel" may be synonymous with and / or equivalent to the following terms: "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar term representing a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices over a RAT for sending and receiving information.

[1050] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[1051] The terms "coupled", "communicatively coupled" and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between elements that are considered to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including by wired or other interconnection, by wireless communication channels or links, etc.

[1052] The term "cell" refers to a structural element containing one or more fields. The term "field" refers to the individual contents of a cell, or a data element containing the contents.

[1053] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[1054] The term "SSB" refers to a SS / PBCH block.

[1055] The term "primary cell" refers to an MCG cell operating on a primary frequency, in which the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[1056] The term "primary SCG cell", for DC operation, refers to the SCG cell in which the UE performs random access when performing the synchronization reconfiguration procedure.

[1057] The term "secondary cell", for a UE configured with CA, refers to a cell that provides additional radio resources over a special cell.

[1058] The term "secondary cell group", for a UE configured with DC, refers to a subset of serving cells including a PSCell and zero or more secondary cells.

[1059] The term "serving cell", for a UE in RRC_CONNECTED without CA / DC configuration, refers to a primary cell, of which there is only one serving cell.

[1060] The term "serving cell" or "serving cells", for a UE configured with CA / DC in RRC_CONNECTED, refers to a group of cells including a special cell and all secondary cells.

[1061] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.

[1062] The term "machine learning" or "ML" refers to the use of computer systems that implement algorithms and / or statistical models to perform specific tasks without explicit instructions, relying instead on patterns and reasoning. ML algorithms build or estimate mathematical models (called "ML models", etc.) based on sample data (called "training data", "model training information", etc.) to make predictions or decisions without being explicitly programmed to perform such tasks. In general, an ML algorithm is a computer program that learns from experience and some performance metrics about some tasks, and an ML model can be any object or data structure created after training an ML algorithm with one or more training data sets. After training, the ML model can be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept from the term "ML model", for the purposes of this disclosure, these terms discussed herein can be used interchangeably.

[1063] The terms "machine learning model", "ML model", etc. may also refer to ML methods and concepts used by ML-assisted solutions. "ML-assisted solutions" are solutions that use ML algorithms to solve specific use cases during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbors (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA)), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a specific ML model may have many sub-models as components, and the ML model may train all sub-models together. During inference, separately trained ML models may also be linked together in an ML pipeline. "ML pipeline" is a set of functional, functional, or functional entities specific to ML-assisted solutions; an ML pipeline may include one or more data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and actors. "Actors" are entities that host ML-assisted solutions using the output of ML model inference. The term "ML training host" refers to an entity that hosts model training, such as a network function. The term "ML inference host" refers to the entity, such as a network function, that hosts the model during inference mode (which includes model execution and any online learning (if applicable)). The ML host informs the participants of the output of the ML algorithm, and the participants make decisions about actions ("actions" are performed by the participants based on the output of the ML-assisted solution). The term "model inference information" refers to the information used as input to the ML model for determining inferences; the data used to train the ML model and the data used to determine inferences may overlap, however, "training data" and "inference data" refer to different concepts.

Claims

1. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE), configure the UE to: identifying a set of sidelink resources for transmission of a sidelink message, wherein: The set of sidelink resources is in an unlicensed spectrum, and wherein the set of sidelink resources comprises individual resource blocks (RBs) interleaved in the frequency domain; and The sidelink message is sent or received on the set of sidelink resources.

2. One or more NTCRMs as claimed in claim 1, wherein: The resource pool of K RBs is divided into M subchannels of N RBs. wherein the set of side link resources is one of the M subchannels, and wherein, The remaining K–M*N RBs are not used for sidelink transmission.

3. One or more NTCRMs as claimed in claim 1, wherein: When the instructions are executed, the UE is further configured to: receiving a radio resource control (RRC) message indicating a resource pool for sidelink communication, wherein the RRC message includes an indication that an interleaved RB mapping is used for the resource pool, and The set of side link resources is identified based on the indication.

4. One or more NTCRMs as claimed in claim 3, wherein: The indication is a cell-specific indication based on a regional requirement for sidelink communications in an unlicensed spectrum.

5. One or more NTCRMs as claimed in claim 3, wherein: When the instructions are executed, the UE is further configured to: Receiving configuration information indicating a set of interlaces included in the set of side link resources in the resource pool, wherein the configuration information includes one or more of the following: an indication of the lowest or highest RB of the set of interlaces or a corresponding interlace in the set of interlaces; a number of consecutive interlaces to use in the frequency domain; The size of the interleaved physical resource blocks (PRBs); Allocation of allowed frequency resources according to a Listen Before Talk (LBT) type; or A bitmap used to indicate the set of interlaces.

6. The one or more NTCRMs of claim 1, wherein: When the instructions are executed, the UE is further configured to: A message is received to configure a number of interlaces to which subchannels in the set of sidelink resources are mapped.

7. One or more NTCRMs according to any one of claims 1 to 6, wherein: The set of side link resources is a first set of side link resources, and Wherein, when the instruction is executed, the UE is also configured to: identifying a second set of sidelink resources including RBs adjacent to corresponding RBs of the first set of sidelink resources; and Simultaneously with sending or receiving the sidelink message on the first set of sidelink resources, sending or receiving the sidelink message or another sidelink message on the second set of sidelink resources and an intra-cell guard band between the first set of sidelink resources and the second set of sidelink resources.

8. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE), configure the UE to: identifying resource allocations for a physical sidelink feedback channel (PSFCH) or a sidelink synchronization signal block (S-SSB); and Immediately before the resource allocation, a cyclic prefix extension is applied.

9. One or more NTCRMs as claimed in claim 8, wherein: The cyclic prefix extension has the following length: Wherein, l is the symbol to which the cyclic prefix extension is applied, μ is a value based on the subcarrier spacing, and Y is the time period.

10. One or more NTCRMs as claimed in claim 9, wherein: Y is less than or equal to 16 microseconds.

11. The one or more NTCRMs of claim 8, wherein: If a previous sidelink transmission by the UE or another UE is to end one symbol before the start of the PSFCH or the S-SSB, the cyclic prefix extension is applied before the PSFCH or the S-SSB.

12. The one or more NTCRMs of claim 8, wherein: The S-SSB is sent outside the channel occupancy time of the UE, and Wherein, if one or more of the following is true, then listen-before-talk type 2A is used for the SSB: The S-SSB transmission is at most 1 millisecond long; or The duty cycle of the S-SSB is at most 1 / 20 over the observation period.

13. One or more NTCRMs according to any one of claims 8 to 12, wherein: When the instructions are executed, the UE is further configured to: performing a listen before talk (LBT) procedure before transmission of the PSFCH, Wherein, the LBT process stops at a specified time, and the specified time is the same for all UEs communicating on the same sidelink carrier.

14. One or more non-transitory computer readable media (NTCRM) having instructions stored thereon, which when executed by one or more processors of a user equipment (UE), configure the UE to: receiving configuration information indicating two starting symbols allowed for sidelink transmission of the UE; and Based on the configuration information, the sidelink transmission is sent.

15. One or more NTCRMs as claimed in claim 14, wherein: The two start symbols correspond to respective start positions within the time slot.

16. The one or more NTCRMs of claim 14, wherein: The two starting symbols correspond to any symbol within a preconfigured set of values.

17. The one or more NTCRMs of claim 14, wherein: When the instructions are executed, the UE is further configured to: A preconfigured cyclic prefix extension is applied prior to the sidelink transmission.

18. The one or more NTCRMs of claim 14, wherein: When the instructions are executed, the UE is further configured to: A listen-before-talk process is performed before the sidelink transmission.

19. The one or more NTCRMs of claim 14, wherein: The LBT process stops at a specified time, which is the same for all UEs communicating on the same sidelink carrier.

20. One or more NTCRMs according to any one of claims 14 to 19, wherein: The sidelink transmission is a physical sidelink shared channel (PSSCH) or a physical sidelink control channel (PSCCH).