Sidelink synchronization method and apparatus, terminal, chip, and storage medium

Abstract

Provided in the embodiments of the present application is a sidelink synchronization method. The method comprises: on first frequency domain resources, a terminal sending or receiving sidelink synchronization signal blocks (S-SSBs), wherein the first frequency domain resources are some of frequency domain resources of a system. The method enables the sending or receiving of the S-SSB by using a portion of the frequency-domain resources in the system frequency-domain resources, so that the sending or receiving of the S-SSB can be performed over a relatively small bandwidth, thereby being able to take into consideration terminals with different capabilities in the same communication system, and ensuring that all the terminals can achieve synchronization.

Description

Sideline synchronization method, device, terminal, chip and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and specifically to a side synchronization method, device, terminal, chip and storage medium. Background Art

[0002] The sidelink (SL) synchronization process is a very important step in the SL system and occurs before SL communication. In existing SL technologies, it is assumed that all terminals in the system have the same capabilities, such as supporting the same bandwidth, transmission power, etc. Therefore, in the existing technology, the frequency domain resources and positions for sending / receiving the sidelink synchronization signal block (Sidelink Synchronization Signal Block, S-SSB) are supported by all terminals. For example, in the current sidelink transmission over unlicensed spectrum (Sidelink Over Unlicensed Spectrum, SL-U) system, if there are multiple resource block (RB) sets in the frequency domain, and S-SSB needs to be sent on multiple RB sets, then the terminal also needs to try to detect and receive S-SSB on multiple RB sets.

[0003] However, with the evolution of technology, supporting multiple terminals with different communication capabilities within the same communication system has become inevitable. Assuming all terminals have the same communication capabilities will create difficulties in SL synchronization between terminals with different capabilities. Therefore, when terminals with different capabilities coexist in the system, ensuring SL synchronization between them is a pressing issue.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a side synchronization method, device, terminal, chip, and storage medium.

[0006] In a first aspect, an embodiment of the present application provides a sidelink synchronization method, applied to a terminal, the method comprising: sending or receiving a sidelink synchronization signal block S-SSB on a first frequency domain resource; wherein the first frequency domain resource is part of the system frequency domain resources.

[0007] In the second aspect, an embodiment of the present application provides a sidelink synchronization device, which includes: a transceiver unit for sending or receiving a sidelink synchronization signal block S-SSB on a first frequency domain resource; wherein the first frequency domain resource is part of the system frequency domain resources.

[0008] In a third aspect, an embodiment of the present application provides a terminal including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned side synchronization method.

[0009] In a fourth aspect, an embodiment of the present application provides a chip for implementing the above-mentioned side synchronization method. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned side synchronization method.

[0010] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute the above-mentioned side synchronization method.

[0011] In a sixth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the above-mentioned side synchronization method.

[0012] In a seventh aspect, an embodiment of the present application provides a computer program, which, when running on a computer, enables the computer to execute the above-mentioned side synchronization method.

[0013] This method uses part of the system frequency domain resources to send or receive S-SSB, so that the transmission or reception of S-SSB can be performed on a relatively small bandwidth, thereby taking into account terminals with different capabilities in the same communication system, thereby ensuring that all terminals can achieve synchronization. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0015] FIG1 is a schematic diagram of sideline communication within network coverage provided by an embodiment of the present application;

[0016] FIG2 is a schematic diagram of sideline communication with partial network coverage provided by an embodiment of the present application;

[0017] FIG3 is a schematic diagram of sideline communication outside network coverage provided by an embodiment of the present application;

[0018] FIG4 is a schematic diagram of sideline communication with a central control node provided in an embodiment of the present application;

[0019] FIG5 is a schematic diagram of a unicast transmission method provided in an embodiment of the present application;

[0020] FIG6 is a schematic diagram of a multicast transmission method provided in an embodiment of the present application;

[0021] FIG7 is a schematic diagram of a broadcast transmission method provided in an embodiment of the present application;

[0022] FIG8 is a schematic diagram of the time slot structure in NR-V2X provided in an embodiment of the present application;

[0023] FIG9 is a schematic diagram showing changes in the OFDM symbols available in a time slot of a PSSCH in different transmissions provided by an embodiment of the present application;

[0024] FIG10 is a schematic diagram of a second-order SCI mapping method provided in an embodiment of the present application;

[0025] FIG11 is a schematic diagram of the time-frequency domain position of a PSCCH DMRS provided in an embodiment of the present application;

[0026] FIG12 is a schematic diagram of the time domain position of 4 DMRS symbols when the PSSCH has 13 symbols provided in an embodiment of the present application;

[0027] FIG13 is a schematic diagram of a single-symbol DMRS frequency domain type 1 provided in an embodiment of the present application;

[0028] FIG14 is a schematic diagram of the time-frequency position of the SL CSI-RS provided in an embodiment of the present application;

[0029] FIG15 is a schematic diagram of an example of channel occupancy time and channel occupancy provided in an embodiment of the present application;

[0030] FIG16 is a schematic diagram of frequency domain resource division provided in an embodiment of the present application;

[0031] FIG17 is a flow chart of a side synchronization method according to an embodiment of the present application;

[0032] FIG18 is a schematic diagram of a frequency domain resource design solution for S-SSB provided in an embodiment of the present application;

[0033] FIG19 is a second schematic diagram of a frequency domain resource design scheme for S-SSB provided in an embodiment of the present application;

[0034] FIG20 is a schematic diagram of the structure of a lateral synchronization device provided in an embodiment of the present application;

[0035] FIG21 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0036] FIG22 is a schematic structural diagram of a chip according to an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0038] The technical solutions of the embodiments of the present application can be applied to various side communication systems. To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are explained below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0039] 1. Sideline communication in different network coverage environments

[0040] In side communication, according to the network coverage of the communicating terminal, it can be divided into side communication within the network coverage, side communication with partial network coverage, side communication outside the network coverage, and side communication with a central control node, as shown in Figures 1, 2, 3 and 4 respectively.

[0041] As shown in FIG1 , in sideline communications within network coverage, all terminals performing sideline communications are within the coverage of the same base station. Thus, the above terminals can perform sideline communications based on the same sideline configuration by receiving configuration signaling from the base station.

[0042] As shown in Figure 2, in the case of sidelink communication with partial network coverage, some terminals performing sidelink communication are located within the coverage of the base station. These terminals can receive the configuration signaling from the base station and perform sidelink communication according to the configuration of the base station. However, terminals located outside the network coverage cannot receive the configuration signaling from the base station. In this case, the terminals outside the network coverage will determine the sidelink configuration based on the pre-configuration information and the information carried in the Physical Sidelink Broadcast Channel (PSBCH) sent by the terminals within the network coverage, thereby performing sidelink communication.

[0043] As shown in FIG3 , for sideline communications outside network coverage, all terminals performing sideline communications are located outside network coverage, and all terminals determine sideline configurations according to pre-configured information and perform sideline communications.

[0044] As shown in Figure 4 , for sideline communication with a central control node, multiple terminals form a communication group, which includes a central control node, such as UE1 in Figure 4 . The central control node can also be called a cluster header (CH). The central control node has at least one of the following functions, but is not limited to: establishing the communication group; managing the joining and leaving of group members; coordinating resources, allocating sideline transmission resources to other terminals, receiving sideline feedback information from other terminals, and coordinating resources with other communication groups.

[0045] 2. Device to Device (D2D) / Vehicle to Everything (V2X)

[0046] Device-to-device communication is a sidelink transmission technology based on D2D. Unlike traditional cellular systems, where communication data is received or sent via base stations, it offers higher spectrum efficiency and lower transmission latency. The connected vehicle system utilizes direct end-to-end communication. The 3rd Generation Partnership Project (3GPP) defines two transmission modes: Mode 1 and Mode 2.

[0047] Mode 1: The terminal's transmission resources are allocated by the base station, and the terminal transmits data on the sidelink based on the allocated resources. The base station can allocate resources for either single transmissions or semi-static transmissions. As shown in Figure 1, when the terminal is within network coverage, the network allocates transmission resources for sidelink transmissions.

[0048] Mode 2: The terminal selects a resource from the resource pool for data transmission. As shown in Figure 3, when the terminal is outside the cell coverage area, it autonomously selects a transmission resource from the pre-configured resource pool for sidelink transmission. Alternatively, as shown in Figure 1, the terminal autonomously selects a transmission resource from the network-configured resource pool for sidelink transmission.

[0049] 3. New Radio-Vehicle to Everything (NR-V2X)

[0050] In NR-V2X, autonomous driving needs to be supported, which places higher requirements on data interaction between vehicles, such as higher throughput, lower latency, higher reliability, larger coverage, and more flexible resource allocation.

[0051] LTE-V2X supports broadcast transmission, while NR-V2X introduces unicast and multicast transmission modes. For unicast transmission, there is only one receiving terminal. For example, in Figure 5, unicast transmission is performed between UE1 and UE2. For multicast transmission, the receiving terminals are all terminals in a communication group, or all terminals within a certain transmission distance. As shown in Figure 6, UE1, UE2, UE3, and UE4 form a communication group, where UE1 transmits data, and the other terminal devices in the group are all receiving terminals. For broadcast transmission, the receiving terminal is any terminal around the transmitting terminal. As shown in Figure 7, UE1 is the transmitting terminal, and the other terminals around it, UE2 to UE6, are all receiving terminals.

[0052] 4. NR-V2X system frame structure

[0053] The time slot structure in NR-V2X is shown in Figure 8:

[0054] FIG8(a) is a schematic diagram of a time slot structure in which a physical sidelink feedback channel (PSFCH) is not included in the time slot; FIG8(b) is a schematic diagram of a time slot structure in which a PSFCH is included.

[0055] The NR-V2X Physical Sidelink Control Channel (PSCCH) starts at the second sidelink symbol of the timeslot in the time domain, occupies 2 or 3 Orthogonal Frequency Division Multiplexing (OFDM) symbols, and can occupy {10, 12, 15, 20, 25} Physical Resource Blocks (PRBs) in the frequency domain. To reduce the complexity of blind detection of the PSCCH by the user equipment (UE), only one number of PSCCH symbols and PRBs is allowed to be configured in a resource pool. In addition, because the subchannel is the minimum granularity for the allocation of physical sidelink shared channel (PSSCH) resources in NR-V2X, the number of PRBs occupied by the PSCCH must be less than or equal to the number of PRBs contained in a subchannel in the resource pool to avoid additional restrictions on PSSCH resource selection or allocation. In the time domain, the PSSCH also begins with the second sidelink symbol of the timeslot. The last time-domain symbol in the timeslot is the guard period (GP) symbol, and the remaining symbols are mapped to the PSSCH. The first sidelink symbol in the timeslot is a repetition of the second sidelink symbol. The receiving terminal typically uses the first sidelink symbol as an automatic gain control (AGC) symbol; the data on this symbol is not typically used for data demodulation. In the frequency domain, the PSSCH occupies K subchannels, each consisting of N consecutive PRBs.

[0056] When a time slot contains a PSFCH channel, the second to last and third to last symbols in the time slot are used for PSFCH channel transmission, and a time domain symbol before the PSFCH channel is used as a GP symbol, as shown in FIG8 (b).

[0057] 5. Sidelink PSSCH

[0058] In NR-V2X, the PSSCH is used to carry second-order sidelink control information (SCI) (SCI 2-A or SCI 2-B) and data information. The second-order SCI uses polarization coding and fixed quadrature phase shift keying (QPSK) modulation. The data portion of the PSSCH uses low-density parity check (LDPC) code, and the highest supported modulation order is 256QAM.

[0059] In NR-V2X, PSSCH supports up to two stream transmissions and uses a unit precoding matrix to map data on two layers to two antenna ports. At most, only one transport block (TB) can be sent in a PSSCH. However, unlike the transmission method of the PSSCH data part, when PSSCH adopts a dual-stream transmission method, the modulation symbols sent by the second-order SCI on the two streams are exactly the same. This design can ensure the reception performance of the second-order SCI in highly correlated channels.

[0060] Since the maximum number of retransmissions of a PSSCH in NR-V2X is 32, if there are PSFCH resources in the resource pool and the configuration period of PSFCH resources is 2 or 4, the available OFDM symbols in the time slot where different transmissions of a PSSCH are located may change, as shown in Figure 9. If calculated based on the actual number of OFDM symbols in a time slot The difference in the number of symbols available for PSSCH transmission in a time slot may cause Q′ SCI2 Different, and Q′ SCI2 The change of will lead to the change of the size of the TB carried by PSSCH. In order to ensure that the transmission block size (TBS) remains unchanged during multiple transmissions of PSSCH, The actual number of PSFCH symbols is not used. The number of resource elements (REs) occupied by the PSSCH demodulation reference signal (DMRS) and the number of REs occupied by the phase-tracking reference signal (PT-RS), which may change during the retransmission process, are not taken into account.

[0061] The code rate of the second-order SCI can be dynamically adjusted within a certain range. The specific code rate used is indicated by the first-order SCI, so the receiver does not need to perform blind detection of the second-order SCI even after the code rate changes. The modulation symbols of the second-order SCI are mapped in the frequency domain first and then in the time domain, starting from the symbol containing the first PSSCH DMRS. In the OFDM symbol containing the DMRS, the second-order SCI is mapped to the REs not occupied by the DMRS, as shown in Figure 10.

[0062] The data portion of the PSSCH within a resource pool can use multiple different modulation and coding scheme (MCS) tables, including the conventional 64QAM MCS table, the 256QAM MCS table, and the low-spectrum-efficiency 64QAM MCS table. The specific MCS table used in a transmission is indicated by the "MCS table indication" field in the first-order SCI. To control the Peak to Average Power Ratio (PAPR), the PSSCH must be transmitted using contiguous PRBs. Since the subchannel is the minimum frequency-domain resource granularity of the PSSCH, this requires that the PSSCH must occupy contiguous subchannels.

[0063] 6. Sidelink transmission block size

