Method performed by user equipment and user equipment

Abstract

The present disclosure provides a method executed by a user equipment, comprising: receiving a timing advance command in time slot n; and determining a time to apply uplink transmission timing adjustment according to the time slot n in which the timing advance command is received and / or other information related to uplink transmission timing adjustment.

Description

Technical Field

[0001] The present disclosure relates to the technical field of wireless communications, and in particular to a method executed by a user equipment and a corresponding user equipment. Background Art

[0002] In March 2016, at the RAN#71 plenary meeting of the 3rd Generation Partnership Project (3GPP), a new research project on 5G technical standards (see non-patent document 1) was approved. The purpose of this research project is to develop a new wireless (New Radio: NR) access technology to meet all application scenarios, requirements and deployment environments of 5G. NR has three main application scenarios: enhanced mobile broadband communication (Enhanced MobileBroadband: eMBB), massive machine type communication (massive Machine Type Communication: mMTC) and ultra-reliable and low latency communication (Ultra-Reliable and Low Latency Communications: URLLC). In June 2017, at the RAN#75 plenary meeting of the 3rd Generation Partnership Project (3GPP), the corresponding 5G NR work project (see non-patent document 2) was approved.

[0003] The waveform supported by 5G in the downlink direction is CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing), and the waveforms supported in the uplink direction include CP-OFDM and DFT-s-OFDM (Discrete Fourier Transformation Spread Orthogonal Frequency Division Multiplexing). Each waveform supports a variety of subcarrier spacing (SCS) and cyclic prefix (CP) length combinations. Sometimes, a given SCS, or a combination of SCS and CP length is called a "parameter set" (numerology). The parameter sets supported by 5G are shown in Table 1, which defines two CP types: "normal" and "extended". Each SCS (expressed in Δf, in kHz) corresponds to an "SCS configuration" (expressed in μ).

[0004] Table 1 Parameter sets supported by 5G

[0005] μ <![CDATA[Δf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 Normal 1 30 normal 2 60 Normal, Extended 3 120 normal 4 240 normal

[0006] The basic time unit of 5G is T c =1 / (Δf max ·N f ) seconds, where Δf max =480·10 3 Hertz, N f =4096. Constant κ = T s / T c =64, where T s It is the basic time unit of LTE. s =1 / (Δf ref ·N f，ref ) seconds, Δf ref =15·10 3 Hertz, N f，ref =2048.

[0007] In the time domain, the length of a 5G radio frame (or system frame, sometimes referred to as a frame, with a frame number ranging from 0 to 1023) is 10 milliseconds. Each frame contains 10 subframes (with subframe numbers ranging from 0 to 9) of 1 millisecond in length, each of which contains The time slot number range in a subframe is ), and each time slot contains OFDM symbols. Table 2 shows the different SCS configurations. and Obviously, the number of OFDM symbols in each subframe In addition, each frame is divided into two half-frames of equal size, wherein the first half-frame (half-frame 0) includes sub-frames 0-4, and the second half-frame (half-frame 1) includes sub-frames 5-9.

[0008] Table 2 Time domain parameters related to SCS configuration μ

[0009]

[0010] In 5G, from the perspective of the UE, in a serving cell, the uplink frame i used for transmission should be earlier than the corresponding downlink frame i by (N TA +N TA，offset )·T c Seconds, see Figure 1 Among them, N TArepresents the timing advance value (also called timing adjustment value, timing adjustment value, or time alignment value, time alignment value), N TA，offset Indicates timing advance offset.

[0011] N TA The value of may be determined and / or adjusted by an indication of a higher layer (eg, a protocol layer located above the physical layer) signaling, for example, by a timing advance command and / or a timing adjustment indication. TA，offset The value of can be configured by the high-level parameter n-TimingAdvanceOffset, or a default value can be used. If two uplink carriers are configured in the serving cell, the two uplink carriers use the same N TA，offset The determination and / or adjustment of N TA The mechanism for adjusting the value of can be called "transmission timing adjustment". One of the reasons for performing transmission timing adjustment is to reduce uplink interference by roughly aligning the uplink time slot boundaries of signals transmitted by different UEs when they arrive at the base station.

[0012] In the scenario of Carrier Aggregation (CA) and / or Dual Connectivity (DC), a UE may need to transmit signaling and / or data on multiple uplink carriers. At this time, different uplink carriers may be deployed in different geographical locations, thus requiring different timing advance values. To this end, 5G defines the concept of TAG (Timing Advanced Group, also known as Time Alignment Group): a group of (uplink-configured) service cells belonging to the same TAG use the same timing reference cell and the same timing advance value (for example, the timing advance value indicated by the same timing advance command).

[0013] If a TAG includes a SpCell, the TAG is called a PTAG (Primary Timing Advance Group), otherwise the TAG is called a STAG (Secondary Timing Advance Group).

[0014] In the random access process, the response to the random access preamble (Random Access Preamble) may be called RAR (Random Access Response). The RAR may include a timing advance command, for example, an index value (denoted as T) indicated by the "Timing Advance Command" field. A ), whose value range is 0, 1, 2, ..., 3846. The timing advance value indicated by the timing advance command is N TA =T A ·16·64 / 2 μ , where μ corresponds to the SCS used for the first uplink transmission after the UE receives the RAR.

[0015] In other cases, the T indicated by the timing advance command A The value range of is 0, 1, 2, ..., 63. At this time, the timing advance command is used to change the current timing advance value (denoted as N TA_old ) is adjusted to a new timing advance value (denoted as N TA_new ). TA_new =N TA_old +(T A -31)·16·64 / 2 μ ). If the UE has multiple active uplink BWPs (active UL BWPs) in the TAG indicated by the timing advance command, then the μ corresponds to the maximum SCS among the multiple active uplink BWPs.

[0016] If the UE receives a timing advance command in uplink time slot n, it will accordingly apply the adjustment to the uplink transmission timing starting from the start of uplink time slot n+k+1. in,

[0017] ●N T，1 Represents the duration of N1 symbols, where N1 corresponds to the PDSCH processing time defined by "UE processing capability 1" when additional PDSCH DM-RS is configured.

[0018] ●N T，2 Represents the duration of N2 symbols, where N2 corresponds to the PUSCH preparation time defined by "UE processing capability 1".

[0019] The SCS used to determine N1 and N2 is the smallest of the following:

[0020] ◆The SCS used by all uplink BWPs configured in all uplink carriers configured in the TAG indicated by the timing advance command.

[0021] ◆The SCS used by all relevant downlink BWPs (eg, all downlink BWPs configured in the downlink carriers corresponding to all the uplink carriers).

[0022] ●N TA，max It is the maximum timing advance value that can be provided by a 12-bit timing advance command field.

[0023] ●Determine N TA，max The SCS used is the smallest of the following:

[0024] ◆The SCS used by all uplink BWPs configured in all uplink carriers configured in the TAG indicated by the timing advance command.

[0025] ◆The SCS used by the initial active UL BWP (or initial UL BWP, initial UL BWP, for example, configured by the higher layer parameter initialuplinkBWP).

[0026] ● is the number of time slots in each subframe.

[0027] ●Determine n and The SCS used is the smallest of the following:

[0028] ◆The SCS used by all uplink BWPs configured in all uplink carriers configured in the TAG indicated by the timing advance command.

[0029] ●T sf is the duration of a subframe, i.e. 1 millisecond.

[0030] In the existing 3GPP standard specifications for 5G, the mechanisms related to transmission timing adjustment have at least the following problems:

[0031] ●When the UE determines the time slot n+k+1 for applying the uplink transmission timing adjustment according to the time slot n of the received timing advance command, there is a problem in the method of determining k. For example, in the calculation formula of k (i.e. ), N TA，max The units of the two items are inconsistent, and adding them directly will result in a huge loss of precision, which will make the timing of the UE's uplink transmission timing adjustment extremely inaccurate (for example, k corresponds to a large delay, resulting in the UE being unable to make uplink transmission timing adjustments in a timely manner). For another example, there is no unambiguous definition of the time when transmission timing adjustments are applied during random access. For another example, there is no definition of the PDSCH processing time (N T，1 ) and PUSCH preparation time (N T，2For another example, there is a problem with the definition of time slot k and time slot n+k+1 (for example, it is impossible to receive a timing advance command within the time corresponding to uplink time slot k in TDD).

[0032] In addition, as 3GPP identifies more advanced V2X (Vehicle-to-everything) business requirements, the standardization of 5G-based V2X has begun to be put on the agenda. V2X communication refers to the communication between a vehicle and any entity that may affect the vehicle. Typical V2X communications include V2I (Vehicle-to-Infrastructure), V2N (Vehicle-to-network), V2V (Vehicle-to-vehicle), V2P (Vehicle-to-Pedestrian), etc. In June 2018, at the 3GPP RAN#80 plenary meeting, a new research project on 3GPP NR V2X (see non-patent document 3, hereinafter referred to as the V2X (Rel-16) research project, or the V2X Phase 3 research project) was approved. In V2X (Rel-16), the interface between UEs for V2X communication is called PC5, which is also called sidelink (referred to as "straight" or "side", or SL for short) link in the physical layer to distinguish it from uplink and downlink. One of the goals of the V2X (Rel-16) research project is to study the design of a new NR-based SL interface, including a new SL synchronization mechanism.

[0033] The signals and channels used for SL synchronization in V2X (Rel-16) include

[0034] SL PSS (Sidelink Primary Synchronization Signal), also known as S-PSS or PSSS (Primary Sidelink Synchronization Signal).

[0035] SL SSS (Sidelink Secondary Synchronization Signal), also known as S-SSS or SSSS (Secondary Sidelink Synchronization Signal).

[0036] PSBCH (Physical Sidelink Broadcast Channel).

[0037] SL PSS, SL SSS and PSBCH are organized in blocks on the time-frequency resource grid, called SL SSB (Sidelink SS / PBCH block), or S-SSB. The transmission bandwidth of SL SSB is within the SL BWP (Sidelink Bandwidth Part) configured for the UE.

[0038] In V2X (Rel-16), the problems that may be faced in the design of SL synchronization mechanism include at least:

[0039] ●5G (Rel-15) UE may misdetect SL PSS as 5G (Rel-15) PSS, and / or misdetect SL SSS as 5G (Rel-15) SSS, and / or misdetect PSBCH as 5G (Rel-15) PBCH, thereby unnecessarily increasing the cell search and / or system access time of 5G (Rel-15) UE. Therefore, SL PSS and PSS, and / or SL SSS and SSS, and / or PSBCH and PBCH must be well distinguished in terms of signal / channel design, and / or resource allocation, and / or resource mapping, and / or other aspects.

[0040] ●The SL synchronization ID also needs to be correctly defined and indicated in the SL SSB.

[0041] ●The resources of SL SSB must be configured correctly.

[0042] ●SL-related physical layer channels must be able to be correctly scrambled.

[0043] ●UEs that may perform SL communications must be able to obtain consistent synchronization information (for example, synchronization information determined according to the highest priority synchronization reference, such as OFDM symbol timing, time slot, subframe, frame numbering, etc.).

[0044] Prior art literature

[0045] Non-patent literature

[0046] Non-patent literature 1: RP-160671, New SID Proposal: Study on New Radio Access Technology

[0047] Non-Patent Document 2: RP-170855, New WID on New Radio Access Technology

[0048] Non-patent document 3: RP-181429, New SID: Study on NR V2X Summary of the invention

[0049] In order to solve at least part of the above problems, the present disclosure provides a method performed by a user equipment and a user equipment, which can improve the calculation method of the time for applying the uplink transmission timing adjustment, so that the UE can adjust the uplink transmission timing in a timely manner, thereby ensuring that the uplink transmission timing error of the UE is always within a reasonable range.

[0050] According to the first aspect of an embodiment of the present disclosure, a method executed by a user equipment is proposed, comprising: receiving a timing advance command in time slot n; and determining a time to apply an uplink transmission timing adjustment based on the time slot n in which the timing advance command is received and / or other information related to the uplink transmission timing adjustment.

[0051] According to the method of the first aspect of the embodiment of the present disclosure, the time for applying the uplink transmission timing adjustment is any one of the following: the starting point of time slot n+k+1; the starting point of the first uplink time slot starting from the time slot n+k+1 including time slot n+k+1; the starting point of the first downlink time slot starting from the time slot n+k+1 including time slot n+k+1; the starting point of the first flexible time slot starting from the time slot n+k+1 including time slot n+k+1; the starting point of the first flexible time slot starting from the time slot n+k+1 including time slot n+k+1 The starting point of the first mixed time slot; the starting point of the first uplink time slot starting from the time slot n+k+1 excluding the time slot n+k+1; the starting point of the first downlink time slot starting from the time slot n+k+1 excluding the time slot n+k+1; the starting point of the first flexible time slot starting from the time slot n+k+1 excluding the time slot n+k+1; and the starting point of the first mixed time slot starting from the time slot n+k+1 excluding the time slot n+k+1, wherein k is determined by any one of the following formulas (1) to (12):

[0052]

[0053]

[0054]

[0055]

[0056]

[0057]

[0058]

[0059]

[0060]

[0061]

[0062]

