RU2796259C2 - User equipment method and user equipment - Google Patents

Abstract

FIELD: wireless communication technology.

SUBSTANCE: invention relates to the method performed by the user equipment and the corresponding user equipment. A user equipment communication method is proposed, which includes receiving an advance command in an interval n and determining when to apply an uplink transmission time adjustment in accordance with an interval n in which the advance command is received and/or other information related to the uplink transmission time adjustment.

EFFECT: providing the possibility of timely adjustment of the transmission time on the uplink, so that the error of the transmission time on the uplink for the UE always remains within the proper range.

4 cl, 7 dwg, 2 tbl

Description

Technical field

The present description relates to the field of wireless communication technology, and more specifically to the method performed by the user equipment, and the corresponding user equipment.

Prerequisites for the creation of the invention

In March 2016, RAN Plenary No. 71 of the 3rd Generation Systems Partnership Project (3GPP) approved a new research project on 5G technology standards (see Non-Patent Document 1). The goal of the research project is to develop a new radio access technology (NR) that meets all application scenarios, requirements and needs of the 5G network deployment environment. NR has three application scenarios: Evolved Mobile Broadband (eMBB), Machine Type Mass Communication (mMTC) and Ultra Reliable Low Latency Communication (URLLC). In June 2017, the 3rd Generation Systems Partnership Project (3GPP) RAN Plenary Meeting No. 75 approved the related NR 5G Technology Working Draft (see Non-Patent Document 2).

The signal supported by 5G in the downlink direction is CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing), and the signals supported in the uplink direction include CP-OFDM and DFT-s-OFDM ( orthogonal frequency division multiplexing with discrete Fourier transform extension). Each signal supports multiple combinations of subcarrier spacing (SCS) and cyclic prefix (CP) length values. Sometimes a given SCS value, or a combination of SCS value and CP length, is referred to as a "numerical value". The numerical values supported by 5G are shown in Table 1, which defines two types of CP - "normal" and "extended". Each SCS value (denoted as Δ f and expressed in kHz) corresponds to an "SCS configuration" (denoted as μ).

Table 1. Numerical values supported by 5G

µ ∆ f ＝ 2 ^µ 15[kHz] Cyclic prefix 0 15 Normal 1 thirty Normal 2 60 normal, extended 3 120 Normal 4 240 Normal

The basic unit time interval 5G is T _c =1/(Δ f _max · N _f ) seconds, where Δ f _max =480·10 ³ Hz, and N _f =4096. Constant κ = T _s /T _c =64, where T _s is the basic unit time interval in LTE, T _s =1/(Δ f _ref N _{f , ref} ) seconds, Δ f _ref = 15 10 ³ Hz, N _{f , ref} =2048.

интервалов (число интервалов в подкадре составляет

), а каждый интервал содержит

символов OFDM. В таблице 2 показаны значения

и

при различных конфигурациях SCS. Очевидно, что число символов OFDM в каждом подкадре составляет

. Кроме того, каждый кадр дополнительно разделяют на два полукадра одного размера, причем первая половина кадра (полукадр 0) содержит подкадры 0-4, а вторая половина кадра (полукадр 1) содержит подкадры 5-9.In the time domain, the length of a 5G radio frame (or system frame, sometimes simply called a "frame", with a frame number ranging from 0 to 1023) is 10 milliseconds. Each frame contains 10 subframes with a duration of 1 millisecond (the number of subframes per frame is in the range 0-9), each subframe includes

slots (the number of slots in a subframe is

), and each interval contains

OFDM symbols. Table 2 shows the values

And

with different SCS configurations. Obviously, the number of OFDM symbols in each subframe is

. In addition, each frame is further divided into two half-frames of the same size, with the first half of the frame (half-frame 0) containing subframes 0-4, and the second half of the frame (half-frame 1) containing subframes 5-9.

Table 2. Time domain parameters associated with the μ SCS configuration

µ

0 14 1 1 14 2 2 14 4 3 14 8 4 14 16

In 5G, from the point of view of the UE in the serving cell, an uplink frame i for transmission must precede the corresponding downlink frame i by ( N _TA + N _{TA , offset} ) · T _s seconds. See FIG. 1, where N _TA is the advance value (also known as the time adjustment value or timing value), and N _{TA , offset} is the advance offset.

The value of N _TA can be determined and/or adjusted with a signaling command of a higher layer (eg, a protocol layer located above the physical layer), for example, determined and/or adjusted with an advance command and/or a time adjustment indication. The value of N _{TA, offset} may be configured with the higher level parameter n-TimingAdvanceOffset , or a default value may be used. If two uplink carriers are configured in the serving cell, the two uplink carriers use the same value of N _{TA , offset} . The mechanism for determining and/or adjusting the N _TA value may be referred to as "transmission time adjustment". One reason for performing transmission timing adjustment is to reduce uplink interference by substantially equalizing the uplink slot boundaries for incoming base station signals transmitted by other UEs.

In Carrier Aggregation (CA) and/or Dual Connectivity (DC) scenarios, the UE may need to transmit signaling and/or data on multiple uplink carriers. In this case, different uplink carriers may be deployed in different geographic locations and therefore different advance values are required. For this reason, 5G defines the concept of a TAG (Timing Advanced Group, also known as a Time Alignment Group): a group of serving cells (configured with uplink) belonging to the same TAG , uses the same timing reference cell and the same advance value (eg, the advance value specified by the same advance instruction).

If a particular TAG includes a SpCell, that TAG is called a PTAG (Primary Timing Advance Group); otherwise, such a TAG is called a STAG (Secondary Timing Advance Group).

In the random access procedure, the response to the random access preamble may be called RAR (Random Access Response). The RAR may contain a lookahead command, for example, an index value (denoted as T _A ) is indicated by a Lookahead Command field whose value range is 0, 1, 2, ..., 3846. The lookahead value indicated by the lookahead command is N _TA = T _A 16·64/2 ^μ , where μ corresponds to the SCS of the first uplink transmission after the UE receives the RAR.

In other cases, the range of T _A values indicated by the lookahead instruction is 0, 1, 2, ..., 63. In this case, the lookahead instruction is used to adjust the current advance value (denoted as N _{TA_old} ) to a new advance value (denoted as N _{TA_new} ). N _{TA_new} = N _{TA_old} + ( T _A - 31) 16 64/2 ^µ ). If the UE has a plurality of active uplink bandwidth portions (BWPs) in the TAG indicated by the lookahead command, µ corresponds to the largest SCS among the plurality of active uplink BWP portions.

восходящей линии связи, гдеIf the UE receives the advance command in uplink slot n , accordingly, uplink transmission time adjustment is applied from the start point of slot n+k+ 1.

uplink, where

N _{T ,1} represents the duration of N ₁ symbols, where N ₁ corresponds to the PDSCH processing time determined by the "UE processing capabilities 1" when the additional DM-RS for the PDSCH is configured.

N _{T ,2} represents the duration of N ₂ symbols, where N ₂ corresponds to the PUSCH preparation time defined by "UE processing capabilities 1".

The SCS used in determining N ₁ and N ₂ is the smallest SCS of the following:

SCS of all uplink BWP portions configured on all uplink carriers configured for the TAG indicated by the lookahead command.

SCS of all relevant downlink BWP parts (eg, all downlink BWP parts configured for downlink carriers corresponding to all uplink carriers).

N _{TA , max} represents the largest advance value that can be provided by the 12-bit lookahead command field.

The SCS used in determining N _{TA , max} , is the smallest SCS of the following:

The SCS of all uplink BWP portions configured for all uplink carriers configured in the TAG indicated by the lookahead command.

The SCS of the initial active uplink BWP (initial active UL BWP or initial UL BWP, eg configured with the initialuplinkBWP higher layer parameter).

представляет собой число интервалов в каждом подкадре.

is the number of slots in each subframe.

, представляет собой наименьший SCS из следующих:SCS used in determining n and

, is the smallest SCS of the following:

The SCS of all uplink BWP portions configured for all uplink carriers configured in the TAG indicated by the lookahead command.

T _sf is the duration of the subframe, i.e. 1 millisecond.

In the existing 3GPP standard specifications over 5G networks, the mechanism relating to transmission time adjustment has at least the following problems.

) единицы N _{TA , max} и 0,5 несовместимы и их прямое сложение приведет к значительной потере точности, вследствие чего корректирование времени передачи UE по восходящей линии связи становится чрезвычайно неточным (например, k соответствует большой задержке, из-за чего UE становится неспособным своевременно выполнять корректирование времени передачи по восходящей линии связи). В другом примере во время произвольного доступа не удается однозначно определять время применения корректирования времени передачи. В другом примере не удается однозначно определить время обработки PDSCH (N _{T ,1}) и время подготовки PUSCH (N _{T ,2}). В другом примере существуют проблемы при определении интервала k и интервала n+k+1 (например, невозможно принять команду опережения в момент времени, соответствующий интервалу k восходящей линии связи в TDD).When the UE, in accordance with the interval n in the received look-ahead command, determines the interval n+k+ 1 to be applied to adjust the uplink transmission time, the method of determining k causes problems. For example, in the formula for calculating k (i.e.

) the units of N _{TA , max} and 0.5 are inconsistent and their direct addition will lead to a significant loss of accuracy, so that the UE's uplink transmission time adjustment becomes extremely inaccurate (for example, k corresponds to a large delay, causing the UE to become unable to timely perform uplink transmission time adjustment). In another example, during random access, it is not possible to uniquely determine when to apply the transmission time adjustment. In another example, the PDSCH processing time ( N _{T ,1} ) and PUSCH preparation time ( N _{T ,2} ) cannot be uniquely determined. In another example, there are problems in determining slot k and slot n+k+ 1 (eg, it is not possible to receive the lookahead command at the time corresponding to uplink slot k in TDD).

In addition, as the 3GPP establishes improved service requirements for V2X ("vehicle - any objects"), the standardization of V2X based on 5G has become on the agenda. V2X communication refers to communication between a vehicle and any object that may affect the vehicle. Typical V2X communications include V2I (vehicle-infrastructure), V2N (vehicle-network), V2V (vehicle-vehicle), V2P (vehicle-pedestrian), etc. June 2018 plenary RAN meeting No. 80 of the 3GPP project approved a new research project (see non-patent document 6, hereinafter briefly referred to as the V2X research project (Issue 16) or V2X phase 3 research project) on the 3GPP V2X NR. In V2X (Release 16), the interface for realizing V2X communication between UE and UE in the physical layer is called PC5, which is also called direct connection (or abbreviated herein as SL) to distinguish it from uplink connection and downlink connection. communication lines. One of the goals of the V2X Research Project (Release 16) is to study a new NR-based SL interface scheme that incorporates new SL synchronization mechanisms.

Signals and channels for SL synchronization in V2X (release 16) include:

PSS SL (Direct Link Primary Timing Signal), also known as S-PSS or PSSS (Direct Link Primary Timing Signal);

SSS SL (Direct Link Secondary Timing), also known as S-SSS or SSSS (Direct Link Secondary Timing); And

PSBCH (Physical Direct Connect Broadcast Channel).

PSS SL, SSS SL and PSBCH are organized into blocks in the Time Frequency Resource Grid called SSB SL blocks (Direct Connected SS/PBCH blocks, Direct Connected Sync/Physical Broadcast Channel blocks) or S-SSB blocks. The transmission bandwidth of the SSB SL blocks is within the BWP SL (part of the direct connection bandwidth) configured for the UE.

In V2X (release 16), potential SL timing engine design issues include at least the following.

The 5G UE (Release 15) may erroneously identify PSS SL as 5G PSS (Release 15), and/or erroneously determine SSS SL as 5G SSS (Release 15), and/or erroneously determine PSBCH as 5G PBCH (Release 15), thereby unnecessarily increasing the cell search time and/or system access time of the 5G UE equipment (Release 15). Thus, it is necessary to be able to clearly distinguish between PSS SL and PSS, and/or between SSS SL and SSS, and/or between PSBCH and PBCH in the signal/channel scheme, and/or resource allocation, and/or resource mapping, and/or in other aspects.

It is also necessary to be able to correctly determine and specify the SL synchronization identifier in the SSB SL.

It is necessary to be able to properly configure SSB SL resources.

It is necessary to be able to properly scramble the SL related physical layer channel.

A UE that can perform SL communication should be able to obtain negotiated timing information (e.g., timing information determined according to the highest priority timing reference information such as OFDM symbol time, intervals, subframes, frame numbers, and etc.).

Prior Art Document

Non-Patent Documents

Non-Patent Document 1: RP-160671, New SID Proposal: Study on New Radio Access Technology

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