[0064] PSSCH follows the transport block size (TBS) determination mechanism of the physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) in the New Radio (NR), that is, the TBS is determined based on the reference value of the number of REs used for PSSCH in the time slot where the PSSCH is located, so that the actual code rate is as close to the target code rate as possible. The purpose of using the reference value of the number of REs instead of the actual number of REs here is to ensure that the number of REs used to determine the TBS remains unchanged during the PSSCH retransmission process, so that the determined TBS size is the same. To achieve this goal, the reference value N of the number of REs occupied by PSSCH in the TBS determination process is used. RE Determine according to formula (1):

[0065] where n PRB is the number of PRBs occupied by PSSCH, is the number of REs occupied by the first-order SCI (including the REs occupied by the DMRS of the PSCCH), is the number of REs occupied by the second-order SCI, N′ RErepresents the number of reference REs that can be used for PSSCH in a PRB, which is determined by formula (2):

[0066] in: Indicates the number of subcarriers in a PRB; Indicates the number of symbols available for sidelink in a time slot, excluding the last GP symbol and the first symbol used for AGC. or 3. The specific value is indicated by the "PSFCH symbol number" field in the first-order SCI, which is the reference value of the number of symbols occupied by PSFCH. The value of is configured by the Radio Resource Control (RRC) layer parameters and is used to indicate the reference value of the number of REs occupied by PT-RS and CSI-RS. It represents the average number of DMRS REs in a time slot and is related to the DMRS patterns allowed in the resource pool, as shown in Table 1.

[0067] Table 1 DMRS patterns allowed in the resource pool and The corresponding relationship

[0068] 7. Sidelink DMRS

[0069] In NR-V2X, the DMRS pattern of the PSCCH is the same as that of the NR physical downlink control channel (PDCCH). That is, the DMRS exists in each OFDM symbol of the PSCCH and is located in the frequency domain at {#1, #5, #9} REs of a PRB, as shown in Figure 11. The DMRS sequence of the PSCCH is generated by formula (3):

[0070] The pseudo-random sequence c(m) is given by Initialize, where l is the index of the OFDM symbol where the DMRS is located in the time slot, is the index of the time slot where the DMRS is located in the system frame, Indicates the number of OFDM symbols in a time slot, N ID ∈{0,1,...,65535}, in a resource pool N ID The specific value is configured or pre-configured by the network.

[0071] NR-V2X draws on the design of the NR Uu interface and adopts multiple time-domain PSSCH DMRS patterns. The number of available DMRS patterns within a resource pool is related to the number of PSSCH symbols in the resource pool. For a specific number of PSSCH symbols (including the first AGC symbol) and PSCCH symbols, the available DMRS patterns and the position of each DMRS symbol within the pattern are shown in Table 2. Figure 12 shows a schematic diagram of the time-domain position of four DMRS symbols when the PSSCH has 13 symbols.

[0072] Table 2 Number and position of DMRS symbols under different PSSCH and PSCCH symbol numbers

[0073] If multiple time-domain DMRS patterns are configured within the resource pool, the transmitting UE selects the specific time-domain DMRS pattern to use and indicates this in the first-order SCI. This design allows high-speed UEs to select a high-density DMRS pattern, thereby ensuring accurate channel estimation, while low-speed UEs can use a low-density DMRS pattern, thereby improving spectrum efficiency.

[0074] The generation method of the PSSCH DMRS sequence is almost identical to that of the PSCCH DMRS sequence. The only difference is the initialization formula c(m) of the pseudo-random sequence. init middle, p i The i-th cyclic redundancy check (CRC) of the PSCCH that schedules the PSSCH, where L=24 is the number of bits of the PSCCH CRC.

[0075] NR PDSCH and PUSCH support two frequency domain DMRS patterns, namely DMRS frequency domain type 1 and DMRS frequency domain type 2. For each frequency domain type, there are two different types: single DMRS symbol and double DMRS symbol. Single symbol DMRS frequency domain type 1 supports 4 DMRS ports, single symbol DMRS frequency domain type 2 can support 6 DMRS ports, and in the case of double DMRS symbols, the number of supported ports is doubled. However, in NR-V2X, since PSSCH only needs to support a maximum of two DMRS ports, only single symbol DMRS frequency domain type 1 is supported, as shown in Figure 13.

[0076] 8. Sidelink Channel State Information Reference Signal (CSI-RS)

[0077] To better support unicast communication, NR-V2X supports SL CSI-RS. SL CSI-RS is sent only when the following three conditions are met:

[0078] 1) The UE sends the corresponding PSSCH, that is, the UE cannot only send SL CSI-RS;

[0079] 2) Sidelink CSI reporting is activated by higher-layer signaling;

[0080] 3) When sidelink CSI reporting is activated by higher layer signaling, the corresponding bit in the second-order SCI sent by the UE triggers the sidelink CSI reporting.

[0081] The maximum number of ports supported by SL CSI-RS is two. For two ports, SL CSI-RSs from different ports are code-division multiplexed across two adjacent REs in the same OFDM symbol. Within a PRB, the number of SL CSI-RSs per port is one, meaning the density is one. Therefore, within a PRB, an SL CSI-RS appears in at most one OFDM symbol, the specific location of which is determined by the transmitting terminal. To avoid impacting the resource mapping of the PSCCH and second-order SCI, the SL CSI-RS cannot be located in the same OFDM symbol as the PSCCH and second-order SCI. Because the channel estimation accuracy of the OFDM symbol where the PSSCH DMRS resides is higher, and the SL CSI-RSs for two ports occupy two consecutive REs in the frequency domain, the SL CSI-RS cannot be transmitted in the same OFDM symbol as the PSSCH DMRS. The OFDM symbol location of the SL CSI-RS is indicated by the sl-CSI-RS-FirstSymbol parameter in the PC5RRC protocol.

[0082] The position of the first RE occupied by the SL CSI-RS within a PRB is indicated by the sl-CSI-RS-FreqAllocation parameter in the PC5RRC. If the SL CSI-RS is a single port, this parameter is a 12-bit bitmap corresponding to the 12 REs within a PRB. If the SL CSI-RS is a dual port, this parameter is a 6-bit bitmap. In this case, the SL CSI-RS occupies two REs, 2f(1) and 2f(1)+1, where f(1) represents the index of the bit with a value of 1 in the bitmap. The frequency domain position of the SL CSI-RS is also determined by the transmitting terminal, but the determined frequency domain position of the SL CSI-RS cannot conflict with the PT-RS. FIG14 shows a schematic diagram of the time-frequency position of an SL CSI-RS. In FIG14 , the number of SL CSI-RS ports is 2, the sl-CSI-RS-FirstSymbol is 8, and the sl-CSI-RS-FreqAllocation is [b5, b4, b3, b2, b1, b0] = [0, 0, 0, 1, 0, 0].

[0083] 9. 5G unlicensed (unlicensed) spectrum communications (NR-unlicensed, NR-U)

[0084] The NR system introduced by the 3GPP R15 standard is a communication technology for use on existing and new licensed spectrum. The NR system can achieve seamless coverage, high spectrum efficiency, high peak rate and high reliability of cellular networks. In the Long Term Evolution (LTE) system, unlicensed spectrum (or unlicensed spectrum) has been used as a supplementary frequency band to the licensed spectrum for cellular networks. Similarly, the NR system can also use unlicensed spectrum as part of 5G cellular network technology to provide services to users. In the 3GPP R16 standard, the NR system for unlicensed spectrum, called NR-unlicensed (NR-U), was discussed.

[0085] The NR-U system supports two networking modes: licensed spectrum assisted access and unlicensed spectrum independent access. The former requires the use of licensed spectrum to access the network, and the unlicensed spectrum is used as a secondary carrier; the latter can be independently networked through unlicensed spectrum, and the UE can directly access the network through the unlicensed spectrum. The range of unlicensed spectrum used by the NR-U system introduced in 3GPP R16 is concentrated in the 5GHz and 6GHz frequency bands, such as 5925-7125MHz in the United States, or 5925-6425MHz in Europe. In the R16 standard, band 46 (5150MHz-5925MHz) is newly defined for use as unlicensed spectrum.

[0086] Unlicensed spectrum is spectrum designated by countries and regions for use by radio equipment. This spectrum is generally considered shared spectrum, meaning that as long as communications devices meet national or regional regulatory requirements for the spectrum, they can use it without having to apply for exclusive spectrum authorization from the national or regional spectrum management agency. Because the use of unlicensed spectrum must comply with specific national and regional regulations, such as the "Listen Before Talk" (LBT) principle, NR technology requires corresponding enhancements to meet regulatory requirements for unlicensed frequency bands and efficiently utilize unlicensed spectrum to provide services. The 3GPP Release 16 standard primarily standardizes the following aspects of NR-U technology: channel sensing process; initial access process; control channel design; Hybrid Automatic Repeat Request (HARQ) and scheduling; and scheduling-free grant transmission.

[0087] 10. Channel monitoring: LBT

[0088] To ensure the harmonious coexistence of various communication systems using unlicensed spectrum for wireless communications, some countries and regions have established regulatory requirements for the use of unlicensed spectrum. For example, according to European regulations, when communicating on unlicensed spectrum, communication devices must adhere to the "LBT" principle. This means that before transmitting signals on a channel in the unlicensed spectrum, they must first perform LBT, or channel sensing. Only if the channel sensing result indicates that the channel is idle, or if LBT is successful, can the communication device transmit signals on that channel. If the channel sensing result indicates that the channel is busy, or if LBT fails, the communication device cannot transmit signals on that channel. Furthermore, to ensure fair use of shared spectrum resources, if a communication device successfully performs LBT on an unlicensed spectrum channel, the duration for which it can use that channel for communication cannot exceed a certain limit. This mechanism, by limiting the maximum duration of communication after a successful LBT, ensures that different communication devices have the opportunity to access the shared channel, thereby enabling harmonious coexistence of different communication systems on the shared spectrum.

[0089] Although channel sensing is not a global regulatory requirement, it can provide interference avoidance and friendly coexistence benefits for communication transmissions between communication systems on shared spectrum. Therefore, in the design of NR systems on unlicensed spectrum, channel sensing is a feature that must be supported by the communication equipment in the system. From the perspective of system networking, channel sensing includes two mechanisms: load-based equipment (LBE) LBT, also known as dynamic channel sensing or dynamic channel occupancy, and frame-based equipment (FBE) LBT, also known as semi-static channel sensing or semi-static channel occupancy.

[0090] 11. Dynamic channel monitoring

[0091] Dynamic channel monitoring can also be considered as an LBT method based on LBE, and its channel monitoring principle is that the communication equipment performs LBT on the carrier of the unlicensed spectrum after the service arrives, and starts sending signals on the carrier after the LBT is successful. The LBT method of dynamic channel monitoring includes Type 1 (Type1) channel access method and Type 2 (Type2) channel access method. The Type 1 channel access method is a multi-slot channel detection with random backoff based on the adjustment of the contention window size, wherein the corresponding channel access priority (Channel Access Priority Class, CAPC) p can be selected according to the priority of the service to be transmitted. The Type 2 channel access method is a channel access method based on a fixed-length monitoring time slot, wherein the Type 2 channel access method includes Type 2A channel access, Type 2B channel access and Type 2C channel access. The Type 1 channel access method is mainly used for communication equipment to initiate channel occupancy, and the Type 2 channel access method is mainly used for communication equipment to share channel occupancy. A special case that needs to be explained is that when the base station initiates channel occupancy for the synchronization signal / physical broadcast channel (SS / PBCH) block within the Discovery Reference Symbol (DRS) window and the DRS window does not include UE unicast data transmission, if the length of the DRS window does not exceed 1ms and the duty cycle of the DRS window transmission does not exceed 1 / 20, then the base station can use Type2A channel access to initiate channel occupancy.

[0092] FIG15 shows an example of a channel occupancy time obtained by a communication device after successful LBT on a channel of an unlicensed spectrum and signal transmission using resources within the channel occupancy time.

[0093] 12. Default channel access mode on the base station side: Type 1 channel access

[0094] Taking the base station as an example, the channel access parameters corresponding to the channel access priority p on the base station side are shown in Table 3. In Table 3, m p It refers to the number of fallback slots corresponding to the channel access priority p, and CWp refers to the contention window (CW) size corresponding to the channel access priority p. min,p Refers to the CW corresponding to the channel access priority p p Minimum value, CW max,p Refers to the CW corresponding to the channel access priority p p The maximum value, T mcot,p It refers to the maximum channel occupancy time corresponding to the channel access priority p.

[0095] If the channel access process is completed, the base station can use the channel to transmit the service to be transmitted. The maximum time length that the base station can use the channel for transmission cannot exceed T mcot,p .

[0096] Table 3 Channel access parameters corresponding to different channel access priorities p

[0097] 13. Channel occupancy time sharing on the base station side

[0098] When the base station initiates the Channel Occupancy Time (COT), in addition to using the resources within the COT for downlink transmission, the resources within the COT can also be shared with the UE for uplink transmission. When the resources within the COT are shared with the UE for uplink transmission, the channel access mode that the UE can use is Type 2A channel access, Type 2B channel access, or Type 2C channel access. Among them, Type 2A channel access, Type 2B channel access, and Type 2C channel access are all channel access modes based on fixed-length monitoring time slots.

[0099] Type 2A channel access:

[0100] The UE uses a 25μs single-slot channel detection method. Specifically, under Type 2A channel access, the UE can monitor the channel for 25μs before starting transmission and transmit after successful channel monitoring.

[0101] Type 2B channel access:

[0102] The UE uses a 16μs single-slot channel detection method. Specifically, in Type 2B channel access, the UE can monitor the channel for 16μs before starting transmission and transmit after successful channel monitoring. The gap between the start position of each transmission and the end position of the previous transmission is 16μs.

[0103] Type 2C channel access:

[0104] The UE transmits after the gap ends without performing channel detection. Specifically, under Type 2C channel access, the UE can directly transmit, where the gap between the start position of the transmission and the end position of the previous transmission is less than or equal to 16μs. The length of the transmission does not exceed 584μs.

[0105] 14. Channel access parameter indication (including cyclic prefix extension (CPE))