[0063]

[0064] Among them, the is the number of time slots in each subframe, the N T，1 is the PDSCH processing time corresponding to the physical downlink shared channel PDSCH processing capability 1, wherein N T，2 is the PUSCH preparation time corresponding to the PUSCH timing capability 1 of the physical uplink shared channel, wherein N TA，max is the maximum timing advance value, N is the duration corresponding to the maximum timing advance value, and T sf is the duration of a subframe, the T c =1 / (Δf max ·N f ), where Δf max =480·10 3 Hertz, N f =4096.

[0065] According to the method of the first aspect of the embodiment of the present disclosure, Replace with and the T sf Replace with T f , wherein the is the number of time slots in each frame, the T f is the duration of one frame.

[0066] According to the method of the first aspect of the embodiment of the present disclosure, when determining the time slot n, the N T，1 、N T，2 、N TA，max , Said and any one of the time slots n+k+1, the SCS used is any one of the following subcarrier spacing SCS, or the minimum SCS or maximum SCS of any one of the following, and the any one of the following includes: the SCS used by all uplink BWPs configured in all uplink carriers configured in the timing advance group TAG; the SCS used by all relevant downlink BWPs; the SCS used by the initial valid uplink BWP; the SCS used by the initial valid downlink BWP; the SCS used by the first uplink transmission after the user equipment receives the RAR; and the SCS used by the downlink transmission including the timing advance command.

[0067] According to the method of the first aspect of the embodiment of the present disclosure, the BWP where the first uplink transmission is located is an initial valid uplink BWP or a valid uplink BWP, and the initial valid uplink BWP and / or the valid uplink BWP are on the uplink carrier corresponding to the random access preamble, or on other uplink carriers.

[0068] According to the method of the first aspect of the embodiment of the present disclosure, the SCS used when determining the time slot n+k+1 is the same as the SCS used when determining the time slot n.

[0069] According to the method of the first aspect of the embodiment of the present disclosure, when the PDSCH processing time is represented by the number of symbols as N1,

[0070] If the N T，1 The unit is milliseconds, then the N T，1 The relationship between and N1 is any one of the following equations (13) to (15), or one of the following equations (13) to (15) in the case of a normal cyclic prefix CP and another in the case of an extended cyclic prefix CP,

[0071] N T，1 =N1·(2048+144)·κ·2 -μ ·T c 10 3

[0072] …(13)

[0073] N T，1 =N1·(2048+512)·κ·2 -μ ·T c 10 3

[0074] …(14)

[0075] N T，1 =N1·((2048+144)·κ·2 -μ+16·κ)·T c 10 3

[0076] …(15)

[0077] If the N T，1 The unit is seconds, then N T，1 The relationship between and N1 is any one of the following equations (16) to (18), or one of the following equations (16) to (18) in the case of a normal cyclic prefix CP and another in the case of an extended cyclic prefix CP,

[0078] N T，1 =N1·(2048+144)·κ·2 -μ ·T c

[0079] …(16)

[0080] N T，1 =N1·(2048+512)·κ·2 -μ ·T c

[0081] …(17)

[0082] N T，1 =N1·((2048+144)·κ·2 -μ +16·κ)·T c

[0083] …(18).

[0084] According to the method of the first aspect of the embodiment of the present disclosure, when the PUSCH preparation time is expressed as N2 in terms of the number of symbols,

[0085] If the N T，2 The unit is milliseconds, then the N T，2 The relationship between N2 and N2 is any one of the following equations (19) to (21), or one of the following equations (19) to (21) in the case of a normal cyclic prefix CP and another in the case of an extended cyclic prefix CP,

[0086] N T，2 =N2·(2048+144)·κ·2 -μ ·T c 10 3

[0087] …(19)

[0088] N T，2 =N2·(2048+512)·κ·2-μ ·T c 10 3

[0089] …(20)

[0090] N T，2 =N2·((2048+144)·κ·2 -μ +16·κ)·T c 10 3

[0091] …(twenty one)

[0092] If the N T，2 The unit is seconds, then N T，2 The relationship between N2 and N2 is any one of the following equations (22) to (24), or one of the following equations (22) to (24) in the case of a normal cyclic prefix CP and another in the case of an extended cyclic prefix CP,

[0093] N T，2 =N2·(2048+144)·κ·2 -μ ·T c

[0094] …(twenty two)

[0095] N T，2 =N2·(2048+512)·κ·2 -μ ·T c

[0096] …(twenty three)

[0097] N T，2 =N2·((2048+144)·κ·2 -μ +16·κ)·T c

[0098] …(twenty four).

[0099] According to the method of the first aspect of the embodiment of the present disclosure, the normal CP situation refers to any one of the following situations or any combination of multiple situations in an "and" or "or" manner: any uplink BWP configured in any uplink carrier configured in the TAG is configured with a normal CP; at least one uplink BWP in each uplink carrier configured in the TAG is configured with a normal CP; all uplink BWPs configured in all uplink carriers configured in the TAG are configured with a normal CP; at least one of all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG is configured with a normal CP; all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG are configured with a normal CP; at least one of the downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG is configured with a normal CP; and the downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG are configured with a normal CP. P is configured with a normal CP, and the extended CP situation refers to any one of the following situations or any combination of multiple situations in an "and" or "or" manner: any uplink BWP configured in any uplink carrier configured in the TAG is configured with an extended CP; at least one uplink BWP in each uplink carrier configured in the TAG is configured with an extended CP; all uplink BWPs configured in all uplink carriers configured in the TAG are configured with an extended CP; at least one of all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG is configured with an extended CP; all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG are configured with an extended CP; at least one of the downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG is configured with an extended CP; and the downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG are configured with an extended CP.

[0100] According to a second aspect of an embodiment of the present disclosure, a user device is provided, comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, execute the method performed by the user device according to any one of the first aspects.

[0101] Effects of the Invention

[0102] According to the present disclosure, by improving the calculation method of the time for applying the uplink transmission timing adjustment, the UE can adjust the uplink transmission timing in time, ensuring that the uplink transmission timing error of the UE is always within a reasonable range. BRIEF DESCRIPTION OF THE DRAWINGS

[0103] The above and other features of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0104] Figure 1 It is a diagram showing the concept of advancing uplink frames relative to downlink frames in the existing 3GPP standard specifications for 5G.

[0105] Figure 2 is a flowchart showing a method executed by a user equipment according to the first embodiment of the present disclosure.

[0106] Figure 3 is a flowchart showing a method executed by a user equipment according to the second embodiment of the present disclosure.

[0107] Figure 4 is a flowchart showing a method executed by a user equipment according to the third embodiment of the present disclosure.

[0108] Figure 5 is a flowchart showing a method executed by a user equipment according to a fourth embodiment of the present disclosure.

[0109] Figure 6 is a flowchart showing a method executed by a user equipment according to a fifth embodiment of the present disclosure.

[0110] Figure 7 is a block diagram schematically illustrating a user equipment involved in the present disclosure. DETAILED DESCRIPTION

[0111] The present disclosure is described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below. In addition, for the sake of simplicity, detailed descriptions of known technologies that are not directly related to the present disclosure are omitted to prevent confusion in the understanding of the present disclosure.

[0112] The following uses a 5G mobile communication system and its subsequent evolution versions as an example application environment to specifically describe multiple implementations of the present disclosure. However, it should be noted that the present disclosure is not limited to the following implementations, but is applicable to more other wireless communication systems, such as communication systems after 5G and 4G mobile communication systems before 5G.

[0113] The following describes some of the terms involved in the present disclosure. Unless otherwise specified, the terms involved in the present disclosure are defined herein. The terms given in the present disclosure may be named differently in LTE, LTE-Advanced, LTE-Advanced Pro, NR and subsequent communication systems, but unified terms are used in the present disclosure, and when applied to a specific system, they can be replaced by the terms used in the corresponding system.

[0114] 3GPP: 3rd Generation Partnership Project

[0115] BWP: Bandwidth Part, bandwidth fragment

[0116] CA: Carrier Aggregation

[0117] CP: Cyclic Prefix

[0118] CP-OFDM: Cyclic Prefix Orthogonal Frequency Division Multiplexing

[0119] DC: Dual Connectivity

[0120] DFT-s-OFDM: Discrete Fourier Transformation Spread Orthogonal Frequency Division Multiplexing

[0121] DL: Downlink

[0122] DL-SCH: Downlink Shared Channel, downlink shared channel

[0123] DM-RS: Demodulation reference signal

[0124] eMBB: Enhanced Mobile Broadband

[0125] IE: Information Element

[0126] LCID: Logical Channel ID, logical channel identifier

[0127] LTE-A: Long Term Evolution-Advanced, an upgraded version of long-term evolution technology

[0128] MAC: Medium Access Control

[0129] MAC CE: MAC Control Element

[0130] MCG: Master Cell Group

[0131] mMTC: massive Machine Type Communication

[0132] NR — New Radio

[0133] NUL: Normal Uplink, normal uplink

[0134] OFDM: Orthogonal Frequency Division Multiplexing

[0135] PBCH: Physical Broadcast Channel

[0136] PDSCH: Physical Downlink Shared Channel, physical downlink shared channel

[0137] PSBCH: Physical Sidelink Broadcast Channel, physical sidelink broadcast channel

[0138] PSCCH: Physical Sidelink Control Channel, physical sidelink control channel

[0139] PSSCH: Physical Sidelink Shared Channel, physical straight shared channel

[0140] PSS: Primary Synchronization Signal

[0141] PSSS: Primary Sidelink Synchronization Signal, main straight synchronization signal

[0142] PTAG: Primary Timing Advance Group

[0143] PUSCH: Physical uplink shared channel, physical uplink shared channel

[0144] RAR: Random Access Response, random access response

[0145] RB: Resource Block

[0146] RE:Resource Element

[0147] RRC: Radio Resource Control

[0148] SCG: Secondary Cell Group

[0149] SCS: Subcarrier Spacing, subcarrier spacing

[0150] SFN: System Frame Number, system frame number

[0151] SIB: System Information Block

[0152] SL: Sidelink, straight

[0153] SL BWP: Sidelink Bandwidth Part, straight bandwidth segment

[0154] SL PSS: Sidelink Primary Synchronization Signal, straight main synchronization signal

[0155] SL SSB: Sidelink SS / PBCH block, straight synchronization signal / physical broadcast channel block

[0156] SL SSS: Sidelink Secondary Synchronization Signal, straight auxiliary synchronization signal

[0157] SpCell:Special Cell, special cell

[0158] SSB: SS / PBCH block, synchronization signal / physical broadcast channel block

[0159] SSS: Secondary Synchronization Signal, auxiliary synchronization signal

[0160] SSSS: Secondary Sidelink Synchronization Signal, auxiliary straight line synchronization signal

[0161] STAG: Secondary Timing Advance Group

[0162] SUL: Supplementary Uplink

[0163] TA: Timing Advance

[0164] TAG: Timing Advanced Group, timing advanced group

[0165] TDD: Time Division Duplexing

[0166] UE:User Equipment

[0167] UL: Uplink

[0168] URLLC: Ultra-Reliable and Low Latency Communication

[0169] V2I: Vehicle-to-Infrastructure

[0170] V2N: Vehicle-to-network

[0171] V2P: Vehicle-to-Pedestrian

[0172] V2V: Vehicle-to-vehicle

[0173] V2X: Vehicle-to-everything

[0174] Unless otherwise specified, in all embodiments and implementations of the present disclosure:

[0175] ●T c =1 / (Δf max ·N f ) seconds, where Δf max =480·10 3 Hertz, N f =4096.

[0176] ●T s =1 / (Δf ref ·Nf，ref ) seconds, where Δf ref =15·10 3 Hertz, N f，ref =2048.

[0177] κ=T s / T c =64.

[0178] ● is the number of time slots in each subframe.

[0179] ● is the number of time slots in each frame.

[0180] ●T sf is the duration of a subframe. sf =1 millisecond.

[0181] ●T f is the duration of a frame, T f =10 milliseconds.

[0182] ●A downlink time slot refers to a time slot in which all symbols are downlink symbols.

[0183] ●A flexible time slot refers to a time slot in which all symbols are flexible symbols.

[0184] ●An uplink time slot refers to a time slot in which all symbols are uplink symbols.

[0185] A mixed time slot refers to a time slot containing at least two of downlink symbols, flexible symbols, and uplink symbols.

[0186] ●The resources (e.g., resource blocks, or subcarriers) occupied by a physical layer channel or signal, or a combination of multiple physical layer channels and / or signals (e.g., SSB, or SL SSB) in the frequency domain are numbered starting from 0, and the resources (e.g., symbols, or time slots, or subframes, or frames) occupied in the time domain are also numbered starting from 0. For example, the lowest-numbered resource block of an SSB is numbered 0, and the lowest-numbered subcarrier of the resource block is numbered 0.

[0187] [Example 1]

[0188] Next, combine Figure 2 To illustrate the method executed by the user equipment in the first embodiment of the present disclosure.

[0189] Figure 2 is a flowchart showing a method executed by a user equipment according to the first embodiment of the present disclosure.