Non-Patent Document 3: RP-181429, New SID: Study on NR V2X

Statement of the Invention

In order to solve at least some of the above problems, the present description proposes a method performed by the user equipment and the user equipment, which can improve the method of calculating the moment to apply the uplink transmission time adjustment so that the UE can adjust the uplink transmission time in a timely manner. , while ensuring that the uplink transmission time error for the UE always remains within the proper range.

According to a first aspect of the embodiments of the present disclosure, a method is provided by a user equipment, comprising receiving an advance command in an interval n and determining, according to an interval n , in which the advance command is received and/or other information related to the uplink transmission time correction. link, the point at which the uplink transmission time adjustment is applied.

In the method according to the first aspect of the embodiments of the present description, the timing for applying the uplink transmission time adjustment is any of the following: start of slot n+k+ 1; the start of the first uplink slot, starting from slot n+k+ 1, including slot n+ k+ 1; the beginning of the first downlink slot starting from slot n+k+ 1, including slot n+k+ 1; the beginning of the first variable interval, starting from the interval n+k+ 1, including the interval n+k+ 1; the beginning of the first hybrid interval, starting from the interval n+k+ 1, including the interval n+k+ 1; the start of the first uplink slot starting from slot n+k+ 1 excluding slot n+k+ 1; the start of the first downlink slot from slot n+k+ 1 excluding slot n+k+ 1; the start of the first variable interval, starting at interval n+k+ 1, excluding interval n+k+ 1, and the beginning of the first hybrid interval, starting at interval n+k+ 1, excluding interval n+k+ 1, where k is determined by any one of the following formulas (1)-(12):

- число интервалов в каждом подкадре, N _{T ,1} - время обработки физического совместно применяемого канала для передачи данных по нисходящей линии связи (PDSCH), соответствующее возможностям 1 обработки PDSCH, N _{T ,2} - время подготовки физического совместно применяемого канала для передачи данных по восходящей линии связи (PUSCH), соответствующее возможностям 1 синхронизации PUSCH, N _{TA , max} - наибольшее значение опережения, N - продолжительность, соответствующая наибольшему значению опережения, T _sf - продолжительность одного подкадра и T _c =1/(Δf _max ·N _f ), где Δf _max =480·10³ Гц и N _f =4096.Where

is the number of slots in each subframe, N _{T ,1} is _the physical downlink shared data channel (PDSCH) processing time corresponding to PDSCH processing capabilities 1, N _T uplink (PUSCH) corresponding to PUSCH sync capabilities 1, N _{TA , max} is the largest advance value, N is the duration corresponding to the largest advance value, T _sf is the duration of one subframe, and T _c =1/(Δ f _max ·N _f ), where Δ f _max =480·10 ³ Hz and N _f =4096.

заменяется на

и T _sf заменяется на T _f , где

представляет собой число интервалов в каждом кадре, а T _f представляет собой длительность одного кадра.In the method according to the first aspect of the embodiments of the present description

is replaced by

and T _sf is replaced by T _f , where

is the number of slots in each frame, and T _f is the duration of one frame.

,

и интервала n+k+1, используемый разнос поднесущих (SCS) представляет собой SCS в любом одном из следующих элементов, или наименьший SCS, или наибольший SCS в любом одном из следующих элементов, включая: SCS всех частей BWP восходящей линии связи, сконфигурированных для всех несущих восходящей линии связи, сконфигурированных в группе опережения (TAG); SCS всех соответствующих частей BWP нисходящей линии связи; SCS начальной (-ых) активной (-ых) BWP восходящей линии связи; SCS начальной (-ых) активной (-ых) BWP нисходящей линии связи; SCS первой передачи по восходящей линии связи после приема RAR оборудованием пользователя; и SCS передачи по нисходящей линии связи, включающей команду опережения.In the method in accordance with the first aspect of the embodiments of the present description, when determining any one of the intervals n, N _{T ,1} , N _{T ,2} , N _{TA , max} ,

,

and an interval of n+k+ 1, the subcarrier spacing (SCS) used is the SCS in any one of the following, or the smallest SCS, or the largest SCS in any one of the following, including: the SCS of all uplink BWP portions configured for all uplink carriers configured in the advance group (TAG); SCS of all relevant parts of the downlink BWP; SCS of the initial(s) active BWP(s) of the uplink; SCS of the initial(s) active(s) BWP downlink; SCS of the first uplink transmission after receiving the RAR by the user equipment; and a downlink transmission SCS including the lookahead command.

In the method according to the first aspect of the embodiments of the present description, the BWP in which the first uplink transmission is located is the initial active uplink BWP or active uplink BWP, wherein the initial active uplink BWP and/or active BWP uplink carriers are on the uplink carrier corresponding to the random access preamble or on another uplink carrier.

In the method according to the first aspect of the embodiments of the present description, the SCS used to determine the interval n+k+ 1 is the same as the SCS used to determine the interval n.

In the method according to the first aspect of the embodiments of the present description, in the case where the PDSCH processing time is designated as N ₁ according to the number of symbols,

if N _{T ,1} is expressed in milliseconds, the relationship between N _{T ,1} and N ₁ is any one of the following relationships (13)-(15) or one of the following relationships (13)-(15) in the case of a normal cyclic prefix ( CP) and another of them in case of extended CP,

N _{T ,1} = N ₁ (2048+144) κ 2 ^{- μ} T _c 10 ³ ... (13)

N _{T ,1} = N ₁ (2048+512) κ 2 ^{- µ} T _c 10 ³ … (14)

N _{T ,1} = N ₁ ((2048+144) κ 2 ^{- μ} +16 κ ) T _c 10 ³ ... (15)

if N _{T, 1} is expressed in seconds, the relationship between N _{T, 1} and N ₁ is any one of the following relationships (16)-(18) or one of the following relationships (16)-(18) in the case of normal CP and the other of which in case of extended CP,

N _{T ,1} = N ₁ (2048+144) κ 2 ^{- μ} T _c ... (16)

N _{T ,1} = N ₁ (2048+512) κ 2 ^{- μ} T _c ... (17)

N _{T ,1} = N ₁ ((2048+144) κ 2 ^{- μ} +16 κ ) T _c ... (18).

In the method according to the first aspect of the embodiments of the present invention, in the case where the PUSCH preparation time is indicated as N ₂ according to the number of symbols,

if N _{T ,2} is expressed in milliseconds, the relationship between N _{T ,2} and N ₂ is any of the following relationships (19)-(21) or one of the following relationships (19)-(21) in the case of normal CP and the other of them in case of extended CP,

N _{T ,2} = N ₂ (2048+144) κ 2 ^{- μ} T _c 10 ³ ... (19)

N _{T ,2} = N ₂ (2048+512) κ 2 ^{- μ} T _c 10 ³ ... (20)

N _{T ,2} = N ₂ ((2048+144) κ 2 ^{- μ} +16 κ ) T _c 10 ³ ... (21)

if N _{T ,2} is expressed in seconds, the ratio between N _{T ,2} and N ₂ is any one of the following ratios (22)-(24) or one of the following ratios (22)-(24) in the case of normal CP and the other of which in case of extended CP,

N _{T ,2} = N ₂ (2048+144) κ 2 ^{- µ} T _c … (22)

N _{T ,2} = N ₂ (2048+512) κ 2 ^{- μ} T _c ... (23)

N _{T ,2} = N ₂ ((2048+144) κ 2 ^{- μ} +16 κ ) T _c ... (24).

In the method according to the first aspect of the embodiments of the present disclosure, a normal CP case refers to any one of the following cases, or any combination of a plurality of the following cases combined in an "and" or "or" fashion: any uplink BWP configured for any the uplink carrier configured in the TAG is configured with a normal CP; at least one uplink BWP on each uplink carrier configured in the TAG is configured with a normal CP; all uplink BWP parts configured for all uplink carriers configured in TAG are configured with normal CPs; at least one of all downlink BWP portions configured for downlink carriers corresponding to all uplink carriers configured in TAG is configured with a normal CP; all parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG are configured with normal CPs; at least one of the downlink BWP portions corresponding to all uplink BWP portions configured for all uplink carriers configured in the TAG is configured with a normal CP; and downlink BWPs corresponding to all uplink BWPs configured for all uplink carriers configured in TAG are configured with normal CPs, and the extended CP case refers to any one of the following cases, or any combination of a plurality of the following cases, combined by "and" or "or" principle: any uplink BWP configured for any uplink carrier configured in TAG is configured with extended CP; at least one uplink BWP on each uplink carrier configured in the TAG is configured with an extended CP; all uplink BWP parts configured for all uplink carriers configured in TAG are configured with extended CPs; at least one of all downlink BWP portions configured for downlink carriers corresponding to all uplink carriers configured in TAG is configured with extended CP; all parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG are configured with extended CPs; at least one of the downlink BWP portions corresponding to all uplink BWP portions configured for all uplink carriers configured in the TAG is configured with extended CP; and all parts of the downlink BWP corresponding to all parts of the uplink BWP configured for all uplink carriers configured in the TAG are configured with extended CPs.

According to a second aspect of the embodiments of the present disclosure, there is provided a user equipment including a processor and a memory in which instructions are stored, wherein the instructions, when executed by the processor, perform a method executed by the user equipment in accordance with any one of the elements of the first aspect.

Invention Effect

According to the present description, it is possible to improve the timing calculation method for applying uplink transmission time adjustment so that the UE can correct the uplink transmission time in a timely manner, while ensuring that the uplink transmission time error for the UE always remains within proper range.

Brief description of graphic materials

The above and other features of the present description will be better understood from the following detailed description in conjunction with the accompanying drawings.

FIG. 1 is a diagram illustrating the concept in which an uplink frame is advanced relative to a downlink frame in the current standard 3GPP specifications on 5G.

FIG. 2 is a block diagram of a method performed by a user equipment according to Embodiment 1 of the present invention.

FIG. 3 is a block diagram of a method performed by a user equipment according to Embodiment 2 of the present invention.

FIG. 4 is a block diagram of a method performed by a user equipment according to Embodiment 3 of the present invention.

FIG. 5 is a block diagram of a method performed by a user equipment according to Embodiment 4 of the present invention.

FIG. 6 is a block diagram of a method performed by a user equipment according to Embodiment 5 of the present invention.

FIG. 7 is a block diagram of user equipment related to the present disclosure.

Detailed description

The following is a detailed present description with reference to the accompanying drawings and specific embodiments. It should be noted that the present description is not limited to the specific embodiments described below. In addition, for the sake of simplicity, a detailed description of the prior art not directly related to the present description is omitted in order to avoid confusion in the understanding of the present description.

A plurality of embodiments according to the present description are detailed below using the 5G mobile communication system and its later enhancements as examples of the application environment. However, it should be noted that the present invention is not limited to the following embodiments, and, moreover, it is applicable to many other wireless communication systems such as a communication system later than 5G and a 4G mobile communication system earlier than 5G.

Some terms related to the present description are described below. Unless specifically stated otherwise, terms related to the present description should be understood in accordance with the definitions given in this document. The terms used in the present description may be referred to differently in the communication systems of LTE, LTE-Advanced, LTE-Advanced Pro, NR and communication systems of later versions, but in the present description the unified terminology is used. If used in a particular system, the terms may be replaced by the terms used in the corresponding system.

3GPP: 3rd Generation Partnership Project

BWP: part of the strip width

CA: carrier aggregation

CP: cyclic prefix

CP-OFDM: Orthogonal Frequency Division Multiplexing with cyclic prefix

DC: double connection

DFT-s-OFDM: Orthogonal Frequency Division Multiplexing with Discrete Fourier Transform Extension

DL: downlink

DL-SCH: Downlink Data Shared Channel

DM-RS: demodulation reference signal

eMBB: Enhanced Mobile Broadband

IE: information element

LCID: logical channel ID, logical channel identifier

LTE-A: an advanced standard for the long-term evolution of communication networks

MAC: Media Access Control

MAC CE: MAC control element

MCG: main cell group

mMTC: Machine Type Mass Communication

NR: new radio network

NUL: normal uplink

OFDM: Orthogonal Frequency Division Multiplexing

PBCH: Physical Broadcast Channel

PDSCH: Physical Shared Channel for Downlink Data

PSBCH: Direct Connect Physical Broadcast Channel

PSCCH: Direct Connect Physical Control Channel

PSSCH: Physical Shared Channel for Direct Connect Data

PSS: Primary Synchronization Signal

PSSS: Primary Synchronization Signal on Direct Connection

PTAG: Primary Lead Group

PUSCH: Physical Shared Channel for Uplink Data