[0106] In the NR-U system, when the UE is scheduled to transmit the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH), the base station can indicate the channel access method corresponding to the PUSCH or PUCCH by carrying the downlink control information (DCI) of the uplink grant (UL grant) or downlink grant (DL grant). Since some channel access methods need to meet the gap requirements of 16μs or 25μs, the UE can ensure the gap size between two transmissions by transmitting an extended cyclic prefix (CPE). Accordingly, the base station can indicate the CPE length of the first symbol of the UE's uplink transmission.

[0107] When specifically indicating, the base station can explicitly indicate channel access parameters such as CPE length, channel access mode or channel access priority to the UE through joint coding. The following describes the characteristics of the indication mode of channel access parameters introduced in different DCI formats.

[0108] 1) Fallback uplink grant for scheduling PUSCH transmission (DCI format 0_0):

[0109] The standard pre-sets a set of joint channel access mode and CPE length indications, as shown in Table 4. The fallback uplink grant includes 2-bit LBT indication information, which is used to indicate the jointly coded channel access mode and CPE length from the set shown in Table 4. The channel access mode and CPE length are used for PUSCH transmission. If the channel access mode is Type 1 channel access, the UE selects the channel access priority (CAPC) based on the service priority.

[0110] 2) Fallback downlink grant for scheduling PDSCH transmission (DCI format 1_0):

[0111] The standard presets a set of joint indications of channel access mode and CPE length, as shown in Table 4. The fallback downlink grant includes 2-bit LBT indication information, which is used to indicate the jointly coded channel access mode and CPE length from the set shown in Table 4. The channel access mode and CPE length are used for PUCCH transmission, where the PUCCH can carry a positive acknowledgment (ACK) or negative acknowledgment (NACK) corresponding to the PDSCH. If the channel access mode is Type 1 channel access, the UE determines the channel access priority CAPC = 1 for transmitting the PUCCH.

[0112] Table 4 Channel access mode and CPE length joint indication set

[0113] In Table 4, the value of C1 is specified by the protocol. When the subcarrier spacing is 15 kHz and 30 kHz, C1 = 1; when the subcarrier spacing is 60 kHz, C1 = 2. The values ​​of C2 and C3 are configured by higher-layer parameters. When the subcarrier spacing is 15 kHz and 30 kHz, the values ​​of C2 and C3 range from 1 to 28; when the subcarrier spacing is 60 kHz, the values ​​of C2 and C3 range from 2 to 28.

[0114] 3) Non-fallback uplink grant for scheduling PUSCH transmission (DCI format 0_1):

[0115] The higher layer configures an LBT parameter indication set, which includes at least one jointly coded channel access method, CPE length, and CAPC. The non-fallback uplink grant includes LBT indication information, which is used to indicate the jointly coded channel access method, CPE length, and CAPC from the above-mentioned LBT parameter indication set. The channel access method, CPE length, and CAPC are used for PUSCH transmission. If the indicated channel access method is Type 2 channel access, the CAPC indicated at the same time is the CAPC used by the base station when obtaining the COT. The LBT indication information includes a maximum of 6 bits.

[0116] 4) Non-fallback downlink grant for scheduling PDSCH transmission (DCI format 1_1):

[0117] The high layer configures an LBT parameter indication set, and the LBT parameter indication set includes at least one jointly coded channel access method and CPE length. The non-fallback downlink authorization includes LBT indication information, and the LBT indication information is used to indicate the jointly coded channel access method and CPE length from the above-mentioned LBT parameter indication set. The channel access method and CPE length are used for PUCCH transmission, wherein the PUCCH can carry ACK or NACK information corresponding to the PDSCH. If the channel access method is Type 1 channel access, the UE determines that the channel access priority CAPC=1 for transmitting the PUCCH. The LBT indication information includes a maximum of 4 bits.

[0118] In addition to the above explicit indications, the base station can also implicitly indicate the channel access method within the COT. When the UE receives an UL grant or DL ​​grant sent by the base station indicating that the channel access type corresponding to the PUSCH or PUCCH is Type 1 channel access, if the UE can determine that the PUSCH or PUCCH belongs to the COT of the base station, for example, the UE receives a DCI format 2_0 sent by the base station and determines that the PUSCH or PUCCH belongs to the COT of the base station based on the DCI format 2_0, then the UE can update the channel access type corresponding to the PUSCH or PUCCH to Type 2A channel access instead of Type 1 channel access.

[0119] 15. Channel access parameter indication (including CPE)

[0120] The frequency domain resource division of the sidelink is similar to that of Uu, as shown in Figure 16. When there are multiple carriers in the frequency domain resources, the terminal and the system need to support the carrier aggregation function. The system can also only support a single-carrier scenario, in which case carrier aggregation is not required. The frequency resources of a carrier can be divided into one or more bandwidth parts (Band Width Part, BWP). Currently, when there are multiple BWPs in the frequency domain, only one BWP can be activated at the same time, and in the SL system, the system currently only supports one sidelink bandwidth part (SL BWP). In the NR-U (unlicensed band) system, a BWP is divided into multiple RB sets (sets), each RB set is 20MHz in size, and an RB set is the smallest unit of LBT. For example, in Figure 16, BWP 1 is divided into RB set 0 to RB set 4.

[0121] The above briefly explains the relevant technologies / terms involved in the embodiments of this application, which will not be repeated in the following embodiments.

[0122] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the objects associated before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). This application does not limit its specific implementation method.

[0123] It should also be understood that the terminal in the embodiments of the present application may refer to an access terminal, user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal device, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.

[0124] Existing SL technologies assume that all terminals in the system have the same capabilities, such as supporting the same bandwidth and transmit power. Therefore, in existing technologies, the frequency domain resources and locations for transmitting / receiving S-SSBs are supported by all terminals. For example, in the current SL-U system, if there are multiple RB sets in the frequency domain, and S-SSBs need to be transmitted on multiple RB sets, then the terminal must also attempt to detect and receive S-SSBs on multiple RB sets.

[0125] With the evolution of technology, supporting multiple terminal devices with different communication capabilities within the same communication system has become an inevitable problem. If we continue to assume that all terminals have the same communication capabilities, it will cause certain difficulties for communication with terminals with weak capabilities (such as smart watches, wristbands, AR / VR glasses, etc.). For example, weak-capability terminals generally cannot support the same bandwidth as mobile phones. For example, a mobile phone supports a bandwidth of 100MHz, while the smart watch communicating with it can only support a maximum bandwidth of 5MHz or 20MHz. As a result, in real-world communication scenarios, the following problems will arise due to the unequal terminal capabilities (bandwidth):

[0126] 1) When a fully capable terminal (such as a mobile phone) communicates with a weak-capability terminal, if the communication bandwidth of the fully capable terminal is reduced to ensure normal communication of the weak-capability terminal, it will lead to system bandwidth congestion and waste of bandwidth resources.

[0127] 2) If full-capability terminals still use full-bandwidth communication, weak-capability terminals will not be able to participate. For example, if a full-capability terminal sends data via broadcast or multicast, a weak-capability terminal, as the receiving end, will not be able to receive the data at full bandwidth.

[0128] The SL synchronization process, as a very important link and step in the SL system, occurs before SL communication. It is very efficient to consider a solution for the synchronization process and sending / receiving S-SSB to solve the communication problem between terminals with different capabilities. Because the steps of the synchronization process are simple, the amount of data sent and received is small, and the resources occupied are small, so the sending / receiving of S-SSB is placed on a smaller bandwidth for operation, terminal devices with different capabilities can be taken into account at the same time, thereby ensuring that all devices can be synchronized. The subsequent communication process, due to the difference in service type and data volume, can be discussed separately from the solution of this application.

[0129] In view of this, the present application provides a sideline synchronization method, apparatus, terminal, chip, and storage medium. The method can be executed, for example, by a terminal, or by a chip, chip system, or circuit configured in the terminal, though this is not a limitation in the present application. For ease of description, the following description uses execution by a terminal as an example.

[0130] In this method, the terminal may send or receive an S-SSB on a first frequency domain resource, where the first frequency domain resource is part of the system frequency domain resources. By using part of the system frequency domain resources to send or receive the S-SSB, the method enables the transmission or reception of the S-SSB to be performed over a relatively small bandwidth, thereby taking into account terminals with different capabilities in the same communication system, thereby ensuring that all terminals can achieve synchronization.

[0131] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0132] FIG17 is a flow chart of a side synchronization method according to an embodiment of the present application. As shown in FIG17 , the side synchronization method may include the following steps:

[0133] S1701, the terminal sends or receives S-SSB on the first frequency domain resources; wherein the first frequency domain resources are part of the frequency domain resources in the system frequency domain resources.

[0134] The first frequency domain resource can be determined, for example, by definition, preconfiguration, or network configuration. The first frequency domain resource can be used as a common frequency domain resource between different terminals in the communication system for transmitting or receiving S-SSBs. In other words, each terminal must at least transmit or receive S-SSBs on the first frequency domain resource.

[0135] Exemplarily, there may be multiple terminal devices with different capabilities in a communication system. Among them, the first frequency domain resource can be determined according to the capabilities of different terminals in the communication system. For example, each terminal can report its own capabilities to the network device, so that the network device can configure the first frequency domain resource by comprehensively considering the capabilities of each terminal. As an example, the first frequency domain resource configured by the network device needs to take into account the terminals with weaker capabilities in the communication system, so that the terminals with weaker capabilities can at least have the ability to send / receive S-SSB on the first frequency domain resource, and then ensure that all terminals can achieve synchronization on the premise of taking into account the terminals with weak capabilities. As another example, each terminal can be pre-configured with a relatively small common frequency domain resource for S-SSB transmission or reception to take into account the terminals with weaker capabilities in the communication system.

[0136] For the convenience of description, in the embodiments of the present application, the terminal with stronger capabilities is referred to as the first type of terminal, and the terminal with weaker capabilities is referred to as the second type of terminal. Among them, the first type of terminal can also be called a terminal with full capabilities or a high-capability terminal (such as a mobile phone); the second type of terminal can also be called a weak-capability terminal (such as a smart watch, a smart bracelet, AR / VR glasses, etc.). Generally, the bandwidth supported by the second type of terminal for sending / receiving information is relatively small, or rather, the second type of terminal can support sending / receiving information on a sub-bandwidth, but cannot support sending / receiving information on the full bandwidth. In addition, in some scenarios, the transmission power of the second type of terminal is also small, and the encoding / decoding capabilities may also be limited.

[0137] The following introduces several possible implementation manners of the sidelink synchronization method in the embodiments of the present application:

[0138] In the first implementation manner (denoted as implementation manner #1), the system frequency domain resource may include multiple S-SSB frequency domain resources in an SL BWP; the first frequency domain resource is part of the multiple S-SSB frequency domain resources.

[0139] For example, assume that the system supports an SL BWP and supports N (N>1) S-SSB frequency domain resources included in the SL BWP, or rather, the system frequency domain resource includes N S-SSB frequency domain resources in an SL BWP. Then, the first frequency domain resource can be, for example, N1 (N1<N) S-SSB frequency domain resources among the N S-SSB frequency domain resources. Among them, the value of N1 can be determined by definition, pre-configuration or network configuration.

[0140] In some embodiments, the frequency domain positions and / or the number of the multiple S-SSB frequency domain resources are pre-configured or network-configured. For example, when the system frequency domain resource includes N S-SSB frequency domain resources in an SL BWP, the frequency domain positions and / or the number (i.e., the value of N) of the N S-SSB frequency domain resources are pre-configured or network-configured.

[0141] As an example, when the multiple (such as N) S-SSB frequency domain resources are continuously distributed, the frequency domain positions of the multiple S-SSB frequency domain resources can be determined based on the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources. That is to say, when the starting position of the first S-SSB frequency domain resource and the total length of all S-SSB frequency domain resources are determined, the frequency domain positions of the multiple continuously distributed S-SSB frequency domain resources can be determined.

[0142] As another example, when the multiple (e.g., N) S-SSB frequency domain resources are non-continuously distributed, the frequency domain positions of the multiple S-SSB frequency domain resources may be determined based on the starting position and length of each S-SSB frequency domain resource. That is, when the starting position and length of each S-SSB frequency domain resource are determined, the frequency domain positions of the multiple non-continuously distributed S-SSB frequency domain resources may be determined.

[0143] As another example, when the multiple (such as N) S-SSB frequency domain resources are distributed non-continuously, the frequency domain positions of the multiple S-SSB frequency domain resources can be determined based on the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval between two adjacent S-SSB frequency domain resources. That is to say, when the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval between two adjacent S-SSB frequency domain resources are determined, the frequency domain positions of the multiple non-continuously distributed S-SSB frequency domain resources can be determined. Among them, the total length of the multiple S-SSB frequency domain resources can refer to the length between the starting position of the first S-SSB frequency domain resource and the ending position of the last S-SSB frequency domain resource in the multiple S-SSB frequency domain resources, or it can also refer to the sum of the lengths of each S-SSB frequency domain resource in the multiple S-SSB frequency domain resources.

[0144] Exemplarily, the interval between the two adjacent S-SSB frequency domain resources can be indicated by the number of subchannels or resource blocks between the two adjacent S-SSB frequency domain resources. For example, the interval between two adjacent S-SSB frequency domain resources is G, which may mean that the interval between two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks. Wherein, G is an integer greater than or equal to 0. For example, when G>0, it means that the interval between two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks; when G=0, it means that there is no interval between two adjacent S-SSB frequency domain resources or the interval is 0, that is, the two adjacent S-SSB frequency domain resources are continuous in the frequency domain.

[0145] It should be noted that in the embodiments of this application, the "frequency domain position" of the S-SSB frequency domain resource may be abbreviated as "position" in some scenarios. Or rather, the "position" of the S-SSB frequency domain resource mentioned in the embodiments of this application refers to the "frequency domain position" of the S-SSB frequency domain resource without causing ambiguity. For example, the starting position of the above S-SSB frequency domain resource refers to the starting frequency domain position of the S-SSB frequency domain resource.

[0146] In some embodiments, the number of multiple S-SSB frequency domain resources in the above SL BWP is: the number of repetitions of one S-SSB in this SL BWP. For example, if the number of repetitions of one S-SSB in this SL BWP is N times, then the number of multiple S-SSB frequency domain resources in this SL BWP is N.

[0147] It should be understood that in practical applications, the value of N above can be configured as an integer greater than or equal to 1. That is, the system can support at least one S-SSB frequency domain resource in this SL BWP. The configuration of N1 can satisfy: 1 ≤ N1 ≤ N. That is, the first frequency domain resource can be configured as part of the system frequency domain resources to accommodate terminals with weak capabilities (i.e., implementation method #1), or the first frequency domain resource can also be configured as all of the system frequency domain resources.

[0148] In the second implementation method (denoted as implementation method #2), the system frequency domain resources include multiple sub-bandwidths in one SL BWP, and at least one of the multiple sub-bandwidths contains S-SSB frequency domain resources; the first frequency domain resource is part of the multiple sub-bandwidths, and this part of the sub-bandwidth contains S-SSB frequency domain resources.

[0149] For example, assume that the system supports one SL BWP and supports K (K > 1) sub-bandwidths in this SL BWP. Or rather, the system frequency domain resources include K sub-bandwidths in one SL BWP. Then, the first frequency domain resource can be, for example, K1 (K1 < K) sub-bandwidths among the K sub-bandwidths. The value of K1 can be determined by definition, pre-configuration, or network configuration, and S-SSB frequency domain resources are configured in the K1 sub-bandwidths.

[0150] In some embodiments, for each of the part of the sub-bandwidths (such as the above K1 sub-bandwidths), the frequency domain resources for sending S-SSB may include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in this sub-bandwidth.

[0151] For example, assuming that the part of the sub-bandwidth includes sub-bandwidth #1, the frequency domain resources for sending the S-SSB in sub-bandwidth #1 may include all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in sub-bandwidth #1. When the frequency domain resources for sending the S-SSB include all S-SSB frequency domain resources in sub-bandwidth #1, it means that the terminal needs to occupy all S-SSB frequency domain resources in sub-bandwidth #1 to send the S-SSB; when the frequency domain resources for sending the S-SSB include part of the S-SSB frequency domain resources in sub-bandwidth #1, it means that the terminal does not need to occupy all S-SSB frequency domain resources in sub-bandwidth #1 to send the S-SSB.

[0152] As an example, whether the terminal needs to occupy all S-SSB frequency domain resources in the sub-bandwidth to transmit S-SSB can be determined based on the network configuration. For example, when the network configuration requires the terminal to occupy all S-SSB frequency domain resources in the sub-bandwidth to transmit S-SSB, the terminal can transmit S-SSB on all S-SSB frequency domain resources in the sub-bandwidth based on the network configuration; as another example, the terminal can independently determine whether to occupy all S-SSB frequency domain resources in the sub-bandwidth to transmit S-SSB. For example, when the terminal's capability supports it to occupy all S-SSB frequency domain resources in the sub-bandwidth to transmit S-SSB, the terminal can transmit S-SSB on all S-SSB frequency domain resources in the sub-bandwidth; as another example, the transmitting terminal can also determine whether to occupy all S-SSB frequency domain resources in the sub-bandwidth to transmit S-SSB based on instructions from other terminals in the communication system. For example, a weak-capability terminal in a communication system may instruct the sending terminal to occupy all S-SSB frequency domain resources in the sub-bandwidth to send S-SSB, so as to simplify the complexity of the weak-capability terminal in detecting S-SSB. In this case, the sending terminal can send S-SSB on all S-SSB frequency domain resources in the sub-bandwidth.

[0153] In some embodiments, the sub-bandwidths in the portion of sub-bandwidths (such as the K1 sub-bandwidths mentioned above) are adjacent in the frequency domain; or, the sub-bandwidths in the portion of sub-bandwidths are not adjacent in the frequency domain; or, a portion of the sub-bandwidths in the portion of sub-bandwidths are adjacent in the frequency domain.

[0154] That is, when the terminal sends an S-SSB on this part of the sub-bandwidth, the sub-bandwidths in this part of the sub-bandwidth may be adjacent in the frequency domain. In this way, the frequency domain resources for sending the S-SSB are relatively evenly distributed, and the transmit power in the frequency domain is also relatively even, thereby helping to avoid the impact on communication performance. In some embodiments, the sub-bandwidths in this part of the sub-bandwidth may also be non-adjacent in the frequency domain, or may be partially adjacent and partially non-adjacent.

[0155] In some embodiments, in a sub-bandwidth including S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources included in each sub-bandwidth is pre-configured or network configured.

[0156] For example, assuming that among the above-mentioned K sub-bandwidths, K2 sub-bandwidths contain (are configured with) S-SSB frequency domain resources, then in this scenario, the frequency domain position and / or quantity of the S-SSB frequency domain resources contained in each of the K2 sub-bandwidths can be pre-configured or network configured.

[0157] As an example, in a sub-bandwidth containing S-SSB frequency domain resources (for example, in the K2 sub-bandwidths mentioned above), when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth and the total length of the S-SSB frequency domain resources in the sub-bandwidth. That is to say, when the starting position of the first S-SSB frequency domain resource in a certain sub-bandwidth and the total length of all S-SSB frequency domain resources in the sub-bandwidth are determined, the frequency domain position of the continuously distributed S-SSB frequency domain resources in the sub-bandwidth can be determined.

[0158] As another example, in a sub-bandwidth containing S-SSB frequency domain resources (for example, in the K2 sub-bandwidths mentioned above), when the S-SSB frequency domain resources are non-continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in the sub-bandwidth. That is to say, when the starting position and length of each S-SSB frequency domain resource in a certain sub-bandwidth are determined, the frequency domain positions of each S-SSB frequency domain resource that is non-continuously distributed in the sub-bandwidth can be determined.

[0159] As another example, in a sub-bandwidth containing S-SSB frequency domain resources (for example, in the K2 sub-bandwidths mentioned above), when the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth, the total length of the S-SSB frequency domain resources in the sub-bandwidth, and the interval between two adjacent S-SSB frequency domain resources in the sub-bandwidth. In other words, when the starting position of the first S-SSB frequency domain resource in a certain sub-bandwidth, the total length of the S-SSB frequency domain resources in the sub-bandwidth, and the interval between two adjacent S-SSB frequency domain resources in the sub-bandwidth are determined, the frequency domain positions of each S-SSB frequency domain resource that is discontinuously distributed in the sub-bandwidth can be determined. Among them, the total length of the S-SSB frequency domain resources in the sub-bandwidth may refer to the length between the starting position of the first S-SSB frequency domain resource and the ending position of the last S-SSB frequency domain resource in the sub-bandwidth, or may also refer to the sum of the lengths of each S-SSB frequency domain resource in the sub-bandwidth.

[0160] Exemplarily, the interval between the two adjacent S-SSB frequency domain resources can be indicated, for example, by the number of subchannels or resource blocks between the two adjacent S-SSB frequency domain resources. For example, the interval between two adjacent S-SSB frequency domain resources is G, which may mean that the interval between the two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks. Wherein, G is an integer greater than or equal to 0.

[0161] In some embodiments, in the sub-bandwidth containing S-SSB frequency domain resources (for example, in the above-mentioned K2 sub-bandwidths), the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth can be independently configured or pre-configured, for example.

[0162] In some embodiments, in a sub-bandwidth containing S-SSB frequency domain resources (for example, in the K2 sub-bandwidths described above), the number of S-SSB frequency domain resources contained in each sub-bandwidth is: the number of repetitions of an S-SSB in the sub-bandwidth. For example, if an S-SSB is repeated M times in a certain sub-bandwidth, the number of S-SSB frequency domain resources in the sub-bandwidth is M. In some embodiments, the number of S-SSB frequency domain resources contained in each sub-bandwidth can be, for example, independently configured or pre-configured, and the number of S-SSB frequency domain resources contained in different sub-bandwidths can be the same or different.

[0163] In some embodiments, the sub-bandwidth may be a resource block set (RB set), a channel, a frequency range, or a resource pool (frequency domain resource pool). In other words, the sub-bandwidth in the embodiments of the present application may also be referred to as (or replaced by) a resource block set, a channel, a frequency range, or a resource pool.

[0164] Exemplarily, in the case where the sub-bandwidth is a frequency range or a resource pool, multiple sub-bandwidths in the above SL BWP (i.e., multiple sub-bandwidths included in the system frequency domain resources) may overlap or not overlap in the frequency domain; in the case where the sub-bandwidth is a set of resource blocks or a channel, multiple sub-bandwidths in the above SL BWP do not overlap in the frequency domain.

[0165] It should be understood that in practical applications, the value of K above can be configured as an integer greater than or equal to 1, that is, the system can support at least one sub-bandwidth included in the above SL BWP. The configuration of K1 can satisfy: 1 ≤ K1 ≤ K, that is, the first frequency domain resource can be configured as a part of the system frequency domain resources to accommodate terminals with weak capabilities (i.e., implementation method #2), or the first frequency domain resource can also be configured as all of the system frequency domain resources.

[0166] In the third implementation method (denoted as implementation method #3), the system frequency domain resources include multiple SL BWPs, and at least one SL BWP in the multiple SL BWPs includes S-SSB frequency domain resources; the first frequency domain resource is a part of the multiple SL BWPs, and this part of the SL BWPs includes S-SSB frequency domain resources.

[0167] For example, assume that the system supports X (X > 1) SL BWPs, or rather, the system frequency domain resources include X SL BWPs. Then, the first frequency domain resource can, for example, be X1 (X1 < X) SL BWPs among the X SL BWPs. Among them, the value of X1 can be determined by definition, pre-configuration, or network configuration, and S-SSB frequency domain resources are configured in the X1 sub-bandwidths.

[0168] In some embodiments, for each SL BWP in this part of the SL BWPs (such as the above X1 SL BWPs), the frequency domain resources for sending S-SSB may include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the SL BWP.

[0169] For example, assume that this part of the SL BWPs includes SL BWP#1. Then, the frequency domain resources for sending S-SSB in SL BWP#1 may include all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in SL BWP#1. When the frequency domain resources for sending S-SSB include all S-SSB frequency domain resources in SL BWP#1, it means that the terminal needs to occupy all S-SSB frequency domain resources in SL BWP#1 for S-SSB transmission; when the frequency domain resources for sending S-SSB include part of the S-SSB frequency domain resources in SL BWP#1, it means that the terminal does not need to occupy all S-SSB frequency domain resources in SL BWP#1 for S-SSB transmission.

[0170] As an example, whether the terminal needs to occupy all the S-SSB frequency domain resources in the SL BWP to transmit the S-SSB may be determined based on the network configuration; as another example, the terminal may independently determine whether to occupy all the S-SSB frequency domain resources in the SL BWP to transmit the S-SSB; as yet another example, the transmitting terminal may also determine whether to occupy all the S-SSB frequency domain resources in the SL BWP to transmit the S-SSB based on the instructions of other terminals in the communication system. For example, a weak-capability terminal in the communication system may instruct the transmitting terminal to occupy all the S-SSB frequency domain resources in the SL BWP to transmit the S-SSB, so as to simplify the complexity of the weak-capability terminal in detecting the S-SSB. In this case, the transmitting terminal may transmit the S-SSB on all the S-SSB frequency domain resources in the SL BWP.

[0171] In some embodiments, the SL BWPs in the part of SL BWPs (such as the X1 SL BWPs mentioned above) are adjacent in the frequency domain; or, the SL BWPs in the part of SL BWPs are not adjacent in the frequency domain; or, some of the SL BWPs in the part of SL BWPs are adjacent in the frequency domain.

[0172] That is to say, when the terminal sends an S-SSB on this part of the SL BWP, the SL BWPs in this part of the SL BWP can be adjacent in the frequency domain. In this way, the frequency domain resources for sending the S-SSB are relatively evenly distributed, and the transmission power in the frequency domain is also relatively even, which helps to avoid the impact on communication performance. In some embodiments, the SL BWPs in this part of the SL BWP can also be non-adjacent in the frequency domain, or can be partially adjacent and partially non-adjacent.

[0173] In some embodiments, in the SL BWP including S-SSB frequency domain resources, the frequency domain location and / or quantity of the S-SSB frequency domain resources included in each SL BWP is pre-configured or network configured.

[0174] For example, assuming that among the X SL BWPs mentioned above, X2 SL BWPs include (are configured with) S-SSB frequency domain resources, then in this scenario, the frequency domain position and / or quantity of the S-SSB frequency domain resources included in each SL BWP in the X2 SL BWPs can be pre-configured or network configured.

[0175] As an example, in an SL BWP containing S-SSB frequency domain resources (for example, in the X2 SL BWPs mentioned above), when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP and the total length of the S-SSB frequency domain resources in the SL BWP. That is to say, when the starting position of the first S-SSB frequency domain resource in a certain SL BWP and the total length of all S-SSB frequency domain resources in the SL BWP are determined, the frequency domain position of the continuously distributed S-SSB frequency domain resources in the SL BWP can be determined.

[0176] As another example, in an SL BWP that includes S-SSB frequency domain resources (e.g., in the X2 SL BWPs described above), when the S-SSB frequency domain resources are non-contiguously distributed, the frequency domain positions of the S-SSB frequency domain resources included in each SL BWP are determined based on the starting position and length of each S-SSB frequency domain resource in the SL BWP. In other words, when the starting position and length of each S-SSB frequency domain resource in a certain SL BWP are determined, the frequency domain positions of each non-contiguously distributed S-SSB frequency domain resource in the SL BWP can be determined.

[0177] As another example, in an SL BWP containing S-SSB frequency domain resources (for example, in the X2 SL BWPs mentioned above), when the S-SSB frequency domain resources are non-continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP, the total length of the S-SSB frequency domain resources in the SL BWP, and the interval between two adjacent S-SSB frequency domain resources in the SL BWP. In other words, when the starting position of the first S-SSB frequency domain resource in a certain SL BWP, the total length of the S-SSB frequency domain resources in the SL BWP, and the interval between two adjacent S-SSB frequency domain resources in the SL BWP are determined, the frequency domain positions of each non-continuously distributed S-SSB frequency domain resource in the SL BWP can be determined. Among them, the total length of the S-SSB frequency domain resources in the SL BWP may refer to the length between the starting position of the first S-SSB frequency domain resource and the ending position of the last S-SSB frequency domain resource in the SL BWP, or it may also refer to the sum of the lengths of each S-SSB frequency domain resource in the SL BWP.

[0178] Exemplarily, the interval between two adjacent S-SSB frequency-domain resources, for example, can be indicated by the number of sub-channels or resource blocks separated by the two adjacent S-SSB frequency-domain resources. For example, if the interval between two adjacent S-SSB frequency-domain resources is G, it can mean that the interval between the two adjacent S-SSB frequency-domain resources is G sub-channels or G resource blocks. Here, G is an integer greater than or equal to 0.

[0179] In some embodiments, in the SL BWP containing S-SSB frequency-domain resources (such as in the above X2 SL BWPs), the frequency-domain position of the S-SSB frequency-domain resources included in each SL BWP can be, for example, independently configured or pre-configured.

[0180] In some embodiments, in the SL BWP containing S-SSB frequency-domain resources (such as in the above X2 SL BWPs), the number of S-SSB frequency-domain resources included in each SL BWP is: the number of repetitions of one S-SSB within this SL BWP. For example, if one S-SSB is repeated L times in a certain SL BWP, then the number of S-SSB frequency-domain resources in this SL BWP is L. In some embodiments, the number of S-SSB frequency-domain resources included in each SL BWP can be, for example, independently configured or pre-configured, and the number of S-SSB frequency-domain resources included in different SL BWPs can be the same or different.

[0181] It should be understood that in practical applications, the configuration of X1 above can satisfy: 1 ≤ X1 ≤ X, that is, the first frequency-domain resource can be configured as part of the system frequency-domain resources to accommodate terminals with weak capabilities (i.e., implementation method #3), or the first frequency-domain resource can also be configured as all of the system frequency-domain resources.

[0182] In the fourth implementation method (denoted as implementation method #4), the system frequency-domain resources include multiple carriers, and at least one of the multiple carriers contains S-SSB frequency-domain resources; the first frequency-domain resource is part of the multiple carriers, and this part of the carriers contains S-SSB frequency-domain resources.

[0183] For example, assume the system supports Y (Y > 1) carriers, or rather, the system frequency-domain resources include Y carriers. Then, the first frequency-domain resource can be, for example, Y1 (Y1 < Y) carriers among the Y carriers. Here, the value of Y1 can be determined by definition, pre-configuration, or network configuration, and S-SSB frequency-domain resources are configured in these Y1 carriers.

[0184] In some embodiments, for each of these carriers (such as the above Y1 carriers), the frequency-domain resources for transmitting S-SSB can include: all the S-SSB frequency-domain resources or part of the S-SSB frequency-domain resources in this carrier.

[0185] For example, assuming that the part of the carriers includes carrier #1, then the frequency domain resources for sending S-SSB in carrier #1 may include all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in carrier #1. When the frequency domain resources for sending S-SSB include all S-SSB frequency domain resources in carrier #1, it means that the terminal needs to occupy all S-SSB frequency domain resources in carrier #1 to send S-SSB; when the frequency domain resources for sending S-SSB include part of the S-SSB frequency domain resources in carrier #1, it means that the terminal may not need to occupy all S-SSB frequency domain resources in carrier #1 to send S-SSB.

[0186] As an example, whether the terminal needs to occupy all the S-SSB frequency domain resources in the carrier to transmit S-SSB can be determined based on the network configuration; as another example, the terminal can also independently determine whether to occupy all the S-SSB frequency domain resources in the carrier to transmit S-SSB; as another example, the transmitting terminal can also determine whether to occupy all the S-SSB frequency domain resources in the carrier to transmit S-SSB based on the instructions of other terminals in the communication system. For example, a weak-capability terminal in the communication system can instruct the transmitting terminal to occupy all the S-SSB frequency domain resources in the carrier to transmit S-SSB, so as to simplify the complexity of the weak-capability terminal in detecting S-SSB. In this case, the transmitting terminal can transmit S-SSB on all S-SSB frequency domain resources in the carrier.

[0187] In some embodiments, the carriers in the portion of carriers (such as the Y1 carriers mentioned above) are adjacent in the frequency domain; or, the carriers in the portion of carriers are not adjacent in the frequency domain; or, some of the carriers in the portion of carriers are adjacent in the frequency domain.

[0188] That is, when the terminal sends an S-SSB on this part of the carriers, the carriers in this part of the carriers may be adjacent in the frequency domain. In this way, the frequency domain resources for sending the S-SSB are relatively evenly distributed, and the transmit power in the frequency domain is also relatively even, thereby helping to avoid the impact on communication performance. In some embodiments, the carriers in this part of the carriers may also be non-adjacent in the frequency domain, or may be partially adjacent and partially non-adjacent.

[0189] In some embodiments, in a carrier including S-SSB frequency domain resources, the frequency domain position and / or number of S-SSB frequency domain resources included in each carrier is pre-configured or network configured.

[0190] For example, assuming that among the above-mentioned Y carriers, Y2 carriers contain (are configured with) S-SSB frequency domain resources, then in this scenario, the frequency domain position and / or quantity of the S-SSB frequency domain resources contained in each of the Y2 carriers can be pre-configured or network configured.

[0191] As an example, in a carrier containing S-SSB frequency domain resources (for example, in the Y2 carriers mentioned above), when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each carrier is based on the starting position of the first S-SSB frequency domain resource in the carrier and the total length of the S-SSB frequency domain resources in the carrier. That is to say, when the starting position of the first S-SSB frequency domain resource in a carrier and the total length of all S-SSB frequency domain resources in the carrier are determined, the frequency domain position of the continuously distributed S-SSB frequency domain resources in the carrier can be determined.

[0192] As another example, in a carrier containing S-SSB frequency domain resources (for example, in the Y2 carriers mentioned above), when the S-SSB frequency domain resources are non-continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource in the carrier. That is to say, when the starting position and length of each S-SSB frequency domain resource in a certain carrier are determined, the frequency domain positions of each S-SSB frequency domain resource that is non-continuously distributed in the carrier can be determined.

[0193] As another example, in a carrier containing S-SSB frequency domain resources (for example, in the Y2 carriers mentioned above), when the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each carrier is based on the starting position of the first S-SSB frequency domain resource in the carrier, the total length of the S-SSB frequency domain resources in the carrier, and the interval between two adjacent S-SSB frequency domain resources in the carrier. In other words, when the starting position of the first S-SSB frequency domain resource in a carrier, the total length of the S-SSB frequency domain resources in the carrier, and the interval between two adjacent S-SSB frequency domain resources in the carrier are determined, the frequency domain positions of each S-SSB frequency domain resource that is discontinuously distributed in the carrier can be determined. The total length of the S-SSB frequency domain resources in the carrier may refer to the length between the starting position of the first S-SSB frequency domain resource in the carrier and the ending position of the last S-SSB frequency domain resource, or may refer to the sum of the lengths of each S-SSB frequency domain resource in the carrier.

[0194] Exemplarily, the interval between two adjacent S-SSB frequency-domain resources can be indicated, for example, by the number of sub-channels or resource blocks separated by the two adjacent S-SSB frequency-domain resources. For example, if the interval between two adjacent S-SSB frequency-domain resources is G, it can mean that the interval between the two adjacent S-SSB frequency-domain resources is G sub-channels or G resource blocks. Here, G is an integer greater than or equal to 0.

[0195] In some embodiments, in a carrier containing S-SSB frequency-domain resources (such as in the above-mentioned Y2 carriers), the frequency-domain positions of the S-SSB frequency-domain resources included in each carrier can be configured independently or pre-configured, for example.

[0196] In some embodiments, in a carrier containing S-SSB frequency-domain resources (such as in the above-mentioned Y2 carriers), the number of S-SSB frequency-domain resources included in each carrier is: the number of repetitions of one S-SSB within the carrier. For example, if one S-SSB is repeated U times in a certain carrier, then the number of S-SSB frequency-domain resources in this carrier is U. In some embodiments, the number of S-SSB frequency-domain resources included in each carrier can be configured independently or pre-configured, and the number of S-SSB frequency-domain resources included in different carriers can be the same or different.

[0197] It should be understood that in practical applications, the configuration of the above-mentioned Y1 can satisfy: 1 ≤ Y1 ≤ Y, that is, the first frequency-domain resource can be configured as part of the system frequency-domain resources to accommodate terminals with weak capabilities (i.e., implementation method #4), or the first frequency-domain resource can also be configured as all of the system frequency-domain resources.

[0198] It should also be understood that the above-mentioned carrier can be a scenario considering Carrier Aggregation. Here, "carrier" can also be referred to as "sub-carrier" or "Carrier Component (CC)" for example.

[0199] In some embodiments, the system frequency-domain resources can also include a second frequency-domain resource, which is the frequency-domain resource in the system frequency-domain resources other than the first frequency-domain resource. The second frequency-domain resource can be used to send or receive service data.

[0200] As an example, in implementation method #1, assume that the system frequency-domain resources include N S-SSB frequency-domain resources in one SL BWP. Then in this implementation method, if the first frequency-domain resource is N1 (N1 < N) S-SSB frequency-domain resources among the N S-SSB frequency-domain resources, the second frequency-domain resource can be N - N1 S-SSB frequency-domain resources other than the N1 S-SSB frequency-domain resources among the N S-SSB frequency-domain resources.

[0201] In another example, in Implementation #2, assuming that the system frequency-domain resources include K sub-bandwidths in one SL BWP, then in this implementation, if the first frequency-domain resource is K1 (K1 < K) sub-bandwidths among the K sub-bandwidths, the second frequency-domain resource can be K - K1 sub-bandwidths among the K sub-bandwidths excluding the K1 sub-bandwidths.

[0202] In yet another example, in Implementation #3, assuming that the system frequency-domain resources include X SL BWPs, then in this implementation, if the first frequency-domain resource is X1 (X1 < X) SL BWPs among the X SL BWPs, the second frequency-domain resource can be X - X1 SL BWPs among the X SL BWPs excluding the X1 SL BWPs.

[0203] In still another example, in Implementation #4, assuming that the system frequency-domain resources include Y carriers, then in this implementation, if the first frequency-domain resource is Y1 (Y1 < Y) carriers among the Y carriers, the second frequency-domain resource can be Y - Y1 carriers among the Y carriers excluding the Y1 carriers.

[0204] According to the method of this embodiment, the terminal can use the first frequency-domain resource for the transmission / reception of S-SSB and use the second frequency-domain resource for the transmission / reception of service data. In this way, the transmission / reception of S-SSB can be restricted within a smaller bandwidth, which is conducive to more efficient utilization of frequency-domain resources. For example, in Implementation #3, the second type of terminal (low-capability terminal) can, by switching the SL BWP, use the SL BWP corresponding to the first frequency-domain resource for the transmission / reception of S-SSB and use the SL BWP corresponding to the second frequency-domain resource for the transmission / reception of service data. In this way, while efficiently utilizing the frequency-domain resources, the problem of coexistence of the second type of terminal and the first type of terminal in the same communication system can be solved.

[0205] In some embodiments, the second frequency-domain resource does not include the S-SSB frequency-domain resource, or in other words, except for the first frequency-domain resource, other frequency-domain resources may not be configured with the S-SSB frequency-domain resource. In this way, the second frequency-domain resource can be better used for the communication of service data.

[0206] In some embodiments, when the terminal has the ability to transmit or receive S-SSB on the second frequency-domain resource, the second frequency-domain resource can be used for the transmission or reception of S-SSB.

[0207] That is to say, if a certain terminal (such as a certain first type of terminal) has the ability to transmit or receive S-SSB on the second frequency-domain resource, then in addition to being able to transmit or receive S-SSB on the first frequency-domain resource, the terminal can also transmit or receive S-SSB on the second frequency-domain resource.

[0208] According to the method of this embodiment, on the one hand, the terminal uses part of the frequency domain resources in the system frequency domain resources to send or receive S-SSB, so that the transmission or reception of S-SSB can be performed on a relatively small bandwidth, thereby taking into account terminals with different capabilities in the same communication system to ensure that all terminals in the communication system can achieve synchronization. On the other hand, in addition to defining, pre-configuring or network-configuring public frequency domain resources (first frequency domain resources) for sending / receiving S-SSB, additional frequency domain resources (second frequency domain resources) for sending / receiving S-SSB can also be defined, pre-configured or network-configured as a supplement to prevent the terminal from being unable to send S-SSB due to LBT failure of certain frequency band resources.

[0209] The above text introduces the side synchronization method provided in the embodiment of the present application in combination with Figure 17. To facilitate understanding of the embodiment of the present application, several possible implementation schemes of the side synchronization method applicable to the embodiment of the present application are introduced below.

[0210] As an example, a frequency domain resource design scheme for S-SSB may include:

[0211] Solution 1: One SL BWP contains N (N is greater than or equal to 1) S-SSB frequency domain resources.

[0212] Solution 2: One SL BWP includes K (K is greater than or equal to 1) sub-bandwidths, and among the K sub-bandwidths, at least one sub-bandwidth includes M (M is greater than or equal to 1) S-SSB frequency domain resources.

[0213] Exemplarily, the above sub-bandwidth may also be referred to as (defined as) an RB set, a channel (Channel), a frequency range (FR) or a resource pool (frequency domain resource pool).

[0214] In one possible embodiment, the number of S-SSB frequency domain resources contained in each of the above sub-bandwidths is independently configured or pre-configured, that is, the number of S-SSB frequency domain resources in different sub-bandwidths may be the same or different, and there is no limitation on this.

[0215] Solution 3: There are X (X is greater than 1) SL BWPs in the frequency domain. Among the X SL BWPs, at least one SL BWP contains L (L is greater than or equal to 1) S-SSB frequency domain resources.

[0216] In one possible manner, the number of S-SSB frequency domain resources contained in the above-mentioned different SL BWPs is independently configured or pre-configured, that is, the number of S-SSB frequency domain resources in different SL BWPs may be the same or different, and there is no limitation on this.

[0217] Solution 4: There are Y (Y is greater than 1) carriers in the frequency domain. Among the Y carriers, at least one carrier contains U (U is greater than or equal to 1) S-SSB frequency domain resources.

[0218] In one possible embodiment, the number of S-SSB frequency domain resources contained in the above-mentioned different carriers is independently configured or pre-configured, that is, the number of S-SSB frequency domain resources in different carriers can be the same or different, and there is no limitation on this.

[0219] For example, the above carrier may be a scenario in which carrier aggregation is considered, wherein "carrier" may also be referred to as "subcarrier" or "carrier component".

[0220] It should be noted that the configuration method of the S-SSB frequency domain resources in the above-mentioned schemes 1 to 4 may, for example, include: configuring the S-SSB frequency domain resources by the network, or configuring the S-SSB frequency domain resources by pre-configuration.

[0221] Among them, the configuration of the above-mentioned N / M / L / U S-SSB frequency domain resources may include the configuration of the position and number (i.e., N / M / L / U) of the N / M / L / U S-SSB frequency domain resources.

[0222] Exemplarily, the location of the S-SSB frequency domain resource may be indicated, for example, in the following manner 1, manner 2, or manner 3:

[0223] Mode 1: When multiple S-SSB frequency domain resources are continuously distributed, the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources may be indicated. That is, based on the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources, the positions of the multiple continuously distributed S-SSB frequency domain resources may be determined.

[0224] Method 2: When multiple S-SSB frequency domain resources are non-contiguously distributed, the starting position and length of each S-SSB frequency domain resource may be indicated. That is, based on the starting position and length of each S-SSB frequency domain resource, the positions of the multiple non-contiguously distributed S-SSB frequency domain resources may be determined.

[0225] Mode 3: When multiple S-SSB frequency domain resources are non-continuously distributed, the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval G between two adjacent S-SSB frequency domain resources may be indicated. That is, based on the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval G between two adjacent S-SSB frequency domain resources, the positions of the multiple non-continuously distributed S-SSB frequency domain resources may be determined.

[0226] Exemplarily, the above-mentioned interval G may refer to an interval of G subchannels, or may also refer to an interval of G resource blocks. Here, G is an integer greater than or equal to 0. For example, when G>0, it means that the interval between two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks; when G=0, it means that there is no interval between two adjacent S-SSB frequency domain resources or the interval is 0, that is, the two adjacent S-SSB frequency domain resources are continuous in the frequency domain.

[0227] Exemplarily, the number (quantity) of the above-mentioned S-SSB frequency domain resources is equivalent to the number of repetitions of an S-SSB in the frequency domain. For example, if an S-SSB is repeated N times in the frequency domain, the number of S-SSB frequency domain resources is N.

[0228] As an example, a manner in which a transmitting terminal of an S-SSB transmits an S-SSB in the frequency domain may include:

[0229] Sending method 1:

[0230] This transmission method can be applied to the frequency domain resource design scheme in the above-mentioned scheme one, for example.

[0231] Exemplarily, for the N S-SSB frequency domain resources in Solution 1, the terminal may send an S-SSB on at least one of the S-SSB frequency domain resources. For example, among the N S-SSB frequency domain resources, N1 (1≤N1≤N) S-SSB frequency domain resources must send S-SSBs, that is, the terminal must send S-SSBs on at least the N1 S-SSB frequency domain resources.

[0232] In some embodiments, the terminal may also transmit an S-SSB on at least one of the (N-N1) S-SSB frequency domain resources other than the N1 S-SSB frequency domain resources.

[0233] Sending method 2:

[0234] This transmission method can be applied to the frequency domain resource design scheme in the above-mentioned scheme 2, for example.

[0235] For example, for the K sub-bandwidths included in the SL BWP in Solution 2, the terminal can send at least one S-SSB on at least one of the sub-bandwidths. For example, among the K sub-bandwidths of the SL BWP, K1 (1≤K1≤K) sub-bandwidths must send S-SSBs, that is, the terminal must send S-SSBs on at least the K1 sub-bandwidths.

[0236] As an implementation manner, the terminal may send at least one S-SSB on each of the K1 sub-bandwidths.

[0237] As another implementation manner, the terminal may occupy all S-SSB frequency domain resources in each of the K1 sub-bandwidths to transmit the S-SSB. For example, assuming that each of the K1 sub-bandwidths contains y1 S-SSB frequency domain resources, the terminal needs to occupy y1 S-SSB frequency domain resources in each sub-bandwidth to transmit the S-SSB.

[0238] As another implementation method, the terminal may occupy all S-SSB frequency domain resources on part of the K1 sub-bandwidths to send S-SSB, while on another part of the sub-bandwidth, it may not need to occupy all S-SSB frequency domain resources to send S-SSB.

[0239] In some embodiments, the terminal may further transmit at least one S-SSB on at least one of the (K-K1) sub-bandwidths other than the K1 sub-bandwidths.

[0240] Exemplarily, when a terminal transmits an S-SSB on multiple sub-bandwidths, the multiple sub-bandwidths may be adjacent in the frequency domain. In this way, the frequency domain resources for transmitting the S-SSB are relatively evenly distributed, and the transmit power in the frequency domain is also relatively even, thereby facilitating avoiding an impact on communication performance. In some embodiments, the multiple sub-bandwidths for transmitting the S-SSB may also be non-adjacent in the frequency domain, or may be partially adjacent and partially non-adjacent.

[0241] Sending method 3:

[0242] This transmission method can be applied to the frequency domain resource design scheme in the above-mentioned scheme three, for example.

[0243] For example, for the X SL BWPs in Solution 3, the terminal may send at least one S-SSB on at least one of the SL BWPs. For example, among the X SL BWPs, X1 (1≤X1≤X) SL BWPs must send S-SSBs, that is, the terminal must send S-SSBs on at least the X1 SL BWPs.

[0244] As an implementation manner, the terminal may send at least one S-SSB on each of the X1 SL BWPs.

[0245] As another implementation manner, the terminal may occupy all S-SSB frequency domain resources on each of the X1 SL BWPs to transmit the S-SSB. For example, assuming that each of the X1 SL BWPs includes y2 S-SSB frequency domain resources, the terminal needs to occupy the y2 S-SSB frequency domain resources of each SL BWP to transmit the S-SSB.

[0246] As another implementation method, the terminal may occupy all S-SSB frequency domain resources on some of the X1 SL BWPs to send S-SSBs, while on another part of the SL BWPs, it may not need to occupy all S-SSB frequency domain resources to send S-SSBs.

[0247] In some embodiments, the terminal may further transmit at least one S-SSB on at least one SL BWP among the (X-X1) SL BWPs other than the X1 SL BWPs.

[0248] Exemplarily, when a terminal sends an S-SSB on multiple SL BWPs, the multiple SL BWPs may be adjacent in the frequency domain. In this way, the frequency domain resources for sending the S-SSB are relatively evenly distributed, and the transmit power in the frequency domain is also relatively even, thereby helping to avoid impact on communication performance. In some embodiments, the multiple SL BWPs for sending the S-SSB may also be non-adjacent in the frequency domain, or may be partially adjacent and partially non-adjacent.

[0249] Sending method 4:

[0250] This transmission method can be applied to the frequency domain resource design scheme in the above-mentioned scheme four, for example.

[0251] For example, for the Y carriers in Solution 4, the terminal may send at least one S-SSB on at least one of the carriers. For example, among the Y carriers, Y1 (1≤Y1≤Y) carriers must send S-SSBs, that is, the terminal must send S-SSBs on at least the Y1 carriers.

[0252] As an implementation method, the terminal may send at least one S-SSB on each of the Y1 carriers.

[0253] As another implementation, the terminal may occupy all S-SSB frequency domain resources on each of the Y1 carriers to transmit the S-SSB. For example, assuming that each of the Y1 carriers includes y3 S-SSB frequency domain resources, the terminal needs to occupy all y3 S-SSB frequency domain resources of each carrier to transmit the S-SSB.

[0254] As another implementation method, the terminal may occupy all S-SSB frequency domain resources on some of the Y1 carriers to send S-SSB, while on other carriers it may not need to occupy all S-SSB frequency domain resources to send S-SSB.

[0255] In some embodiments, the terminal may also send at least one S-SSB on at least one carrier among the (Y-Y1) carriers other than the Y1 carriers.

[0256] Exemplarily, when a terminal transmits an S-SSB on multiple carriers, the multiple carriers may be adjacent in the frequency domain. In this way, the frequency domain resources for transmitting the S-SSB are relatively evenly distributed, and the transmit power in the frequency domain is also relatively even, thereby facilitating avoiding an impact on communication performance. In some embodiments, the multiple carriers transmitting the S-SSB may also be non-adjacent in the frequency domain, or may be partially adjacent and partially non-adjacent.

[0257] It should be noted that the S-SSB frequency domain resources for sending S-SSB mentioned in sending modes 1 to 4 can also be understood as the default / mandatory frequency domain resources for sending S-SSB.

[0258] It should also be noted that the terminals in the above-mentioned sending modes 1 to 4 can be first-category terminals or second-category terminals.

[0259] The first category of terminals refers to fully capable terminals, or in other words, highly capable or high-capability terminals, such as mobile phones; the second category of terminals refers to less capable terminals, such as smartwatches, wristbands, AR / VR glasses, etc. Typically, the bandwidth supported by the second category of terminals for sending / receiving information is relatively small, or in other words, the second category of terminals can support information transmission / reception within a sub-bandwidth, but not across the full bandwidth. Furthermore, in some scenarios, the transmit power of the second category of terminals is also low, and their encoding / decoding capabilities may be limited.

[0260] When the terminal sending the S-SSB is a first-category terminal, the terminal needs to send the S-SSB at the default / mandatory frequency domain resource position for sending the S-SSB. In addition, in some scenarios, this type of terminal can also send the S-SSB on other frequency domain resources. When the terminal sending the S-SSB is a second-category terminal, the terminal can send the S-SSB only at the default / mandatory frequency domain resource position for the S-SSB, and the terminal is not required to send the S-SSB on other frequency domain resources. In some scenarios, if the second-category terminal has the ability to send the S-SSB on other frequency domain resources, then the second-category terminal can also send the S-SSB on frequency domain resources other than the default / mandatory S-SSB frequency domain resources.

[0261] In one possible manner, the above-mentioned default / mandatory frequency domain resources for sending S-SSB can be determined, for example, by definition, configuration or pre-configuration. The default / mandatory frequency domain resources for sending S-SSB can be used as public frequency domain resources for sending S-SSB. The public frequency domain resources include but are not limited to at least one continuous frequency band in the frequency domain, at least one sub-bandwidth (such as K1 sub-bandwidths in sending mode 2), at least one continuous frequency domain resource in SL BWP, at least one resource pool, at least one SL BWP (such as X1 SL BWPs in sending mode 3) or at least one carrier (such as Y1 carriers in sending mode 4).

[0262] As an example, a manner in which a receiving terminal of an S-SSB receives the S-SSB in the frequency domain may include:

[0263] Receiving method 1:

[0264] Corresponding to the transmission method 1, this reception method can be applied to the frequency domain resource design scheme in the above-mentioned scheme 1, for example.

[0265] Exemplarily, the terminal may detect / receive S-SSB at N1 S-SSB frequency domain resource positions (default / mandatory frequency domain resource positions) in transmission mode 1. In some embodiments, the terminal may also detect / receive S-SSB at other frequency domain resource positions.

[0266] Receiving method 2:

[0267] Corresponding to the sending method 2, this receiving method can be applied to the frequency domain resource design scheme in the above-mentioned scheme 2, for example.

[0268] Exemplarily, the terminal may detect / receive S-SSB in K1 sub-bandwidths (default / mandatory frequency domain resource locations) in transmission mode 2. In some embodiments, the terminal may also detect / receive S-SSB in other sub-bandwidths.

[0269] Receiving method 3:

[0270] Corresponding to the transmission mode 3, this reception mode may be applicable to the frequency domain resource design scheme in the above-mentioned scheme 3, for example.

[0271] Exemplarily, the terminal may detect / receive S-SSB in X1 SL BWPs (default / mandatory frequency domain resource locations) in transmission mode 3. In some embodiments, the terminal may also detect / receive S-SSB in other SL BWPs.

[0272] Receiving method 4:

[0273] Corresponding to the sending mode 4, this receiving mode can be applied to the frequency domain resource design scheme in the above-mentioned scheme 4, for example.

[0274] Exemplarily, the terminal may detect / receive S-SSB on Y1 carriers (default / mandatory frequency domain resource locations) in transmission mode 4. In some embodiments, the terminal may also detect / receive S-SSB on other carriers.

[0275] It should be noted that the terminals in the above-mentioned receiving modes 1 to 4 may be first-category terminals or second-category terminals. When the terminal receiving the S-SSB is a first-category terminal or a second-category terminal, the terminal needs to detect / receive the S-SSB at least at the default / mandatory frequency domain resource position. When the terminal receiving the S-SSB is a first-category terminal, the terminal has full capabilities, so it can additionally detect / receive the S-SSB at other frequency domain resource positions. In some scenarios, if the second-category terminal has the ability to detect / receive the S-SSB at other frequency domain resource positions, then the second-category terminal can also detect / receive the S-SSB at frequency domain resource positions other than the default / mandatory frequency domain resources.

[0276] For ease of understanding, the following describes a possible implementation process of the side synchronization method applicable to the implementation of this application in conjunction with Figures 18 and 19.

[0277] Figure 18 (a) is a schematic diagram of a frequency domain resource design scheme for S-SSB provided in an embodiment of the present application. As shown in Figure 18 (a), the system supports one BWP (SL BWP) and supports multiple transmission resources for S-SSB in the frequency domain. In other words, the system frequency domain resources may include multiple S-SSB frequency domain resources in one BWP. The intervals between the multiple S-SSB frequency domain resources can be defined by configuration / pre-configuration.

[0278] Taking Figure (a) in Figure 18 as an example, the system frequency domain resources may include 3 S-SSB frequency domain resources in a BWP, and one or more S-SSB frequency domain resources among the 3 S-SSB frequency domain resources can be used as default / mandatory frequency domain resources, that is, the transmitting terminal must at least send S-SSB on the one or more frequency domain resources, and the receiving terminal must at least receive S-SSB on the one or more frequency domain resources.

[0279] Exemplarily, if a terminal is a first-category terminal, then the terminal is capable of sending S-SSB on frequency domain resources other than the default / mandatory frequency domain resources. For example, the terminal can send S-SSB on all S-SSB frequency domain resources. If a terminal is a second-category terminal, then the terminal needs to send S-SSB on at least the default / mandatory S-SSB resources. For example, the terminal can only send S-SSB on the default / mandatory resources.

[0280] Exemplarily, if a terminal is a first-category terminal, then the terminal is capable of receiving S-SSB on frequency domain resources other than the default / mandatory frequency domain resources. For example, the terminal can receive S-SSB on all S-SSB frequency domain resources. If a terminal is a second-category terminal, then the terminal needs to receive S-SSB on at least the default / mandatory frequency domain resources. For example, the terminal can only receive S-SSB on the default / mandatory resources.

[0281] Figure 18(b) is a schematic diagram of another S-SSB frequency domain resource design scheme provided in an embodiment of the present application. As shown in Figure 18(b), the system supports two BWPs (SL BWPs), and the two BWPs are independently configured with S-SSB frequency domain resources.

[0282] In some scenarios, BWP#0 can be used as the default / mandatory BWP (i.e., the default / mandatory frequency domain resource). In this scenario, the transmitting terminal must at least transmit S-SSB on BWP#0, and the receiving terminal must at least receive S-SSB on BWP#0.

[0283] In some scenarios, BWP#1 can be used as an additional frequency domain resource. In this scenario, Category 1 terminals can choose whether to transmit S-SSBs on BWP#1 and / or the amount of S-SSB frequency domain resources to use for S-SSB transmission. Category 2 terminals, due to limited capabilities, are generally unable to transmit or receive S-SSBs on BWP#1.

[0284] Figure 18(c) is a schematic diagram of another frequency domain resource design solution for S-SSB provided in an embodiment of the present application. As shown in Figure 18(c), the system configures / supports two BWPs (SL BWPs).

[0285] In some scenarios, BWP#0 can be used as the default / mandatory BWP (i.e., the default / mandatory frequency domain resource), and BWP#0 is configured / pre-configured with S-SSB frequency domain resources. In this scenario, the terminal needs to send / receive S-SSB on BWP#0. Among them, both the first and second category terminals send / receive S-SSB on BWP#0.

[0286] In some scenarios, for the second type of terminals, S-SSB can be sent / received on BWP#0, and service data can be sent / received by switching from BWP#0 to BWP#1.

[0287] Figure 19 is a schematic diagram of another frequency domain resource design scheme for S-SSB provided in an embodiment of the present application.

[0288] In the example of Figure 19, the entire frequency domain resources can be divided into multiple sub-bandwidths, or in other words, the system frequency domain resources can include multiple sub-bandwidths in one SL BWP. The multiple sub-bandwidths can be, for example, multiple frequency ranges, multiple resource pools, multiple RB sets, or multiple channels.

[0289] In one example, the multiple sub-bandwidths may be multiple frequency ranges, such as frequency range #0 to frequency range #2 in Figure 19. The frequency ranges may or may not overlap.

[0290] In another example, the multiple sub-bandwidths may be multiple resource pools, such as resource pool #0 to resource pool #2 in Figure 19. The resource pools may or may not overlap with each other.

[0291] In another example, the multiple sub-bandwidths may be multiple RB sets, such as RB set #0 to RB set #2 in FIG19 . There is no overlap between the RB sets. In some embodiments, a guard interval may be configured between two adjacent RB sets.

[0292] As another example, the multiple sub-bandwidths may be multiple channels (not shown in FIG19 ), and there is no overlap between the channels.

[0293] In some scenarios, sub-bandwidth #1 (e.g., frequency range #1, resource pool #1, or RB set #1) can be used as a default / mandatory frequency domain resource (default / mandatory frequency band), or in other words, as a public frequency domain resource. In this scenario, the terminal must at least transmit / receive S-SSB in sub-bandwidth #1.

[0294] In some scenarios, sub-bandwidth #0 (e.g., frequency range #0, resource pool #0, or RB set #0) can be used as an additional / optional frequency domain resource. In this scenario, the terminal can selectively transmit / receive S-SSB on sub-bandwidth #0.

[0295] It can be understood that in the example shown in Figure 19, sub-bandwidth #2 (such as frequency range #2, resource pool #2 or RB set #2) does not include S-SSB frequency domain resources, so all terminals will not send / receive S-SSB on sub-bandwidth #2.

[0296] An embodiment of the present application designs a method for designing frequency domain resources for sidelink synchronization signals. In this method, in order to support communication and coexistence between terminals with different capabilities in the same system, and to ensure that the sidelink synchronization process can be completed, a smaller frequency band resource (frequency domain resource) can be defined / configured in the frequency domain for sending / receiving S-SSB. Among them, this smaller frequency band resource can be used as a public frequency domain resource dedicated to the transmission of system messages such as synchronization, so that the synchronization between all terminals of the side link can be guaranteed first. In addition, the method also supports additional frequency band resources for sending additional S-SSBs, and the additional frequency band resources can be used as a supplement to the transmission / reception of synchronization signals between full-capability terminals. In some embodiments, for weak-capability terminals, the synchronization process and the service data communication process can be placed on different frequency band resources by BWP switching, so that the frequency domain resources can be used more efficiently.

[0297] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0298] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0299] Based on the aforementioned embodiments, the embodiments of the present application provide corresponding side synchronization devices.

[0300] FIG20 is a schematic diagram of the structure of a side synchronization device provided in an embodiment of the present application, which is applied to a terminal. As shown in FIG20 , the side synchronization device 2000 includes:

[0301] The transceiver unit 2000 is used to send or receive a sidelink synchronization signal block S-SSB on a first frequency domain resource; wherein the first frequency domain resource is part of the system frequency domain resources.

[0302] In some embodiments, the system frequency domain resources include multiple S-SSB frequency domain resources in a sidelink bandwidth part SL BWP; the first frequency domain resources are part of the S-SSB frequency domain resources in the multiple S-SSB frequency domain resources.

[0303] In some embodiments, the frequency domain positions and / or quantities of the multiple S-SSB frequency domain resources are pre-configured or network configured.

[0304] In some embodiments, when the multiple S-SSB frequency domain resources are continuously distributed, the frequency domain positions of the multiple S-SSB frequency domain resources are determined based on the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources; when the multiple S-SSB frequency domain resources are discontinuously distributed, the frequency domain positions of the multiple S-SSB frequency domain resources are determined based on the starting position and length of each S-SSB frequency domain resource; or, are determined based on the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval between two adjacent S-SSB frequency domain resources.

[0305] In some embodiments, the number of the multiple S-SSB frequency domain resources is: the number of repetitions of an S-SSB in the SL BWP.

[0306] In some embodiments, the system frequency domain resources include multiple sub-bandwidths in an SL BWP, at least one of the multiple sub-bandwidths includes S-SSB frequency domain resources; the first frequency domain resources are part of the sub-bandwidths in the multiple sub-bandwidths, and the part of the sub-bandwidth includes S-SSB frequency domain resources.

[0307] In some embodiments, for each sub-bandwidth in the portion of the sub-bandwidth, the frequency domain resources for sending S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the sub-bandwidth.

[0308] In some embodiments, the sub-bandwidths in the portion of sub-bandwidths are adjacent in the frequency domain; or, the sub-bandwidths in the portion of sub-bandwidths are not adjacent in the frequency domain; or, a portion of the sub-bandwidths in the portion of sub-bandwidths are adjacent in the frequency domain.

[0309] In some embodiments, in a sub-bandwidth including S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources included in each sub-bandwidth is pre-configured or network configured.

[0310] In some embodiments, in a sub-bandwidth including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth and the total length of the S-SSB frequency domain resources in the sub-bandwidth; when the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in the sub-bandwidth; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth, the total length of the S-SSB frequency domain resources in the sub-bandwidth, and the interval between two adjacent S-SSB frequency domain resources in the sub-bandwidth.

[0311] In some embodiments, in a sub-bandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each sub-bandwidth is: the number of repetitions of an S-SSB in the sub-bandwidth; wherein, the number of S-SSB frequency domain resources contained in different sub-bandwidths is the same or different.

[0312] In some embodiments, a sub-bandwidth is a set of resource blocks, a channel, a frequency range, or a resource pool.

[0313] In some embodiments, when the sub-bandwidth is a frequency range or a resource pool, the multiple sub-bandwidths in the SL BWP overlap or do not overlap in the frequency domain; when the sub-bandwidth is a resource block set or a channel, the multiple sub-bandwidths in the SL BWP do not overlap in the frequency domain.

[0314] In some embodiments, the system frequency domain resources include multiple SL BWPs, at least one of which includes S-SSB frequency domain resources; the first frequency domain resources are part of the multiple SL BWPs, which includes S-SSB frequency domain resources.

[0315] In some embodiments, for each SL BWP in the portion of SL BWPs, the frequency domain resources for sending the S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the SL BWP.

[0316] In some embodiments, the SL BWPs in the portion of SL BWPs are adjacent in the frequency domain; or, the SL BWPs in the portion of SL BWPs are not adjacent in the frequency domain; or, some of the SL BWPs in the portion of SL BWPs are adjacent in the frequency domain.

[0317] In some embodiments, in the SL BWP including S-SSB frequency domain resources, the frequency domain location and / or quantity of the S-SSB frequency domain resources included in each SL BWP is pre-configured or network configured.

[0318] In some embodiments, in a SL BWP including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP and the total length of the S-SSB frequency domain resources in the SL BWP; when the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each SL BWP is determined based on the starting position and length of each S-SSB frequency domain resource in the SL BWP; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP, the total length of the S-SSB frequency domain resources in the SL BWP, and the interval between two adjacent S-SSB frequency domain resources in the SL BWP.

[0319] In some embodiments, in a SL BWP including S-SSB frequency domain resources, the number of S-SSB frequency domain resources included in each SL BWP is: the number of repetitions of an S-SSB in the SL BWP; wherein, the number of S-SSB frequency domain resources included in different SL BWPs is the same or different.

[0320] In some embodiments, the system frequency domain resources include multiple carriers, at least one of the multiple carriers contains S-SSB frequency domain resources; the first frequency domain resources are part of the multiple carriers, and the part of the carriers contains S-SSB frequency domain resources.

[0321] In some embodiments, for each carrier in the portion of carriers, the frequency domain resources for sending S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the carrier.

[0322] In some embodiments, the carriers in the portion of carriers are adjacent in the frequency domain; or, the carriers in the portion of carriers are not adjacent in the frequency domain; or, some of the carriers in the portion of carriers are adjacent in the frequency domain.

[0323] In some embodiments, in a carrier including S-SSB frequency domain resources, the frequency domain position and / or number of S-SSB frequency domain resources included in each carrier is pre-configured or network configured.

[0324] In some embodiments, in a carrier including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each carrier is determined based on the starting position of the first S-SSB frequency domain resource in the carrier and the total length of the S-SSB frequency domain resources in the carrier; when the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource in the carrier; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the carrier, the total length of the S-SSB frequency domain resources in the carrier, and the interval between two adjacent S-SSB frequency domain resources in the carrier.

[0325] In some embodiments, in a carrier containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each carrier is: the number of repetitions of an S-SSB in the carrier; wherein, the number of S-SSB frequency domain resources contained in different carriers is the same or different.

[0326] In some embodiments, the system frequency domain resources further include second frequency domain resources, which are frequency domain resources in the system frequency domain resources except the first frequency domain resources; the second frequency domain resources are used to send or receive service data.

[0327] In some embodiments, the second frequency domain resources do not include S-SSB frequency domain resources.

[0328] In some embodiments, the system frequency domain resources also include second frequency domain resources, which are frequency domain resources in the system frequency domain resources other than the first frequency domain resources; when the device 2000 has the ability to send or receive S-SSB on the second frequency domain resources, the second frequency domain resources are used to send or receive S-SSB.

[0329] Those skilled in the art should understand that the relevant description of the above-mentioned side synchronization device in the embodiment of the present application can be understood with reference to the relevant description of the side synchronization method in the embodiment of the present application.

[0330] Figure 21 is a schematic structural diagram of a communication device 2100 provided in an embodiment of the present application. The communication device 2100 shown in Figure 21 includes a processor 2110, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0331] Optionally, as shown in FIG21 , the communication device 2100 may further include a memory 2120. The processor 2110 may call and execute a computer program from the memory 2120 to implement the method in the embodiment of the present application.

[0332] The memory 2120 may be a separate device independent of the processor 2110 , or may be integrated into the processor 2110 .

[0333] Optionally, as shown in FIG21 , the communication device 2100 may further include a transceiver 2130 , and the processor 2110 may control the transceiver 2130 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0334] The transceiver 2130 may include a transmitter and a receiver. The transceiver 2130 may further include an antenna, and the number of antennas may be one or more.

[0335] The communication device 2100 may specifically be a terminal in an embodiment of the present application, and the communication device 2100 may implement the corresponding processes implemented by the terminal in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0336] Figure 22 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 2200 shown in Figure 22 includes a processor 2210, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0337] Optionally, as shown in FIG22 , the chip 2200 may further include a memory 2220. The processor 2210 may call and execute a computer program from the memory 2220 to implement the method in the embodiment of the present application.

[0338] The memory 2220 may be a separate device independent of the processor 2210 , or may be integrated into the processor 2210 .

[0339] Optionally, the chip 2200 may further include an input interface 2230. The processor 2210 may control the input interface 2230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0340] Optionally, the chip 2200 may further include an output interface 2240. The processor 2210 may control the output interface 2240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0341] The chip can be applied to the terminal in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0342] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0343] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0344] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0345] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0346] The present application also provides a computer-readable storage medium for storing a computer program. This computer-readable storage medium can be applied to a terminal in the present application, and the computer program causes a computer to execute the corresponding processes implemented by the terminal in each method of the present application. For the sake of brevity, these are not further described here.