[0190] like Figure 2As shown, in the first embodiment of the present disclosure, the steps performed by the user equipment UE include: step S101 and step S102.

[0191] Specifically, in step S101, a timing advance command is received.

[0192] For example, a timing advance command is received from a base station in time slot n.

[0193] The timing advance command may indicate an index value (denoted as T A ).

[0194] ● The timing advance command may be included in a RAR, which may be a response to a random access preamble. For example, the RAR may be a MAC PDU, which may include a MAC subPDU; the payload of the MAC subPDU may include a "Timing Advance Command" field for placing the timing advance command. The size of the "Timing Advance Command" field may be 12 bits, and the index value T indicated by it may be 12 bits. A The range can be 0, 1, 2, ..., 3846.

[0195] ◆At this time, the TAG corresponding to the timing advance command may be the TAG to which the cell corresponding to the uplink carrier corresponding to the random access preamble belongs, or may be indicated in the RAR (for example, indicated in the MAC sub-PDU included in the RAR), or may be a TAG indicated in other ways. Embodiment 1 of the present disclosure does not limit the TAG corresponding to the timing advance command at this time.

[0196] ●The timing advance command may also be included in a MAC CE called "Timing Advance Command". For example, the MAC CE may be identified by a MAC subheader, the MAC subheader may be used for DL-SCH, and the value of the LCID field in the MAC subheader may be 61. For another example, the MAC CE may include a TAG field and a "Timing Advance Command" field. The TAG field may be 2 bits, used to determine the TAG corresponding to the timing advance command; the "Timing Advance Command" field may be 6 bits, and the index value indicated by it is T A The range can be 0, 1, 2, ..., 63.

[0197] ● The timing advance command may also be included in other high-layer messages (such as other MAC messages or RRC messages). Embodiment 1 of the present disclosure does not limit the message carrying the timing advance command.

[0198] When determining the time slot n, the SCS used may be an SCS in any of the following items (if there is only one SCS in the items), and may be the minimum SCS in any one or more of the following items, or the maximum SCS in any one or more of the following items:

[0199] ◆The SCS used by all uplink BWPs configured in all uplink carriers configured in the TAG.

[0200] ◆The SCS used by all relevant downlink BWPs (eg, all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG, and also, the downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG).

[0201] ◆The SCS used by the initial active UL BWP (or initial UL BWP, initial UL BWP, for example, configured by the higher layer parameter initialuplinkBWP).

[0202] ◆The SCS used by the initial active DL BWP (or initial DL BWP, initialDL BWP, for example, configured by the higher layer parameter initialDownlinkBWP).

[0203] ◆The SCS used by the UE for the first uplink transmission after receiving the RAR. The BWP for the first uplink transmission may be an initial valid uplink BWP or a valid uplink BWP; the initial valid uplink BWP and / or the valid uplink BWP may be on the uplink carrier corresponding to the random access preamble or on other uplink carriers.

[0204] ◆The SCS used by the downlink transmission (e.g. PDSCH) containing the timing advance command.

[0205] ● When determining the time slot n, the SCS used may also be determined in other ways. Embodiment 1 of the present disclosure does not limit the SCS used when determining the time slot n.

[0206] ●The type of the time slot n may not be limited (for example, it may be a downlink time slot, a flexible time slot, an uplink time slot, or a mixed time slot), or it may be limited to any one of a downlink time slot, a flexible time slot, an uplink time slot and a mixed time slot, or it may be limited to a combination of any two or more of a downlink time slot, a flexible time slot, an uplink time slot and a mixed time slot.

[0207] In addition, in step S102, the time for applying the uplink transmission timing adjustment is determined according to the time of receiving the timing advance command and / or other information related to the uplink transmission timing adjustment.

[0208] For example, according to the time slot n of the received timing advance command and other information related to the uplink transmission timing adjustment, the time t for applying the uplink transmission timing adjustment is determined (for example, applying the adjustment of the uplink transmission timing from time t, or applying the adjustment of the uplink transmission timing before time t, or applying the adjustment of the uplink transmission timing no later than time t). The time t may be any one of the following:

[0209] ●The starting point of time slot n+k+1.

[0210] ●The starting point of the first uplink time slot starting from time slot n+k+1 (including time slot n+k+1).

[0211] ●The starting point of the first downlink time slot starting from time slot n+k+1 (including time slot n+k+1).

[0212] ●The starting point of the first flexible time slot starting from time slot n+k+1 (including time slot n+k+1).

[0213] ●The starting point of the first mixed time slot starting from time slot n+k+1 (including time slot n+k+1).

[0214] ●The starting point of the first uplink time slot starting from time slot n+k+1 (excluding time slot n+k+1).

[0215] ●The starting point of the first downlink time slot starting from time slot n+k+1 (excluding time slot n+k+1).

[0216] ●The starting point of the first flexible time slot starting from time slot n+k+1 (excluding time slot n+k+1).

[0217] ●The starting point of the first mixed time slot starting from time slot n+k+1 (excluding time slot n+k+1).

[0218] in,

[0219] ●The k can be determined in any of the following ways:

[0220] (a).

[0221] (b).

[0222] (c).

[0223] (d).

[0224] (e).

[0225] (f).

[0226] (g).

[0227] (h).

[0228] (i).

[0229] (j).

[0230] (k).

[0231] (1).

[0232] in,

[0233] ◆Optionally, in any of the above equations, Replace Put T sf Change to T f .

[0234] ◆N T，1 It is the PDSCH processing time corresponding to PDSCH processing capability 1.

[0235] in,

[0236] ○ Sometimes, when the context is clear, for example, when it can be seen from the context that it refers to the capabilities related to PDSCH processing, PDSCH processing capability 1 can also be called UE processing capability 1.

[0237] ○ The PDSCH processing capability 1 may be the PDSCH processing capability 1 when an additional PDSCH DM-RS is configured. For example, the dmrs-AdditionalPosition parameter in the DMRS-DownlinkConfig in the high-level parameter dmrs-DownlinkForPDSCHMappingTypeA is not configured or the configured value is not "pos0", or the dmrs-AdditionalPosition parameter in the DMRS-DownlinkConfig in the high-level parameter dmrsDownlinkForPDSCH-MappingTypeB is not configured or the configured value is not "pos0".

[0238] ○N T，1 The unit of can be milliseconds or seconds. For example, in formulas (a), (b), (c), (d), (e), (f), and (g), N T，1 The unit of N can be milliseconds. In formulas (h), (i), (j), (k), and (l), N T，1 The unit can be seconds.

[0239] ○ The PDSCH processing time can also be expressed as the number of symbols, denoted as N1. T，1 It may be a duration of N1 symbols, wherein the N1 symbols may be N1 consecutive symbols.

[0240] ○ Optionally, if the N T，1 The unit is milliseconds, then the N T，1 The relationship between N1 and N2 can be fixed to any one of the following (i.e., regardless of how the CP is configured), or one of the following (e.g., the first one) can be used in the case of a normal CP, and another of the following can be used in the case of an extended CP.

[0241] One (such as the second one):

[0242] ◇N T，1 =N1·(2048+144)·κ·2 -μ ·T c 10 3

[0243] ◇N T，1 =N1·(2048+512)·κ·2 -μ ·T c 10 3

[0244] ◇N T，1 =N1·((2048+144)·κ·2-μ +16·κ)·T c 10 3

[0245] ○ Optionally, if the N T，1 The unit is seconds, then N T，1 The relationship between N1 and N2 may be fixed to any one of the following (i.e., regardless of how the CP is configured), or one of the following (e.g., the first one) may be used in the case of a normal CP, and another of the following (e.g., the second one) may be used in the case of an extended CP:

[0246] ◇N T，1 =N1·(2048+144)·κ·2 -μ ·T c

[0247] ◇N T，1 =N1·(2048+512)·κ·2 -μ ·T c

[0248] ◇N T，1 =N1·((2048+144).κ.2 -μ +16·κ).T c

[0249] Optionally, the normal CP situation may refer to any one or more of the following in any combination in an “and” or “or” manner:

[0250] ◇Any uplink BWP configured in any uplink carrier configured in the TAG is configured with a normal CP.

[0251] ◇ In each uplink carrier configured in the TAG, at least one uplink BWP is configured with a normal CP.

[0252] ◇All uplink BWPs configured in all uplink carriers configured in the TAG are configured with normal CPs.

[0253] ◇At least one of all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG is configured with a normal CP.

[0254] ◇All downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG are configured with normal CPs.

[0255] ◇At least one of the downlink BWPs corresponding to all the uplink BWPs configured in all the uplink carriers configured in the TAG is configured with a normal CP.

[0256] ◇The downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG are configured with normal CPs.

[0257] ○ Optionally, the normal CP situation may also refer to any situation that does not belong to the "extended CP situation" (when the extended CP situation does not refer to any situation that does not belong to the "normal CP situation").

[0258] Optionally, the extended CP may refer to any combination of any one or more of the following in an “and” or “or” manner:

[0259] ◇ Any uplink BWP configured in any uplink carrier configured in the TAG is configured with an extended CP.

[0260] ◇ In each uplink carrier configured in the TAG, at least one uplink BWP is configured with an extended CP.

[0261] ◇All uplink BWPs configured in all uplink carriers configured in the TAG are configured with extended CP.

[0262] ◇At least one of all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG is configured with an extended CP.

[0263] ◇All downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG are configured with extended CPs.

[0264] ◇At least one of the downlink BWPs corresponding to all the uplink BWPs configured in all the uplink carriers configured in the TAG is configured with an extended CP.

[0265] ◇The downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG are configured with extended CPs.

[0266] ○ Optionally, the extended CP situation may also refer to any situation that does not belong to the “normal CP situation” (when the normal CP situation does not refer to any situation that does not belong to the “extended CP situation”).

[0267] ◆N T，2 is the PUSCH preparation time corresponding to PUSCH timing capability 1.

[0268] ○ Sometimes, when the context is clear, for example, when the context shows that it refers to capabilities related to PUSCH timing, PUSCH timing capability 1 may also be referred to as UE processing capability 1.

[0269] ○N T，2 The unit of can be milliseconds or seconds. For example, in formulas (a), (b), (c), (d), (e), (f), and (g), N T，2 The unit of N can be milliseconds. In formulas (h), (i), (j), (k) and (1), N T，2 The unit can be seconds.

[0270] ○ The PUSCH preparation time can also be expressed in terms of the number of symbols, denoted as N2. T，2 It may be a duration of N2 symbols, where the N2 symbols may be N2 consecutive symbols.

[0271] ○ Optionally, if the N T，2 The unit is milliseconds, then the N T，2 The relationship between N2 and N2 may be fixed to any one of the following (i.e., regardless of how the CP is configured), or one of the following (e.g., the first one) may be used in the case of a normal CP, and another of the following (e.g., the second one) may be used in the case of an extended CP:

[0272] ◇N T，2 =N2·(2048+144)·κ·2 -μ ·T c 10 3

[0273] ◇N T，2 =N2·(2048+512)·κ·2 -μ ·T c 10 3

[0274] ◇N T，2 =N2·((2048+144)·κ·2 -μ +16·κ)·T c 10 3

[0275] ○ Optionally, if the N T，2 The unit is seconds, then N T，2 The relationship between N2 and N2 may be fixed to any one of the following (i.e., regardless of how the CP is configured), or one of the following (e.g., the first one) may be used in the case of a normal CP, and another of the following (e.g., the second one) may be used in the case of an extended CP:

[0276] ◇NT，2 =N2·(2048+144)·κ·2 -μ ·T c

[0277] ◇N T，2 =N2·(2048+512)·κ·2 -μ ·T c

[0278] ◇N T，2 =N2·((2048+144)·κ·2 -μ +16·κ).T c

[0279] Optionally, the normal CP situation may refer to any one or more of the following in any combination in an “and” or “or” manner:

[0280] ◇Any uplink BWP configured in any uplink carrier configured in the TAG is configured with a normal CP.

[0281] ◇ In each uplink carrier configured in the TAG, at least one uplink BWP is configured with a normal CP.

[0282] ◇All uplink BWPs configured in all uplink carriers configured in the TAG are configured with normal CPs.

[0283] ◇At least one of all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG is configured with a normal CP.

[0284] ◇All downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG are configured with normal CPs.

[0285] ◇At least one of the downlink BWPs corresponding to all the uplink BWPs configured in all the uplink carriers configured in the TAG is configured with a normal CP.

[0286] ◇The downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG are configured with normal CPs.

[0287] ○ Optionally, the normal CP situation may also refer to any situation that does not belong to the "extended CP situation" (when the extended CP situation does not refer to any situation that does not belong to the "normal CP situation").

[0288] Optionally, the extended CP may refer to any combination of any one or more of the following in an “and” or “or” manner:

[0289] ◇ Any uplink BWP configured in any uplink carrier configured in the TAG is configured with an extended CP.

[0290] ◇ In each uplink carrier configured in the TAG, at least one uplink BWP is configured with an extended CP.

[0291] ◇All uplink BWPs configured in all uplink carriers configured in the TAG are configured with extended CP.

[0292] ◇At least one of all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG is configured with an extended CP.

[0293] ◇All downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG are configured with extended CPs.