RAR: random access response

RB: resource block

RE: resource element

RRC: radio resource control

SCG: secondary cell group

SCS: subcarrier spacing

SFN: frame number in the system

SIB: system information block;

SL: direct connection

BWP SL: part of direct connection bandwidth

PSS SL: Primary Synchronization Signal in direct connection

SSB SL: Direct Connect SS/PBCH Block, Direct Connect Synchronization/Physical Broadcast Channel Block

SSS SL: Secondary Synchronization Signal for Direct Connection

SpCell: special cell

SSB: SS/PBCH block

SSS: Secondary Synchronization Signal

SSSS: Secondary Synchronization Signal on Direct Connection

STAG: secondary advance group

SUL: Supplemental Uplink

TA: advance

TAG: advance group

TDD: Time Division Duplex

UE: user equipment

UL: uplink

URLLC: Ultra Reliable Low Latency Communication

V2I: Vehicle - Infrastructure

V2N: vehicle - network

V2P: vehicle - pedestrian

V2V: vehicle - vehicle

V2X: vehicle - any objects

Unless otherwise noted, in all embodiments and implementations of this disclosure:

T _c =1/(Δ f _max ·N _f ) seconds, where Δ f _max =480 · 10 ³ Hz and N _f =4096.

T _s =1/(Δ f _ref ·N _{f , ref} ) seconds, where Δ f _ref =15 · 10 ³ Hz and N _{f , ref} =2048.

κ = T _s /T _c =64.

представляет собой число интервалов в каждом подкадре.

is the number of slots in each subframe.

представляет собой число интервалов в каждом кадре.

is the number of slots in each frame.

T _sf is the duration of one subframe. T _sf =1 millisecond.

T _f is the duration of one frame. T _f =10 milliseconds.

A downlink interval refers to an interval in which all symbols are downlink symbols.

Variable spacing refers to a span in which all characters are variable characters.

An uplink interval refers to an interval in which all symbols are uplink symbols.

A hybrid slot refers to a slot that contains at least two of the downlink symbols, variable symbols, and uplink symbols.

Resources (eg, resource blocks or subcarriers) occupied by a physical layer channel or signal, or a combination of multiple channels and/or physical layer signals (eg, SSB or SSB SL) in the frequency domain are numbered starting from 0, and resources (eg, symbols, or slots or subframes or frames) occupied in the time domain are also numbered starting from 0. For example, for SSB, the lowest numbered resource block number is 0, and for a resource block, the lowest numbered subcarrier number is 0.

[Embodiment 1]

The method performed by the user equipment according to Embodiment 1 of the present disclosure will be described below with reference to FIG. 2.

FIG. 2 is a block diagram of a method performed by a user equipment according to Embodiment 1 of the present invention.

As shown in FIG. 2, in Embodiment 1 of the present description, steps performed by a user equipment (UE) include step S101 and step S102.

Specifically, in step S101, an advance command is received.

For example, the advance command is received from the base station in the interval n . Wherein:

The lookahead instruction may indicate an index value (denoted as T _A ).

The lookahead command may be included in the RAR, and the RAR may be a response to the random access preamble. For example, the RAR may be a MAC PDU, which may include a MAC subPDU; the MAC subPDU load may include a Lookahead Command field to accommodate the lookahead command. The size of the Lookahead Command field may be 12 bits, and the range of values of the T _A index thus specified may be 0, 1, 2, ..., 3846.

In this case, the TAG corresponding to the lookahead 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 (eg, indicated in the MAC subPDU included in the RAR), or may be a TAG specified in other ways. Embodiment 1 of the present description in this case does not limit the TAG corresponding to the advance command.

The lookahead command can also be included in the MAC CE, referred to as the "Ahead Command". For example, the MAC CE may be identified by the MAC subheader, the MAC subheader may be used for the DL-SCH, and the value of the LCID field in the MAC subheader may be 61. In another example, the MAC CE may include a TAG field and a Lookahead Command field. The TAG field may be 2 bits long to determine the TAG corresponding to the lookahead command; the Lookahead Command field may be 6 bits, and the range of the index value T _A thus specified may be 0, 1, 2, ..., 63.

The lookahead command may also be included in other higher layer messages (such as other MAC messages or RRC messages). Embodiment 1 of the present description does not limit the message containing the lookahead command.

In determining the interval n , the SCS used may be the SCS in any one of the following elements (if there is only one SCS in those elements), or may be the smallest SCS in any one or more of the following elements, or may be the smallest SCS in any one or a set of the following elements:

SCS of all uplink BWP parts configured for all uplink carriers configured in TAG.

SCS of all relevant parts of the downlink BWP (e.g., all parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG, or in another example, parts of the downlink BWP corresponding to all parts uplink BWP configured for all uplink carriers configured in the TAG).

SCS of initial(s) active uplink BWP(s) (initial(s) active BWP(s) UL or referred to(s) as initial(s) uplink BWP(s) BWP UL), such as all configured with the higher-level parameter initialuplinkBWP ).

SCS of initial(s) active downlink BWP(s) (initial(s) active(s) BWP DL or referred to(s) as initial(s) BWP downlink(s) BWP DL), such as all configured with the higher-level parameter initialDownlinkBWP ).

The SCS of the first uplink transmission after receiving the RAR by the UE. The BWP in which the first uplink transmission is located may be the initial active uplink BWP, or may be the active uplink BWP; the initial active uplink BWP and/or the active uplink BWP may be on an uplink carrier corresponding to the random access preamble, or may be on a different uplink carrier.

The SCS of a downlink transmission (eg, PDSCH) containing an advance command.

Once the interval n is defined, the SCS used can also be determined in other ways. Option 1 implementation of the present description does not limit the SCS used in determining the interval n.

The slot type n may not be limited in any way (for example, the slot may be a downlink slot, or may be a variable slot, or may be an uplink slot, or may be a hybrid slot), or may be limited to any one of the downlink slot, variable slot, uplink slot, and hybrid slot, or may be limited to a combination of any two or more of the downlink slot, variable slot, uplink slot, and hybrid slot.

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

For example, according to the interval n in which the advance command is received and other information related to the uplink transmission time adjustment, the time t of applying the uplink transmission time adjustment is determined (for example, starting to apply the uplink transmission time adjustment communication from time t ; in another example, starting to apply uplink transmission time adjustment until time t ; in yet another example, starting to apply uplink transmission time adjustment at time no later than time t ). Time t can be any of the following:

Beginning of interval n+k+ 1.

Start of the first uplink slot, starting from slot n+k+ 1 (including slot n+k+ 1).

Beginning of the first downlink slot, starting from slot n+k+ 1 (including slot n+k+ 1).

Beginning of the first variable interval, starting from interval n+k+ 1 (including interval n+k+ 1).

Beginning of the first hybrid interval, starting from interval n+k+ 1 (including interval n+k+ 1).

Beginning of the first uplink slot, starting from slot n+k+ 1 (excluding slot n+k+ 1).

Start of the first downlink slot, starting from slot n+k+ 1 (excluding slot n+k+ 1).

Beginning of the first variable interval, starting from interval n+k+ 1 (excluding interval n+k+ 1).

Beginning of the first hybrid interval, starting from interval n+k+ 1 (excluding interval n+k+ 1).

Wherein:

k can be defined in any of the following ways:

(a).

(b).

(c).

(d).

(e).

(f).

(g).

(h).

(i).

(j).

(k).

(l).

Wherein:

также можно заменять на

и T _sf можно заменять на T _f .Optional in any of the above equations

can also be replaced with

and T _sf can be replaced by T _f .

N _{T ,1} is the PDSCH processing time corresponding to PDSCH processing capabilities 1.

Wherein:

In some cases where the context is clear, such as when it can be seen from the context that PDSCH processing capabilities are meant, PDSCH processing capabilities 1 can also be understood as processing capabilities 1 for the UE.

PDSCH processing capabilities 1 may be PDSCH processing capabilities 1 if an additional DM-RS PDSCH is configured. For example, the dmrs-AdditionalPosition parameter in DMRS-DownlinkConfig in the higher-level dmrs-DownlinkForPDSCHMappingTypeA parameter is not configured, or the configured value is not " pos0 ", or the dmrs-AdditionalPosition parameter in DMRS-DownlinkConfig in the higher-level dmrs-DownlinkForPDSCH-MappingTypeB parameter is not configured, or the configured value is not " pos0 ".

N _{T, 1} can be expressed in milliseconds or seconds. For example, in formulas (a), (b), (c), (d), (e), (f) and (g) N _{T ,1} can be expressed in milliseconds. In formulas (h), (i), (j), (k) and (l) N _{T ,1} can be expressed in seconds.

The PDSCH processing time may also be represented according to the number of symbols, denoted as N ₁ . For example, N _{T ,1} may be the duration of N ₁ symbols, where N ₁ symbols may be N ₁ consecutive symbols.

Optionally, if N _{T ,1} is in milliseconds, the relationship between N _{T ,1} and N ₁ may be fixed for any of the following (i.e., regardless of how the CP is configured), or in the case of a normal CP, one of the following (for example, the first), and in the case of an extended CP, use another of the following (for example, the second):

N _{T ,1} = N ₁ (2048+144) κ 2 ^{- µ} T _c 10 ³

N _{T ,1} = N ₁ (2048+512) κ 2 ^{- µ} T _c 10 ³

N _{T ,1} = N ₁ ((2048+144) κ 2 ^{- µ} +16 κ ) T _c 10 ³

Optionally, if N _{T ,1} is in seconds, the relationship between N _{T ,1} and N ₁ may be fixed for any of the following (i.e., regardless of how the CP is configured), or in the case of a normal CP, one of the following (for example, the first), and in the case of an extended CP, use another of the following (for example, the second):

N _{T ,1} = N ₁ (2048+144) κ 2 ^{- µ} T _c

N _{T ,1} = N ₁ (2048+512) κ 2 ^{- µ} T _c

N _{T ,1} = N ₁ ((2048+144) κ 2 ^{- µ} +16 κ ) T _c

Optionally, a normal CP case may refer to any one of the following cases, or any combination of a plurality of the following cases combined in an "and" or "or" fashion.

Any uplink BWP configured for any uplink carrier is configured in a TAG with a normal CP.

At least one uplink BWP on each uplink carrier configured in the TAG is configured with a normal CP.

All parts of the uplink BWP configured for all uplink carriers configured in the TAG are configured with normal CPs.

At least one of all downlink BWP portions configured for downlink carriers corresponding to all uplink carriers configured in TAG is configured with a normal CP.

All parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG are configured with normal CPs.

At least one of the downlink BWP portions corresponding to all uplink BWP portions configured for all uplink carriers configured in the TAG is configured with a normal CP.

The parts of the downlink BWP corresponding to all the parts of the uplink BWP configured for all the uplink carriers configured in the TAG are configured with normal CPs.

Optionally, a normal CP case can also refer to any case that is not an "extended CP case" (unless an extended CP case refers to any case that is not a "normal CP case").

Optionally, the extended CP case may refer to any one of the following cases, or any combination of a plurality of the following cases, grouped by "and" or "or".

Any uplink BWP configured for any uplink carrier configured in TAG is configured with extended CP.

At least one uplink BWP on each uplink carrier configured in the TAG is configured with an extended CP.

All parts of the uplink BWP configured for all uplink carriers configured in the TAG are configured with extended CPs.

At least one of all downlink BWP portions configured for downlink carriers corresponding to all uplink carriers configured in TAG is configured with extended CP.

All parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG are configured with extended CPs.

At least one of the parts of the downlink BWP corresponding to all parts of the uplink BWP configured for all the uplink carriers configured in the TAG is configured with an extended CP.

The parts of the downlink BWP corresponding to all the parts of the uplink BWP configured for all the uplink carriers configured in the TAG are configured with extended CPs.

Optionally, the extended CP case can also refer to any case that is not a "normal CP case" (unless the normal CP case refers to any case that is not a "widened CP case").

N _{T ,2} is the PUSCH preparation time corresponding to PUSCH synchronization capabilities 1. Wherein:

In some cases where the context is clear, such as when it can be seen from the context that PUSCH synchronization related capabilities are meant, PUSCH synchronization capabilities 1 can also be understood to mean processing capabilities 1 for the UE.

N _{T ,2} can be expressed in milliseconds or seconds. For example, in formulas (a), (b), (c), (d), (e), (f) and (g) N _{T ,2} can be expressed in milliseconds. In formulas (h), (i), (j), (k) and (l) N _{T ,2} can be expressed in seconds.