[0347] The present application also provides a computer program product including computer program instructions. This computer program product can be applied to a terminal in the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the terminal in each method of the present application. For the sake of brevity, these instructions are not further described here.

[0348] The present application also provides a computer program. This computer program can be applied to the terminal in the present application. When the computer program is executed on a computer, it causes the computer to execute the corresponding process implemented by the terminal in each method of the present application. For the sake of brevity, it is not further described here.

[0349] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0350] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0351] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0352] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0353] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0354] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0355] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A sideline synchronization method, applied to a terminal, the method comprising: Send or receive a sidelink synchronization signal block S-SSB on a first frequency domain resource; wherein the first frequency domain resource is part of the system frequency domain resources.

2. The method according to claim 1, wherein: The system frequency domain resources include a plurality of S-SSB frequency domain resources in a sidelink bandwidth part SL BWP; The first frequency domain resources are part of the multiple S-SSB frequency domain resources.

3. The method according to claim 2, wherein: The frequency domain positions and / or quantities of the multiple S-SSB frequency domain resources are pre-configured or network configured.

4. The method according to claim 2 or 3, wherein: In the case where the multiple S-SSB frequency domain resources are continuously distributed, the frequency domain positions of the multiple S-SSB frequency domain resources are determined based on the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources; In the case that the multiple S-SSB frequency domain resources are distributed non-continuously, the frequency domain positions of the multiple S-SSB frequency domain resources are determined based on the starting position and length of each S-SSB frequency domain resource; or, are determined based on the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval between two adjacent S-SSB frequency domain resources.