[0294] ◇At least one of the downlink BWPs corresponding to all the uplink BWPs configured in all the uplink carriers configured in the TAG is configured with an extended CP.

[0295] ◇The downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG are configured with extended CPs.

[0296] ○ Optionally, the extended CP situation may also refer to any situation that does not belong to the “normal CP situation” (when the normal CP situation does not refer to any situation that does not belong to the “extended CP situation”).

[0297] ◆N TA，max Refers to the maximum timing advance value. For example, N TA，max It can be equal to the maximum timing advance value that can be provided by a 12-bit timing advance command field (for example, 2 for SCS). μ 15 kHz, N TA，max =T A，max ·16·64 / 2 μ , where T A，max is the maximum index value that can be indicated by the timing advance command field, such as 3846).

[0298] ◆N refers to the duration corresponding to the maximum timing advance value. The unit of N can be milliseconds or seconds. For example, in formula (f), the unit of N can be milliseconds, N and N TA，max The relationship can be N = N TA，max ·T c 10 3 For example, in formula (k), the unit of N can be seconds, N and N TA，max The relationship can be N = N TA，max ·T c .

[0299] ●In determining the N T，1 、N T，2 、N TA，max , Said and any one of the time slots n+k+1, the SCS used may be an SCS in any of the following items (if there is only one SCS in the item), or the minimum SCS in any one or more of the following items, or the maximum SCS in any one or more of the following items:

[0300] ◆The SCS used by all uplink BWPs configured in all uplink carriers configured in the TAG.

[0301] ◆The SCS used by all relevant downlink BWPs (eg, all downlink BWPs configured in the downlink carriers corresponding to all uplink carriers configured in the TAG, and also, the downlink BWPs corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG).

[0302] ◆The SCS used by the initial valid uplink BWP (eg configured via the higher layer parameter initialuplinkBWP).

[0303] ◆The SCS used by the initial valid downlink BWP (eg configured via the higher layer parameter initialDownlinkBWP).

[0304] ◆The SCS used by the UE for the first uplink transmission after receiving the RAR. The BWP for the first uplink transmission may be an initial valid uplink BWP or a valid uplink BWP; the initial valid uplink BWP and / or the valid uplink BWP may be on the uplink carrier corresponding to the random access preamble or on other uplink carriers.

[0305] ◆The SCS used by the downlink transmission (e.g. PDSCH) containing the timing advance command.

[0306] ●When determining the time slot n+k+1, the SCS used may also be the same as the SCS used when determining the time slot n.

[0307] ●In determining the N T，1 、N T，2 、N TA，max , Said When determining any one of the time slots n+k+1, the SCS used may also be determined in other ways. T，1 、NT，2 、N TA，max , Said There is no limitation on the SCS used in any one of the time slots n+k+1.

[0308] ●The type of the time slot n+k+1 may not be limited in any way (for example, it may be a downlink time slot, a flexible time slot, an uplink time slot, or a mixed time slot), or it may be limited to the same type as the time slot n (for example, if the time slot n is an uplink time slot, and the time slot n+k+1 is also limited to an uplink time slot, it means that time slots n, n+1, ..., n+k+1 are all uplink time slots; at this time, in the case of unpaired spectrum, there may be a non-uplink time slot between time slot n and time slot n+k+1, and the non-uplink time slot does not participate in the time slot numbering here), or it may be limited to any one of a downlink time slot, a flexible time slot, an uplink time slot and a mixed time slot, or it may be limited to a combination of any two or more of the downlink time slot, the flexible time slot, the uplink time slot and the mixed time slot.

[0309] Optionally, in embodiment 1 of the present disclosure, the uplink carrier may refer to a normal uplink carrier (NUL carrier, sometimes also referred to as UL carrier) configured by uplinkConfigCommon and uplinkConfig (if any), or may refer to a supplementary uplink carrier (SUL carrier) configured by supplementaryUplinkConfig and supplementaryUplink (if any).

[0310] Optionally, in Embodiment 1 of the present disclosure, the correspondence between the uplink carrier and the downlink carrier may be determined according to the cells to which the uplink carrier and the downlink carrier belong (for example, a given uplink carrier corresponds to a downlink carrier belonging to the same cell), or may be determined in other ways.

[0311] Optionally, in Embodiment 1 of the present disclosure, depending on the specific configuration method, "all uplink carriers configured in the TAG" may also refer to all uplink carriers belonging to the TAG, "any uplink carrier configured in the TAG" may also refer to any uplink carrier belonging to the TAG, and "each uplink carrier configured in the TAG" may also refer to each uplink carrier belonging to the TAG.

[0312] Optionally, in Embodiment 1 of the present disclosure, depending on the specific configuration method, "all downlink carriers configured in the TAG" may also refer to all downlink carriers belonging to the TAG, "any downlink carrier configured in the TAG" may also refer to any downlink carrier belonging to the TAG, and "each downlink carrier configured in the TAG" may also refer to each downlink carrier belonging to the TAG.

[0313] Optionally, in the first embodiment of the present disclosure, the correspondence between the uplink BWP and the downlink BWP may exist in all uplink BWPs, or may only exist in a part of the uplink BWPs (for example, the correspondence exists only in TDD, or for a given uplink BWP or downlink BWP, whether the correspondence exists depends on the configuration of the uplink BWP or downlink BWP). The correspondence between the uplink BWP and the downlink BWP may be determined according to the ID of the BWP (for example, an uplink BWP with an ID of 1 corresponds to a downlink BWP with an ID of 1), or may be determined in other ways. If the correspondence between the uplink BWP and the downlink BWP only exists in a part of the uplink BWP, then "the downlink BWP corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG" may also be expressed as "the downlink BWP corresponding to all uplink BWPs configured in all uplink carriers configured in the TAG (if any)", wherein the downlink BWP corresponding to all uplink BWPs may refer to the downlink BWP corresponding to each of the uplink BWPs.

[0314] Optionally, in the first embodiment of the present disclosure, unless otherwise specified, the initial valid uplink BWP may be one or more of the following:

[0315] ●The initial valid uplink BWP configured for all uplink carriers configured for the UE.

[0316] ● An initial valid uplink BWP configured in one of the uplink carriers configured for the UE. For example, an initial valid uplink BWP configured in the uplink carrier configured in the cell that sends the timing advance command.

[0317] ●The initial valid uplink BWP configured in all uplink carriers configured in the TAG.

[0318] ● An initial valid uplink BWP configured in one of the uplink carriers configured in the TAG. For example, an initial valid uplink BWP configured in an uplink carrier configured in a primary cell (eg, MCG or SCG) of a cell group (eg, MCG or SCG) to which the TAG belongs.

[0319] ●The initial valid uplink BWP configured in the uplink carrier where the first uplink transmission after the UE receives the RAR is located.

[0320] Optionally, in the first embodiment of the present disclosure, unless otherwise specified, the initial valid downlink BWP may be one or more of the following:

[0321] ●The initial valid downlink BWP configured for all downlink carriers configured for the UE.

[0322] ● An initial valid downlink BWP configured in one of the downlink carriers configured for the UE. For example, an initial valid downlink BWP configured in the downlink carrier configured in the cell that sends the timing advance command.

[0323] ●The initial valid downlink BWP configured in all downlink carriers configured in all cells configured in the TAG.

[0324] ● An initial valid downlink BWP configured in a downlink carrier configured in one of the cells configured in the TAG. For example, an initial valid downlink BWP configured in a downlink carrier configured in a primary cell of a cell group (eg, MCG or SCG) to which the TAG belongs.

[0325] Optionally, in the first embodiment of the present disclosure, “all uplink BWPs” configured in a given uplink carrier may include an initial valid uplink BWP, or may not include an initial valid uplink BWP.

[0326] Optionally, in the first embodiment of the present disclosure, “all downlink BWPs” configured in a given downlink carrier may include an initial valid downlink BWP, or may not include an initial valid downlink BWP.

[0327] Thus, according to the first embodiment, the present disclosure provides a method for improving the method for determining the time for applying the uplink transmission timing adjustment, so that the UE can adjust the uplink transmission timing in a timely manner, thereby ensuring that the uplink transmission timing error of the UE is maintained within a reasonable range.

[0328] [Example 2]

[0329] Next, combine Figure 3 To illustrate the method executed by the user equipment in the second embodiment of the present disclosure.

[0330] Figure 3 is a flowchart showing a method executed by a user equipment according to the second embodiment of the present disclosure.

[0331] like Figure 3As shown, in the second embodiment of the present disclosure, the steps performed by the user equipment UE include: step S201 and step S202.

[0332] Specifically, in step S201, configuration information of parameters related to the SL SSB is obtained (such as whether the parameters have been configured, or the configured values ​​of the parameters). For example, the configuration information is obtained from predefined information or preconfigured information, or the configuration information is obtained from a base station (for example, the configuration information is obtained through DCI or MAC CE or RRC signaling), or the configuration information is obtained from other UEs, or when the parameter is not configured, a default value is used.

[0333] in,

[0334] ●The parameters related to the SL SSB may include parameters related to the time-frequency position (i.e., the position in time and / or frequency) of the SL SSB. The time-frequency position of the SL SSB may be the time-frequency position where the SL SSB may be sent (in this case, it can also be said that the SL SSB is a candidate SL SSB, and the time-frequency position is the time-frequency position of the candidate SL SSB), or it may be the time-frequency position of the SL SSB actually sent.

[0335] The parameters related to the time-frequency position of the SL SSB may include the position of a subcarrier (e.g., the position of the center frequency of the subcarrier), wherein the SCS corresponding to the subcarrier may be the SCS used by the SL SSB. For example, the position of the subcarrier may correspond to the position of a subcarrier of the SL SSB, such as the resource block n of the SL SSB. PRB The position of subcarrier k. PRB can be a value in the set {0, 1, ..., 19}, and k can be a value in the set {0, 1, ..., 11}.

[0336] The parameters related to the time-frequency position of the SL SSB may also include one or more of the following:

[0337] ◆Configuration information related to the SL carrier where the SL BWP where the SL SSB is located is located. For example, the offset between the lowest subcarrier of common resource block 0 (also known as point A) and the lowest available subcarrier of the SL carrier (such as expressed in the number of resource blocks), and / or the SCS used by the SL carrier, and / or the carrier bandwidth of the SL carrier (such as expressed in the number of resource blocks), and / or the position of the direct current subcarrier of the SL carrier.

[0338] ◆Parameter configuration information related to the SL BWP where the SL SSB is located. For example, the number of the starting resource block of the SL BWP, and / or the size of the SL BWP (such as expressed in the number of resource blocks).

[0339] ◆The position of the SL SSB in the SL BWP. For example, the number of the starting resource block of the SL SSB in the SL BWP. Another example, the number of the starting subcarrier of the SL SSB in the SL BWP. Another example, the number of the starting subband of the SL SSB in the SL BWP.

[0340] ● The parameters related to the SL SSB may also be obtained in other ways. The second embodiment of the present disclosure does not limit the method for obtaining the parameters related to the SL SSB.

[0341] In addition, in step S202, the SL SSB is received according to the parameters related to the SL SSB.

[0342] in,

[0343] ●The SL SSB may include SL PSS, SL SSS and PSBCH.

[0344] ●The SL SSB may include 240 consecutive subcarriers in the frequency domain (eg, subcarriers are numbered 0, 1, ..., 239 in order from low to high according to the center frequency of the subcarriers).

[0345] ●The SL SSB may include 4 consecutive OFDM symbols in the time domain (eg, numbered as OFDM symbols 0, 1, 2, 3 in time sequence).

[0346] ●The length of the sequence used by the SL PSS (referred to as SL PSS sequence in this disclosure) may be 127.

[0347] ●The length of the sequence used by the SL SSS (referred to as SL SSS sequence in this disclosure) can be 127.

[0348] The SL PSS sequence and / or the SL SSS sequence may be associated with a SL synchronization identity (SLsynchronization identity, denoted as ). For example, different The value of can correspond to different SLPSS sequences and / or SL SSS sequences.

[0349] ● The value range set of can be {0, 1, ..., 83}, or {0, 1, ..., 167}, or {0, 1, ..., 251}, or {0, 1, ..., 335}, or {0, 1, ..., 419}, or {0, 1, ..., 503}, or {0, 1, ..., 587}, or {0, 1, ..., 671}, or {0, 1, ..., 755}, or {0, 1, ..., 839}, or {0, 1, ..., 923}, or {0, 1, ..., 1007}, or {0, 1, ..., 1091}, or any other set of integers.

[0350] ●Optionally, the Can be and Determine, for example, using one of the following methods:

[0351] ◆

[0352] ◆

[0353] ◆

[0354] ◆

[0355] ◆

[0356] ◆

[0357] ◆

[0358] ◆

[0359] ◆

[0360] ◆

[0361] ◆

[0362] ◆

[0363] ◆

[0364] ◆

[0365] ◆

[0366] ◆

[0367] ◆

[0368] ● Optionally, the time domain and frequency domain resources in the SL SSB occupied by the PSBCH may be one of the following:

[0369] ◆The subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 1, the subcarrier set {0, 1, ..., 239} in OFDM symbol 2, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