The PUSCH preparation time may also be represented according to the number of symbols, denoted as N ₂ . For example, N _{T ,2} may be the duration of N ₂ symbols, where N ₂ symbols may be N ₂ consecutive symbols.

Optionally, if N _{T ,2} is expressed in milliseconds, the relationship between N _{T ,2} and N ₂ may be fixed for any one of the following (i.e., regardless of how the CP is configured), or in the case of a normal CP, one may be used. of the following (for example, the first), and in the case of an extended CP, another of the following (for example, the second) can be used:

N _{T ,2} = N ₂ (2048+144) κ 2 ^{- µ} T _c 10 ³

N _{T ,2} = N ₂ (2048+512) κ 2 ^{- µ} T _c 10 ³

N _{T ,2} = N ₂ ((2048+144) κ 2 ^{- µ} +16 κ ) T _c 10 ³

Optionally, if N _{T ,2} is in seconds, the relationship between N _T,2 and N ₂ may be fixed for any one of the following (i.e., regardless of how the CP is configured), or in the case of a normal CP, one may be used. of the following (for example, the first), and in the case of an extended CP, another of the following (for example, the second) can be used:

N _{T ,2} = N ₂ (2048+144) κ 2 ^{- µ} T _c

N _{T ,2} = N ₂ (2048+512) κ 2 ^{- µ} T _c

N _{T ,2} = N ₂ ((2048+144) κ 2 ^{- µ} +16 κ ) T _c

Optionally, a normal CP case may refer to any one of the following cases, or any combination of a plurality of the following cases combined in an "and" or "or" fashion.

Any uplink BWP configured for any uplink carrier is configured in a TAG with a normal CP.

At least one uplink BWP on each uplink carrier configured in the TAG is configured with a normal CP.

All parts of the uplink BWP configured for all uplink carriers configured in the TAG are configured with normal CPs.

At least one of all downlink BWP portions configured for downlink carriers corresponding to all uplink carriers configured in TAG is configured with a normal CP.

All parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG are configured with normal CPs.

At least one of the downlink BWP portions corresponding to all uplink BWP portions configured for all uplink carriers configured in the TAG is configured with a normal CP.

The parts of the downlink BWP corresponding to all the parts of the uplink BWP configured for all the uplink carriers configured in the TAG are configured with normal CPs.

Optionally, a normal CP case can also refer to any case that is not an "extended CP case" (unless an extended CP case refers to any case that is not a "normal CP case").

Optionally, the extended CP case may refer to any one of the following cases, or any combination of a plurality of the following cases, grouped by "and" or "or".

Any uplink BWP configured for any uplink carrier configured in TAG is configured with extended CP.

At least one uplink BWP on each uplink carrier configured in the TAG is configured with an extended CP.

All parts of the uplink BWP configured for all uplink carriers configured in the TAG are configured with extended CPs.

At least one of all downlink BWP portions configured for downlink carriers corresponding to all uplink carriers configured in TAG is configured with extended CP.

All parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG are configured with extended CPs.

At least one of the parts of the downlink BWP corresponding to all parts of the uplink BWP configured for all the uplink carriers configured in the TAG is configured with an extended CP.

The parts of the downlink BWP corresponding to all the parts of the uplink BWP configured for all the uplink carriers configured in the TAG are configured with extended CPs.

Optionally, the extended CP case can also refer to any case that is not a "normal CP case" (unless the normal CP case refers to any case that is not a "widened CP case").

N _{TA , max} refers to the largest lead value. For example,N _{TA , max} may be equal to the largest lookahead value that a 12-bit lookahead command field can provide (e.g. for SCS 2^µ15 kHz, N _TA,max =T _{A , max} 16 64/2^µ, WhereT _{A , max} is the largest index value that can be specified by the lookahead command field, such as 3846).

N refers to the duration corresponding to the largest advance value. N can be expressed in milliseconds or seconds. For example, in formula (f), N may be expressed in milliseconds, and the ratio between N and N _{TA, max} may be N = N _{TA , max} · T _c ·10 ³ . In another example, in formula (k), N may be expressed in seconds and the ratio between N and N _{TA, max} may be N = N _{TA , max} · T _c .

,

и интервала n+k+1 используемый SCS может представлять собой SCS в любом одном из следующих элементов (при наличии в элементах только одного SCS), или может представлять собой наименьший SCS в любом одном или множестве из следующих элементов, или может представлять собой наибольший SCS в любом одном или множестве из следующих элементов:When determining any of N _{T ,1} , N _{T ,2} , N _{TA , max} ,

,

and interval n+k+ 1, the SCS used may be the SCS in any one of the following elements (if there is only one SCS in the elements), or may be the smallest SCS in any one or more of the following elements, or may be the largest SCS in any one or more of the following:

SCS of all uplink BWP parts configured for all uplink carriers configured in TAG.

SCS of all relevant parts of the downlink BWP (e.g., all parts of the downlink BWP configured for downlink carriers corresponding to all uplink carriers configured in TAG, or in another example, parts of the downlink BWP corresponding to all parts uplink BWP configured for all uplink carriers configured in the TAG).

SCS of the initial(s) active uplink BWP(s) (eg, all configured via the higher layer initialuplinkBWP parameter).

SCS of the initial(s) active downlink BWP(s) (eg, all configured via the higher layer initialDownlinkBWP parameter) .

The SCS of the first uplink transmission after receiving the RAR by the UE. The BWP in which the first uplink transmission resides may be the initial active uplink BWP or the active uplink BWP; the initial active uplink BWP and/or the active uplink BWP may be on an uplink carrier corresponding to the random access preamble, or may be on a different uplink carrier.

The SCS of a downlink transmission (eg, PDSCH) containing an advance command.

When determining the interval n+k+ 1, the SCS used can also be the same as the SCS used when determining the interval n .

,

и интервала n+k+1 используемый SCS также может быть определен другими способами. Вариант 1 осуществления настоящего описания не ограничивает SCS, используемый при определении любого из N _{T ,1}, N _{T ,2}, N _{TA , max} ,

,

и интервала n+k+1.When determining any of N _{T ,1} , N _{T ,2} , N _{TA , max} ,

,

and interval n+k+ 1, the SCS used can also be determined in other ways. Embodiment 1 of the present disclosure does not limit the SCS used in determining any of N _{T ,1} , N _{T ,2} , N _{TA , max} ,

,

and interval n+k+ 1.

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

Optionally, in Embodiment 1 of the present description, the uplink carrier may refer to a normal uplink carrier (NUL carrier, also referred to as UL carrier in some cases) configured by uplinkConfigCommon and uplinkConfig (if present), or may refer to a supplemental uplink carrier link (SUL carrier) configured via supplementaryUplinkConfig and supplementaryUplink (if present).

Optionally, in Embodiment 1 of the present description, the correspondence between the uplink carrier and the downlink carrier can be determined according to the cell to which the uplink carrier and the downlink carrier belong (for example, this uplink carrier corresponds to the downlink carrier connection belonging to the same cell), or may be determined according to other methods.

Optionally, in Embodiment 1 of the present description, depending on the specific configuration mode, the expression "all uplink carriers configured in TAG" may also refer to all uplink carriers belonging to TAG, the expression "any uplink carrier configured in 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.

Optionally, in Embodiment 1 of the present description, depending on the specific configuration mode, the expression "all downlink carriers configured in TAG" may also refer to all downlink carriers belonging to TAG, the expression "any downlink carrier configured in TAG ' may also refer to any downlink carrier belonging to a TAG, and 'each downlink carrier configured in a TAG' may also refer to each downlink carrier belonging to a TAG.

Optionally, in Embodiment 1 of the present disclosure, a correspondence between an uplink BWP and a downlink BWP may exist in all uplink BWPs, or may only exist in some uplink BWPs (e.g., this correspondence exists only in the case of TDD or the existence of a correspondence for given uplink BWP or downlink BWP 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 part identifiers of the BWP (eg, the uplink BWP with ID 1 corresponds to the downlink BWP with ID 1 as well) or can be determined according to other methods. If a correspondence between the uplink BWP and the downlink BWP exists only in some parts of the uplink BWP, "parts of the downlink BWP corresponding to all parts of the uplink BWP configured for all uplink carriers configured in the TAG", may also be expressed as "parts of the downlink BWP (if any) corresponding to all parts of the uplink BWP configured for all uplink carriers configured in the TAG" where the parts of the downlink BWP corresponding to all parts of the uplink BWP links may refer to portions of the downlink BWP corresponding to portions of the uplink BWP bandwidth.

Optionally, in Embodiment 1 of the present description, unless otherwise indicated, the initial(s) active(s) uplink BWP(s) may be one or a plurality of the following.

Initial active uplink BWPs configured for all uplink carriers configured for the UE.

An initial active uplink BWP configured for one of the uplink carriers configured for the UE, such as an initial active uplink BWP configured for an uplink carrier configured in the cell that transmits the advance command.

Initial active uplink BWPs configured for all uplink carriers configured in the TAG.

An initial active uplink BWP configured for one of the uplink carriers configured in a TAG, e.g. an initial active uplink BWP configured for an uplink carrier configured in a primary cell of a cell group (e.g. to which the TAG belongs.

An initial active uplink BWP configured for the uplink carrier on which the first uplink transmission is located after the UE receives the RAR.

Optionally, in Embodiment 1 of the present disclosure, unless otherwise indicated, the initial(s) active(s) downlink BWP(s) may be one or more of the following:

Initial active downlink BWPs configured for all downlink carriers configured for the UE.

An initial active downlink BWP configured for one of the downlink carriers configured for the UE, such as an initial active downlink BWP configured for a downlink carrier configured in the cell that transmits the advance command.

Initial active downlink BWPs configured for all downlink carriers configured in all cells configured in the TAG.

Initial active downlink BWP configured for a downlink carrier configured in one of the cells configured in the TAG, e.g. , to which the TAG belongs.

Optionally, in Embodiment 1 of the present description, "all parts of the uplink BWP" configured for a given uplink carrier may or may not include an initial active uplink BWP.

Optionally, in Embodiment 1 of the present description, "all parts of the downlink BWP" configured for a given downlink carrier may or may not include an initial active downlink BWP.

Thus, according to the description of Embodiment 1, the present description proposes a method for improving a method for determining when to apply the uplink transmission time adjustment so that the UE can correct the uplink transmission time in a timely manner while ensuring that the transmission time error uplink for the UE remained within the proper range.

[Embodiment 2]

The method performed by the user equipment in Embodiment 2 of the present description will be described below with reference to FIG. 3.

FIG. 3 is a block diagram of a method performed by a user equipment according to Embodiment 2 of the present invention.

As shown in FIG. 3, in Embodiment 2 of the present description, the steps performed by the user equipment (UE) include step S201 and step S202.

Specifically, in step S201, acquisition of parameter configuration information related to the SSB SL (eg, whether a parameter has been configured, or a configured parameter value) is obtained. For example, configuration information is obtained from predetermined information or preconfigured information, or configuration information is obtained from a base station (for example, configuration information is obtained using DCI or MAC CE or RRC signaling), or configuration information is obtained from another UE, or use the default value if the parameter is not configured.

Wherein:

A parameter related to the SSB SL may include a parameter related to the time-frequency position (ie, time and/or frequency position) of the SSB SL. The SSB SL time-frequency position may be the time-frequency position at which SSB SL transmission is possible (in which case the SL SSB may also be referred to as an SSB SL candidate, and the time-frequency position is the time-frequency position of the SSB SL candidate), or may represent the time-frequency position at which the actual SSB SL transmission occurs.

The parameter related to the time-frequency position of the SSB SL may include the position of the subcarrier (eg, the position of the center frequency of the subcarrier), where the SCS corresponding to the subcarrier may be the SCS of the SSB SL. For example, the subcarrier position may correspond to the position of a particular SSB SL subcarrier, eg the position of subcarrier k of the SSB SL resource block n _PRB . n _PRB may be a value in the set {0, 1, ..., 19} and k may be a value in the set {0, 1,..., 11}.

The parameter relating to the time-frequency position of the SSB SL may also include one or a plurality of the following.

Configuration information related to the SL carrier on which the SL BWP resides on which the SL SSB resides, such as the offset (eg, represented by the number of resource blocks) between the smallest subcarrier (also known as point A) of common resource block 0 and the smallest available subcarrier of the carrier SL, and/or SCS of the SL carrier, and/or the carrier bandwidth (eg, represented by the number of resource blocks) of the SL carrier, and/or the position of the immediately current subcarrier of the SL carrier.

Parameter configuration information related to the BWP SL in which the SSB SL resides, such as the number of the initial BWP SL resource block and/or the size of the BWP SL (eg, represented by the number of resource blocks).

The position of the SSB SL in the BWP SL, such as the number of the initial resource block of the SSB SL in the BWP SL; in another example, the number of the initial SSB SL subcarrier in the BWP SL; in another example, the number of the initial SSB SL subband in the BWP SL.

The parameter related to SSB SL can also be obtained in other ways. Embodiment 2 of the present description does not limit the method for obtaining a parameter related to SSB SL. In addition, in step S202, the SSB SL is received according to the parameter related to the SSB SL. Wherein:

SSB SL may include PSS SL, SSS SL and PSBCH.

An SSB SL may include 240 consecutive subcarriers in the frequency domain (eg, sequentially numbered as subcarriers 0, 1, ... and 239 in ascending order of subcarrier center frequencies).

The SSB SL may include 4 consecutive OFDM symbols in the time domain (eg, consecutively numbered as OFDM symbols 0, 1, 2, and 3 in chronological order).

The length of the sequence used by the PSS SL (herein referred to as the PSS SL sequence) may be 127.

The length of the sequence used by the SSS SL (herein referred to as the SSS SL sequence) may be 127.

). Например, различные значения

могут соответствовать различным последовательностям PSS SL и/или последовательностям SSS SL.The PSS SL sequence and/or the SSS SL sequence may be associated with an SL sync ID (SL sync ID denoted as

). For example, different values

may correspond to different PSS SL sequences and/or SSS SL sequences.

может представлять собой {0, 1, ..., 83}, или может представлять собой {0, 1, ..., 167}, или может представлять собой {0, 1, ..., 251}, или может представлять собой {0, 1, ..., 335}, или может представлять собой {0, 1, ..., 419}, или может представлять собой {0, 1, ..., 503}, или может представлять собой {0, 1, ..., 587}, или может представлять собой {0, 1, ..., 671}, или может представлять собой {0, 1, ..., 755}, или может представлять собой {0, 1, ..., 839}, или может представлять собой {0, 1, ..., 923}, или может представлять собой {0, 1, ..., 1007}, или может представлять собой {0, 1, ..., 1091}, или может представлять собой другой целочисленный набор.Set of value ranges

may be {0, 1, ..., 83}, or may be {0, 1, ..., 167}, or may be {0, 1, ..., 251}, or may be is {0, 1, ..., 335}, or may be {0, 1, ..., 419}, or may be {0, 1, ..., 503}, or may be { 0, 1, ..., 587}, or may be {0, 1, ..., 671}, or may be {0, 1, ..., 755}, or may be {0, 1, ..., 839}, or may be {0, 1, ..., 923}, or may be {0, 1, ..., 1007}, or may be {0, 1, ..., 1091}, or may be another integer set.

могут быть определены с помощью

и

, например с помощью одного из следующих способов:Not necessary

can be defined with

And

, for example using one of the following methods:

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

subcarrier set {0, 1, ..., 47} and subcarrier set {192, 193, ..., 239} in OFDM symbol 1, subcarrier set {0, 1, ..., 239} in OFDM symbol 2, and subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 239} in OFDM symbol 1, subcarrier set {0, 1, ..., 239} in OFDM symbol 2, subcarrier set {0, 1, ..., 47}, and subcarrier set {192, 193, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 239} in OFDM symbol 1, subcarrier set {0, 1, ..., 47}, subcarrier set {192, 193, ..., 239} in OFDM symbol 2, and subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 47} and subcarrier set {192, 193, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 239} in OFDM symbol 1, and subcarrier set {0, 1, ..., 239} in OFDM symbol 2.