5. The method according to any one of claims 2 to 4, wherein: The number of the multiple S-SSB frequency domain resources is: the number of repetitions of an S-SSB in the SL BWP.

6. The method according to claim 1, wherein: The system frequency domain resources include multiple sub-bandwidths in one SL BWP, and at least one sub-bandwidth of the multiple sub-bandwidths includes S-SSB frequency domain resources; The first frequency domain resource is a portion of the sub-bandwidths among the multiple sub-bandwidths, and the portion of the sub-bandwidth includes an S-SSB frequency domain resource.

7. The method according to claim 6, wherein: For each sub-bandwidth in the partial sub-bandwidth, the frequency domain resources for sending the S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the sub-bandwidth.

8. The method according to claim 6 or 7, wherein: The sub-bandwidths in the partial sub-bandwidths are adjacent in the frequency domain; or, The sub-bandwidths in the partial sub-bandwidths are not adjacent in the frequency domain; or, Some of the sub-bandwidths are adjacent in the frequency domain.

9. The method according to any one of claims 6 to 8, wherein: In the sub-bandwidth containing S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources contained in each sub-bandwidth is pre-configured or network configured.

10. The method according to any one of claims 6 to 9, wherein: In a sub-bandwidth including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each sub-bandwidth is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth and the total length of the S-SSB frequency domain resources in the sub-bandwidth; In the case where the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in the sub-bandwidth; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth, the total length of the S-SSB frequency domain resources in the sub-bandwidth, and the interval between two adjacent S-SSB frequency domain resources in the sub-bandwidth.