[0370] ◆The subcarrier set in OFDM symbol 1 is {0, 1, ..., 239}, the subcarrier set in OFDM symbol 2 is {0, 1, ..., 239}, and the subcarrier set in OFDM symbol 3 is {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239}.

[0371] ◆The subcarrier set {0, 1, ..., 239} in OFDM symbol 1, the subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 2, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

[0372] ◆The subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 0, the subcarrier set {0, 1, ..., 239} in OFDM symbol 1, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 2.

[0373] ◆The subcarrier set in OFDM symbol 0 is {0, 1, ..., 239}, the subcarrier set in OFDM symbol 1 is {0, 1, ..., 239}, and the subcarrier set in OFDM symbol 2 is {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239}.

[0374] ◆The subcarrier set {0, 1, ..., 239} in OFDM symbol 0, the subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 1, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 2.

[0375] ◆The subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 0, the subcarrier set {0, 1, ..., 239} in OFDM symbol 1, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

[0376] ◆The subcarrier set in OFDM symbol 0 is {0, 1, ..., 239}, the subcarrier set in OFDM symbol 1 is {0, 1, ..., 239}, and the subcarrier set in OFDM symbol 3 is {0, 1, ..., 47} and the subcarrier set is {192, 193, ..., 239}.

[0377] ◆The subcarrier set {0, 1, ..., 239} in OFDM symbol 0, the subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 1, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

[0378] ◆The subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 0, the subcarrier set {0, 1, ..., 239} in OFDM symbol 2, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

[0379] ◆The subcarrier set in OFDM symbol 0 is {0, 1, ..., 239}, the subcarrier set in OFDM symbol 2 is {0, 1, ..., 239}, and the subcarrier set in OFDM symbol 3 is {0, 1, ..., 47} and the subcarrier set is {192, 193, ..., 239}.

[0380] ◆The subcarrier set {0, 1, ..., 239} in OFDM symbol 0, the subcarrier set {0, 1, ..., 47} and the subcarrier set {192, 193, ..., 239} in OFDM symbol 2, and the subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

[0381] ● Optionally, when mapping the PSBCH data to REs in the SL SSB, the mapping may be performed in the time domain in one of the following orders:

[0382] ◆OFDM symbol 0, OFDM symbol 1, OFDM symbol 2.

[0383] ◆OFDM symbol 0, OFDM symbol 1, OFDM symbol 3.

[0384] ◆OFDM symbol 0, OFDM symbol 2, OFDM symbol 1.

[0385] ◆OFDM symbol 0, OFDM symbol 2, OFDM symbol 3.

[0386] ◆OFDM symbol 0, OFDM symbol 3, OFDM symbol 1.

[0387] ◆OFDM symbol 0, OFDM symbol 3, OFDM symbol 2.

[0388] ◆OFDM symbol 1, OFDM symbol 0, OFDM symbol 2.

[0389] ◆OFDM symbol 1, OFDM symbol 0, OFDM symbol 3.

[0390] ◆OFDM symbol 1, OFDM symbol 2, OFDM symbol 0.

[0391] ◆OFDM symbol 1, OFDM symbol 2, OFDM symbol 3.

[0392] ◆OFDM symbol 1, OFDM symbol 3, OFDM symbol 0.

[0393] ◆OFDM symbol 1, OFDM symbol 3, OFDM symbol 2.

[0394] ◆OFDM symbol 2, OFDM symbol 0, OFDM symbol 1.

[0395] ◆OFDM symbol 2, OFDM symbol 0, OFDM symbol 3.

[0396] ◆OFDM symbol 2, OFDM symbol 1, OFDM symbol 0.

[0397] ◆OFDM symbol 2, OFDM symbol 1, OFDM symbol 3.

[0398] ◆OFDM symbol 2, OFDM symbol 3, OFDM symbol 0.

[0399] ◆OFDM symbol 2, OFDM symbol 3, OFDM symbol 1.

[0400] ◆OFDM symbol 3, OFDM symbol 0, OFDM symbol 1.

[0401] ◆OFDM symbol 3, OFDM symbol 0, OFDM symbol 2.

[0402] ◆OFDM symbol 3, OFDM symbol 1, OFDM symbol 0.

[0403] ◆OFDM symbol 3, OFDM symbol 1, OFDM symbol 2.

[0404] ◆OFDM symbol 3, OFDM symbol 2, OFDM symbol 0.

[0405] ◆OFDM symbol 3, OFDM symbol 2, OFDM symbol 1.

[0406] ● Optionally, the time domain and frequency domain resources in the SL SSB occupied by the DM-RS for the PSBCH may be one of the following:

[0407] ◆The subcarrier set {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v} in OFDM symbol 1, the subcarrier set {0+v, 4+v, 8+v,..., 236+v} in OFDM symbol 2, and the subcarrier set {0+v, 4+v, 8+v,..., 236+v} in OFDM symbol 3.

[0408] ◆The subcarrier set in OFDM symbol 1 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 2 is {0+v, 4+v, 8+v,..., 236+v}, and the subcarrier set in OFDM symbol 3 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}.

[0409] ◆The subcarrier set in OFDM symbol 1 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 2 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}, and the subcarrier set in OFDM symbol 3 is {0+v, 4+v, 8+v,..., 236+v}.

[0410] ◆The subcarrier set {0+v, 4+v, 8+v, ..., 44+v} and the subcarrier set {192+v, 196+v, ..., 236+v} in OFDM symbol 0, the subcarrier set {0+v, 4+v, 8+v, ..., 236+v} in OFDM symbol 1, and the subcarrier set {0+v, 4+v, 8+v, ..., 236+v} in OFDM symbol 2.

[0411] ◆The subcarrier set in OFDM symbol 0 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 1 is {0+v, 4+v, 8+v,..., 236+v}, and the subcarrier set in OFDM symbol 2 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}.

[0412] ◆The subcarrier set in OFDM symbol 0 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 1 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}, and the subcarrier set in OFDM symbol 2 is {0+v, 4+v, 8+v,..., 236+v}.

[0413] ◆The subcarrier set {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v} in OFDM symbol 0, the subcarrier set {0+v, 4+v, 8+v,..., 236+v} in OFDM symbol 1, and the subcarrier set {0+v, 4+v, 8+v,..., 236+v} in OFDM symbol 3.

[0414] ◆The subcarrier set in OFDM symbol 0 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 1 is {0+v, 4+v, 8+v,..., 236+v}, and the subcarrier set in OFDM symbol 3 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}.

[0415] ◆The subcarrier set in OFDM symbol 0 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 1 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}, and the subcarrier set in OFDM symbol 3 is {0+v, 4+v, 8+v,..., 236+v}.

[0416] ◆The subcarrier set {0+v, 4+v, 8+v, ..., 44+v} and the subcarrier set {192+v, 196+v, ..., 236+v} in OFDM symbol 0, the subcarrier set {0+v, 4+v, 8+v, ..., 236+v} in OFDM symbol 2, and the subcarrier set {0+v, 4+v, 8+v, ..., 236+v} in OFDM symbol 3.

[0417] ◆The subcarrier set in OFDM symbol 0 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 2 is {0+v, 4+v, 8+v,..., 236+v}, and the subcarrier set in OFDM symbol 3 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}.

[0418] ◆The subcarrier set in OFDM symbol 0 is {0+v, 4+v, 8+v,..., 236+v}, the subcarrier set in OFDM symbol 2 is {0+v, 4+v, 8+v,..., 44+v} and the subcarrier set {192+v, 196+v,..., 236+v}, and the subcarrier set in OFDM symbol 3 is {0+v, 4+v, 8+v,..., 236+v}.

[0419] Where v is an integer constant. For example, v can be equal to mod 4.

[0420] ● Optionally, when mapping the DM-RS for the PSBCH to the RE in the SL SSB, the mapping may be performed in one of the following orders in the time domain:

[0421] ◆OFDM symbol 0, OFDM symbol 1, OFDM symbol 2.

[0422] ◆OFDM symbol 0, OFDM symbol 1, OFDM symbol 3.

[0423] ◆OFDM symbol 0, OFDM symbol 2, OFDM symbol 1.

[0424] ◆OFDM symbol 0, OFDM symbol 2, OFDM symbol 3.

[0425] ◆OFDM symbol 0, OFDM symbol 3, OFDM symbol 1.

[0426] ◆OFDM symbol 0, OFDM symbol 3, OFDM symbol 2.

[0427] ◆OFDM symbol 1, OFDM symbol 0, OFDM symbol 2.

[0428] ◆OFDM symbol 1, OFDM symbol 0, OFDM symbol 3.

[0429] ◆OFDM symbol 1, OFDM symbol 2, OFDM symbol 0.

[0430] ◆OFDM symbol 1, OFDM symbol 2, OFDM symbol 3.

[0431] ◆OFDM symbol 1, OFDM symbol 3, OFDM symbol 0.

[0432] ◆OFDM symbol 1, OFDM symbol 3, OFDM symbol 2.

[0433] ◆OFDM symbol 2, OFDM symbol 0, OFDM symbol 1.

[0434] ◆OFDM symbol 2, OFDM symbol 0, OFDM symbol 3.

[0435] ◆OFDM symbol 2, OFDM symbol 1, OFDM symbol 0.

[0436] ◆OFDM symbol 2, OFDM symbol 1, OFDM symbol 3.

[0437] ◆OFDM symbol 2, OFDM symbol 3, OFDM symbol 0.

[0438] ◆OFDM symbol 2, OFDM symbol 3, OFDM symbol 1.

[0439] ◆OFDM symbol 3, OFDM symbol 0, OFDM symbol 1.

[0440] ◆OFDM symbol 3, OFDM symbol 0, OFDM symbol 2.

[0441] ◆OFDM symbol 3, OFDM symbol 1, OFDM symbol 0.

[0442] ◆OFDM symbol 3, OFDM symbol 1, OFDM symbol 2.

[0443] ◆OFDM symbol 3, OFDM symbol 2, OFDM symbol 0.

[0444] ◆OFDM symbol 3, OFDM symbol 2, OFDM symbol 1.

[0445] ●Optionally, the SL PSS sequence may be defined as one of the following:

[0446] ◆d PSS (n) = 1-2x(m)

[0447] ◆d PSS (n) = 2x(m) - 1

[0448] in,

[0449] ○

[0450] ○0≤n<127

[0451] ○P is a constant. P can be one of 17, 18, 19, 20, 21, 22, 23, 24, and 25.

[0452] ○x(i+7)=(x(i+4)+x(i))mod 2

[0453] ○[x(6) x(5) x(4) x(3) x(2) x(1) x(0)]=[1 1 1 0 1 1 0]

[0454] ●Optionally, the SL SSS sequence may be defined as one of the following:

[0455] ◆d sSS (n)=[1-2x0((n+m0)mod 127)][1-2x1((n+m1)mod 127)]

[0456] ◆d SSS (n)=[2x0((n+m0)mod 127)-1][1-2x1((n+m1)mod 127)]

[0457] ◆d SSS (n)=[1-2x0((n+m0)mod 127)][2x1((n+m1)mod 127)-1]