subcarrier set {0, 1, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 239} in OFDM symbol 1, and subcarrier set {0, 1, ..., 47} , and subcarrier set {192, 193, ..., 239} in OFDM symbol 2.

subcarrier set {0, 1, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 47}, subcarrier set {192, 193, ..., 239} in OFDM symbol 1, and subcarrier set {0, 1, ..., 239} in OFDM symbol 2.

subcarrier set {0, 1, ..., 47} and subcarrier set {192, 193, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 239} in OFDM symbol 1, and subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 239} in OFDM symbol 1, and subcarrier set {0, 1, ..., 47} , and subcarrier set {192, 193, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 47}, subcarrier set {192, 193, ..., 239} in OFDM symbol 1, and subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 47} and subcarrier set {192, 193, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 239} in OFDM symbol 2, and subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 239} in OFDM symbol 2, and subcarrier set {0, 1, ..., 47} , and subcarrier set {192, 193, ..., 239} in OFDM symbol 3.

subcarrier set {0, 1, ..., 239} in OFDM symbol 0, subcarrier set {0, 1, ..., 47}, subcarrier set {192, 193, ..., 239} in OFDM symbol 2, and subcarrier set {0, 1, ..., 239} in OFDM symbol 3.

Optionally, if the PSBCH data is mapped to the RE in the SSB SL, the mapping may be performed in the time domain in one of the following sequences:

symbol 0 OFDM, symbol 1 OFDM, symbol 2 OFDM.

symbol 0 OFDM, symbol 1 OFDM, symbol 3 OFDM.

symbol 0 OFDM, symbol 2 OFDM, symbol 1 OFDM.

symbol 0 OFDM, symbol 2 OFDM, symbol 3 OFDM.

symbol 0 OFDM, symbol 3 OFDM, symbol 1 OFDM.

OFDM symbol 0, OFDM symbol 3, OFDM symbol 2.

OFDM symbol 1, OFDM symbol 0, OFDM symbol 2.

OFDM symbol 1, OFDM symbol 0, OFDM symbol 3.

OFDM symbol 1, OFDM symbol 2, OFDM symbol 0.

OFDM symbol 1, OFDM symbol 2, OFDM symbol 3.

OFDM symbol 1, OFDM symbol 3, OFDM symbol 0.

OFDM symbol 1, OFDM symbol 3, OFDM symbol 2.

OFDM symbol 2, OFDM symbol 0, OFDM symbol 1.

OFDM symbol 2, OFDM symbol 0, OFDM symbol 3.

OFDM symbol 2, OFDM symbol 1, OFDM symbol 0.

OFDM symbol 2, OFDM symbol 1, OFDM symbol 3.

OFDM symbol 2, OFDM symbol 3, OFDM symbol 0.

OFDM symbol 2, OFDM symbol 3, OFDM symbol 1.

OFDM symbol 3, OFDM symbol 0, OFDM symbol 1.

OFDM symbol 3, OFDM symbol 0, OFDM symbol 2.

OFDM symbol 3, OFDM symbol 1, OFDM symbol 0.

OFDM symbol 3, OFDM symbol 1, OFDM symbol 2.

OFDM symbol 3, OFDM symbol 2, OFDM symbol 0.

OFDM symbol 3, OFDM symbol 2, OFDM symbol 1.

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

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

subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 1, subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 2, subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v } and subcarrier set {192+ v , 196+ v , ..., 236+ v } in symbol 3 OFDM.

subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 1, subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v }, subcarrier set {192+ v , 196+ v , ..., 236+ v } in OFDM symbol 2, and subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in symbol 3 OFDM.

subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v } and subcarrier set {192+ v , 196+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 1 and subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in symbol 2 OFDM.

subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 1, subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v } and subcarrier set {192+ v , 196+ v , ..., 236+ v } in symbol 2 OFDM.

subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v }, subcarrier set {192+ v , 196+ v , ..., 236+ v } in OFDM symbol 1, and subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in symbol 2 OFDM.

subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v } and subcarrier set {192+ v , 196+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 1 and subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in symbol 3 OFDM.

subcarrier set {0+v, 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 1 and subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v } and subcarrier set {192+ v , 196+ v , ..., 236+ v } in symbol 3 OFDM.

subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v } and subcarrier set {192+v, 196+ v , ..., 236+ v } in OFDM symbol 1 and subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in symbol 3 OFDM.

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

subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 2, subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v } and subcarrier set {192+ v , 196+ v , ..., 236+ v } in symbol 3 OFDM.

subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in OFDM symbol 0, subcarrier set {0+ v , 4+ v , 8+ v , ..., 44+ v }, subcarrier set {192+ v , 196+ v , ..., 236+ v } in OFDM symbol 2, and subcarrier set {0+ v , 4+ v , 8+ v , ..., 236+ v } in symbol 3 OFDM.

mod 4. v is an integer constant. For example, v could be equal to

mod 4.

Optionally, if the DM-RS used for the PSBCH is mapped to the RE in the SSB SL, the mapping may be done in the time domain in one of the following sequences:

symbol 0 OFDM, symbol 1 OFDM, symbol 2 OFDM.

symbol 0 OFDM, symbol 1 OFDM, symbol 3 OFDM.

symbol 0 OFDM, symbol 2 OFDM, symbol 1 OFDM.

symbol 0 OFDM, symbol 2 OFDM, symbol 3 OFDM.

symbol 0 OFDM, symbol 3 OFDM, symbol 1 OFDM.

OFDM symbol 0, OFDM symbol 3, OFDM symbol 2.

OFDM symbol 1, OFDM symbol 0, OFDM symbol 2.

OFDM symbol 1, OFDM symbol 0, OFDM symbol 3.

OFDM symbol 1, OFDM symbol 2, OFDM symbol 0.

OFDM symbol 1, OFDM symbol 2, OFDM symbol 3.

OFDM symbol 1, OFDM symbol 3, OFDM symbol 0.

OFDM symbol 1, OFDM symbol 3, OFDM symbol 2.

OFDM symbol 2, OFDM symbol 0, OFDM symbol 1.

OFDM symbol 2, OFDM symbol 0, OFDM symbol 3.

OFDM symbol 2, OFDM symbol 1, OFDM symbol 0.

OFDM symbol 2, OFDM symbol 1, OFDM symbol 3.

OFDM symbol 2, OFDM symbol 3, OFDM symbol 0.

OFDM symbol 2, OFDM symbol 3, OFDM symbol 1.

OFDM symbol 3, OFDM symbol 0, OFDM symbol 1.

OFDM symbol 3, OFDM symbol 0, OFDM symbol 2.

OFDM symbol 3, OFDM symbol 1, OFDM symbol 0.

OFDM symbol 3, OFDM symbol 1, OFDM symbol 2.

OFDM symbol 3, OFDM symbol 2, OFDM symbol 0.

OFDM symbol 3, OFDM symbol 2, OFDM symbol 1.

Optionally, the PSS SL sequence may be defined as one of the following:

Where:

0 ≤ n < 127

P is a constant. P may be one of 17, 18, 19, 20, 21, 22, 23, 24 and 25.

x ( i +7) = ( x ( i +4) + x ( i )) mod 2

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

Optionally, the SSS SL sequence may be defined as one of the following:

d _SSS (n) = [1-2 × ₀ (( n + m ₀ ) mod 127)][1-2 × ₁ (( n + m ₁ ) mod 127)]

d _SSS (n) = [2 × ₀ (( n + m ₀ ) mod 127) - 1][1-2 × ₁ (( n + m ₁ ) mod 127)]

d _SSS (n) = [1-2 × ₀ (( n + m ₀ ) mod 127)][2 × ₁ (( n + m ₁ ) mod 127) - 1]

d _SSS (n) = [2 × ₀ (( n + m ₀ ) mod 127) - 1][2 × ₁ (( n + m ₁ ) mod 127) - 1]

Where:

0 ≤ n < 127

Q is a constant. Q may be one of 45, 50, 55, 60, 65 and 70.

x ₀ ( i +7) = ( x ₀ ( i +4) + x ₀ ( i )) mod 2

x ₁ ( i +7) = ( x ₁ ( i +1) + x ₁ ( i )) mod 2

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

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

Optionally, the time domain and frequency domain resources in the SL SSB occupied by the SL PSS may be one or two sets of subcarriers in an OFDM symbol s . s may be 0, or may be 1, or may be 2, or may be 3, and one or two sets of subcarriers may be one of the following:

{0, 1, ..., 126}

{1, 2, ..., 127}

{2, 3, ..., 128}

{3, 4, ..., 129}

{4, 5, ..., 130}

{5, 6, ..., 131}

{6, 7, ..., 132}

{7, 8, ..., 133}

{8, 9, ..., 134}

{9, 10, ..., 135}

{10, 11, ..., 136}

{11, 12, ..., 137}

{12, 13, ..., 138}

{13, 14, ..., 139}

{14, 15, ..., 140}

{15, 16, ..., 141}

{16, 17, ..., 142}

{17, 18, ..., 143}

{18, 19, ..., 144}

{19, 20, ..., 145}