11. The method according to any one of claims 6 to 10, wherein: In a sub-bandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each sub-bandwidth is: the number of repetitions of an S-SSB in the sub-bandwidth; wherein, the number of S-SSB frequency domain resources contained in different sub-bandwidths is the same or different.

12. The method according to any one of claims 6 to 11, wherein: The sub-bandwidth is a set of resource blocks, a channel, a frequency range or a resource pool.

13. The method according to claim 12, wherein: In the case where the sub-bandwidth is a frequency range or a resource pool, the multiple sub-bandwidths in the SL BWP overlap or do not overlap in the frequency domain; In the case where the sub-bandwidth is a resource block set or a channel, multiple sub-bandwidths in the SL BWP do not overlap in the frequency domain.

14. The method according to claim 1, wherein: The system frequency domain resources include multiple SL BWPs, at least one SL BWP of the multiple SL BWPs includes an S-SSB frequency domain resource; The first frequency domain resource is a part of the SL BWPs among the multiple SL BWPs, and the part of the SL BWPs includes S-SSB frequency domain resources.

15. The method according to claim 14, wherein: For each SL BWP in the partial SL BWP, the frequency domain resources for sending the S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the SL BWP.

16. The method according to claim 14 or 15, wherein: The SL BWPs in the part of SL BWPs are adjacent in the frequency domain; or, The SL BWPs in the part of SL BWPs are not adjacent in the frequency domain; or, Some of the SL BWPs are adjacent in the frequency domain.