[0458] ◆d SSS (n)=[2x0((n+m0)mod 127)-1][2x1((n+m ( )mod 127)-1]

[0459] in,

[0460] ○

[0461] ○

[0462] ○0≤n<127

[0463] ○Q is a constant. Q can be one of 45, 50, 55, 60, 65, and 70.

[0464] ○x0(i+7)=(x0(i+4)+x0(i))mod 2

[0465] ○x1(i+7)=(x1(i+1)+x1(i))mod 2

[0466] ○[x0(6) x0(5) x0(4) x0(3) x0(2) x0(1) x0(0)]=[0 0 0 0 0 0 1]

[0467] ○[x1(6) x1(5) x1(4) x1(3) x1(2) x1(1) x1(0)]=[0 0 0 0 0 0 1]

[0468] ● Optionally, the time domain and frequency domain resources in the SL SSB occupied by the SL PSS may be one or two subcarrier sets in the OFDM symbol s. Wherein, s may be 0, 1, 2, or 3, and the one or two subcarrier sets may be one of the following:

[0469] ◆{0, 1, ..., 126}

[0470] ◆{1, 2, ..., 127}

[0471] ◆{2, 3, ..., 128}

[0472] ◆{3, 4, ..., 129}

[0473] ◆{4, 5, ..., 130}

[0474] ◆{5, 6, ..., 131}

[0475] ◆{6, 7, ..., 132}

[0476] ◆{7, 8, ..., 133}

[0477] ◆{8, 9, ..., 134}

[0478] ◆{9, 10, ..., 135}

[0479] ◆{10, 11, ..., 136}

[0480] ◆{11, 12, ..., 137}

[0481] ◆{12, 13, ..., 138}

[0482] ◆{13, 14, ..., 139}

[0483] ◆{14, 15, ..., 140}

[0484] ◆{15, 16, ..., 141}

[0485] ◆{16, 17, ..., 142}

[0486] ◆{17, 18, ..., 143}

[0487] ◆{18, 19, ..., 144}

[0488] ◆{19，20，...，145}

[0489] ◆{20，21，...，146}

[0490] ◆{21，22，...，147}

[0491] ◆{22，23，...，148}

[0492] ◆{23，24，...，149}

[0493] ◆{24，25，...，150}

[0494] ◆{25，26，...，151}

[0495] ◆{26，27，...，152}

[0496] ◆{27，28，...，153}

[0497] ◆{28，29，...，154}

[0498] ◆{29，30，...，155}

[0499] ◆{30，31，...，156}

[0500] ◆{31，32，...，157}

[0501] ◆{32，33，...，158}

[0502] ◆{33，34，...，159}

[0503] ◆{34，35，...，160}

[0504] ◆{35，36，...，161}

[0505] ◆{36，37，...，162}

[0506] ◆{37，38，...，163}

[0507] ◆{38，39，...，164}

[0508] ◆{39，40，...，165}

[0509] ◆{40，41，...，166}

[0510] ◆{41，42，...，167}

[0511] ◆{42，43，...，168}

[0512] ◆{43，44，...，169}

[0513] ◆{44，45，...，170}

[0514] ◆{45，46，...，171}

[0515] ◆{46，47，...，172}

[0516] ◆{47，48，...，173}

[0517] ◆{48，49，...，174}

[0518] ◆{49，50，...，175}

[0519] ◆{50，51，...，176}

[0520] ◆{51，52，...，177}

[0521] ◆{52，53，...，178}

[0522] ◆{53，54，...，179}

[0523] ◆{54，55，...，180}

[0524] ◆{55，56，...，181}

[0525] ◆{56，57，...，182}

[0526] ◆{57，58，...，183}

[0527] ◆{58，59，...，184}

[0528] ◆{59，60，...，185}

[0529] ◆{60，61，...，186}

[0530] ◆{61，62，...，187}

[0531] ◆{62，63，...，188}

[0532] ◆{63，64，...，189}

[0533] ◆{64，65，...，190}

[0534] ◆{65，66，...，191}

[0535] ◆{66，67，...，192}

[0536] ◆{67，68，...，193}

[0537] ◆{68，69，...，194}

[0538] ◆{69，70，...，195}

[0539] ◆{70，71，...，196}

[0540] ◆{71，72，...，197}

[0541] ◆{72，73，...，198}

[0542] ◆{73，74，...，199}

[0543] ◆{74，75，...，200}

[0544] ◆{75，76，...，201}

[0545] ◆{76，77，...，202}

[0546] ◆{77，78，...，203}

[0547] ◆{78，79，...，204}

[0548] ◆{79，80，...，205}

[0549] ◆{80，81，...，206}

[0550] ◆{81，82，...，207}

[0551] ◆{82，83，...，208}

[0552] ◆{83，84，...，209}

[0553] ◆{84，85，...，210}

[0554] ◆{85，86，...，211}

[0555] ◆{86，87，...，212}

[0556] ◆{87，88，...，213}

[0557] ◆{88，89，...，214}

[0558] ◆{89，90，...，215}

[0559] ◆{90，91，...，216}

[0560] ◆{91，92，...，217}

[0561] ◆{92，93，...，218}

[0562] ◆{93，94，...，219}

[0563] ◆{94，95，...，220}

[0564] ◆{95，96，...，221}

[0565] ◆{96，97，...，222}

[0566] ◆{97，98，...，223}

[0567] ◆{98，99，...，224}

[0568] ◆{99，100，...，225}

[0569] ◆{100，101，...，226}

[0570] ◆{101，102，...，227}

[0571] ◆{102，103，...，228}

[0572] ◆{103，104，...，229}

[0573] ◆{104，105，...，230}

[0574] ◆{105，106，...，231}

[0575] ◆{106，107，...，232}

[0576] ◆{107，108，...，233}

[0577] ◆{108，109，...，234}

[0578] ◆{109，110，...，235}

[0579] ◆{110，111，...，236}

[0580] ◆{111，112，...，237}

[0581] ◆{112，113，...，238}

[0582] ◆{113，114，...，239}

[0583] ◆{55}，{183，184，...，308}

[0584] ◆{54，55}，{183，184，...，307}

[0585] ◆{53，54，55}，{183，184，...，306}

[0586] ◆{52，53，...，55}，{183，184，...，305}

[0587] ◆{51，52，...，55}，{183，184，...，304}

[0588] ◆{50，51，...，55}，{183，184，...，303}

[0589] ◆{49，50，...，55}，{183，184，...，302}

[0590] ◆{48，49，...，55}，{183，184，...，301}

[0591] ◆{47，48，...，55}，{183，184，...，300}

[0592] ◆{46，47，...，55}，{183，184，...，299}

[0593] ◆{45，46，...，55}，{183，184，...，298}

[0594] ◆{44，45，...，55}，{183，184，...，297}

[0595] ◆{43，44，...，55}，{183，184，...，296}

[0596] ◆{42，43，...，55}，{183，184，...，295}

[0597] ◆{41，42，...，55}，{183，184，...，294}

[0598] ◆{40，41，...，55}，{183，184，...，293}

[0599] ◆{39，40，...，55}，{183，184，...，292}

[0600] ◆{38，39，...，55}，{183，184，...，291}

[0601] ◆{37，38，...，55}，{183，184，...，290}

[0602] ◆{36，37，...，55}，{183，184，...，289}

[0603] ◆{35，36，...，55}，{183，184，...，288}

[0604] ◆{34，35，...，55}，{183，184，...，287}

[0605] ◆{33，34，...，55}，{183，184，...，286}

[0606] ◆{32，33，...，55}，{183，184，...，285}

[0607] ◆{31，32，...，55}，{183，184，...，284}

[0608] ◆{30，31，...，55}，{183，184，...，283}

[0609] ◆{29，30，...，55}，{183，184，...，282}

[0610] ◆{28，29，...，55}，{183，184，...，281}

[0611] ◆{27，28，...，55}，{183，184，...，280}

[0612] ◆{26，27，...，55}，{183，184，...，279}

[0613] ◆{25，26，...，55}，{183，184，...，278}

[0614] ◆{24，25，...，55}，{183，184，...，277}

[0615] ◆{23，24，...，55}，{183，184，...，276}

[0616] ◆{22，23，...，55}，{183，184，...，275}

[0617] ◆{21，22，...，55}，{183，184，...，274}

[0618] ◆{20，21，...，55}，{183，184，...，273}

[0619] ◆{19，20，...，55}，{183，184，...，272}

[0620] ◆{18，19，...，55}，{183，184，...，271}

[0621] ◆{17，18，...，55}，{183，184，...，270}

[0622] ◆{16，17，...，55}，{183，184，...，269}

[0623] ◆{15，16，...，55}，{183，184，...，268}

[0624] ◆{14，15，...，55}，{183，184，...，267}

[0625] ◆{13，14，...，55}，{183，184，...，266}

[0626] ◆{12，13，...，55}，{183，184，...，265}

[0627] ◆{11，12，...，55}，{183，184，...，264}

[0628] ◆{10，11，...，55}，{183，184，...，263}

[0629] ◆{9，10，...，55}，{183，184，...，262}

[0630] ◆{8，9，...，55}，{183，184，...，261}

[0631] ◆{7，8，...，55}，{183，184，...，260}

[0632] ◆{6，7，...，55}，{183，184，...，259}

[0633] ◆{5, 6, ..., 55}, {183, 184, ..., 258}

[0634] ◆{4, 5, ..., 55}, {183, 184, ..., 257}

[0635] ◆{3, 4, ..., 55}, {183, 184, ..., 256}

[0636] ◆{2, 3, ..., 55}, {183, 184, ..., 255}

[0637] ◆{1,2,...,55},{183,184,...,254}

[0638] ◆{0, 1, ..., 55}, {183, 184, ..., 253}

[0639] ● Optionally, when mapping the SL PSS to the REs in the SL SSB, the mapping may be performed in the frequency domain in descending order of subcarrier numbers. For example, the SL PSS sequence is d PSS (0), d PSS (1), ..., d PSS (126), then when mapping the SL PSS to the RE in the SL SSB (denoted as (k, l) p，μ , where k is the number of the subcarrier, l is the number of the OFDM symbol, p is the number of the antenna port, and μ is the subcarrier spacing configuration), the mapping is performed in the descending order of k. Optionally, the mapping can be performed in the ascending or descending order of l (for the case where the SL PSS occupies only one OFDM symbol, there is no difference between mapping in the ascending order of l and mapping in the descending order of l). For example, if the SL PSS occupies the subcarrier set {57, 58, ..., 183} in OFDM symbol 0, then d PSS (0) is mapped to (l=0, k=183), d PSS (1) Mapping to (l=0, k=182), ..., d PSS (126) is mapped to (l=0, k=57).

[0640] ●Optionally, when mapping the SL PSS to the RE in the SL SSB, mapping may also be performed in the frequency domain in ascending order of subcarrier numbers.

[0641] ● Optionally, the time domain and frequency domain resources occupied by the SL SSS may be one or two subcarrier sets in the OFDM symbol s. Wherein, s may be 0, 1, 2, or 3, and the one or two subcarrier sets may be one of the following:

[0642] ◆{0, 1, ..., 126}

[0643] ◆{1, 2, ..., 127}

[0644] ◆{2, 3, ..., 128}

[0645] ◆{3, 4, ..., 129}

[0646] ◆{4, 5, ..., 130}

[0647] ◆{5, 6, ..., 131}

[0648] ◆{6, 7, ..., 132}

[0649] ◆{7, 8, ..., 133}

[0650] ◆{8, 9, ..., 134}

[0651] ◆{9, 10, ..., 135}

[0652] ◆{10, 11, ..., 136}

[0653] ◆{11, 12, ..., 137}

[0654] ◆{12, 13, ..., 138}

[0655] ◆{13, 14, ..., 139}

[0656] ◆{14, 15, ..., 140}

[0657] ◆{15, 16, ..., 141}

[0658] ◆{16, 17, ..., 142}

[0659] ◆{17, 18, ..., 143}

[0660] ◆{18, 19, ..., 144}

[0661] ◆{19, 20, ..., 145}

[0662] ◆{20, 21, ..., 146}

[0663] ◆{21，22，...，147}

[0664] ◆{22，23，...，148}

[0665] ◆{23，24，...，149}

[0666] ◆{24，25，...，150}

[0667] ◆{25，26，...，151}

[0668] ◆{26，27，...，152}

[0669] ◆{27，28，...，153}

[0670] ◆{28，29，...，154}

[0671] ◆{29，30，...，155}

[0672] ◆{30，31，...，156}

[0673] ◆{31，32，...，157}

[0674] ◆{32，33，...，158}

[0675] ◆{33，34，...，159}

[0676] ◆{34，35，...，160}

[0677] ◆{35，36，...，161}

[0678] ◆{36，37，...，162}

[0679] ◆{37，38，...，163}

[0680] ◆{38，39，...，164}

[0681] ◆{39，40，...，165}

[0682] ◆{40，41，...，166}

[0683] ◆{41，42，...，167}

[0684] ◆{42，43，...，168}

[0685] ◆{43，44，...，169}

[0686] ◆{44，45，...，170}

[0687] ◆{45，46，...，171}

[0688] ◆{46，47，...，172}

[0689] ◆{47，48，...，173}

[0690] ◆{48，49，...，174}

[0691] ◆{49，50，...，175}

[0692] ◆{50，51，...，176}

[0693] ◆{51，52，...，177}

[0694] ◆{52，53，...，178}

[0695] ◆{53，54，...，179}

[0696] ◆{54，55，...，180}

[0697] ◆{55，56，...，181}

[0698] ◆{56，57，...，182}

[0699] ◆{57，58，...，183}

[0700] ◆{58，59，...，184}

[0701] ◆{59，60，...，185}

[0702] ◆{60，61，...，186}

[0703] ◆{61，62，...，187}

[0704] ◆{62，63，...，188}

[0705] ◆{63，64，...，189}

[0706] ◆{64，65，...，190}

[0707] ◆{65，66，...，191}

[0708] ◆{66，67，...，192}

[0709] ◆{67，68，...，193}

[0710] ◆{68，69，...，194}

[0711] ◆{69，70，...，195}

[0712] ◆{70，71，...，196}

[0713] ◆{71，72，...，197}

[0714] ◆{72，73，...，198}

[0715] ◆{73，74，...，199}

[0716] ◆{74，75，...，200}

[0717] ◆{75，76，...，201}

[0718] ◆{76，77，...，202}

[0719] ◆{77，78，...，203}

[0720] ◆{78，79，...，204}

[0721] ◆{79，80，...，205}

[0722] ◆{80，81，...，206}

[0723] ◆{81，82，...，207}

[0724] ◆{82，83，...，208}

[0725] ◆{83，84，...，209}

[0726] ◆{84，85，...，210}

[0727] ◆{85，86，...，211}

[0728] ◆{86，87，...，212}

[0729] ◆{87，88，...，213}

[0730] ◆{88，89，...，214}

[0731] ◆{89，90，...，215}

[0732] ◆{90，91，...，216}

[0733] ◆{91，92，...，217}

[0734] ◆{92，93，...，218}

[0735] ◆{93，94，...，219}

[0736] ◆{94，95，...，220}

[0737] ◆{95，96，...，221}

[0738] ◆{96，97，...，222}

[0739] ◆{97，98，...，223}

[0740] ◆{98，99，...，224}

[0741] ◆{99，100，...，225}

[0742] ◆{100，101，...，226}

[0743] ◆{101，102，...，227}

[0744] ◆{102，103，...，228}

[0745] ◆{103，104，...，229}

[0746] ◆{104，105，...，230}

[0747] ◆{105，106，...，231}

[0748] ◆{106，107，...，232}

[0749] ◆{107，108，...，233}

[0750] ◆{108，109，...，234}

[0751] ◆{109，110，...，235}

[0752] ◆{110，111，...，236}

[0753] ◆{111，112，...，237}

[0754] ◆{112，113，...，238}

[0755] ◆{113，114，...，239}

[0756] ◆{55}，{183，184，...，308}

[0757] ◆{54，55}，{183，184，...，307}

[0758] ◆{53，54，55}，{183，184，...，306}

[0759] ◆{52，53，...，55}，{183，184，...，305}

[0760] ◆{51，52，...，55}，{183，184，...，304}

[0761] ◆{50，51，...，55}，{183，184，...，303}

[0762] ◆{49，50，...，55}，{183，184，...，302}

[0763] ◆{48，49，...，55}，{183，184，...，301}

[0764] ◆{47，48，...，55}，{183，184，...，300}

[0765] ◆{46，47，...，55}，{183，184，...，299}

[0766] ◆{45，46，...，55}，{183，184，...，298}

[0767] ◆{44，45，...，55}，{183，184，...，297}

[0768] ◆{43，44，...，55}，{183，184，...，296}

[0769] ◆{42，43，...，55}，{183，184，...，295}

[0770] ◆{41，42，...，55}，{183，184，...，294}

[0771] ◆{40，41，...，55}，{183，184，...，293}

[0772] ◆{39，40，...，55}，{183，184，...，292}

[0773] ◆{38，39，...，55}，{183，184，...，291}

[0774] ◆{37，38，...，55}，{183，184，...，290}

[0775] ◆{36，37，...，55}，{183，184，...，289}

[0776] ◆{35，36，...，55}，{183，184，...，288}

[0777] ◆{34，35，...，55}，{183，184，...，287}

[0778] ◆{33，34，...，55}，{183，184，...，286}

[0779] ◆{32，33，...，55}，{183，184，...，285}

[0780] ◆{31，32，...，55}，{183，184，...，284}

[0781] ◆{30，31，...，55}，{183，184，...，283}

[0782] ◆{29，30，...，55}，{183，184，...，282}

[0783] ◆{28，29，...，55}，{183，184，...，281}

[0784] ◆{27，28，...，55}，{183，184，...，280}

[0785] ◆{26，27，...，55}，{183，184，...，279}

[0786] ◆{25，26，...，55}，{183，184，...，278}

[0787] ◆{24，25，...，55}，{183，184，...，277}

[0788] ◆{23，24，...，55}，{183，184，...，276}

[0789] ◆{22，23，...，55}，{183，184，...，275}

[0790] ◆{21，22，...，55}，{183，184，...，274}

[0791] ◆{20，21，...，55}，{183，184，...，273}

[0792] ◆{19，20，...，55}，{183，184，...，272}

[0793] ◆{18，19，...，55}，{183，184，...，271}

[0794] ◆{17，18，...，55}，{183，184，...，270}

[0795] ◆{16，17，...，55}，{183，184，...，269}

[0796] ◆{15，16，...，55}，{183，184，...，268}

[0797] ◆{14，15，...，55}，{183，184，...，267}

[0798] ◆{13，14，...，55}，{183，184，...，266}

[0799] ◆{12，13，...，55}，{183，184，...，265}

[0800] ◆{11，12，...，55}，{183，184，...，264}

[0801] ◆{10，11，...，55}，{183，184，...，263}

[0802] ◆{9，10，...，55}，{183，184，...，262}

[0803] ◆{8，9，...，55}，{183，184，...，261}

[0804] ◆{7，8，...，55}，{183，184，...，260}

[0805] ◆{6，7，...，55}，{183，184，...，259}

[0806] ◆{5，6，...，55}，{183，184，...，258}

[0807] ◆{4，5，...，55}，{183，184，...，257}

[0808] ◆{3, 4, ..., 55}, {183, 184, ..., 256}

[0809] ◆{2, 3, ..., 55}, {183, 184, ..., 255}

[0810] ◆{1,2,...,55},{183,184,...,254}

[0811] ◆{0, 1, ..., 55}, {183, 184, ..., 253}

[0812] ● Optionally, when mapping the SL SSS to the RE in the SL SSB, the mapping may be performed in descending order of subcarriers in the frequency domain. For example, the SL SSS sequence is d SSS (0), d SSS (1), ..., d SSS (126), then when mapping the SL SSS to the RE in the SL SSB (denoted as (k, l) p，μ , where k is the number of the subcarrier, l is the number of the OFDM symbol, p is the number of the antenna port, and μ is the subcarrier spacing configuration), the mapping is performed in the order of k decreasing. Optionally, the mapping can be performed in the order of l increasing or decreasing (for the case where the SL SSS occupies only one OFDM symbol, there is no difference between mapping in the order of l increasing and mapping in the order of l decreasing). For example, if the SL SSS occupies the subcarrier set {57, 58, ..., 183} in OFDM symbol 2, then d SSS (0) is mapped to (l=2, k=183), d SSS (1) Mapped to (l=2, k=182), ..., d SSS (126) is mapped to (l=2, k=57).

[0813] ○ Optionally, when mapping the SL SSS to the RE in the SL SSB, mapping can also be performed in the frequency domain in ascending order of subcarrier numbers.

[0814] Thus, according to the second embodiment, the present disclosure provides a method, which avoids the 5G (Rel-15) UE from unnecessarily increasing the cell search and / or system access time due to mistakenly confusing part or all of the SL SSB with part or all of the SSB by improving the resource mapping method of SL PSS and / or SL SSS and / or PSBCH in SL SSB, and / or the design of SL synchronization ID, and / or the design of SL PSS sequence, and / or the design of SL SSS sequence, etc.

[0815] [Example 3]

[0816] Next, combine Figure 4 To illustrate the method executed by the user equipment in the third embodiment of the present disclosure.

[0817] Figure 4 is a flowchart showing a method executed by a user equipment according to the third embodiment of the present disclosure.

[0818] like Figure 4 As shown, in the third embodiment of the present disclosure, the steps performed by the user equipment UE include: step S301 and step S302.

[0819] Specifically, in step S301, configuration information of parameters related to the SL SSB is obtained. For example, the configuration information is obtained from predefined information or preconfigured information, or the configuration information is obtained from a base station (for example, the configuration information is obtained through DCI or MACCE or RRC signaling), or the configuration information is obtained from other UEs, or a default configuration is used when the parameter is not configured.

[0820] in,

[0821] ●The SL SSB may include SL PSS, SL SSS and PSBCH.

[0822] ●The SL SSB may contain 240 consecutive subcarriers in the frequency domain.

[0823] ●The SL SSB may be a SL SSB that may be sent (or a candidate SL SSB), or may be a SL SSB that is actually sent.

[0824] ● The configuration information may include an indication of a reference frequency position. For example, a reference frequency position is indicated by a parameter absoluteFrequencySL-SSB of type ARFCN-ValueNR. The position of the SL SSB in the frequency domain may also be indicated by other means, for example, indicating a reference frequency position and an offset.

[0825] The configuration information may include the SCS used by the SL SSB. For example, a SCS is indicated by a parameter sl-ssbSubcarrierSpacing of type SubcarrierSpacing.

[0826] In addition, in step S302, the position of each subcarrier of the SL SSB in the frequency domain is determined according to the configuration information, wherein the position of the subcarrier in the frequency domain may refer to the position of the center frequency of the subcarrier.

[0827] For example, when determining the position of each subcarrier of the SL SSB in the frequency domain, it is assumed that the reference frequency position corresponds to resource block n in the SL SSB. PRB The position of subcarrier k, where n PRB can be a value in the set {0, 1, ..., 19}, k can be a value in the set {0, 1, ..., 11}, and n PRB = 10 and k = 0 are not used at the same time. For example, if n PRB =0, k=0, the reference frequency position indicated by the parameter absoluteFrequencySL-SSB is 3000000kHz, the SCS indicated by the parameter sl-ssbSubcarrierSpacing is 15kHz, then the position of subcarrier 0 of the SL SSB in the frequency domain is 3000000kHz, the position of subcarrier 1 in the frequency domain is 3000015kHz, the position of subcarrier 2 in the frequency domain is 3000030kHz, ..., the position of subcarrier 239 in the frequency domain is 3003585kHz.

[0828] According to the method in the above-mentioned third embodiment, since the interpretation of the indicated reference frequency position is different from 5G (Rel-15) when determining the position of the subcarrier of the SL SSB in the frequency domain, it is avoided that the 5G (Rel-15) UE unnecessarily increases the cell search and / or system access time due to mistakenly confusing the SLSSB with the SSB.

[0829] [Example 4]

[0830] Next, combine Figure 5 To illustrate the method executed by the user equipment in the fourth embodiment of the present disclosure.

[0831] Figure 5 is a flowchart showing a method executed by a user equipment according to a fourth embodiment of the present disclosure.

[0832] like Figure 5 As shown, in the fourth embodiment of the present disclosure, the steps performed by the user equipment UE include:

[0833] Specifically, in step S401, information related to synchronization is obtained. For example, information related to synchronization is obtained once at time t0, recorded as first synchronization information; and information related to synchronization is obtained again at time t1, recorded as second synchronization information.

[0834] in,

[0835] ●The time t0≤t1.

[0836] The synchronization-related information may be predefined information or preconfigured information stored in the UE, or may be configuration information received by the UE from other entities, such as configuration information obtained from a GNSS system, or configuration information obtained from SSB, SL SSB, SIB, etc. sent by an LTE or 5G base station. The first synchronization information and the second synchronization information may be obtained in the same manner or in a different manner.

[0837] ●The entity sending the SL SSB may be other UEs (such as LTE UE or 5G UE), a 5G base station, an LTE base station, or other entities.

[0838] ●The SL SSB may include SL PSS, SL SSS and PSBCH, wherein the PSBCH may carry SLMIB.

[0839] The configuration information indicated by the SL SSB may include one or more of the following:

[0840] ◆Information related to OFDM symbols, such as OFDM symbol timing, SCS, length, CP type, etc.

[0841] ◆Information related to time slots and / or subframes and / or frames, such as time slot timing, direct time slot number, direct subframe number, direct frame number, etc.

[0842] The SL SSB may also indicate information related to a synchronization reference (or synchronization source), for example, an identifier of the synchronization reference, or a type of entity corresponding to the synchronization reference, or a priority of the entity corresponding to the synchronization reference, and so on.

[0843] in,

[0844] ◆The synchronization-related information may be associated with one or more synchronization references. If the synchronization-related information is associated with multiple synchronization references, the contents of the configuration information indicated by the multiple synchronization references may not be exactly the same. For example, the direct time slot number, direct subframe number, direct frame number, etc. indicated by the SL SSB sent at different times may be different, but they all indicate the same frame structure information, symbol timing, and time slot timing information.

[0845] ◆The synchronization reference may refer to an entity that provides the synchronization-related information.

[0846] ◆The synchronization reference may be a direct synchronization reference or an indirect synchronization reference. For example, if entities B and C obtain the synchronization-related information from entity A, and entity B indicates the synchronization-related information to the UE, but entity C does not indicate the synchronization-related information to the UE, then entity A is a direct synchronization reference for entity B and entity C, entity B is a direct synchronization reference for the UE, entity A is an indirect synchronization reference for the UE, and entity C is neither a direct synchronization reference nor an indirect synchronization reference for the UE.

[0847] ◆ Among the one or more synchronization references associated with the synchronization-related information, there may be a root synchronization reference (root synchronization reference). The root synchronization reference is a direct synchronization reference or an indirect synchronization reference of all other synchronization references.

[0848] ◆The SL SSB may indicate information related to one or more synchronization references associated with the synchronization-related information, such as one or more of the following:

[0849] ○ The type of one or more synchronization references associated with the synchronization-related information. For example, the type of the root synchronization reference associated with the synchronization-related information (such as GNSS).

[0850] o The number of synchronization references associated with the synchronization-related information (including or excluding an entity indicating the synchronization-related information to the UE).

[0851] ○ The coverage status of one or more synchronization references associated with the synchronization-related information. For example, the coverage status may be "in coverage", for example, the RSRP and / or RSRQ and / or other measurement quantities measured on the frequency used for SL communication meet certain conditions (such as the "S criterion" for cell selection). For another example, the coverage status may be "out of coverage", for example, the RSRP and / or RSRQ and / or other measurement quantities measured on the frequency used for SL communication do not meet the corresponding "coverage" conditions.

[0852] In addition, in step S402, it is determined whether to apply and / or send the reference synchronization information according to one or more of the following:

[0853] ●The time t0.

[0854] ●The time t1.

[0855] ●The first synchronization information.

[0856] ●The second synchronization information.

[0857] - Information about the synchronization reference associated with the first synchronization information.

[0858] - Information about the synchronization reference to which the second synchronization information is associated.

[0859] The reference synchronization information may be the first synchronization information or the second synchronization information.

[0860] For example, if one or more of the following conditions are met (in any combination of "and" or "or"), the reference synchronization information is applied and / or the reference synchronization information is sent:

[0861] ● The priority of one or more synchronization references associated with the first synchronization information and the priority of one or more synchronization references associated with the second synchronization information satisfy a certain relationship. For example, the former is higher than the latter; or the former is equal to the latter; or the former is lower than the latter.

[0862] ● The coverage status of one or more synchronization references associated with the first synchronization information and the coverage status of one or more synchronization references associated with the second synchronization information satisfy a certain relationship. For example, the former is "covered" and the latter is "not covered"; or the former is "not covered" and the latter is "covered"; or the former is "not covered" and the latter is "not covered"; or the former is "covered" and the latter is "covered".

[0863] ● The number of synchronization references associated with the first synchronization information and the number of synchronization references associated with the second synchronization information satisfy a certain relationship. For example, the former is greater than the latter; or the former is equal to the latter; or the former is less than the latter.

[0864] ● t1-t0 meets certain conditions. For example, t1-t0≥Δ; or t1-t0>Δ; or t1-t0<Δ; or t1-t0≤Δ. Δ can be a predefined or preconfigured constant, or a parameter configured through high-level signaling.

[0865] Specifically, for example, if the priority of the root synchronization reference associated with the first synchronization information is lower than the priority of the root synchronization reference associated with the second synchronization information, the second synchronization information is applied and / or the second synchronization information is sent; for another example, if the root synchronization reference associated with the first synchronization information is in a "no coverage" state and the root synchronization reference associated with the second synchronization information is in a "coverage" state, the second synchronization information is applied and / or the second synchronization information is sent; for another example, if the number of synchronization references associated with the first synchronization information is greater than the number of synchronization references associated with the second synchronization information, the second synchronization information is applied and / or the second synchronization information is sent.

[0866] Thus, according to the fourth embodiment, the present disclosure provides a method, which enables UEs under various coverage conditions to use the same synchronization information and thus perform SL communication with each other by forwarding the received synchronization information that meets specific conditions (such as the highest priority).

[0867] [Example 5]

[0868] Next, combine Figure 6 To illustrate the method executed by the user equipment in the fifth embodiment of the present disclosure.

[0869] Figure 6 is a flowchart showing a method executed by a user equipment according to a fifth embodiment of the present disclosure.

[0870] like Figure 6 As shown, in the fifth embodiment of the present disclosure, the steps performed by the user equipment UE include:

[0871] Specifically, in step S501, configuration information of parameters related to scrambling of the SL channel (such as whether the parameters have been configured, or the configured values ​​of the parameters) is obtained. For example, the configuration information is obtained from predefined information or preconfigured information, or the configuration information is obtained from a base station (for example, the configuration information is obtained through DCI or MAC CE or RRC signaling), or the configuration information is obtained from other UEs, or when the parameter is not configured, a default value is used.

[0872] in,

[0873] ●The SL channel may be a channel related to SL synchronization, a channel related to SL communication, or other channels transmitted on the SL carrier. Specifically, the channel may be PSBCH, PSCCH, PSSCH, or PSFCH.

[0874] The parameters may include one or more of the following:

[0875] ◆SL Sync ID (recorded as ). The value range of can be the same as that in the second embodiment, or can be other value ranges.

[0876] ◆The first scrambling code ID (denoted as n ID，1 ). ID，1 The value set of can be {0, 1, ..., 65535}, or a subset of {0, 1, ..., 65535}. Optionally, n ID，1 It can be an identifier related to one or more transmissions of the SL channel, such as an RNTI assigned to the UE, or the ID of the UE, or the ID of the target UE, or the ID of the target UE group, or the SL synchronization ID. ID，1 It can also be equal to the SL synchronization ID.

[0877] ◆The second scrambling code ID (denoted as n ID，2 ). ID，2 The value set of can be {0, 1, ..., 65535}, or a subset of {0, 1, ..., 65535} (e.g., {0, 1, ..., 1023}, or {1024, 1025, ..., 2047}, or {2048, 2049, ..., 4095}, or {4096, 4097, ..., 6143}, or other subsets). Optionally, n ID，2 It may be an identifier related to one or more transmissions of the SL channel, such as an RNTI assigned to the UE, or the ID of the UE, or the ID of the target UE, or the ID of the target UE group. ID，2 It can also be equal to the SL synchronization ID.

[0878] ◆The first offset constant (denoted as M1): M1 may be a predefined constant in the set {0, 1, ..., 65535} (for example, M1=1008. For another example, M1=1024).

[0879] ◆The second offset constant (denoted as M2): M2 can be a predefined constant in the set {0, 1, ..., 65535} (for example, M2 = 1024. For another example, M2 = 1008).

[0880] In addition, in step S502, a scrambling sequence of the SL channel is determined according to the configuration information.

[0881] in,

[0882] ●The scrambling sequence can be a pseudo-random sequence.

[0883] For example, the pseudo-random sequence c(n) may be defined as follows:

[0884] c(n)=(x1(n+N C )+x2(n+N c ))mod 2

[0885] x1(n+31)=(x1(n+3)+x1(n))mod 2

[0886] x2(n+31)=(x2(n+3)+x2(n+2)+x2(n+1)+x2(n))mod 2

[0887] in,

[0888] ◆N C =1600.

[0889] ◆x1(n) is initialized to x1(0)=1, x1(n)=0, n=1, 2, ..., 30.

[0890] x2(n) is initialized to Among them, c init The value can be one of the following:

[0891] ○

[0892] ○

[0893] ○c init =n ID，1 2 15 +n ID，2 .

[0894] ○c init =n ID，1 2 15 +n ID，2 +M2.

[0895] Thus, according to Embodiment 5, the present disclosure provides a method for at least partially avoiding the conflict between the scrambling sequence of the SL channel and the scrambling sequence of 5G (Rel-15) related channels (such as PBCH, PUSCH, PUCCH, etc.) when initializing the scrambling sequence of the SL channel, thereby greatly reducing the possible mutual interference between the SL channel and the 5G (Rel-15) related channels.

[0896] [Modifications]

[0897] Next, use Figure 7 A user equipment as a variation example that can execute the method executed by the user equipment described in detail above in the present disclosure is described.

[0898] Figure 7 is a block diagram showing a user equipment UE involved in the present disclosure.

[0899] like Figure 7 As shown, the user equipment UE80 includes a processor 801 and a memory 802. The processor 801 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 802 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories, etc. The memory 802 stores program instructions. When the instructions are executed by the processor 801, the above method performed by the user equipment described in detail in the present disclosure may be executed.

[0900] The method of the present invention and the equipment involved have been described above in conjunction with the preferred embodiments. Those skilled in the art will appreciate that the method shown above is merely exemplary, and the embodiments described above can be combined with each other without contradiction. The method of the present invention is not limited to the steps and sequence shown above. The network node and user equipment shown above may include more modules, for example, modules that can be developed or developed in the future and can be used for base stations, MMEs, or UEs, etc. The various identifiers shown above are merely exemplary and not restrictive, and the present invention is not limited to specific information elements that serve as examples of these identifiers. Those skilled in the art may make many changes and modifications based on the teachings of the illustrated embodiments.

[0901] It should be understood that the above embodiments of the present disclosure can be implemented by software, hardware, or a combination of software and hardware. For example, the various components inside the base station and user equipment in the above embodiments can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and the like.

[0902] In this application, "base station" may refer to a mobile communication data and control exchange center with a large transmission power and a wide coverage area, including functions such as resource allocation scheduling, data reception and transmission, etc. "User equipment" may refer to a user mobile terminal, such as a mobile phone, a notebook, etc., which can communicate wirelessly with a base station or a micro base station.

[0903] In addition, the embodiments of the present disclosure disclosed herein can be implemented on a computer program product. More specifically, the computer program product is a product as follows: having a computer-readable medium, a computer program logic is encoded on the computer-readable medium, and when executed on a computing device, the computer program logic provides relevant operations to implement the above-mentioned technical solutions of the present disclosure. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present disclosure. This arrangement of the present disclosure is typically provided as software, code and / or other data structures arranged or encoded on a computer-readable medium such as an optical medium (e.g., CD-ROM), a floppy disk or a hard disk, or other media such as firmware or microcode on one or more ROM or RAM or PROM chips, or downloadable software images in one or more modules, shared databases, etc. Software or firmware or such a configuration can be installed on a computing device so that one or more processors in the computing device execute the technical solutions described in the embodiments of the present disclosure.

[0904] In addition, each functional module or each feature of the base station equipment and terminal equipment used in each of the above embodiments can be implemented or executed by a circuit, and the circuit is generally one or more integrated circuits. The circuit designed to perform the various functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC) or a general-purpose integrated circuit, a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, or a discrete hardware component, or any combination of the above devices. The general-purpose processor may be a microprocessor, or the processor may be an existing processor, a controller, a microcontroller or a state machine. The above-mentioned general-purpose processor or each circuit may be configured by a digital circuit, or may be configured by a logic circuit. In addition, when, due to the progress of semiconductor technology, an advanced technology that can replace the current integrated circuit appears, the present disclosure may also use the integrated circuit obtained by using the advanced technology.