{20, 21, ..., 146}

{21, 22, ..., 147}

{22, 23, ..., 148}

{23, 24, ..., 149}

{24, 25, ..., 150}

{25, 26, ..., 151}

{26, 27, ..., 152}

{27, 28, ..., 153}

{28, 29, ..., 154}

{29, 30, ..., 155}

{30, 31, ..., 156}

{31, 32, ..., 157}

{32, 33, ..., 158}

{33, 34, ..., 159}

{34, 35, ..., 160}

{35, 36, ..., 161}

{36, 37, ..., 162}

{37, 38, ..., 163}

{38, 39, ..., 164}

{39, 40, ..., 165}

{40, 41, ..., 166}

{41, 42, ..., 167}

{42, 43, ..., 168}

{43, 44, ..., 169}

{44, 45, ..., 170}

{45, 46, ..., 171}

{46, 47, ..., 172}

{47, 48, ..., 173}

{48, 49, ..., 174}

{49, 50, ..., 175}

{50, 51, ..., 176}

{51, 52, ..., 177}

{52, 53, ..., 178}

{53, 54, ..., 179}

{54, 55, ..., 180}

{55, 56, ..., 181}

{56, 57, ..., 182}

{57, 58, ..., 183}

{58, 59, ..., 184}

{59, 60, ..., 185}

{60, 61, ..., 186}

{61, 62, ..., 187}

{62, 63, ..., 188}

{63, 64, ..., 189}

{64, 65, ..., 190}

{65, 66, ..., 191}

{66, 67, ..., 192}

{67, 68, ..., 193}

{68, 69, ..., 194}

{69, 70, ..., 195}

{70, 71, ..., 196}

{71, 72, ..., 197}

{72, 73, ..., 198}

{73, 74, ..., 199}

{74, 75, ..., 200}

{75, 76, ..., 201}

{76, 77, ..., 202}

{77, 78, ..., 203}

{78, 79, ..., 204}

{79, 80, ..., 205}

{80, 81, ..., 206}

{81, 82, ..., 207}

{82, 83, ..., 208}

{83, 84, ..., 209}

{84, 85, ..., 210}

{85, 86, ..., 211}

{86, 87, ..., 212}

{87, 88, ..., 213}

{88, 89, ..., 214}

{89, 90, ..., 215}

{90, 91, ..., 216}

{91, 92, ..., 217}

{92, 93, ..., 218}

{93, 94, ..., 219}

{94, 95, ..., 220}

{95, 96, ..., 221}

{96, 97, ..., 222}

{97, 98, ..., 223}

{98, 99, ..., 224}

{99, 100, ..., 225}

{100, 101, ..., 226}

{101, 102, ..., 227}

{102, 103, ..., 228}

{103, 104, ..., 229}

{104, 105, ..., 230}

{105, 106, ..., 231}

{106, 107, ..., 232}

{107, 108, ..., 233}

{108, 109, ..., 234}

{109, 110, ..., 235}

{110, 111, ..., 236}

{111, 112, ..., 237}

{112, 113, ..., 238}

{113, 114, ..., 239}

{55}, {183, 184, ..., 308}

{54, 55}, {183, 184, ..., 307}

{53, 54, 55}, {183, 184, ..., 306}

{52, 53, ..., 55}, {183, 184, ..., 305}

{51, 52, ..., 55}, {183, 184, ..., 304}

{50, 51, ..., 55}, {183, 184, ..., 303}

{49, 50, ..., 55}, {183, 184, ..., 302}

{48, 49, ..., 55}, {183, 184, ..., 301}

{47, 48, ..., 55}, {183, 184, ..., 300}

{46, 47, ..., 55}, {183, 184, ..., 299}

{45, 46, ..., 55}, {183, 184, ..., 298}

{44, 45, ..., 55}, {183, 184, ..., 297}

{43, 44, ..., 55}, {183, 184, ..., 296}

{42, 43, ..., 55}, {183, 184, ..., 295}

{41, 42, ..., 55}, {183, 184, ..., 294}

{40, 41, ..., 55}, {183, 184, ..., 293}

{39, 40, ..., 55}, {183, 184, ..., 292}

{38, 39, ..., 55}, {183, 184, ..., 291}

{37, 38, ...., 55}, {183, 184, ..., 290}

{36, 37, ..., 55}, {183, 184, ..., 289}

{35, 36, ..., 55}, {183, 184, ..., 288}

{34, 35, ..., 55}, {183, 184, ..., 287}

{33, 34, ..., 55}, {183, 184, ..., 286}

{32, 33, ..., 55}, {183, 184, ..., 285}

{31, 32, ..., 55}, {183, 184, ..., 284}

{30, 31, ..., 55}, {183, 184, ..., 283}

{29, 30, ..., 55}, {183, 184, ..., 282}

{28, 29, ..., 55}, {183, 184, ..., 281}

{27, 28, ..., 55}, {183, 184, ..., 280}

{26, 27, ..., 55}, {183, 184, ..., 279}

{25, 26, ..., 55}, {183, 184, ..., 278}

{24, 25, ..., 55}, {183, 184, ..., 277}

{23, 24, ..., 55}, {183, 184, ..., 276}

{22, 23, ..., 55}, {183, 184, ..., 275}

{21, 22, ..., 55}, {183, 184, ..., 274}

{20, 21, ..., 55}, {183, 184, ..., 273}

{19, 20, ..., 55}, {183, 184, ..., 272}

{18, 19, ..., 55}, {183, 184, ..., 271}

{17, 18, ..., 55}, {183, 184, ..., 270}

{16, 17, ..., 55}, {183, 184, ..., 269}

{15, 16, ..., 55}, {183, 184, ..., 268}

{14, 15, ..., 55}, {183, 184, ..., 267}

{13, 14, ..., 55}, {183, 184, ..., 266}

{12, 13, ..., 55}, {183, 184, ..., 265}

{11, 12, ..., 55}, {183, 184, ..., 264}

{10, 11, ..., 55}, {183, 184, ..., 263}

{9, 10, ..., 55}, {183, 184, ..., 262}

{8, 9, ..., 55}, {183, 184, ..., 261}

{7, 8, ..., 55}, {183, 184, ..., 260}

{6, 7, ..., 55}, {183, 184, ..., 259}

{5, 6, ..., 55}, {183, 184, ..., 258}

{4, 5, ..., 55}, {183, 184, ..., 257}

{3, 4, ..., 55}, {183, 184, ..., 256}

{2, 3, ..., 55}, {183, 184, ..., 255}

{1, 2, ..., 55}, {183, 184, ..., 254}

{0, 1, ..., 55}, {183, 184, ..., 253}

Optionally, when matching PSS SL to RE in SSB SL, the matching can be done in the frequency domain in descending order of subcarrier numbers. For example, if the PSS SL sequence is denoted as d _PSS (0), d _PSS (1), ..., d _PSS (126), then when matching the PSS SL with RE resource elements (identified as ( k , l ) _{p , μ} , where k is the subcarrier number, l is the OFDM symbol number, p is the antenna port number, and μ is the subcarrier spacing configuration) in SSB SL, matching is performed in descending order of k . Optionally, the mapping may be performed in ascending or descending l order (when the PSS SL signals occupy only one OFDM symbol, it does not matter whether the mapping is performed in ascending l order or in descending l order). For example, if the PSS SL signals occupy subcarrier set {57, 58, ..., 183} in OFDM symbol 0, then d _PSS (0) is mapped to ( l =0, k =183), d _PSS (1) is mapped to ( l =0, k =182), ..., and d _PSS (126) is mapped to ( l =0, k =57).

Optionally, when mapping PSS SL to RE in SSB SL, the mapping can also be performed in the frequency domain in ascending order of subcarrier numbers.

Optionally, the time domain and frequency domain resources occupied by the SL SSS may be one or two sets of subcarriers in an OFDM symbol s . Here, s may be 0, or may be 1, or may be 2, or may be 3, and one or two sets of subcarriers may be one of the following:

{0, 1, ..., 126}

{1, 2, ..., 127}

{2, 3, ..., 128}

{3, 4, ..., 129}

{4, 5, ..., 130}

{5, 6, ..., 131}

{6, 7, ..., 132}

{7, 8, ..., 133}

{8, 9, ..., 134}

{9, 10, ..., 135}

{10, 11, ..., 136}

{11, 12, ..., 137}

{12, 13, ..., 138}

{13, 14, ..., 139}

{14, 15, ..., 140}

{15, 16, ..., 141}

{16, 17, ..., 142}

{17, 18, ..., 143}

{18, 19, ..., 144}

{19, 20, ..., 145}

{20, 21, ..., 146}

{21, 22, ..., 147}

{22, 23, ..., 148}

{23, 24, ..., 149}

{24, 25, ..., 150}

{25, 26, ..., 151}

{26, 27, ..., 152}

{27, 28, ..., 153}

{28, 29, ..., 154}

{29, 30, ..., 155}

{30, 31, ..., 156}

{31, 32, ..., 157}

{32, 33, ..., 158}

{33, 34, ..., 159}

{34, 35, ..., 160}

{35, 36, ..., 161}

{36, 37, ..., 162}

{37, 38, ..., 163}

{38, 39, ..., 164}

{39, 40, ..., 165}

{40, 41, ..., 166}

{41, 42, ..., 167}

{42, 43, ..., 168}

{43, 44, ..., 169}

{44, 45, ..., 170}

{45, 46, ..., 171}

{46, 47, ..., 172}

{47, 48, ..., 173}

{48, 49, ..., 174}

{49, 50, ..., 175}

{50, 51, ..., 176}

{51, 52, ..., 177}

{52, 53, ..., 178}

{53, 54, ..., 179}

{54, 55, ..., 180}

{55, 56, ..., 181}

{56, 57, ..., 182}

{57, 58, ..., 183}

{58, 59, ..., 184}

{59, 60, ..., 185}

{60, 61, ..., 186}

{61, 62, ..., 187}

{62, 63, ..., 188}

{63, 64, ..., 189}

{64, 65, ..., 190}

{65, 66, ..., 191}

{66, 67, ..., 192}

{67, 68, ..., 193}

{68, 69, ..., 194}

{69, 70, ..., 195}

{70, 71, ..., 196}

{71, 72, ..., 197}

{72, 73, ..., 198}

{73, 74, ..., 199}

{74, 75, ..., 200}

{75, 76, ..., 201}

{76, 77, ..., 202}

{77, 78, ..., 203}

{78, 79, ..., 204}

{79, 80, ..., 205}

{80, 81, ..., 206}

{81, 82, ..., 207}

{82, 83, ..., 208}

{83, 84, ..., 209}

{84, 85, ..., 210}

{85, 86, ..., 211}

{86, 87, ..., 212}

{87, 88, ..., 213}

{88, 89, ..., 214}

{89, 90, ..., 215}

{90, 91, ..., 216}

{91, 92, ..., 217}

{92, 93, ..., 218}

{93, 94, ..., 219}

{94, 95, ..., 220}

{95, 96, ..., 221}

{96, 97, ..., 222}

{97, 98, ..., 223}

{98, 99, ..., 224}

{99, 100, ..., 225}

{100, 101, ..., 226}

{101, 102, ..., 227}

{102, 103, ..., 228}

{103, 104, ..., 229}

{104, 105, ..., 230}

{105, 106, ..., 231}

{106, 107, ..., 232}

{107, 108, ..., 233}

{108, 109, ..., 234}

{109, 110, ..., 235}

{110, 111, ..., 236}

{111, 112, ..., 237}

{112, 113, ..., 238}

{113, 114, ..., 239}

{55}, {183, 184, ..., 308}

{54, 55}, {183, 184, ..., 307}

{53, 54, 55}, {183, 184, ..., 306}

{52, 53, ..., 55}, {183, 184, ..., 305}

{51, 52, ..., 55}, {183, 184, ..., 304}

{50, 51, ..., 55}, {183, 184, ..., 303}

{49, 50, ..., 55}, {183, 184, ..., 302}

{48, 49, ..., 55}, {183, 184, ..., 301}

{47, 48, ..., 55}, {183, 184, ..., 300}

{46, 47, ..., 55}, {183, 184, ..., 299}

{45, 46, ..., 55}, {183, 184, ..., 298}

{44, 45, ..., 55}, {183, 184, ..., 297}

{43, 44, ..., 55}, {183, 184, ..., 296}

{42, 43, ..., 55}, {183, 184, ..., 295}

{41, 42, ..., 55}, {183, 184, ..., 294}

{40, 41, ..., 55}, {183, 184, ..., 293}

{39, 40, ..., 55}, {183, 184, ..., 292}