17. The method according to any one of claims 14 to 16, wherein: In the SL BWP including the S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources included in each SL BWP is pre-configured or network configured.

18. The method according to any one of claims 14 to 17, wherein: In a SL BWP including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP and the total length of the S-SSB frequency domain resources in the SL BWP; When the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position and length of each S-SSB frequency domain resource in the SL BWP; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP, the total length of the S-SSB frequency domain resources in the SL BWP, and the interval between two adjacent S-SSB frequency domain resources in the SL BWP.

19. The method according to any one of claims 14 to 18, wherein: In the SL BWP containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each SL BWP is: the number of repetitions of an S-SSB in the SL BWP; wherein, the number of S-SSB frequency domain resources contained in different SL BWPs is the same or different.

20. The method according to claim 1, wherein: The system frequency domain resources include multiple carriers, at least one carrier among the multiple carriers includes S-SSB frequency domain resources; The first frequency domain resources are part of the multiple carriers, and the part of the carriers includes S-SSB frequency domain resources.

21. The method according to claim 20, wherein: For each carrier in the partial carriers, the frequency domain resources for sending the S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the carrier.

22. The method according to claim 20 or 21, wherein: The carriers in the part of carriers are adjacent in the frequency domain; or, The carriers in the part of carriers are not adjacent in the frequency domain; or, Some of the carrier waves in the partial carrier waves are adjacent in the frequency domain.

23. The method according to any one of claims 20 to 22, wherein: In a carrier including S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources included in each carrier is pre-configured or network configured.

24. The method according to any one of claims 20 to 23, wherein: In a carrier including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each carrier is determined based on the starting position of the first S-SSB frequency domain resource in the carrier and the total length of the S-SSB frequency domain resources in the carrier; In the case where the S-SSB frequency domain resources are non-continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource in the carrier; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the carrier, the total length of the S-SSB frequency domain resources in the carrier, and the interval between two adjacent S-SSB frequency domain resources in the carrier.

25. The method according to any one of claims 20 to 24, wherein: In a carrier containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each carrier is: the number of repetitions of an S-SSB in the carrier; wherein, the number of S-SSB frequency domain resources contained in different carriers is the same or different.

26. The method according to any one of claims 1 to 25, wherein: The system frequency domain resources further include second frequency domain resources, where the second frequency domain resources are frequency domain resources in the system frequency domain resources except the first frequency domain resources; The second frequency domain resources are used to send or receive service data.

27. The method according to claim 26, wherein: The second frequency domain resources do not include S-SSB frequency domain resources.

28. The method according to any one of claims 1 to 26, wherein: The system frequency domain resources further include second frequency domain resources, where the second frequency domain resources are frequency domain resources in the system frequency domain resources except the first frequency domain resources; When the terminal has the ability to send or receive S-SSB on the second frequency domain resources, the second frequency domain resources are used to send or receive S-SSB.

29. A lateral synchronization device, comprising: A transceiver unit is used to send or receive a sidelink synchronization signal block S-SSB on a first frequency domain resource; wherein the first frequency domain resource is part of the system frequency domain resources.

30. The device according to claim 29, wherein: The system frequency domain resources include a plurality of S-SSB frequency domain resources in a sidelink bandwidth part SL BWP; The first frequency domain resources are part of the multiple S-SSB frequency domain resources.

31. The device according to claim 30, wherein The frequency domain positions and / or quantities of the multiple S-SSB frequency domain resources are pre-configured or network configured.

32. The device according to claim 30 or 31, wherein: In the case where the multiple S-SSB frequency domain resources are continuously distributed, the frequency domain positions of the multiple S-SSB frequency domain resources are determined based on the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources; In the case that the multiple S-SSB frequency domain resources are distributed non-continuously, the frequency domain positions of the multiple S-SSB frequency domain resources are determined based on the starting position and length of each S-SSB frequency domain resource; or, are determined based on the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval between two adjacent S-SSB frequency domain resources.

33. The device according to any one of claims 30 to 32, wherein: The number of the multiple S-SSB frequency domain resources is: the number of repetitions of an S-SSB in the SL BWP.

34. The apparatus of claim 29, wherein: The system frequency domain resources include multiple sub-bandwidths in one SL BWP, and at least one sub-bandwidth of the multiple sub-bandwidths includes S-SSB frequency domain resources; The first frequency domain resource is a portion of the sub-bandwidths among the multiple sub-bandwidths, and the portion of the sub-bandwidth includes an S-SSB frequency domain resource.

35. The device according to claim 34, wherein For each sub-bandwidth in the partial sub-bandwidth, the frequency domain resources for sending the S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the sub-bandwidth.

36. The device according to claim 34 or 35, wherein: The sub-bandwidths in the partial sub-bandwidths are adjacent in the frequency domain; or, The sub-bandwidths in the partial sub-bandwidths are not adjacent in the frequency domain; or, Some of the sub-bandwidths are adjacent in the frequency domain.

37. The device according to any one of claims 34 to 36, wherein: In the sub-bandwidth containing S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources contained in each sub-bandwidth is pre-configured or network configured.

38. The device according to any one of claims 34 to 37, wherein: In a sub-bandwidth including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each sub-bandwidth is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth and the total length of the S-SSB frequency domain resources in the sub-bandwidth; In the case where the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in the sub-bandwidth; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth, the total length of the S-SSB frequency domain resources in the sub-bandwidth, and the interval between two adjacent S-SSB frequency domain resources in the sub-bandwidth.

39. The device according to any one of claims 34 to 38, wherein: In a sub-bandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each sub-bandwidth is: the number of repetitions of an S-SSB in the sub-bandwidth; wherein, the number of S-SSB frequency domain resources contained in different sub-bandwidths is the same or different.

40. The device according to any one of claims 34 to 39, wherein: The sub-bandwidth is a set of resource blocks, a channel, a frequency range or a resource pool.

41. The device according to claim 40, wherein In the case where the sub-bandwidth is a frequency range or a resource pool, the multiple sub-bandwidths in the SL BWP overlap or do not overlap in the frequency domain. stack; In the case where the sub-bandwidth is a resource block set or a channel, multiple sub-bandwidths in the SL BWP do not overlap in the frequency domain.

42. The apparatus of claim 29, wherein: The system frequency domain resources include a plurality of SL BWPs, at least one SL BWP of the plurality of SL BWPs includes an S-SSB frequency domain resource; The first frequency domain resource is a part of the SL BWPs among the multiple SL BWPs, and the part of the SL BWPs includes S-SSB frequency domain resources.

43. The device according to claim 42, wherein: For each SL BWP in the partial SL BWP, the frequency domain resources for sending the S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the SL BWP.

44. The device according to claim 42 or 43, wherein: The SL BWPs in the part of SL BWPs are adjacent in the frequency domain; or, The SL BWPs in the part of SL BWPs are not adjacent in the frequency domain; or, Some of the SL BWPs are adjacent in the frequency domain.

45. The device according to any one of claims 42 to 44, wherein In the SL BWP including the S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources included in each SL BWP is pre-configured or network configured.

46. ​​The device according to any one of claims 42 to 45, wherein In a SL BWP including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP and the total length of the S-SSB frequency domain resources in the SL BWP; When the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position and length of each S-SSB frequency domain resource in the SL BWP; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP, the total length of the S-SSB frequency domain resources in the SL BWP, and the interval between two adjacent S-SSB frequency domain resources in the SL BWP.

47. The device according to any one of claims 42 to 46, wherein: In the SL BWP containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each SL BWP is: the number of repetitions of an S-SSB in the SL BWP; wherein, the number of S-SSB frequency domain resources contained in different SL BWPs is the same or different.

48. The apparatus of claim 29, wherein: The system frequency domain resources include multiple carriers, at least one carrier among the multiple carriers includes S-SSB frequency domain resources; The first frequency domain resources are part of the multiple carriers, and the part of the carriers includes S-SSB frequency domain resources.

49. The apparatus of claim 48, wherein: For each carrier in the partial carriers, the frequency domain resources for sending the S-SSB include: all S-SSB frequency domain resources or part of the S-SSB frequency domain resources in the carrier.

50. The device according to claim 48 or 49, wherein The carriers in the part of carriers are adjacent in the frequency domain; or, The carriers in the part of carriers are not adjacent in the frequency domain; or, Some of the carrier waves in the partial carrier waves are adjacent in the frequency domain.

51. The device according to any one of claims 48 to 50, wherein: In a carrier including S-SSB frequency domain resources, the frequency domain position and / or quantity of the S-SSB frequency domain resources included in each carrier is pre-configured or network configured.

52. The device according to any one of claims 48 to 51, wherein: In a carrier including S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each carrier is determined based on the starting position of the first S-SSB frequency domain resource in the carrier and the total length of the S-SSB frequency domain resources in the carrier; In the case where the S-SSB frequency domain resources are non-continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource in the carrier; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the carrier, the total length of the S-SSB frequency domain resources in the carrier, and the interval between two adjacent S-SSB frequency domain resources in the carrier.

53. The device according to any one of claims 48 to 52, wherein: In a carrier containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each carrier is: the number of repetitions of an S-SSB in the carrier; wherein, the number of S-SSB frequency domain resources contained in different carriers is the same or different.

54. The device according to any one of claims 29 to 53, wherein: The system frequency domain resources further include second frequency domain resources, where the second frequency domain resources are frequency domain resources in the system frequency domain resources except the first frequency domain resources; The second frequency domain resources are used to send or receive service data.

55. The apparatus of claim 54, wherein: The second frequency domain resources do not include S-SSB frequency domain resources.

56. The device according to any one of claims 29 to 54, wherein: The system frequency domain resources further include second frequency domain resources, where the second frequency domain resources are frequency domain resources in the system frequency domain resources except the first frequency domain resources; In a case where the device has the capability of sending or receiving S-SSB on the second frequency domain resources, the second frequency domain resources are used to send or receive S-SSB.

57. A terminal, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 28.

58. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 28.

59. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 28.

60. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 28.

61. A computer program causing a computer to execute the method according to any one of claims 1 to 28.

Images