[0905] Although the present disclosure has been illustrated above in conjunction with the preferred embodiments of the present disclosure, it will be understood by those skilled in the art that various modifications, substitutions and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure. Therefore, the present disclosure should not be limited by the above embodiments, but by the attached claims and their equivalents.

Claims

1. A user equipment, comprising: processor; as well as a memory in electronic communication with the processor, The instructions stored in the memory are executable to: A random access response including a timing advance command is received in uplink time slot n, wherein the timing advance command indicates an index value in the form of a 12-bit timing advance command field. , the timing advance command corresponds to a timing advance group TAG, and the TAG is one of a plurality of TAGs; Based on the timing advance value , adjust the uplink transmission timing with subcarrier spacing SCS in the TAG, the timing advance value Based on i) the index value and ii) SCS configuration of the SCS To determine, the SCS is the SCS of the first uplink transmission after the UE receives the random access response; as well as Determine a value for a minimum SCS, the minimum SCS being the minimum SCS of the SCSs of all uplink bandwidth fragments BWP and all configured initial uplink BWPs configured in all uplink carriers in the TAG, wherein each configured initial uplink BWP is provided by a high-layer parameter initialuplinkBWP, and the initial uplink BWP of all configurations is the initial uplink BWP configured for all uplink carriers configured for the user equipment, and the initial uplink BWP of all configurations is different from the initial uplink BWP configured for all uplink carriers configured in the TAG, wherein, The determined value is a value in milliseconds corresponding to the maximum timing advance value for the minimum SCS that can be provided by the 12-bit timing advance command field, The adjustment to the uplink transmission timing is applied from the start of uplink timeslot n+k+1, and k is calculated by the following formula: ,in, N represents the determined value in milliseconds, N T,1 Indicates the PDSCH processing time corresponding to PDSCH processing capability 1. N T,2 Indicates the PUSCH preparation time corresponding to PUSCH timing capability 1, represents the number of time slots in each subframe of the minimum SCS in the SCS of all configured uplink BWPs for all uplink carriers in the TAG, and T sf Represents 1 millisecond.