{38, 39, ..., 55}, {183, 184, ..., 291}

{37, 38, ..., 55}, {183, 184, ..., 290}

{36, 37, ..., 55}, {183, 184, ..., 289}

{35, 36, ..., 55}, {183, 184, ..., 288}

{34, 35, ..., 55}, {183, 184, ..., 287}

{33, 34, ..., 55}, {183, 184, ..., 286}

{32, 33, ..., 55}, {183, 184, ..., 285}

{31, 32, ..., 55}, {183, 184, ..., 284}

{30, 31, ..., 55}, {183, 184, ..., 283}

{29, 30, ..., 55}, {183, 184, ..., 282}

{28, 29, ..., 55}, {183, 184, ..., 281}

{27, 28, ..., 55}, {183, 184, ..., 280}

{26, 27, ..., 55}, {183, 184, ..., 279}

{25, 26, ..., 55}, {183, 184, ..., 278}

{24, 25, ..., 55}, {183, 184, ..., 277}

{23, 24, ..., 55}, {183, 184, ..., 276}

{22, 23, ..., 55}, {183, 184, ..., 275}

{21, 22, ..., 55}, {183, 184, ..., 274}

{20, 21, ..., 55}, {183, 184, ..., 273}

{19, 20, ..., 55}, {183, 184, ..., 272}

{18, 19, ..., 55}, {183, 184, ..., 271}

{17, 18, ..., 55}, {183, 184, ..., 270}

{16, 17, ..., 55}, {183, 184, ..., 269}

{15, 16, ..., 55}, {183, 184, ..., 268}

{14, 15, ..., 55}, {183, 184, ..., 267}

{13, 14, ..., 55}, {183, 184, ..., 266}

{12, 13, ..., 55}, {183, 184, ..., 265}

{11, 12, ..., 55}, {183, 184, ..., 264}

{10, 11, ..., 55}, {183, 184, ..., 263}

{9, 10, ..., 55}, {183, 184, ..., 262}

{8, 9, ..., 55}, {183, 184, ..., 261}

{7, 8, ..., 55}, {183, 184, ..., 260}

{6, 7, ..., 55}, {183, 184, ..., 259}

{5, 6, ..., 55}, {183, 184, ..., 258}

{4, 5, ..., 55}, {183, 184, ..., 257}

{3, 4, ..., 55}, {183, 184, ..., 256}

{2, 3, ..., 55}, {183, 184, ..., 255}

{1, 2, ..., 55}, {183, 184, ..., 254}

{0, 1, ..., 55}, {183, 184, ..., 253}

Optionally, if the PSS SL is mapped to the RE in the SSB SL, the mapping can be done in the frequency domain in descending order of subcarrier numbers. For example, if the SSS SL sequence is denoted as d _SSS (0), d _SSS (1), ..., d _SSS (126), then when the SSS SL signals are mapped to REs (designated as ( k , l ) _{p , μ} , where k is the subcarrier number, l is the OFDM symbol number, p is the antenna port number, and μ is the subcarrier spacing pattern) in SSB SL, matching is performed in descending order of k. Optionally, the mapping may be performed in ascending or descending l order (when the SSS SL signals occupy only one OFDM symbol, it does not matter whether the mapping is performed in ascending l order or in descending l order). For example, if the SSS SL signals occupy subcarrier set {57, 58, ..., 183} in OFDM symbol 2, then d _SSS (0) is mapped to ( l =2, k =183), d _SSS (1) is mapped to ( l =2, k =182),..., and d _SSS (126) is mapped to ( l =2, k =57).

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

Thus, in accordance with the description of Embodiment 2, the present description proposes a method for improving the resource mapping method for a PSS SL and/or an SSS SL and/or a PSBCH in an SSB SL and/or an SL sync ID scheme and/or a sequence scheme. PSS SL, and/or SSS SL sequencing schemes, etc., which allows the 5G UE (Release 15) to avoid erroneous confusion between part or all of the SSB SL and part or all of the SSB, and unnecessary increase in cell search and/or access time to the system.

[Embodiment 3]

The method performed by the user equipment in Embodiment 3 of the present description will be described below with reference to FIG. 4.

FIG. 4 is a block diagram of a method performed by a user equipment according to Embodiment 3 of the present invention.

As shown in FIG. 4, in Embodiment 3 of the present description, steps performed by a user equipment (UE) include step S301 and step S302.

Specifically, in step S301, configuration information of a parameter related to the SSB SL is obtained. For example, configuration information is obtained from predefined information or preconfigured information, or configuration information is obtained from a base station (for example, configuration information is obtained using DCI or MAC CE or RRC signaling), or configuration information is obtained from another UE, or use the default configuration if the parameter is not configured.

Wherein:

SSB SL may include PSS SL, SSS SL and PSBCH.

SSB SL may include 240 consecutive subcarriers in the frequency domain.

The SSB SL may be an SSB SL that is possibly being transmitted (or referred to as an SSB SL candidate), or may be an SSB SL that is actually being transmitted.

The configuration information may include an indication of the position of the frequency reference. For example, to specify the position of the frequency reference, use the absoluteFrequencySL-SSB parameter, the type of which is ARFCN-ValueNR. The position of the SSB SL in the frequency domain can also be indicated in other ways, for example by specifying the position of the frequency reference and the offset.

The configuration information may include SCS SSB SL. For example, SCS is specified using the sl-ssbSubcarrierSpacing parameter, whose type is SubcarrierSpacing.

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

For example, if the position of each SSB SL subcarrier in the frequency domain is determined, the frequency reference position is assumed to correspond to the position of subcarrier k of resource block n _PRB in SSB SL, where n _PRB can be a value in the set {0,1, ..., 19} , k can be a value in the set {0, 1, ..., 11}, while the values n _PRB =10 and k =0 are not used simultaneously. For example, if n _PRB =0 and k =0, the frequency reference position specified by the absoluteFrequencySL-SSB parameter is 3000000 kHz and the SCS specified by the sl-ssbSubcarrierSpacing parameter is 15 kHz, then the 0 SSB SL subcarrier position in the frequency domain is 3000000 kHz, the position of subcarrier 1 in the frequency domain is 3000015 kHz, the position of subcarrier 2 in the frequency domain is 3000030 kHz, ... and the position of subcarrier 239 in the frequency domain is 3003585 kHz.

In accordance with the method described above in Embodiment 3, when determining the position of the SSB SL subcarrier in the frequency domain, the interpretation of the specified position of the reference frequency is different from the interpretation of the specified position of the reference frequency in 5G (Release 15), which allows the 5G UE (Release 15) to avoid erroneous confusion between SSB SL and SSB, as well as an unnecessary increase in cell search time and/or system access.

[Embodiment 4]

The method performed by the user equipment in Embodiment 4 of the present description will be described below with reference to FIG. 5.

FIG. 5 is a block diagram of a method performed by a user equipment according to Embodiment 4 of the present invention.

As shown in FIG. 5, in Embodiment 4 of the present description, the steps performed by the user equipment (UE) include the following steps.

Specifically, in step S401, timing-related information is acquired. For example, timing related information is obtained once at time t ₀ and registered as first timing information; timing related information is reacquired at time t ₁ and registered as second timing information _.

Wherein:

Time t ₀ ≤ t ₁ .

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 received from a GNSS system or configuration information received from SSB, SSB SL, SIB, etc. transmitted by an LTE or 5G base station. The methods for obtaining the first timing information and the second timing information may be the same or different.

The entity transmitting SSB SL may be another UE (such as an LTE UE or a 5G UE), or may be a 5G base station, or may be an LTE base station, or may be other entities.

SSB SL may include PSS SL, SSS SL and PSBCH. The PSBCH may contain the MIB SL.

The configuration information indicated by the SSB SL may include one or more of the following.

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

Information relating to slots and/or subframes and/or frames, such as slot time, slot forward number, subframe forward number, frame forward number, and the like.

The SSB SL may also indicate information related to the timing reference source (or called timing source), such as the ID of the timing reference source, or the type of object corresponding to the timing reference source, or the priority of the object corresponding to the timing reference source, etc. P.

Wherein:

Timing related information may be associated with one or more timing reference sources. If timing-related information is associated with multiple timing reference sources, the contents of the configuration information indicated by the multiple timing reference sources may not be exactly the same. For example, the direct slot numbers indicated by the SSB SL signals, the direct subframe numbers, and the direct frame numbers transmitted at different times may be different, but they all indicate the same frame structure information, symbol time, and slot time information.

A timing reference source may refer to an entity that provides timing related information.

The source of the timing references may be a direct source of the timing references, or may be an indirect source of the timing references. For example, if entities B and C receive synchronization-related information from entity A, and entity B indicates synchronization-related information to the UE, but entity C does not indicate synchronization-related information to the UE, then entity A is a direct source of reference signals. Entity B and Entity C, Entity B is the direct source of timing references for the UE, Entity A is the indirect source of timing references for the UE, and Entity C is neither a direct source of timing references for the UE nor an indirect source of timing references. synchronization signals for the UE.

Among one or multiple timing reference sources associated with timing related information, there may be a root timing reference source. The root clock reference source is the direct clock reference source, or the indirect clock reference source for all other clock reference sources.

The SSB SL may indicate information related to one or a plurality of timing reference sources associated with timing related information, such as one or more of the following.

The type of one or more timing reference sources associated with the timing-related information, such as the type (such as GNSS) of the root timing reference source associated with the timing-related information.

The number of timing reference sources associated with timing related information (including or excluding an entity that indicates timing related information to the UE).

The coverage status for one or more timing reference sources associated with timing related information. For example, the coverage state may be an "in coverage" state, e.g. where RSRP and/or RSRQ and/or other measured values measured at the frequency used for SL data exchange satisfies a certain condition (such as "criterion S » to select a cell). In another example, the coverage state may be an "out of coverage" state, such as where RSRP and/or RSRQ and/or other measured values on the frequency used for SL data exchange do not satisfy the corresponding condition for the "in coverage" state. ".

Also, in step S402, it is determined whether to apply and/or transmit timing reference information according to one or a plurality of the following.

Time t ₀ .

Time t ₁ .

First synchronization information.

Second synchronization information.

Information related to the timing reference source associated with the first timing information.

Information related to the timing reference source associated with the second timing information.

The timing reference information may be the first timing information or the second timing information.

For example, if one or more of the following conditions are satisfied (in any combination of "and" or "or"), the timing reference information is applied and/or the timing reference information is transmitted:

The priority of the one or multiple timing reference sources associated with the first timing information satisfies a particular relationship with the priority of the one or multiple timing reference sources associated with the second timing information. For example, the first is higher than the second; or the first is equal to the second; or the first is lower than the second.

The coverage area state of the one or multiple timing reference sources associated with the first timing information satisfies a particular relationship with the coverage area state of the one or multiple timing reference sources associated with the second timing information. For example, the first is "in the coverage area" and the second is "out of the coverage area"; or the first - "out of the coverage area" and the second - "in the coverage area"; or the first is "out of coverage" and the second is "out of coverage"; or the first - "in the coverage area" and the second - "in the coverage area".

The number of timing reference sources associated with the first timing information satisfies a particular relationship with the number of timing reference sources associated with the second timing information. For example, the first is greater than the second; or the first is equal to the second; or the first is less than the second.

t ₁ - t ₀ corresponds to a specific condition. For example, t ₁ - t ₀ ≥ Δ; or t ₁ - t ₀ >Δ; or t ₁ - t ₀ <Δ; or t ₁ - t ₀ ≤ Δ. Δ may be a predetermined or preconfigured constant, or may be a parameter configured using higher layer signaling.

Specifically, for example, if the priority of the root timing reference associated with the first timing information is lower than the priority of the root timing reference associated with the second timing information, the second timing information is applied and/or the second timing information is transmitted; in another example, if the root timing reference associated with the first timing information is in the "out of coverage" state, the root timing reference associated with the second timing information is in the "in coverage" state, apply the second timing information and/or transmitting second timing information; in another example, if the number of timing reference sources associated with the first timing information is greater than the number of timing reference sources associated with the second timing information, the second timing information is applied and/or the second timing information is transmitted.

Thus, in accordance with the description of Embodiment 4, the present description proposes a method for forwarding received timing information that meets a certain condition (such as the highest priority), so that a UE under different coverage conditions can use the same timing information. and may further communicate over SL with each other.

[Embodiment 5]

The method performed by the user equipment in Embodiment 5 of the present description will be described below with reference to FIG. 6.

FIG. 6 is a block diagram of a method performed by a user equipment according to Embodiment 5 of the present invention.

As shown in FIG. 6, in Embodiment 5 of the present description, the steps performed by the user equipment (UE) include the following steps.

Specifically, in step S501, configuration information of a parameter related to SL channel scrambling (eg, whether a parameter has been configured, or a configured parameter value) is obtained. For example, configuration information is obtained from predetermined information or preconfigured information, or configuration information is obtained from a base station (for example, configuration information is obtained using DCI or MAC CE or RRC signaling), or configuration information is obtained from another UE, or use the default value if the parameter is not configured.

Wherein:

The SL channel may be a channel related to SL timing, or a channel related to SL communication, or other channels transmitted on an SL carrier. In particular, the channel may be a PSBCH, or may be a PSCCH, or may be a PSSCH, or may be a PSFCH.

The parameter may include one or a plurality of the following.

). Диапазон значений

может быть таким же, как в варианте 2 осуществления, или может представлять собой другие диапазоны значений.The SL sync ID (denoted as

). Value range

may be the same as in Embodiment 2, or may be other ranges of values.

The first scrambling code identifier (denoted as n _{ID ,1} ). The set of values n _{ID ,1} may be {0, 1, ..., 65535} or a subset of {0, 1, ..., 65535}. Optionally, n _{ID ,1} may be an identifier relating to one or more SL transmissions, such as an RNTI allocated to a UE, or a UE ID, or a target UE ID, or a target UE group ID, or an SL synchronization ID. Optionally, n _{ID ,1} can also be equal to the SL sync ID.

The second scrambling code identifier (denoted as n _{ID ,2} ). The set of values n _{ID ,2} can be {0, 1, ..., 65535} or a subset of {0, 1, ..., 65535} (for example, {0, 1, ..., 1023}, or { 1024, 1025, ..., 2047}, or {2048, 2049, ..., 4095}, or {4096, 4097, ..., 6143}, or other subsets). Optionally, n _{ID ,2} may be an identifier relating to one or more transmissions on the SL channel, such as an RNTI allocated to a UE, or a UE ID, or a target UE ID, or a target UE group ID. Optionally, n _{ID ,2} can also be equal to the SL sync ID.

The first offset constant (denoted as M ₁ ). The constant M ₁ may be a predefined constant in the set {0, 1, ..., 65535} (for example, M ₁ =1008. In another example, M ₁ =1024).

The second bias constant (denoted as M ₂ ). The constant M ₂ may be a predefined constant in the set {0, 1, ..., 65535} (for example, M ₂ =1024. In another example, M ₂ =1008).

Also, in step S502, the SL scrambling sequence is determined according to the configuration information.

Wherein:

The scrambling sequence may be a pseudo-random sequence.

For example, the pseudo-random sequence c(n ) can be defined as follows:

c(n) = ( x ₁ (n+ N _C ) + x ₂ (n+ N _C )) mod 2

x ₁ ( n +31) = ( x ₁ ( n +3) + x ₁ ( n )) mod 2

x ₂ ( n +31) = ( x ₂ ( n +3) + x ₂ ( n +2) + x ₂ ( n +1) + x ₂ ( n )) mod 2

Where:

NC = ₁₆₀₀ .

x ₁ ( n ) is initialized as x ₁ (0) = 1, x ₁ ( n ) = 0, n =1, 2, ..., 30.

, где значение c _init может быть одним из следующих: x ₂ ( n ) is initialized as

, where the value of c _init can be one of the following:

.

.

c _init = n _{ID ,1} 2 ¹⁵ + n _{ID ,2} .

c _init = n _{ID ,1} 2 ¹⁵ + n _{ID ,2} + M ₂ .

Thus, in accordance with the description of Embodiment 5, the present specification proposes a method for at least partially preventing collisions between an SL channel scrambling sequence and a 5G-related (Release 15) channel scrambling sequence (such as PBCH, PUSCH, PUCCH, etc.). etc.), when initializing the scrambling sequence of the SL channel, which greatly reduces the possible mutual interference between the SL channel and the channel related to 5G (Release 15).

[Modified Embodiment]

Below in this document in FIG. 7 shows the user equipment that can execute the method executed by the user equipment described in detail above in the present description as a modified embodiment.

FIG. 7 is a block diagram of a user equipment (UE) related to the present disclosure.

As shown in FIG. 7, user equipment (UE) 80 includes a processor 801 and a storage device 802. The processor 801 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like. The storage device 802 may include, for example, volatile storage device (such as random access memory (RAM)), hard disk drive (HDD), non-volatile storage device (such as flash memory), or other storage devices. The storage device 802 stores program instructions. The instructions, when executed by the processor 801, may implement the aforementioned method executed by the user equipment detailed herein.

Methods and related devices in accordance with the present description are described above in conjunction with the preferred embodiments. Those skilled in the art should understand that the above methods are by way of example only and the above described embodiments can be combined with each other provided there is no incompatibility. The method of the present description is not limited to the steps and sequences described above. The network node and user equipment shown above may contain additional modules, for example, may further contain modules that may be developed or will be developed in the future for use in base station, MME or UE modules. The various identifiers shown above are by way of example only and are not restrictive, and the present description is not limited to specific information elements that exemplify such identifiers. Those skilled in the art may make various changes and modifications in accordance with the teachings of the illustrated embodiments.

It should be understood that the above embodiments of the present disclosure may be implemented using software, hardware, or a combination of software and hardware. For example, the various components of the base station and the user equipment in the above embodiments may be implemented by a variety of devices, including but not limited to: an analog circuit device, a digital circuit device, a digital signal processing (DSP) circuit, a programmable processor, a dedicated integrated circuit (ASIC), field programmable gate array (FPGA), complex programmable logic device (CPLD), etc.

In the present application, the term "base station" may mean a mobile communication data transmission and control switching center with a large transmitter power and a wide coverage area, which can perform the functions of scheduling resource allocation, receiving and transmitting data, etc. The term "user equipment" means a mobile user terminal such as a terminal device capable of wireless communication with a base station or micro base station, including a mobile phone, laptop, or the like.

In addition, the embodiments of the present disclosure described herein may be implemented on a computer program product. More specifically, a computer program product is a product provided with a computer-readable medium on which computer program logic is encoded. When executed on a computing device, the computer program logic provides the associated operations for implementing the technical solutions described above of the present disclosure. When executed on at least one processor of a computing system, computer program logic allows the processor to perform the operations (methods) described in the embodiments of the present disclosure. Such an arrangement of the present disclosure is typically provided in the form of software, code, and/or other data structures that are configured or encoded on a computer-readable medium, such as an optical medium (e.g., CD-ROM), floppy disk, or hard disk drive, or other media, for example, firmware or microcode on one or more ROM, RAM or PROM chips, or capable of downloading software images, a common database, etc. on one or more modules. Software or firmware or a similar configuration may be installed on the computing equipment so that one or more processors in the computing equipment perform the technical solutions described in the embodiments of the present disclosure.

In addition, each functional unit or each function of the base station device and the terminal device used in each of the above embodiments may be implemented or performed by an electrical circuit, which is usually one or a plurality of integrated circuits. Circuits capable of performing the various functions described herein may include general purpose processors, digital signal processing (DSP) circuits, application specific integrated circuits (ASICs), or general purpose integrated circuits, field programmable gate arrays (FPGAs) or other programmable logic devices, discrete circuits or transistorized logic circuits, or discrete hardware components, or any combination of the foregoing. The general purpose processor may be a microprocessor; or the processor may be an existing processor, controller, microcontroller, or state machine. The aforementioned general purpose processor or each circuit may be configured with a digital circuit, or may be configured with a logic circuit. In addition, when an improved technology emerges that can replace current integrated circuits due to advances in semiconductor technology, integrated circuits produced by this advanced technology may also be used in the present specification.

Although the present description includes the preferred embodiments described herein, those skilled in the art will appreciate that various modifications, substitutions, or changes may be made to the present description without departing from the spirit and scope of the present description. Accordingly, the present description is not to be defined by the above-described embodiments, but by the appended claims or their equivalents.

Claims (25)

1. User equipment for communication, comprising: processor and a storage device in electronic communication with the processor, wherein the instructions stored in the storage device are executed to: receive a random access response including a look-ahead command, the look-ahead command indicates an index value T _A in the form of a 12-bit look-ahead command field, the look-ahead command corresponds to a look-ahead group (TAG), the TAG being one of a plurality of TAGs; adjust, based on the advance value N _TA , the uplink transmission time for TAG with subcarrier spacing (SCS), wherein the advance value N _TA is determined based on i) the index value T _A and ii) the SCS configuration μ for the SCS, where the SCS is the SCS of the first uplink transmission after the user equipment receives the random access response; And determine a value regarding the minimum SCS among the SCSs of all configured uplink bandwidth portions (UL BWPs) for all uplink carriers in the TAG and for all configured initial UL BWPs, each provided with a higher layer parameter initialuplinkBWP , wherein the determined value is the value in ms corresponding to the maximum advance value for the minimum SCS that can be provided by the 12-bit advance command field, and uplink transmission time adjustment is applied from the starting point of the uplink interval, the uplink interval being based on a) the uplink interval in which the advance command is received, b) a certain value, c) a parameter N _{T ,1} representing a physical downlink shared data channel (PDSCH) processing time corresponding to PDSCH processing capabilities 1, d) a parameter N _{T ,2} representing a physical uplink shared data channel (PUSCH) preparation time corresponding to 1 PUSCH synchronization capabilities, e) parameter

, representing the number of slots in each subframe for the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG, and f) a T _sf parameter representing 1 millisecond. 2. A communication method performed by a user equipment, including: receiving a random access response including a look-ahead command indicating an index value T _A in the form of a 12-bit look-ahead command field, the look-ahead command corresponds to a look-ahead group (TAG), the TAG being one of a plurality of TAGs; correction, based on the advance value N _TA , of the uplink transmission time for TAG with subcarrier spacing (SCS), wherein the advance value N _TA is determined based on i) the index value T _A and ii) the SCS configuration μ for the SCS, where the SCS is the SCS of the first uplink transmission after the user equipment receives the random access response; And determining a value regarding the minimum SCS among the SCSs of all configured uplink bandwidth portions (UL BWPs) for all uplink carriers in the TAG and for all configured initial UL BWPs, each provided with a higher layer parameter initialuplinkBWP , wherein the determined value is the value in ms corresponding to the maximum advance value for the minimum SCS that can be provided by the 12-bit advance command field, and uplink transmission time adjustment is applied from the starting point of the uplink interval, the uplink interval being based on a) the uplink interval in which the advance command is received, b) a certain value, c) a parameter N _{T ,1} representing a physical downlink shared data channel (PDSCH) processing time corresponding to PDSCH processing capabilities 1, d) a parameter N _{T ,2} representing a physical uplink shared data channel (PUSCH) preparation time corresponding to 1 PUSCH synchronization capabilities, e) parameter

, representing the number of slots in each subframe for the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG, and f) a T _sf parameter representing 1 millisecond. 3. Base station for communication, comprising: processor and a storage device in electronic communication with the processor, wherein the instructions stored in the storage device are executed to: generate a random access response including a look-ahead command, the look-ahead command indicates an index value T _A in the form of a 12-bit look-ahead command field, the look-ahead command corresponds to a look-ahead group (TAG), where TAG is one of a plurality of TAGs; i) the index value T _A and ii) the sub-carrier spacing (SCS) configuration μ for the SCS are used by the user equipment to determine the advance value N _TA , based on which the user equipment adjusts the uplink transmission time for the TAG with the SCS, with the SCS being the SCS first. uplink transmissions after the user equipment receives the random access response; transmit a random access response to the user equipment; generate a higher-level parameter initialuplinkBWP , based on which the user equipment determines the value regarding the minimum SCS among the SCS of all configured parts of the uplink bandwidth (UL BWP) for all uplink carriers in the TAG and for all configured initial UL BWP, each of which provided by a higher-level parameter; And transmit a higher-level parameter to the user equipment, and the determined value is the value in ms corresponding to the maximum advance value for the minimum SCS that can be provided by the 12-bit advance command field, and uplink transmission time adjustment is applied from the starting point of the uplink interval, the uplink interval being based on a) the uplink interval in which the advance command is received, b) a certain value, c) a parameter N _{T ,1} representing a physical downlink shared data channel (PDSCH) processing time corresponding to PDSCH processing capabilities 1, d) a parameter N _{T ,2} representing a physical uplink shared data channel (PUSCH) preparation time corresponding to 1 PUSCH synchronization capabilities, e) parameter

, representing the number of slots in each subframe for the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG, and f) a T _sf parameter representing 1 millisecond.

Images