2. A method performed by a user equipment, comprising: A random access response is received in an uplink time slot n, the random access response including a timing advance command, the timing advance command indicating an index value in the form of a 12-bit timing advance command field , the timing advance command corresponds to a timing advance group TAG, and the TAG is one of a plurality of TAGs; Based on the timing advance value , adjust the uplink transmission timing with subcarrier spacing SCS in the TAG, the timing advance value Based on i) the index value and ii) SCS configuration of the SCS To determine, the SCS is the SCS of the first uplink transmission after the UE receives the random access response; as well as Determine a value for a minimum SCS, the minimum SCS being the minimum SCS of the SCSs of all uplink bandwidth fragments BWP and all configured initial uplink BWPs configured in all uplink carriers in the TAG, wherein each configured initial uplink BWP is provided by a high-layer parameter initialuplinkBWP, and the initial uplink BWP of all configurations is the initial uplink BWP configured for all uplink carriers configured for the user equipment, and the initial uplink BWP of all configurations is different from the initial uplink BWP configured for all uplink carriers configured in the TAG, wherein, The determined value is a value in milliseconds corresponding to the maximum timing advance value for the minimum SCS that can be provided by the 12-bit timing advance command field, The adjustment to the uplink transmission timing is applied from the start of uplink timeslot n+k+1, and k is calculated by the following formula: ,in, N represents the determined value in milliseconds, N T,1 Indicates the PDSCH processing time corresponding to PDSCH processing capability 1. N T,2 Indicates the PUSCH preparation time corresponding to PUSCH timing capability 1, represents the number of time slots in each subframe of the minimum SCS in the SCS of all configured uplink BWPs for all uplink carriers in the TAG, and T sf Represents 1 millisecond.

Images