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

Abstract

Embodiments of the present invention provide a sidelink synchronization method comprising a terminal transmitting or receiving a sidelink synchronization signal block (S-SSB) on a first frequency domain resource, the first frequency domain resource being a portion of the system frequency domain resources. By using a portion of the system frequency domain resources to transmit or receive the S-SSB, the method enables the transmission or reception of the S-SSB to be performed with a relatively small bandwidth, thereby allowing for the consideration of terminals with different capabilities within the same communication system, and ensuring that all terminals can achieve synchronization.

Description

[Technical Field]

[0001] This application relates to the field of communications technology, and more particularly to sidelink synchronization methods and devices, terminals, chips, and storage media. [Background technology]

[0002] The sidelink (SL) synchronization process is a crucial step in SL systems and takes place 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 and transmit power. Therefore, in conventional technologies, the frequency domain resources and locations for transmitting / receiving sidelink synchronization signal blocks (S-SSB) are supported by all terminals. For example, in current sidelink over unlicensed spectrum (SL-U) systems, if there are multiple resource block (RB) sets in the frequency domain and S-SSB needs to be transmitted over multiple RB sets, then terminals also need to attempt to detect and receive S-SSB over multiple RB sets.

[0003] However, with technological advancements, supporting multiple terminals with different communication capabilities within the same communication system has become an unavoidable problem. Continuing to assume that all terminals have the same communication capabilities leads to certain difficulties in the SL synchronization process between terminals with different capabilities. Therefore, when terminals with different capabilities coexist within a system, ensuring SL synchronization between terminals with different capabilities is an urgent issue that needs to be resolved. [Overview of the Initiative]

[0004] Embodiments of the present application provide a sidelink synchronization method and apparatus, a terminal, a chip, and a storage medium.

[0005] In a first aspect, an embodiment of the present application provides a sidelink synchronization method applicable to a terminal, the method comprising transmitting or receiving a sidelink synchronization signal block (S-SSB) on a first frequency domain resource, the first frequency domain resource being a subset of frequency domain resources within a system frequency domain resource.

[0006] In a second aspect, an embodiment of the present application provides a sidelink synchronization device comprising a transceiver unit configured to transmit or receive a sidelink synchronization signal block (S-SSB) on a first frequency domain resource, wherein the first frequency domain resource is a subset of the system frequency domain resources.

[0007] In a third aspect, an embodiment of the present application provides a terminal comprising a processor and memory. The memory is configured to store computer programs, and the processor performs the side-link synchronization method described above by calling and executing the computer programs stored in the memory.

[0008] In a fourth aspect, an embodiment of the present application provides a chip that implements the above-described sidelink synchronization method. Specifically, the chip includes a processor configured to cause a device on which the chip is mounted to execute the above-described sidelink synchronization method by calling and executing a computer program from memory.

[0009] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, the computer program causing the computer to execute the above-described side-link synchronization method.

[0010] In a sixth aspect, an embodiment of the present application provides a computer program product including computer program instructions, which cause a computer to execute the sidelink synchronization method described above.

[0011] In the seventh aspect, an embodiment of the present application provides a computer program which, when executed on a computer, causes the computer to perform the sidelink synchronization method described above.

[0012] The aforementioned method enables S-SSB transmission or reception with a relatively small bandwidth by using some of the frequency domain resources within the system's frequency domain resources, thereby allowing for the consideration of terminals with different capabilities within the same communication system, and ultimately ensuring that all terminals can achieve synchronization. [Brief explanation of the drawing]

[0013] [Figure 1] This is a schematic diagram of sidelink communication within network coverage provided in the embodiment of the present invention. [Figure 2] This is a schematic diagram of sidelink communication in partial network coverage provided in the embodiment of the present application. [Figure 3] This is a schematic diagram of sidelink communication outside of network coverage provided in the embodiment of the present application. [Figure 4] This is a schematic diagram of a sidelink communication having a central control node provided in an embodiment of the present invention. [Figure 5] This is a schematic diagram of the unicast transmission method provided in the embodiment of the present application. [Figure 6] This is a schematic diagram of the multicast transmission method provided in the embodiment of the present application. [Figure 7] This is a schematic diagram of the broadcast transmission method provided in the embodiment of the present application. [Figure 8] This is a schematic diagram of the slot structure in the NR-V2X provided in the embodiment of the present application. [Figure 9] This is a schematic diagram showing how the OFDM symbols available within a location change in different transmissions of a single PSSCH provided in the embodiment of the present application. [Figure 10]It is a schematic diagram of the mapping method of the second-stage SCI provided in the embodiments of the present application. [Figure 11] It is a schematic diagram of the time domain and frequency domain positions of the PSCCH DMRS provided in the embodiments of the present application. [Figure 12] It is a schematic diagram of the time domain positions of four DMRS symbols when the PSSCH provided in the embodiments of the present application has 13 symbols. [Figure 13] It is a schematic diagram of the single-symbol DMRS frequency domain type 1 provided in the embodiments of the present application. [Figure 14] It is a schematic diagram of the time domain and frequency domain positions of the SL CSI-RS provided in the embodiments of the present application. [Figure 15] It is a schematic diagram showing an example of the channel occupancy time and channel occupancy provided in the embodiments of the present application. [Figure 16] It is a schematic diagram of the frequency domain resource division provided in the embodiments of the present application. [Figure 17] It is a flowchart of the sidelink synchronization method provided in the embodiments of the present application. [Figure 18] It is the first schematic diagram of the frequency domain resource design of the S-SSB provided in the embodiments of the present application. [Figure 19] It is the second schematic diagram of the frequency domain resource design of the S-SSB provided in the embodiments of the present application. [Figure 20] It is a schematic configuration diagram of the sidelink synchronization device provided in the embodiments of the present application. [Figure 21] It is a schematic structural diagram of the communication device provided in the embodiments of the present application. [Figure 22] It is a schematic structural diagram of the chip according to the embodiments of the present application.

Embodiments for Carrying Out the Invention

[0014] The drawings described above are for providing a further understanding of the present application and constitute a part of the present application. The exemplary embodiments of the present application and their descriptions are for explaining the present application and do not constitute an undue limitation to the present application.

[0015] In the following, the technical solutions of the embodiments of the present application will be described with reference to the drawings of the embodiments of the present application, but obviously the embodiments described are only a part of the embodiments of the present application, not all of them. All other embodiments that can be obtained by a person skilled in the art without creative effort based on the embodiments of the present application are included in the scope of protection of the present application.

[0016] The technical solutions of the embodiments of this application are applicable to various side-link communication systems. To facilitate understanding of the technical solutions of the embodiments of this application, related technologies of the embodiments of this application are described below. The following related technologies can be optionally combined with the technical solutions of the embodiments of this application as selectable solutions, and they are all covered within the scope of protection of the embodiments of this application.

[0017] 1. Sidelink communication across different network coverages Sidelink communication can be divided into four types depending on the network coverage status of the terminal performing the communication: sidelink communication within network coverage, sidelink communication in partial network coverage, sidelink communication outside network coverage, and sidelink communication with a central control node, as shown in Figures 1, 2, 3, and 4, respectively.

[0018] As shown in Figure 1, in sidelink communication within network coverage, all terminals performing sidelink communication are within the coverage of the same base station. Therefore, all of these terminals receive the base station's configuration signaling and can perform sidelink communication based on the same sidelink configuration.

[0019] As shown in Figure 2, in the case of sidelink communication in partial network coverage, some of the terminals performing sidelink communication are within the base station's coverage, and these terminals can receive the base station's configuration signaling and perform sidelink communication according to the base station's configuration. On the other hand, terminals outside the network coverage cannot receive the base station's configuration signaling. In this case, terminals outside the network coverage determine the sidelink configuration based on pre-configuration information and information contained in the Physical Sidelink Broadcast Channel (PSBCH) transmitted by terminals within the network coverage, and perform sidelink communication accordingly.

[0020] As shown in Figure 3, in the case of sidelink communication outside of network coverage, all terminals performing sidelink communication are outside of network coverage, and all terminals determine the sidelink configuration based on pre-configuration information and perform sidelink communication.

[0021] As shown in Figure 4, in the case of sidelink communication with a central control node, multiple terminals constitute a single communication group, and this communication group has a central control node (such as UE1 in Figure 4). Here, the central control node may also be called a cluster header (CH). This central control node has at least one of the following functions: responsible for establishing the communication group, managing the joining and leaving of group members, coordinating resources, allocating sidelink transmission resources to other terminals, receiving sidelink feedback information from other terminals, and coordinating resources with other communication groups.

[0022] 2. Device-to-Device (D2D) / Vehicle-to-Everything (V2X) Device-to-device communication is a D2D-based sidelink transmission technology, which differs from the conventional cellular system's method of receiving or transmitting communication data via a base station. Therefore, it has higher spectral efficiency and lower transmission delay. Vehicle internet systems employ a direct communication method between terminals, and the 3rd Generation Partnership Project (3GPP®) defines two transmission modes: Mode 1 and Mode 2.

[0023] Mode 1: The terminal's transmission resources are allocated by the base station, and the terminal transmits data over the sidelink according to the resources allocated by the base station. The base station can allocate resources to the terminal for one-way transmission or for semi-static transmission. As shown in Figure 1, the terminal is within network coverage, and the network allocates transmission resources to the terminal for sidelink transmission.

[0024] Mode 2: The terminal selects one resource from the resource pool to transmit data. As shown in Figure 3, the terminal is outside of cell coverage and autonomously selects a transmission resource from a pre-configured resource pool to perform sidelink transmission. Alternatively, as shown in Figure 1, the terminal autonomously selects a transmission resource from a resource pool configured by the network to perform sidelink transmission.

[0025] 3. New Radio - Vehicle Internet (NR-V2X: New Radio - Vehicle to Everything) Because NR-V2X needs to support autonomous driving, it imposes higher requirements on vehicle-to-vehicle data interaction, including higher throughput, lower latency, higher reliability, wider coverage, and more flexible resource allocation.

[0026] LTE-V2X supports broadcast transmission, while NR-V2X introduces unicast and multicast transmission methods. In unicast transmission, there is only one receiving terminal, and as shown in Figure 5, unicast transmission takes place between UE1 and UE2. In multicast transmission, the receiving side is all terminals in a communication group, or all terminals within a certain transmission distance, and as shown in Figure 6, UE1, UE2, UE3, and UE4 form a communication group, with UE1 transmitting data and all other terminal devices in that group being receiving terminals. In broadcast transmission, the receiving side is any terminal around the transmitting terminal, and as shown in Figure 7, UE1 is the transmitting terminal, and all other terminals around it, UE2 to UE6, are receiving terminals.

[0027] 4. NR-V2X System Frame Structure The slot structure in the NR-V2X is shown in Figure 8.

[0028] Figure 8(a) is a schematic diagram of a slot structure that does not include a physical sidelink feedback channel (PSFCH). Figure 8(b) is a schematic diagram of a slot structure that includes a PSFCH channel.

[0029] In NR-V2X, a Physical Sidelink Control Channel (PSCCH) occupies two or three Orthogonal Frequency Division Multiplexing (OFDM) symbols in the time domain, starting from the second sidelink symbol of the slot, and can occupy {10, 12, 15, 20, 25} Physical Resource Blocks (PRBs) in the frequency domain. To reduce the complexity of blind detection of PSCCHs by User Equipment (UE), only one PSCCH symbol and PRB count is permitted within a single resource pool. Furthermore, since subchannels are the smallest granularity of resource allocation for Physical Sidelink Shared Channels (PSSCHs) in NR-V2X, the number of PRBs occupied by a PSCCH must be less than or equal to the number of PRBs contained in a single subchannel within the resource pool. This avoids imposing additional restrictions on the selection or allocation of PSSCH resources. In the time domain, the PSSCH begins with the second sidelink symbol of the slot, the last time domain symbol of the slot is the Guard Period (GP) symbol, and the remaining symbols are mapped to the PSSCH. The first sidelink symbol of the slot is a repetition of the second sidelink symbol, and the receiving terminal typically uses the first sidelink symbol as the Automatic Gain Control (AGC) symbol, and the data on this symbol is not typically used for data demodulation. The PSSCH occupies K subchannels in the frequency domain, and each subchannel contains N consecutive PRBs.

[0030] If a slot contains a PSFCH channel, the second-to-last and third-to-last symbols of that slot are used for PSFCH channel transmission, as shown in Figure 8(b), and one time-domain symbol preceding the PSFCH channel is used as the GP symbol.

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

[0032] In NR-V2X, the PSSCH supports up to two stream transmissions, mapping data on two layers to two antenna ports using a unit precoding matrix, and transmitting a maximum of one Transport Block (TB) within a single PSSCH. However, unlike the transmission method of the PSSCH data portion, when the PSSCH employs a dual-stream transmission method, the modulation symbols transmitted by the second-stage SCI on the two streams are exactly the same, and such a design can guarantee the reception performance of the second-stage SCI on channels with high correlation.

[0033] Since the maximum number of retransmissions for a single PSSCH in NR-V2X is 32, if a PSFCH resource exists in the resource pool and the configuration cycle of the PSFCH resource is 2 or 4, the number of OFDM symbols available in a slot where different transmissions of a single PSSCH are located may change, as shown in Figure 9.

number

number

number

number

number

[0034] The coding rate of the second-stage SCI is dynamically adjustable within a certain range, and the coding rate used is specifically indicated by the first-stage SCI; therefore, even after the coding rate is changed, the receiver does not need to perform blind detection of the second-stage SCI. As shown in Figure 10, the modulation symbols of the second-stage SCI are mapped starting from the symbol where the first PSSCH DMRS is located, first in the frequency domain and then in the time domain. On the OFDM symbol where the DMRS is located, the second-stage SCI is mapped to REs that are not occupied by the DMRS.

[0035] Within a single resource pool, the data portion of a PSSCH can employ multiple different Modulation and Coding Scheme (MCS) tables. These include the conventional 64QAM MCS table, the 256QAM MCS table, and the low-spectral efficiency 64QAM MCS table. The specific MCS table used in a single transmission is indicated by the "MCS Table Indicator" field of the first-stage SCI. To control the Peak-to-Average Power Ratio (PAPR), the PSSCH must be transmitted using consecutive PRBs. Since subchannels represent the smallest frequency domain resource granularity of the PSSCH, the PSSCH is required to occupy consecutive subchannels.

[0036] 6. Sidelink transmission block size PSSCH follows the transmission block size (TBS) determination mechanism for physical downlink shared channels (PDSCH) and physical uplink shared channels (PUSCH) in New Radio (NR). Specifically, it determines the TBS based on a reference value for the number of REs used by the PSSCH within the slot where it is located, thereby bringing the actual coding rate as close as possible to the target coding rate. The purpose of using a reference value for the number of REs rather than the actual number of REs is to ensure that the number of REs used to determine the TBS during the PSSCH retransmission process remains constant, thereby ensuring that the size of the determined TBS remains the same. To achieve this objective, a reference value N for the number of REs occupied by the PSSCH in the TBS determination process is used. RE This is determined according to Equation 1.

[0037]

number

number

number

number

[0038]

number

number

number

number

number

number

[0039] [Table 1]

[0040] 7. Sidelink DMRS In NR-V2X, the DMRS pattern of the PSCCH is the same as that of the NR Physical Downlink Control Channel (PDCCH), that is, as shown in Figure 11, the DMRS resides on the OFDM symbol of each PSCCH and is located at {#1,#5,#9} REs of a single PRB in the frequency domain. The DMRS sequence of the PSCCH is generated by Equation 3.

[0041]

number

number

number

number

number

[0042] NR-V2X employs multiple time-domain PSSCH DMRS patterns, drawing inspiration from the NR Uu interface design. Within a single resource pool, the number of available DMRS patterns is related to the number of PSSCH symbols in the resource pool. For a given number of PSSCH symbols (including the first AGC symbol) and PSSCH symbols, the available DMRS patterns and the positions of each DMRS symbol within each pattern are shown in Table 2. Figure 12 is a schematic diagram of the time-domain positions of four DMRS symbols when the PSSCH has 13 symbols.

[0043] [Table 2]

[0044] When multiple time-domain DMRS patterns are configured within a resource pool, the specific time-domain DMRS pattern to be adopted is selected by the transmitting UE and indicated in the first-stage SCI. This design allows fast-moving UEs to select high-density DMRS patterns to ensure accuracy in channel estimation, while slow-moving UEs can improve spectral efficiency by adopting low-density DMRS patterns.

[0045] The PSSCH DMRS sequence generation method is almost exactly the same as the PSCCH DMRS sequence generation method, the only difference being the initialization formula C of the pseudo-random sequence c(m). init In,

number

[0046] NR PDSCH and PUSCH support two types of frequency-domain DMRS patterns: DMRS frequency-domain type 1 and DMRS frequency-domain type 2. Each frequency-domain type has two distinct subtypes: single-symbol DMRS and double-symbol DMRS. Single-symbol DMRS frequency-domain type 1 supports four DMRS ports, single-symbol DMRS frequency-domain type 2 supports six DMRS ports, and double-symbol DMRS doubles the number of supported ports. However, in NR-V2X, since the PSSCH needs to support a maximum of two DMRS ports, only single-symbol DMRS frequency-domain type 1 is supported, as shown in Figure 13.

[0047] 8. Sidelink Channel State Information Reference Signal (CSI-RS) To better support unicast communication, the NR-V2X supports SL CSI-RS, which is transmitted only when the following three conditions are met.

[0048] 1) The UE must transmit the corresponding PSSCH; in other words, the UE cannot transmit only SL CSI-RS.

[0049] 2) Higher-level signaling activates side-linked CSI reporting.

[0050] 3) If upper-layer signaling activates sidelink CSI reporting, the corresponding bits of the second-stage SCI sent by the UE trigger sidelink CSI reporting.

[0051] The maximum number of ports supported by SL CSI-RS is 2. In the case of two ports, the SL CSI-RS from different ports are multiplexed using a code-splitting method on two adjacent REs of the same OFDM symbol, and the number of SL CSI-RS from each port within a single PRB is 1, i.e., the density is 1. Therefore, within a single PRB, an SL CSI-RS appears on at most one OFDM symbol, and the specific location of that OFDM symbol is determined by the transmitting terminal. To avoid affecting the resource mapping of the PSCCH and second-stage SCI, SL CSI-RS cannot be located on the same OFDM symbol as the PSCCH and second-stage SCI. The channel estimation accuracy of the OFDM symbol on which the PSSCH DMRS is located is relatively high, and since the SL CSI-RS from two ports occupies two consecutive REs in the frequency domain, SL CSI-RS cannot transmit on the same OFDM symbol as the PSSCH DMRS. The location of the OFDM symbol where SL CSI-RS is located is indicated by the sl-CSI-RS-FirstSymbol parameter in the PC5 RRC.

[0052] The position of the first RE occupied by an SL CSI-RS within a single PRB is indicated by the sl-CSI-RS-FreqAllocation parameter in the PC5 RRC. If the SL CSI-RS has one port, this parameter is a bitmap of length 12, corresponding to 12 REs within a single PRB. If the SL CSI-RS has two ports, this parameter is a bitmap of length 6, in which case the SL CSI-RS occupies two REs: 2f(1) and 2f(1)+1. Here, f(1) represents the index of the bit with a value of 1 in the above 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 must not conflict with the PT-RS. Figure 14 is a schematic diagram of the time domain and frequency domain positions of the SL CSI-RS. In Figure 14, the number of ports for SL CSI-RS is 2, sl-CSI-RS-FirstSymbol is 8, and sl-CSI-RS-FreqAllocation is [b5,b4,b3,b2,b1,b0]=[0,0,0,1,0,0].

[0053] 9. 5G unlicensed (NR-U) spectrum communication The NR system, introduced in the 3GPP R15 standard, is a communication technology for use in existing and new licensed spectra. The NR system enables seamless coverage, high spectral efficiency, high peak rates, and high reliability in cellular networks. Long-Term Evolution (LTE) systems enable the use of unlicensed spectra (or unlicensed spectra) as a complementary frequency band to licensed spectra in cellular networks. Similarly, the NR system can also use unlicensed spectra as part of 5G cellular network technology to provide services to users. The 3GPP R16 standard discusses NR systems used in unlicensed spectra, referred to as NR-unlicensed (NR-U).

[0054] The NR-U system supports two network configuration methods: authorized spectrum-assisted access and unauthorized spectrum-independent access. The former requires access to the network via authorized spectrum, with unauthorized spectrum used as an auxiliary carrier. The latter allows for independent network configuration via unauthorized spectrum, with UEs directly accessing the network via unauthorized spectrum. The range of unauthorized spectrum used by NR-U systems, as introduced in 3GPP R16, is concentrated in the 5GHz and 6GHz frequency bands, e.g., 5925-7125MHz in the US, or 5925-6425MHz in Europe. The R16 standard newly defines band 46 (5150MHz-5925MHz) as being used as the unauthorized spectrum.

[0055] Unlicensed spectra are spectra allocated by countries or regions for the communication of radio equipment, and these spectra are usually considered shared spectra. That is, communication equipment can use these spectra without applying for a specialized spectrum license from a specialized spectrum management body in the country or region, provided that it meets the regulatory requirements set by the country or region for those spectra. The use of unlicensed spectra must meet the specific regulatory requirements of each country or region; for example, communication equipment uses unlicensed spectra in accordance with the "Listen Before Talk (LBT)" principle. Therefore, NR technology needs to be adapted to the regulatory requirements of unlicensed frequency bands and to undergo corresponding enhancements in order to efficiently utilize unlicensed spectra to provide services. The 3GPP R16 standard has completed the standardization of NR-U technology, mainly in aspects such as channel monitoring processes, initial access processes, control channel design, Hybrid Automatic Repeat reQuest (HARQ) and scheduling, and grant-free transmission.

[0056] 10. Channel Monitoring: LBT To ensure that various communication systems using unlicensed spectrum can coexist amicably on that spectrum, some countries or regions have established regulatory requirements that must be met when using unlicensed spectrum. For example, according to European regulations, when communicating on unlicensed spectrum, communication equipment must adhere to the "LBT" principle. That is, communication equipment must first perform LBT, or channel monitoring, before transmitting a signal using a channel on an unlicensed spectrum. Only if the channel monitoring shows that the channel is idle or that LBT was successful, the communication equipment can transmit a signal over that channel. If the channel monitoring by the communication equipment shows that the channel is busy or that LBT failed, the communication equipment cannot transmit a signal over that channel. Furthermore, to ensure fairness in the use of spectrum resources on a shared spectrum, if communication equipment successfully performs LBT on a channel on an unlicensed spectrum, the time that communication equipment can transmit using that channel must not exceed a certain time limit. The mechanism limits the maximum communication time after a single LBT success, thereby giving different communication devices the opportunity to access the shared channel and enabling different communication systems to coexist amicably on the shared spectrum.

[0057] While channel monitoring is not a global regulation, it offers advantages such as interference avoidance and friendly coexistence in communication transmission between communication systems in the shared spectrum. Therefore, in the design process of NR systems in the unlicensed spectrum, channel monitoring is a characteristic that communication equipment in such systems must support. From the perspective of the system's network configuration, channel monitoring includes two mechanisms. One is LBT for load-based equipment (LBE), also known as dynamic channel monitoring or dynamic channel occupancy. The other is LBT for frame-based equipment (FBE), also known as semi-static channel monitoring or semi-static channel occupancy.

[0058] 11. Dynamic Channel Monitoring Dynamic channel monitoring can also be considered a LBE-based LBT scheme, whose channel monitoring principle is that communication equipment performs LBT on an unlicensed spectrum carrier after the service arrives, and begins transmitting signals on that carrier after successful LBT. Dynamic channel monitoring LBT schemes include Type 1 channel access schemes and Type 2 channel access schemes. The Type 1 channel access scheme is a multi-slot channel detection with random backoff based on competition window size adjustment, where a corresponding Channel Access Priority Class (CAPC) p can be selected according to the priority of the service being transmitted. The Type 2 channel access scheme is a channel access scheme based on fixed-length monitoring slots, where Type 2 channel access schemes include Type 2A channel access, Type 2B channel access, and Type 2C channel access. The Type 1 channel access scheme is mainly used for communication equipment to initiate channel occupancy, while the Type 2 channel access scheme is mainly used for communication equipment to share channel occupancy. In a special case, if a base station initiates channel occupancy to transmit a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block within a Discover Reference Symbol (DRS) window, and the DRS window does not contain UE unicast data transmission, the base station may initiate channel occupancy using Type 2A channel access if the DRS window length does not exceed 1 ms and the duty cycle of the DRS window transmission does not exceed 1 / 20.

[0059] Figure 15 shows an example of a single channel occupancy time obtained after a communication device successfully performs LBT on an unlicensed spectrum channel, and the use of resources within that channel occupancy time to transmit a signal.

[0060] 12. Default Channel Access Method on the Base Station Side: Type1 Channel Access Taking the base station as an example, the channel access parameters corresponding to the channel access priority p on the base station side are as shown in Table 3. In Table 3, m p refers to the number of fallback slots corresponding to the channel access priority p, and CW p refers to the contention window (CW) size corresponding to the channel access priority p, CW min,p refers to the minimum value of CW corresponding to the channel access priority p, CW p refers to the minimum value of CW, CW max,p refers to the maximum value of CW corresponding to the channel access priority p, CW p refers to the maximum value of CW, T mcot,p refers to the maximum channel occupancy time length corresponding to the channel access priority p.

[0061] When the channel access process ends, 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 shall not exceed T mcot,p .

[0062]

Table 3

[0063] 13. Sharing of Channel Occupancy Time on the Base Station Side After a base station begins its Channel Occupancy Time (COT), it can not only use the resources within the COT for downlink transmission, but also share those resources with the UE for uplink transmission. When resources within the COT are shared with the UE for uplink transmission, the channel access methods available to the UE are Type 2A channel access, Type 2B channel access, or Type 2C channel access, where Type 2A channel access, Type 2B channel access, and Type 2C channel access are all channel access methods based on fixed-length monitoring slots.

[0064] Type 2A channel access: The UE's channel detection method is a 25μs single-slot channel detection. Specifically, in Type 2A channel access, the UE performs a 25μs channel monitoring before transmission begins, and transmission can commence only after successful channel monitoring.

[0065] Type 2B channel access: The UE's channel detection method is a 16μs single-slot channel detection. Specifically, in Type 2B channel access, the UE performs a 16μs channel monitoring before transmission begins, and transmission can commence only after successful channel monitoring. Here, the gap size between the start position of the current transmission and the end position of the previous transmission is 16μs.

[0066] Type 2C channel access: The UE transmits without channel detection after the gap ends. Specifically, in Type 2C channel access, the UE can transmit directly, where the gap size between the start of the current transmission and the end of the previous transmission is 16 μs or less. The length of the current transmission does not exceed 584 μs.

[0067] 14. Channel access parameter instruction (including Cyclic Prefix Extension (CPE)) In the NR-U system, when a UE schedules transmission on a Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH), the base station can specify the channel access scheme corresponding to the PUSCH or PUCCH via Downlink Control Information (DCI), which includes an uplink grant (UL grant) or downlink grant (DL grant). Since some channel access schemes require a gap of 16 μs or 25 μs, the UE can ensure the gap size between two transmissions by transmitting a cyclic prefix extension (CPE). Accordingly, the base station can specify the CPE length of the first symbol in the UE's uplink transmission.

[0068] In specific instructions, the base station can explicitly instruct the UE on channel access parameters such as CPE length, channel access method, or channel access priority using a co-coding scheme. The following describes the characteristics of channel access parameter instruction methods introduced in different DCI formats.

[0069] 1) Fall backup link grant (DCI format 0_0) for scheduling PUSCH transmission: By default, a set of joint instructions for channel access scheme and CPE length is pre-configured, as shown in Table 4. The fall backup link grant includes 2 bits of LBT instruction information, which is used to indicate the jointly encoded channel access scheme and CPE length from the set shown in Table 4. This channel access scheme and CPE length are used for PUSCH transmission. If the channel access scheme is Type 1 channel access, the UE selects the channel access priority (CAPC) based on the service priority.

[0070] 2) Fallback downlink grant to schedule PDSCH transmission (DCI format 1_0): By default, a set of joint instructions for channel access scheme and CPE length is pre-configured, as shown in Table 4. This fallback downlink grant includes 2 bits of LBT instruction information, which is used to indicate the jointly encoded channel access scheme and CPE length from the set shown in Table 4. This channel access scheme and CPE length are used for PUCCH transmission, which can carry an acknowledgment (ACK) or negative acknowledgment (NACK) corresponding to the PDSCH. If the channel access scheme is Type 1 channel access, the UE determines a channel access priority of CAPC=1 for transmitting the PUCCH.

[0071] [Table 4]

[0072] Table 4 shows that the value of C1 is defined by the protocol; C1=1 when the subcarrier interval is 15kHz and 30kHz, and C1=2 when the subcarrier interval is 60kHz. The values ​​of C2 and C3 are composed of upper-layer parameters; when the subcarrier interval is 15kHz and 30kHz, the range of C2 and C3 values ​​is 1 to 28, and when the subcarrier interval is 60kHz, the range of C2 and C3 values ​​is 2 to 28.

[0073] 3) Non-fall backup link grant (DCI format 0_1) to schedule PUSCH transmission: The upper layer constitutes an LBT parameter instruction set, which includes at least one co-encoded channel access scheme, CPE length, and CAPC. The non-fall backup link grant contains LBT instruction information, which is used to indicate the co-encoded channel access scheme, CPE length, and CAPC from the above LBT parameter instruction set. The channel access scheme, CPE length, and CAPC are used for PUSCH transmission. If the indicated channel access scheme is a Type 2 channel access, the simultaneously indicated CAPC is the CAPC used by the base station when acquiring the COT. The LBT instruction information contains a maximum of 6 bits.

[0074] 4) Non-fallback downlink grant to schedule PDSCH transmission (DCI format 1_1): The upper layer constitutes an LBT parameter instruction set, which includes at least one co-encoded channel access scheme and CPE length. The non-fallback downlink grant contains LBT instruction information, which is used to indicate the co-encoded channel access scheme and CPE length from the above LBT parameter instruction set. The channel access scheme and CPE length are used for PUCCH transmission, where the PUCCH may carry ACK or NACK information corresponding to the PDSCH. If the channel access scheme is a Type 1 channel access, the UE determines a channel access priority CAPC=1 for transmitting the PUCCH. The LBT instruction information includes a maximum of 4 bits.

[0075] In addition to the explicit instructions above, base stations can also implicitly indicate the channel access method within the COT. If a UE receives a UL grant or DL ​​grant from a base station and it indicates that the channel access type corresponding to a PUSCH or PUCCH is Type 1 channel access, the UE can determine that the PUSCH or PUCCH is within the base station's COT. For example, if the UE receives a DCI format 2_0 from a base station and determines, based on the DCI format 2_0, that the PUSCH or PUCCH is within the base station's COT, the UE can update the channel access type corresponding to the PUSCH or PUCCH to Type 2A channel access and not adopt Type 1 channel access.

[0076] 15. Channel access parameter instruction (including CPE) As shown in Figure 16, the partitioning of frequency domain resources in sidelinks and Uu is similar. When frequency domain resources include multiple carriers, the terminal and system must support carrier aggregation functionality; however, the system can also support only single-carrier scenes, in which case carrier aggregation is not required. The frequency resources of a single carrier can be partitioned into one or more Bandwidth Parts (BWPs). Currently, when multiple BWPs exist in the frequency domain, only the activation of one BWP at a time is supported, and in SL systems, the system currently supports only one sidelink Bandwidth Part (SL BWP). In NR-U (unlicensed band) systems, one BWP is partitioned into multiple RB sets, each RB set is 20 MHz in size, and one RB set is the smallest unit of LBT. For example, in Figure 16, BWP 1 is partitioned into RB sets 0 through 4.

[0077] As the above has provided a brief explanation of the relevant technologies and terminology related to the embodiments of this application, they will not be repeated in the following embodiments.

[0078] It should be understood that the terms “system” and “network” as used herein are always interchangeable. The terms “and / or” as used herein describe only related relationships and indicate that three relationships may exist. For example, A and / or B can represent three cases: A existing independently, A and B existing together, or B existing alone. The symbol “ / ” as used herein usually indicates that the relationship between the preceding and following related objects is “or.” Furthermore, it should be understood that the “shows” in the embodiments of this application may mean showing directly, showing indirectly, or showing as having a related relationship. For example, A showing B may mean that A directly shows B, e.g., B can obtain information through A; or A indirectly shows B, e.g., A shows C and B can obtain information through C; or A and B may have a related relationship. Furthermore, it should be understood that in the description of the embodiments of this application, the term “corresponding” may mean that there is a direct or indirect corresponding relationship between the two, or that there is a related relationship between the two, or that there is a relationship such as indicating and being indicated, or configuring and being configured. Furthermore, it should be understood that in the embodiments of this application, “predefined” or “predefined rule” may be implemented by pre-storing within a device (including, for example, terminal equipment and network equipment) a corresponding code, table, or other form that can be used to indicate related information, and this application does not limit the specific forms of such implementation.

[0079] Furthermore, it should be understood that the terminals in the embodiments of this application may refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile base stations, remote base stations, remote terminals, mobile devices, user terminals, terminal equipment, wireless communication equipment, user agents, or user devices. Access terminals may include cellular telephones, cordless telephones, Session Initiation Protocol (SIP) telephones, IoT devices, satellite mobile terminals, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), portable devices with wireless communication capabilities, computing equipment or other processing equipment connected to wireless modems, in-vehicle equipment, wearable devices, terminal equipment for 5G networks, or terminal equipment for future evolving networks.

[0080] In existing SL technology, it is assumed that all terminals in the system have the same capabilities, such as supporting the same bandwidth and transmit power. Therefore, in conventional technology, the frequency domain resources and locations for transmitting / receiving S-SSB are supported by all terminals. For example, in a current SL-U system, if there are multiple RB sets in the frequency domain and S-SSB needs to be transmitted on multiple RB sets, the terminal also needs to attempt to detect and receive S-SSB on multiple RB sets.

[0081] As technology advances, supporting multiple terminal devices with different communication capabilities within the same communication system has become an unavoidable problem. Continuing to assume that all terminals have the same communication capabilities will inevitably lead to certain difficulties in communication for low-capacity terminals (such as smartwatches, bracelets, and AR / VR glasses). For example, low-capacity terminals typically cannot support large bandwidths like those found in mobile phones. For instance, while a mobile phone might support a 100MHz bandwidth, a smartwatch communicating with it might only support a maximum of 5MHz or 20MHz. As a result, in real-world communication scenarios, the imbalance in terminal capabilities (bandwidth) leads to the following problems:

[0082] 1) In communication between a full-capacity terminal (such as a mobile phone) and a low-capacity terminal, if the full-capacity terminal reduces its communication bandwidth to ensure normal communication on the low-capacity terminal, it can cause system bandwidth congestion and waste bandwidth resources.

[0083] 2) If a full-bandwidth communication method is continuously used between full-capacity terminals, low-capacity terminals will not be able to participate in the communication. For example, if a full-capacity terminal transmits data in broadcast or multicast format, low-capacity terminals, as receivers, will not be able to receive data using the full bandwidth.

[0084] The SL synchronization process, as a crucial step in an SL system, takes place before SL communication. Considering solutions for the synchronization process, specifically for S-SSB transmission / reception, is highly efficient for resolving communication issues between terminals with different capabilities. This is because the synchronization process is simple, involves a small amount of data, and consumes few resources. Therefore, performing S-SSB transmission / reception with a narrower bandwidth allows for simultaneous consideration of terminal equipment with different capabilities, thereby ensuring synchronization of all devices. On the other hand, subsequent communication processes, due to their different service types and data volumes, can be discussed separately from the solutions presented here.

[0085] In view of this, the present application provides a sidelink synchronization method and apparatus, a terminal, a chip, and a storage medium. This method may be performed, for example, by a terminal, or by a chip, chip system, or circuit configured in the terminal, and the embodiments of the present application are not limited thereto. For the sake of explanation, an example performed by a terminal will be described below.

[0086] In the above method, a terminal can transmit or receive S-SSB on a first frequency domain resource, where the first frequency domain resource is a portion of the system frequency domain resources. By using a portion of the system frequency domain resources to transmit or receive S-SSB, the above method enables S-SSB transmission or reception to be performed with a relatively small bandwidth, thereby allowing for the consideration of terminals with different capabilities within the same communication system, and ultimately ensuring that all terminals can achieve synchronization.

[0087] To facilitate understanding of the technical solutions in the embodiments of this application, the technical solutions of this application will be described in detail below with reference to specific embodiments. The following related technologies can be optionally combined with the technical solutions of the embodiments of this application as optional solutions, and all of them are included within the scope of protection of the embodiments of this application. The embodiments of this application include at least a portion of the following.

[0088] Figure 17 is a flowchart of a side-link synchronization method provided in an embodiment of the present application. As shown in Figure 17, the side-link synchronization method may include the following steps.

[0089] In step S1701, the terminal transmits or receives S-SSB on a first frequency domain resource, the first frequency domain resource being a portion of the system frequency domain resources.

[0090] Here, the first frequency domain resource may be determined, for example, by definition, preconfiguration, or network configuration. The first frequency domain resource may be used for S-SSB transmission or reception as a common frequency domain resource between different terminals in the communication system. In other words, each terminal must transmit or receive S-SSB on at least the first frequency domain resource.

[0091] For example, a communication system may have multiple terminal devices with different capabilities simultaneously. Here, the first frequency domain resource may be determined, for example, based on the capabilities of different terminals in the communication system. For example, each terminal may report its capabilities to the network equipment, thereby allowing the network equipment to configure the first frequency domain resource by comprehensively considering the capabilities of each terminal. As one example, the first frequency domain resource configured by the network equipment must take into account terminals with lower capabilities in the communication system. This ensures that terminals with lower capabilities have at least the ability to transmit / receive S-SSB on the first frequency domain resource, and thereby ensures that all terminals can achieve synchronization while taking into account terminals with lower capabilities. As another example, each terminal may pre-configure a relatively small common frequency domain resource used for transmitting or receiving S-SSB, taking into account terminals with lower capabilities in the communication system.

[0092] For the sake of explanation, in the embodiments of this application, high-capacity terminals are referred to as Type 1 terminals, and low-capacity terminals are referred to as Type 2 terminals. Here, Type 1 terminals may also be called full-capacity terminals or high-capacity terminals (such as mobile phones), and Type 2 terminals may also be called low-capacity terminals (such as smartwatches, bracelets, and AR / VR glasses). Generally, the bandwidth for transmitting / receiving information that Type 2 terminals support is relatively narrow, or Type 2 terminals can support transmitting / receiving information in one subbandwidth but cannot support transmitting / receiving information in the full bandwidth. Furthermore, in some scenarios, the transmission power of Type 2 terminals may also be low, and their encoding / decoding capabilities may be limited.

[0093] Several possible implementation forms of the sidelink synchronization method according to the embodiments of the present application are described below.

[0094] In the first implementation form (referred to as implementation form #1), the system frequency domain resource may include a plurality of S-SSB frequency domain resources within one SL BWP, and the first frequency domain resource is a part of the S-SSB frequency domain resources among the plurality of S-SSB frequency domain resources.

[0095] For example, assuming that the system supports one SL BWP and the SL BWP supports N (N is greater than 1) S-SSB frequency domain resources, or the system frequency domain resource includes N S-SSB frequency domain resources within one SL BWP, the first frequency domain resource may be, for example, N1 (N1 < N) S-SSB frequency domain resources within the N S-SSB frequency domain resources. Here, the value of N1 can be determined by definition, pre-configuration, or network configuration.

[0096] In some embodiments, the frequency domain position and / or number of the plurality of S-SSB frequency domain resources are pre-configured or configured by the network. For example, when the system frequency domain resource includes N S-SSB frequency domain resources within one SL BWP, the frequency domain position and / or number of the N S-SSB frequency domain resources (i.e., the value of N) are pre-configured or configured by the network.

[0097] As one example, if the plurality of (e.g., N) S-SSB frequency domain resources are continuously distributed, the frequency domain positions of the plurality of 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 plurality of S-SSB frequency domain resources. In other words, if 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 plurality of continuously distributed S-SSB frequency domain resources can be determined.

[0098] As another example, if the multiple (e.g., N) S-SSB frequency domain resources are distributed discontinuously, the frequency domain positions of the multiple S-SSB frequency domain resources can be determined based on the starting position and length of each S-SSB frequency domain resource. In other words, if the starting position and length of each S-SSB frequency domain resource are all determined, the frequency domain positions of the multiple discontinuously distributed S-SSB frequency domain resources can be determined.

[0099] As yet another example, if the plurality of (e.g., N) S-SSB frequency domain resources are distributed discontinuously, the frequency domain positions of the plurality of 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 plurality of S-SSB frequency domain resources, and the distance between two adjacent S-SSB frequency domain resources. In other words, if the starting position of the first S-SSB frequency domain resource, the total length of the plurality of S-SSB frequency domain resources, and the distance between two adjacent S-SSB frequency domain resources are determined, the frequency domain positions of the plurality of discontinuously distributed S-SSB frequency domain resources can be determined. Here, the total length of the plurality of S-SSB frequency domain resources 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 within the plurality of S-SSB frequency domain resources, or it may refer to the sum of the lengths of each S-SSB frequency domain resource within the plurality of S-SSB frequency domain resources.

[0100] Exemplary, the interval between two adjacent S-SSB frequency domain resources can be represented, for example, by the number of subchannels or resource blocks separating the two adjacent S-SSB frequency domain resources. For example, an interval of G between two adjacent S-SSB frequency domain resources can mean that the interval between the two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks, where G is a non-negative integer. For example, if G > 0, it means that the interval between two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks, and if G = 0, it means that there is no interval between the two adjacent S-SSB frequency domain resources, or the interval is 0, i.e., the two adjacent S-SSB frequency domain resources are continuous in the frequency domain.

[0101] In the embodiments of this application, the "frequency domain position" of the S-SSB frequency domain resource can be abbreviated as "position" in some contexts. Alternatively, the "position" of the S-SSB frequency domain resource as referred to in the embodiments of this application refers to the "frequency domain position" of the S-SSB frequency domain resource, unless it creates ambiguity. For example, the starting position of the S-SSB frequency domain resource mentioned above refers to the starting frequency domain position of the S-SSB frequency domain resource.

[0102] In some embodiments, the number of multiple S-SSB frequency domain resources within the SL BWP is the number of repetitions of a single S-SSB in the SL BWP. For example, if the number of repetitions of a single S-SSB in the SL BWP is N, then the number of multiple S-SSB frequency domain resources within the SL BWP is N.

[0103] It should be understood that in actual applications, the value of N above can be configured as an integer greater than or equal to 1. That is, the system can support the SL BWP including at least one S-SSB frequency region resource. The configuration of N1 can satisfy 1≤N1≤N. That is, the first frequency region resource may be configured as a part of the frequency region resources within the system frequency region resources in consideration of low-capability terminals (i.e., implementation form #1), or the first frequency region resource may be configured as all of the frequency region resources within the system frequency region resources.

[0104] In the second implementation form (referred to as implementation form #2), the system frequency region resources include multiple sub-bandwidths within one SL BWP. At least one of the multiple sub-bandwidths includes S-SSB frequency region resources. The first frequency region resource is a part of the multiple sub-bandwidths, and the part of the sub-bandwidths includes S-SSB frequency region resources.

[0105] For example, assuming that the system supports one SL BWP and supports the SL BWP including K (K>1) sub-bandwidths, or the system frequency region resources include K sub-bandwidths within one SL BWP, the first frequency region resource may be, for example, K1 (K1<K) sub-bandwidths within the K sub-bandwidths. Here, the value of K1 can be determined by definition, pre-configuration, or network configuration, and S-SSB frequency region resources are configured in the K1 sub-bandwidths.

[0106] In some embodiments, for each of the part of the sub-bandwidths (e.g., the above K1 sub-bandwidths), the frequency region resources for transmitting S-SSB may include all or part of the S-SSB frequency region resources within the sub-bandwidth.

[0107] For example, assuming that the portion of the subbandwidth includes subbandwidth #1, the frequency domain resources for transmitting S-SSB within subbandwidth #1 may include all S-SSB frequency domain resources within subbandwidth #1 or some of the S-SSB frequency domain resources. If the frequency domain resources for transmitting S-SSB include all S-SSB frequency domain resources within subbandwidth #1, it means that the terminal needs to occupy all of the S-SSB frequency domain resources within subbandwidth #1 to transmit S-SSB. If the frequency domain resources for transmitting S-SSB include some of the S-SSB frequency domain resources within subbandwidth #1, it means that the terminal does not need to occupy all of the S-SSB frequency domain resources within subbandwidth #1 to transmit S-SSB.

[0108] As one example, whether a terminal needs to occupy all S-SSB frequency domain resources within a subbandwidth to transmit S-SSB can be determined based on the network configuration. For example, if the network is configured for a terminal to occupy all S-SSB frequency domain resources within a subbandwidth to transmit S-SSB, the terminal can transmit S-SSB on all S-SSB frequency domain resources within the subbandwidth based on the network configuration. As another example, a terminal can autonomously decide whether to occupy all S-SSB frequency domain resources within a subbandwidth to transmit S-SSB. For example, if the terminal's capabilities support occupying all S-SSB frequency domain resources within a subbandwidth to transmit S-SSB, the terminal can transmit S-SSB on all S-SSB frequency domain resources within the subbandwidth. As yet another example, a transmitting terminal can also decide whether to occupy all S-SSB frequency domain resources within a subbandwidth to transmit S-SSB based on instructions from other terminals in the communication system. For example, a low-capacity terminal in a communication system can instruct a transmitting terminal to transmit S-SSB by occupying all S-SSB frequency domain resources within the subbandwidth, thereby simplifying the complexity of S-SSB detection for the low-capacity terminal. In this case, the transmitting terminal can transmit S-SSB using all S-SSB frequency domain resources within the subbandwidth.

[0109] In some embodiments, each subbandwidth within the subset of subbandwidths (for example, the K1 subbandwidths described above) is adjacent in the frequency domain, or each subbandwidth within the subset of subbandwidths is not adjacent in the frequency domain, or some subbandwidths within the subset of subbandwidths are adjacent in the frequency domain.

[0110] In other words, when a terminal transmits S-SSB over a portion of the subbandwidth, the subbandwidths within that portion may be adjacent to each other in the frequency domain. In this way, the distribution of frequency domain resources for transmitting S-SSB is relatively uniform, and the transmission power in the frequency domain is also relatively uniform, which is advantageous in avoiding impacts on communication performance. In some embodiments, the subbandwidths within that portion of the subbandwidth do not have to be adjacent to each other in the frequency domain, or some may be adjacent and some may not.

[0111] In some embodiments, in subbands containing S-SSB frequency domain resources, the frequency domain locations and / or number of S-SSB frequency domain resources included in each subband are either pre-configured or configured by a network.

[0112] For example, assuming that in the above K subbandwidths, K2 subbandwidths contain (are configured with) S-SSB frequency domain resources, in this scenario, the frequency domain location and / or number of S-SSB frequency domain resources contained in each subbandwidth within the K2 subbandwidths may be pre-configured or configured by the network.

[0113] As one example, if S-SSB frequency domain resources are continuously distributed within a subbandwidth containing S-SSB frequency domain resources (for example, two subbandwidths as described above), the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth is determined based on the starting position of the first S-SSB frequency domain resource within the subbandwidth and the total length of the S-SSB frequency domain resources within the subbandwidth. In other words, if the starting position of the first S-SSB frequency domain resource within a subbandwidth and the total length of all S-SSB frequency domain resources within that subbandwidth are determined, the frequency domain positions of the continuously distributed S-SSB frequency domain resources within that subbandwidth can be determined.

[0114] As another example, if S-SSB frequency domain resources are distributed discontinuously within a subbandwidth containing S-SSB frequency domain resources (for example, two subbandwidths as described above), the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth can be determined based on the starting position and length of each S-SSB frequency domain resource within the subbandwidth. In other words, if the starting position and length of each S-SSB frequency domain resource within a given subbandwidth are all determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource within that subbandwidth can be determined.

[0115] As yet another example, if S-SSB frequency domain resources are discontinuously distributed in a subbandwidth containing S-SSB frequency domain resources (e.g., two subbandwidths as described above), the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth can be determined based on the starting position of the first S-SSB frequency domain resource in the subbandwidth, the total length of the S-SSB frequency domain resources in the subbandwidth, and the distance between two adjacent S-SSB frequency domain resources in the subbandwidth. In other words, if the starting position of the first S-SSB frequency domain resource in a subbandwidth, the total length of the S-SSB frequency domain resources in the subbandwidth, and the distance between two adjacent S-SSB frequency domain resources in the subbandwidth are determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in the subbandwidth can be determined. Here, the total length of the S-SSB frequency domain resources within the subbandwidth may refer to the length between the starting position of the first S-SSB frequency domain resource within the subbandwidth and the ending position of the last S-SSB frequency domain resource, or it may refer to the sum of the lengths of each S-SSB frequency domain resource within the subbandwidth.

[0116] For example, the interval between two adjacent S-SSB frequency domain resources can be represented, for instance, by the number of subchannels or resource blocks separating the two adjacent S-SSB frequency domain resources. For instance, an interval of G between two adjacent S-SSB frequency domain resources can mean that the interval between the two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks, where G is a non-negative integer.

[0117] In some embodiments, in subbandwidths containing S-SSB frequency domain resources (e.g., K2 subbandwidths as described above), the frequency domain locations of the S-SSB frequency domain resources included in each subbandwidth can be configured independently or preconfigured, for example.

[0118] In some embodiments, in a subbandwidth containing S-SSB frequency domain resources (e.g., K2 subbandwidths as described above), the number of S-SSB frequency domain resources in each subbandwidth is the number of repetitions of one S-SSB in the subbandwidth. For example, if one S-SSB is repeated M times in a subbandwidth, the number of S-SSB frequency domain resources in the subbandwidth is M. In some embodiments, the number of S-SSB frequency domain resources in each subbandwidth may be, for example, independently configured or pre-configured, and the number of S-SSB frequency domain resources in different subbandwidths may be the same or different.

[0119] In some embodiments, the subbandwidth described above may be a resource block set (RB set), a channel, a frequency range, or a resource pool (frequency domain resource pool). Alternatively, the subbandwidth in the embodiments of this application may also be referred to (or replaced by) a resource block set, a channel, a frequency range, or a resource pool.

[0120] Exemplarily, when the sub-bandwidth is a frequency range or a resource pool, the multiple sub-bandwidths (i.e., the multiple sub-bandwidths included in the system frequency region resource) within the above SL BWP may or may not overlap in the frequency region. When the sub-bandwidth is a resource block set or a channel, the multiple sub-bandwidths within the above SL BWP do not overlap in the frequency region.

[0121] It should be understood that in actual applications, the value of K above can be configured as an integer greater than or equal to 1, that is, the system can support the above SL BWP including at least one sub-bandwidth. The configuration of K1 can satisfy 1≤K1≤K, that is, the first frequency region resource may be configured as a part of the frequency region resources within the system frequency region resource in consideration of low-capability terminals (i.e., Embodiment #2), or the first frequency region resource may be configured as all of the frequency region resources within the system frequency region resource.

[0122] In a third embodiment (referred to as Embodiment #3), the system frequency region resource includes multiple SL BWPs, at least one of the multiple SL BWPs includes S-SSB frequency region resources, the first frequency region resource is a part of the multiple SL BWPs, and the part of the SL BWPs includes S-SSB frequency region resources.

[0123] For example, assuming that the system supports X (X>1) SL BWPs, or the system frequency region resource includes X SL BWPs, the first frequency region resource may be, for example, X1 (X1<X) SL BWPs within the X SL BWPs. Here, the value of X1 can be determined by definition, pre-configuration, or network configuration, and the S-SSB frequency region resource is configured in the X1 sub-bandwidths.

[0124] In some embodiments, for each SL BWP within some of the SL BWPs (e.g., X1 SL BWPs as described above), the frequency domain resources for transmitting S-SSB may include all S-SSB frequency domain resources within the SL BWP or some of the S-SSB frequency domain resources.

[0125] For example, assuming that some of the SL BWPs include SL BWP#1, the frequency domain resources for transmitting S-SSB within SL BWP#1 may include all of the S-SSB frequency domain resources within SL BWP#1 or some of the S-SSB frequency domain resources. If the frequency domain resources for transmitting S-SSB include all of the S-SSB frequency domain resources within SL BWP#1, it means that the terminal needs to occupy all of the S-SSB frequency domain resources within SL BWP#1 to transmit S-SSB. If the frequency domain resources for transmitting S-SSB include some of the S-SSB frequency domain resources within SL BWP#1, it means that the terminal does not need to occupy all of the S-SSB frequency domain resources within SL BWP#1 to transmit S-SSB.

[0126] As one example, whether a terminal needs to occupy all S-SSB frequency domain resources within the SL BWP to transmit an S-SSB can be determined based on the network configuration. As another example, a terminal can autonomously decide whether to occupy all S-SSB frequency domain resources within the SL BWP to transmit an S-SSB. As yet another example, a transmitting terminal can decide whether to occupy all S-SSB frequency domain resources within the SL BWP to transmit an S-SSB based on instructions from other terminals in the communication system. For example, a low-capacity terminal in the communication system can instruct a transmitting terminal to occupy all S-SSB frequency domain resources within the SL BWP to transmit an S-SSB, thereby simplifying the complexity of S-SSB detection for the low-capacity terminal. In this case, the transmitting terminal can transmit an S-SSB using all S-SSB frequency domain resources within the SL BWP.

[0127] In some embodiments, each SL BWP within the subset of SL BWPs (for example, the X1 SL BWPs described above) is adjacent in the frequency domain, or each SL BWP within the subset of SL BWPs is not adjacent in the frequency domain, or some SL BWPs within the subset of SL BWPs are adjacent in the frequency domain.

[0128] In other words, when a terminal transmits S-SSB on some of the SL BWPs, the SL BWPs within those some may be adjacent to each other in the frequency domain. In this way, the distribution of frequency domain resources for transmitting S-SSB is relatively uniform, and the transmission power in the frequency domain is also relatively uniform, which is advantageous in avoiding impacts on communication performance. In some embodiments, the SL BWPs within those some may not be adjacent to each other in the frequency domain, or some may be adjacent and some may not be adjacent.

[0129] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, the frequency domain locations and / or number of S-SSB frequency domain resources included in each SL BWP are either pre-configured or configured by a network.

[0130] For example, in the above X SL BWPs, if we assume that X2 SL BWPs contain (are configured with) S-SSB frequency domain resources, then in this scenario, the frequency domain location and / or number of S-SSB frequency domain resources contained in each of the X2 SL BWPs may be pre-configured or configured by the network.

[0131] As one example, in an SL BWP containing S-SSB frequency domain resources (for example, two SL BWPs as described above), if 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. In other words, if the starting position of the first S-SSB frequency domain resource in a given SL BWP and the total length of all S-SSB frequency domain resources within the SL BWP are determined, the frequency domain positions of the continuously distributed S-SSB frequency domain resources within the SL BWP can be determined.

[0132] As another example, in an SL BWP containing S-SSB frequency domain resources (for example, two SL BWPs as described above), if the S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP can be determined based on the starting position and length of each S-SSB frequency domain resource within the SL BWP. In other words, if the starting position and length of each S-SSB frequency domain resource within a given SL BWP are all determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource within the SL BWP can be determined.

[0133] As yet another example, in an SL BWP containing S-SSB frequency domain resources (for example, two SL BWPs as described above), if the S-SSB frequency domain resources are distributed discontinuously, 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 distance between two adjacent S-SSB frequency domain resources in the SL BWP. In other words, if the starting position of the first S-SSB frequency domain resource in a given SL BWP, the total length of the S-SSB frequency domain resources in the SL BWP, and the distance between two adjacent S-SSB frequency domain resources in the SL BWP are determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in the SL BWP can be determined. Here, the total length of the S-SSB frequency domain resources within 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 within the SL BWP, or it may refer to the sum of the lengths of each S-SSB frequency domain resource within the SL BWP.

[0134] For example, the interval between two adjacent S-SSB frequency domain resources can be represented, for instance, by the number of subchannels or resource blocks separating the two adjacent S-SSB frequency domain resources. For instance, an interval of G between two adjacent S-SSB frequency domain resources can mean that the interval between the two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks, where G is a non-negative integer.

[0135] In some embodiments, in an SL BWP containing S-SSB frequency domain resources (e.g., X2 SL BWPs as described above), the frequency domain positions of the S-SSB frequency domain resources included in each SL BWP can be configured independently or pre-configured.

[0136] In some embodiments, in a SL BWP (e.g., the above-mentioned X2 SL BWPs) 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 one S-SSB in the SL BWP. For example, if one S-SSB is repeated L times in a SL BWP, the number of S-SSB frequency domain resources in the SL BWP is L. In some embodiments, the number of S-SSB frequency domain resources included in each SL BWP can be configured independently or pre-configured, for example, and the number of S-SSB frequency domain resources included in different SL BWPs may be the same or different.

[0137] It should be understood that in actual applications, the above configuration of X1 can satisfy 1 ≤ X1 ≤ X, that is, the first frequency domain resource may be configured as some of the frequency domain resources within the system frequency domain resources in consideration of low-capability terminals (i.e., implementation form #3), or the first frequency domain resource may be configured as all of the frequency domain resources within the system frequency domain resources.

[0138] In the fourth implementation form (referred to as implementation form #4), the system frequency domain resources include a plurality of carriers, at least one of the plurality of carriers includes S-SSB frequency domain resources, the first frequency domain resource is some of the plurality of carriers, and the some carriers include S-SSB frequency domain resources.

[0139] For example, assuming that the system supports Y (Y > 1) carriers or the system frequency domain resources include Y carriers, the first frequency domain resource may 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 the Y1 carriers.

[0140] In some embodiments, for each carrier within some of the carriers (e.g., the Y1 carriers described above), the frequency domain resources for transmitting S-SSB may include all S-SSB frequency domain resources within the carrier or some of the S-SSB frequency domain resources.

[0141] For example, assuming that some of the carriers include carrier #1, the frequency domain resources for transmitting S-SSB within carrier #1 may include all of the S-SSB frequency domain resources within carrier #1 or some of the S-SSB frequency domain resources. If the frequency domain resources for transmitting S-SSB include all of the S-SSB frequency domain resources within carrier #1, it means that the terminal needs to occupy all of the S-SSB frequency domain resources within carrier #1 to transmit S-SSB. If the frequency domain resources for transmitting S-SSB include some of the S-SSB frequency domain resources within carrier #1, it means that the terminal does not need to occupy all of the S-SSB frequency domain resources within carrier #1 to transmit S-SSB.

[0142] As one example, whether a terminal needs to occupy all of the carrier's S-SSB frequency domain resources to transmit an S-SSB can be determined based on the network configuration. As another example, a terminal can decide whether to occupy all of the carrier's S-SSB frequency domain resources to transmit an S-SSB. As yet another example, a transmitting terminal can decide whether to occupy all of the carrier's S-SSB frequency domain resources to transmit an S-SSB based on instructions from other terminals in the communication system. For example, a low-capacity terminal in the communication system can instruct a transmitting terminal to occupy all of the carrier's S-SSB frequency domain resources to transmit an S-SSB, thereby simplifying the complexity of S-SSB detection for the low-capacity terminal. In this case, the transmitting terminal can transmit an S-SSB using all of the carrier's S-SSB frequency domain resources.

[0143] In some embodiments, each carrier within the subset of carriers (for example, the Y1 carriers described above) is adjacent in the frequency domain, or each carrier within the subset of carriers is not adjacent in the frequency domain, or some carriers within the subset of carriers are adjacent in the frequency domain.

[0144] In other words, when a terminal transmits S-SSB on the aforementioned partial carrier, the carriers within that partial carrier may be adjacent to each other in the frequency domain. In this way, the distribution of frequency domain resources for transmitting S-SSB is relatively uniform, and the transmission power in the frequency domain is also relatively uniform, which is advantageous in avoiding impacts on communication performance. In some embodiments, the carriers within that partial carrier do not have to be adjacent to each other in the frequency domain, or some may be adjacent and some may not be adjacent.

[0145] In some embodiments, in a carrier containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources included in each carrier are either pre-configured or configured by a network.

[0146] For example, assuming that in the above Y carriers, Y2 carriers contain (are configured with) S-SSB frequency domain resources, in this scenario, the frequency domain locations and / or number of S-SSB frequency domain resources contained in each of the Y2 carriers are either pre-configured or configured by the network.

[0147] As one example, in a carrier containing S-SSB frequency domain resources (for example, two carriers Y as described above), if 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 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 other words, if the starting position of the first S-SSB frequency domain resource in a given carrier and the total length of all S-SSB frequency domain resources within that carrier are determined, the frequency domain positions of the continuously distributed S-SSB frequency domain resources within that carrier can be determined.

[0148] As another example, in a carrier containing S-SSB frequency domain resources (for example, the two Y carriers mentioned above), if the S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of each S-SSB frequency domain resource contained in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource within the carrier. In other words, if the starting position and length of each S-SSB frequency domain resource within a given carrier are all determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource within that carrier can be determined.

[0149] As yet another example, in a carrier containing S-SSB frequency domain resources (for example, two carriers Y as described above), if the S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of each S-SSB frequency domain resource contained in each carrier 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 distance between two adjacent S-SSB frequency domain resources in the carrier. In other words, if 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 distance between two adjacent S-SSB frequency domain resources in the carrier are determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in the carrier can be determined. Here, 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 and the ending position of the last S-SSB frequency domain resource in the carrier, or it may refer to the sum of the lengths of each S-SSB frequency domain resource in the carrier.

[0150] For example, the interval between two adjacent S-SSB frequency domain resources can be represented, for instance, by the number of subchannels or resource blocks separating the two adjacent S-SSB frequency domain resources. For instance, an interval of G between two adjacent S-SSB frequency domain resources can mean that the interval between the two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks, where G is a non-negative integer.

[0151] In some embodiments, in carriers containing S-SSB frequency domain resources (e.g., two Y carriers as described above), the frequency domain locations of the S-SSB frequency domain resources contained in each carrier can be configured independently or pre-configured, for example.

[0152] In some embodiments, in a carrier containing S-SSB frequency domain resources (e.g., two carriers Y as described above), the number of S-SSB frequency domain resources in each carrier is the number of repetitions of a single S-SSB in that carrier. For example, if a single S-SSB is repeated U times in a carrier, the number of S-SSB frequency domain resources in that carrier is U. In some embodiments, the number of S-SSB frequency domain resources in each carrier may be, for example, independently configured or pre-configured, and the number of S-SSB frequency domain resources in different carriers may be the same or different.

[0153] It should be understood that in actual applications, the above configuration of Y1 can satisfy 1 ≤ Y1 ≤ Y, meaning that the first frequency domain resource may be configured as a portion of the system frequency domain resource to account for low-capacity terminals (i.e., implementation #4), or the first frequency domain resource may be configured as all frequency domain resources within the system frequency domain resource.

[0154] Furthermore, it should be understood that the above-mentioned carriers may also be in situations where carrier aggregation is considered. Here, "carrier" is also called, for example, "subcarrier" or "carrier component (CC)".

[0155] In some embodiments, the system frequency domain resources further include a second frequency domain resource, the second frequency domain resource being a frequency domain resource other than the first frequency domain resource among the system frequency domain resources. Here, the second frequency domain resource may be used to transmit or receive service data.

[0156] In one example, assuming that in Implementation Form #1, the system frequency domain resource includes N S-SSB frequency domain resources within one SL BWP, in this implementation form, when the first frequency domain resource is N1 (N1 < N) S-SSB frequency domain resources within the N S-SSB frequency domain resources, the second frequency domain resource can be the N - N1 S-SSB frequency domain resources other than the N1 S-SSB frequency domain resources among the N S-SSB frequency domain resources.

[0157] In another example, assuming that in Implementation Form #2, the system frequency domain resource includes K sub-bandwidths within one SL BWP, in this implementation form, when the first frequency domain resource is K1 (K1 < K) sub-bandwidths within the K sub-bandwidths, the second frequency domain resource can be the K - K1 sub-bandwidths other than the K1 sub-bandwidths among the K sub-bandwidths.

[0158] In yet another example, assuming that in Implementation Form #3, the system frequency domain resource includes X SL BWPs, in this implementation form, when the first frequency domain resource is X1 (X1 < X) SL BWPs within the X SL BWPs, the second frequency domain resource can be the X - X1 SL BWPs other than the X1 SL BWPs among the X SL BWPs.

[0159] In yet another example, assuming that in Implementation Form #4, the system frequency domain resource includes Y carriers, in this implementation form, when the first frequency domain resource is Y1 (Y1 < Y) carriers within the Y carriers, the second frequency domain resource can be the Y - Y1 carriers other than the Y1 carriers among the Y carriers.

[0160] According to the method of this embodiment, the terminal can use the first frequency domain resource for S-SSB transmission / reception and the second frequency domain resource for service data transmission / reception. This allows S-SSB transmission / reception to be limited to a single, narrower bandwidth, which is advantageous for more efficient use of frequency domain resources. For example, in implementation #3, the second type terminal (low-capacity terminal) can use the SL BWP corresponding to the first frequency domain resource for S-SSB transmission / reception and the SL BWP corresponding to the second frequency domain resource for service data transmission / reception by switching the SL BWP. This allows for efficient use of frequency domain resources while simultaneously solving the problem of second type terminals and first type terminals coexisting in the same communication system.

[0161] In some embodiments, the second frequency domain resource does not include an S-SSB frequency domain resource, or an S-SSB frequency domain resource does not need to be configured in any other frequency domain resource besides the first frequency domain resource. In this way, the second frequency domain resource can be used more effectively for service data communication.

[0162] In some embodiments, if a terminal has the capability to transmit or receive S-SSB over a second frequency domain resource, the second frequency domain resource may be used to transmit or receive S-SSB.

[0163] In other words, if a terminal (for example, a terminal of a first type) has the capability to transmit or receive S-SSB on a second frequency domain resource, then in addition to transmitting or receiving S-SSB on the first frequency domain resource, the terminal can also transmit or receive S-SSB on the second frequency domain resource.

[0164] According to the method of this embodiment, on the one hand, terminals can transmit or receive S-SSB using a relatively small bandwidth by using some frequency domain resources within the system's frequency domain resources, thereby allowing for the consideration of terminals with different capabilities within the same communication system and ensuring that all terminals in the communication system can achieve synchronization. On the other hand, in addition to defining, pre-configuring, or networking a common frequency domain resource (first frequency domain resource) for use in transmitting / receiving S-SSB, it is possible to prevent terminals from being unable to transmit S-SSB due to LBT failures of some frequency band resources by defining, pre-configuring, or networking additional frequency domain resources (second frequency domain resource) for use in transmitting / receiving S-SSB as a supplement.

[0165] As described above with reference to Figure 17, the side link synchronization method provided in the embodiment of the present application has been explained. To facilitate understanding of the embodiment of the present application, several possible implementations of the side link synchronization method applicable to the embodiment of the present application are described below.

[0166] For example, a proposed frequency domain resource design for S-SSB may include the following:

[0167] Solution 1: One SL BWP contains N (where N is 1 or greater) S-SSB frequency domain resources.

[0168] Solution 2: One SL BWP includes K (where K is 1 or more) subbandwidths, and of the K subbandwidths, at least one subbandwidth includes M (where M is 1 or more) S-SSB frequency domain resources.

[0169] Exemplary, the above subbandwidths are also referred to as (defined as) RB sets, channels, frequency ranges (FRs), or resource pools (frequency domain resource pools).

[0170] In one possible configuration, the number of S-SSB frequency domain resources included in each of the above subbandwidths may be configured independently or preconfigured. That is, the number of S-SSB frequency domain resources in different subbandwidths may be the same or different, and are not limited to this.

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

[0172] In one possible form, the number of S-SSB frequency domain resources included in the different SL BWPs described above may be configured independently or pre-configured. That is, the number of S-SSB frequency domain resources in different SL BWPs may be the same or different, but are not limited to this.

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

[0174] In one possible form, the number of S-SSB frequency domain resources contained in the different carriers described above is either independently configured or pre-configured. That is, the number of S-SSB frequency domain resources in different carriers may be the same or different, and is not limited to this.

[0175] For illustrative purposes, the above carrier may also be a scenario where carrier aggregation is considered. Here, "carrier" may also be called, for example, "subcarrier" or "carrier component."

[0176] Furthermore, the configuration methods for S-SSB frequency domain resources in the above-mentioned 1 to 4 may include, for example, the configuration of S-SSB frequency domain resources by network, or the configuration of S-SSB frequency domain resources by pre-configuration.

[0177] Here, the configuration of the N / M / L / U S-SSB frequency domain resources described above may include the configuration of the locations and number (i.e., N / M / L / U) of the N / M / L / U S-SSB frequency domain resources.

[0178] For example, the location of an S-SSB frequency domain resource may be indicated by, for instance, the following methods 1, 2, or 3.

[0179] Method 1: When multiple S-SSB frequency domain resources are distributed continuously, the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources can be indicated. In other words, the positions of the multiple continuously distributed 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.

[0180] Method 2: When multiple S-SSB frequency domain resources are distributed discontinuously, the starting position and length of each S-SSB frequency domain resource can be indicated. In other words, the positions of the multiple discontinuously distributed S-SSB frequency domain resources can be determined based on the starting position and length of each S-SSB frequency domain resource.

[0181] Method 3: When multiple S-SSB frequency domain resources are distributed discontinuously, 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 can be indicated. In other words, the positions of the multiple discontinuously distributed 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 G between two adjacent S-SSB frequency domain resources.

[0182] For illustrative purposes, the above interval G may refer to the interval between G subchannels, or the interval between G resource blocks, where G is a non-negative integer. For example, if G > 0, it means that the interval between two adjacent S-SSB frequency domain resources is G subchannels or G resource blocks; if G = 0, it means that there is no interval between two adjacent S-SSB frequency domain resources, or the interval is 0, i.e., the two adjacent S-SSB frequency domain resources are continuous in the frequency domain.

[0183] For example, the number (quantity) of S-SSB frequency domain resources mentioned above corresponds to the number of repetitions of a single S-SSB in the frequency domain. For instance, if a single S-SSB is repeated N times in the frequency domain, the number of S-SSB frequency domain resources is N.

[0184] For example, the methods by which an S-SSB transmitting terminal transmits S-SSB in the frequency domain may include the following:

[0185] Transmission method 1: This transmission method can be applied, for example, to the frequency domain resource design proposal in the above-mentioned Option 1.

[0186] For example, in Option 1, for N S-SSB frequency domain resources, the terminal can transmit S-SSB on at least one of them. For instance, of the N S-SSB frequency domain resources, N1 (1 ≤ N1 ≤ N) of them must transmit S-SSB. That is, the terminal needs to transmit S-SSB on at least N1 of the S-SSB frequency domain resources.

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

[0188] Transmission method 2: This transmission method can be applied, for example, to the frequency domain resource design proposal in the above-mentioned Option 2.

[0189] For example, in the SL BWP in Option 2, for each of the K subbandwidths, the terminal can transmit at least one S-SSB on at least one of the subbandwidths. For instance, in the K subbandwidths of the SL BWP, K1 (1 ≤ K1 ≤ K) of the subbandwidths must transmit S-SSBs. That is, the terminal must transmit S-SSBs on at least the K1 subbandwidths.

[0190] As one implementation, the terminal may transmit at least one S-SSB on each of the K1 subbandwidths.

[0191] Alternatively, the terminal may perform S-SSB transmission by occupying all S-SSB frequency domain resources on each of the K1 subbandwidths. For example, assuming that each of the K1 subbandwidths contains y1 S-SSB frequency domain resources, the terminal needs to occupy all y1 S-SSB frequency domain resources on each subbandwidth to perform S-SSB transmission.

[0192] In yet another implementation, the terminal can perform S-SSB transmission by occupying all S-SSB frequency domain resources on a portion of the K1 subbandwidths, while it is not necessary to occupy all S-SSB frequency domain resources on another portion of the subbandwidths to perform S-SSB transmission.

[0193] In some embodiments, the terminal may also transmit at least one S-SSB on at least one of the (K-K1) subbandwidths other than the K1 subbandwidths.

[0194] For example, when a terminal transmits S-SSB over multiple subbandwidths, these subbandwidths may be adjacent in the frequency domain. In this way, the distribution of frequency domain resources for transmitting S-SSB is relatively uniform, and the transmission power in the frequency domain is also relatively uniform, which is advantageous in avoiding impacts on communication performance. In some embodiments, the multiple subbandwidths transmitting S-SSB do not have to be adjacent in the frequency domain, or some may be adjacent and some may not.

[0195] Transmission method 3: The aforementioned transmission method can be applied, for example, to the frequency domain resource design proposal in the above-described plan 3.

[0196] For example, for X SL BWPs in Option 3, the terminal can transmit at least one S-SSB on at least one of the SL BWPs. For instance, of the X SL BWPs, X1 (1 ≤ X1 ≤ X) of them must transmit an S-SSB. That is, the terminal needs to transmit an S-SSB on at least X1 of the SL BWPs.

[0197] As one implementation, the terminal may transmit at least one S-SSB on each of the X1 SL BWPs.

[0198] Alternatively, the terminal may occupy all S-SSB frequency domain resources on each of the X1 SL BWPs to transmit S-SSB signals. For example, assuming that each of the X1 SL BWPs contains y2 S-SSB frequency domain resources, the terminal needs to occupy all y2 S-SSB frequency domain resources on each SL BWP to transmit S-SSB signals.

[0199] In yet another implementation, the terminal can perform S-SSB transmission by occupying all S-SSB frequency domain resources on some of the X1 SL BWPs, while it does not need to occupy all S-SSB frequency domain resources on other parts of the SL BWPs to perform S-SSB transmission.

[0200] In some embodiments, the terminal may also transmit at least one S-SSB on at least one of the (X-X1) SL BWPs other than the X1 SL BWPs.

[0201] For example, when a terminal transmits S-SSB over multiple SL BWPs, these multiple SL BWPs may be adjacent to each other in the frequency domain. In this way, the distribution of frequency domain resources for transmitting S-SSB is relatively uniform, and the transmission power in the frequency domain is also relatively uniform, which is advantageous in avoiding impacts on communication performance. In some embodiments, the multiple SL BWPs transmitting S-SSB do not have to be adjacent to each other in the frequency domain, or some may be adjacent and some may not.

[0202] Transmission method 4: The aforementioned transmission method can be applied, for example, to the frequency domain resource design proposal in the above-described plan 4.

[0203] For example, in Option 4, for Y carriers, the terminal can transmit at least one S-SSB on at least one of those carriers. For instance, of the Y carriers, Y1 (1 ≤ Y1 ≤ Y) carriers must transmit S-SSBs. That is, the terminal needs to transmit S-SSBs on at least Y1 of the carriers.

[0204] As one implementation, the terminal may transmit at least one S-SSB on each of the carriers within the Y1 carriers.

[0205] Alternatively, the terminal may perform S-SSB transmission by occupying all S-SSB frequency domain resources on each carrier within the Y1 carrier. For example, assuming that each carrier within the Y1 carrier contains y3 S-SSB frequency domain resources, the terminal would need to occupy all y3 S-SSB frequency domain resources on each carrier to perform S-SSB transmission.

[0206] In yet another implementation, the terminal can perform S-SSB transmission by occupying all S-SSB frequency domain resources on some of the carriers within the aforementioned Y1 carrier, while it is not necessary to occupy all S-SSB frequency domain resources on other carriers to perform S-SSB transmission.

[0207] In some embodiments, the terminal may also transmit at least one S-SSB on at least one of the (Y-Y1) carriers other than the Y1 carriers.

[0208] For example, when a terminal transmits S-SSB over multiple carriers, these multiple carriers may be adjacent in the frequency domain. In this way, the distribution of frequency domain resources for transmitting S-SSB is relatively uniform, and the transmission power in the frequency domain is also relatively uniform, which is advantageous in avoiding impacts on communication performance. In some embodiments, the multiple carriers transmitting S-SSB do not have to be adjacent in the frequency domain, or some may be adjacent and some may not.

[0209] Furthermore, the S-SSB frequency domain resources that must transmit S-SSB, as mentioned in transmission methods 1 to 4, can also be understood as the default / essential frequency domain resources for transmitting S-SSB.

[0210] The terminals used in transmission methods 1 to 4 described above may be either type 1 or type 2 terminals.

[0211] Here, Type 1 terminals refer to terminals with full capabilities, or high-capacity terminals such as mobile phones, while Type 2 terminals refer to low-capacity terminals such as smartwatches, bracelets, and AR / VR glasses. Generally, Type 2 terminals support a relatively narrow bandwidth for transmitting / receiving information, or they can support transmitting / receiving information in one subbandwidth but not in the full bandwidth. Furthermore, in some scenarios, Type 2 terminals may also have low transmission power and limited encoding / decoding capabilities.

[0212] If a terminal transmitting S-SSB is a first-type terminal, it must transmit S-SSB at the default / required frequency-domain resource location for transmitting S-SSB. Furthermore, in some scenarios, this type of terminal may also transmit S-SSB over other frequency-domain resources. If a terminal transmitting S-SSB is a second-type terminal, it may only transmit S-SSB at the default / required S-SSB frequency-domain resource location, and it is not required to transmit S-SSB over other frequency-domain resources. In some scenarios, if a second-type terminal has the capability to transmit S-SSB over other frequency-domain resources, it may also transmit S-SSB over frequency-domain resources other than the default / required S-SSB frequency-domain resources.

[0213] In one possible form, the default / essential frequency domain resources for transmitting the above S-SSB can be determined, for example, by definition, configuration, or preconfiguration. The default / essential frequency domain resources for transmitting the S-SSB may be a common frequency domain resource for transmitting the S-SSB, where the common frequency domain resource includes, but is not limited to, at least one contiguous frequency band in the frequency domain, at least one subbandwidth (e.g., K1 subbandwidths in transmission method 2), at least one contiguous frequency domain resource in SL BWP, at least one resource pool, at least one SL BWP (e.g., X1 SL BWPs in transmission method 3), or at least one carrier (e.g., Y1 carrier in transmission method 4).

[0214] For example, a receiving terminal of S-SSB may have the following methods for receiving S-SSB in the frequency domain:

[0215] Reception method 1: Corresponding to transmission method 1, this reception method can be applied, for example, to the frequency domain resource design proposal in method 1 described above.

[0216] Exemplary, a terminal can detect / receive S-SSB at N1 S-SSB frequency domain resource locations (default / required frequency domain resource locations) in transmission method 1. In some embodiments, the terminal can also detect / receive S-SSB at other frequency domain resource locations.

[0217] Reception method 2: Corresponding to transmission method 2, this reception method can be applied, for example, to the frequency domain resource design proposal in the above-described solution 2.

[0218] Exemplary, a terminal can detect / receive S-SSB in K1 subbandwidths (default / required frequency domain resource locations) in transmission method 2. In some embodiments, the terminal can also detect / receive S-SSB in other subbandwidths.

[0219] Reception method 3: Corresponding to transmission method 3, this reception method can be applied, for example, to the frequency domain resource design proposal in the above-mentioned scheme 3.

[0220] Exemplary, a terminal can detect / receive S-SSB at X1 SL BWPs (default / required frequency domain resource locations) in transmission method 3. In some embodiments, the terminal can also detect / receive S-SSB at other SL BWPs.

[0221] Reception method 4: Corresponding to transmission method 4, this reception method can be applied, for example, to the frequency domain resource design proposal in the above-described solution 4.

[0222] Exemplary, a terminal can detect / receive S-SSB on one carrier Y in transmission scheme 4 (default / required frequency domain resource location). In some embodiments, the terminal can also detect / receive S-SSB on other carriers.

[0223] The terminals in the above receiving methods 1 to 4 may be either Type 1 or Type 2 terminals. If the terminal receiving S-SSB is either Type 1 or Type 2, the terminal must detect / receive S-SSB at least the default / required frequency domain resource locations. If the terminal receiving S-SSB is Type 1, the terminal has full capability and can detect / receive S-SSB at additional frequency domain resource locations. In some scenarios, if a Type 2 terminal has the capability to detect / receive S-SSB at other frequency domain resource locations, the Type 2 terminal can also detect / receive S-SSB at frequency domain resource locations other than the default / required frequency domain resources.

[0224] To facilitate understanding, a possible implementation flow of a side-link synchronization method applicable to the embodiments of this application will be described below with reference to Figures 18 and 19.

[0225] FIG. 18(a) is a schematic diagram of the frequency domain resource design of the S-SSB provided in the embodiment of the present application. As shown in FIG. 18(a), the system supports one BWP (SL BWP) and supports that the S-SSB has multiple transmission resources in the frequency domain. Alternatively, the system frequency domain resources may include multiple S-SSB frequency domain resources within one BWP. Here, the interval between the multiple S-SSB frequency domain resources may be defined by a configuration / pre-configuration method.

[0226] Taking FIG. 18(a) as an example, the system frequency domain resources may include three S-SSB frequency domain resources within one BWP, and one or more of the three S-SSB frequency domain resources may be used as default / essential frequency domain resources, that is, the transmitting terminal needs to transmit S-SSB on at least the one or more frequency domain resources, and the receiving terminal needs to receive S-SSB on at least the one or more frequency domain resources.

[0227] Exemplarily, when a terminal is a type-1 terminal, the terminal has the ability to transmit S-SSB on frequency domain resources other than the default / essential frequency domain resources. For example, the terminal can transmit S-SSB on all S-SSB frequency domain resources. When a terminal is a type-2 terminal, the terminal needs to transmit S-SSB on at least the default / essential S-SSB resources. For example, the terminal can transmit S-SSB only on the default / essential resources.

[0228] Exemplarily, when a certain terminal is a type-1 terminal, the terminal has the ability to receive S-SSB on frequency domain resources other than the default / essential frequency domain resources. For example, the terminal can receive S-SSB on all S-SSB frequency domain resources. When a certain terminal is a type-2 terminal, the terminal needs to receive S-SSB at least on the default / essential frequency domain resources. For example, the terminal can receive S-SSB only on the default / essential resources.

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

[0230] In some scenarios, BWP#0 can be the default / essential BWP (i.e., the default / essential frequency domain resources). In this scenario, the transmitting terminal needs to transmit S-SSB at least on BWP#0, and the receiving terminal needs to receive S-SSB at least on BWP#0.

[0231] In some scenarios, BWP#1 can be an additional frequency domain resource. In this scenario, the type-1 terminal can select whether to transmit S-SSB on BWP#1, or / and how much of the S-SSB frequency domain resources to occupy to transmit S-SSB. Since the type-2 terminal usually has limited capabilities, it cannot transmit / receive S-SSB on BWP#1.

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

[0233] In some scenarios, BWP#0 may be the default / required BWP (i.e., the default / required frequency domain resource), and an S-SSB frequency domain resource is configured / pre-configured on BWP#0. In this scenario, terminals need to transmit / receive S-SSB on BWP#0, and both first-type and second-type terminals transmit / receive S-SSB on BWP#0.

[0234] In some scenarios, the second type of terminal can send / receive S-SSB on BWP#0, and can switch from BWP#0 to BWP#1 to send / receive service data.

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

[0236] In the example in Figure 19, the entire frequency domain resource may be divided into multiple subbandwidths, or the system frequency domain resource may include multiple subbandwidths within a single SL BWP. Here, the multiple subbandwidths may be, for example, multiple frequency ranges, multiple resource pools, multiple RB sets, or multiple channels.

[0237] In one example, the multiple subbandwidths may be multiple frequency ranges, such as frequency range #0 to frequency range #2 in Figure 19. Here, the frequency ranges may or may not overlap.

[0238] In another example, the multiple subbandwidths may be multiple resource pools, for example, resource pool #0 to resource pool #2 in Figure 19. Here, the resource pools may or may not overlap.

[0239] In yet another example, the multiple subbandwidths may be multiple RB sets, for example, RB sets #0 to #2 in Figure 19, where there is no overlap between each RB set. In some embodiments, a guard period may also be configured between two adjacent RB sets.

[0240] In another example, the multiple subbandwidths may consist of multiple channels (not shown in Figure 19), and there may be no overlap between the channels.

[0241] In some scenarios, subbandwidth #1 (e.g., frequency range #1, resource pool #1, or RB set #1) may be a default / required frequency domain resource (default / required frequency band) or a common frequency domain resource. In this scenario, the terminal must transmit / receive S-SSB in at least subbandwidth #1.

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

[0243] To make it clear, in the example shown in Figure 19, subbandwidth #2 (e.g., frequency range #2, resource pool #2, or RB set #2) does not contain any S-SSB frequency domain resources, so no terminals transmit / receive S-SSB in subbandwidth #2.

[0244] Embodiments of the present invention design a method for designing sidelink synchronization signal frequency domain resources. This method allows for the definition and configuration of relatively small frequency band resources (frequency domain resources) in the frequency domain for S-SSB transmission / reception, in order to support communication and coexistence between terminals of different capabilities within the same system, while simultaneously ensuring that the sidelink synchronization process can be completed. Here, the relatively small frequency band resource may be a common frequency domain resource dedicated to transmitting system messages such as synchronization. In this way, synchronization between all sidelink terminals can be primarily guaranteed. Furthermore, this method also supports additional frequency band resources for transmitting additional S-SSB, which may be used as a complement when transmitting / receiving synchronization signals between full-capacity terminals. In some embodiments, for low-capacity terminals, the synchronization process and service data communication process can be performed on different frequency band resources by switching the BWP, thereby enabling more efficient use of frequency domain resources.

[0245] Preferred embodiments of the present application have been described above with reference to the drawings, but the present application is not limited to the specific details of the embodiments described above. Various simple modifications can be made to the technical solutions of the present application within the scope of the technical concept, and all such simple modifications fall within the scope of the present application. For example, each specific technical feature described in the specific embodiments described above can be combined in any suitable way without contradiction, and to avoid unnecessary repetition, the present application does not describe various possible combinations again. In another example, various different embodiments of the present application can also be combined in any way, as long as they do not contradict the idea of ​​the present application, and these should likewise be treated as part of the disclosures of the present application. In another example, each example and / or technical feature in each example described in the present application can be combined with the prior art in any way, and the technical solutions obtained by such combinations are also included within the scope of the present application.

[0246] Furthermore, to ensure clarity, in the embodiments of the various methods of the present application, the magnitude of the number of each process described above does not indicate the order of execution, and the order of execution of each process should be determined by its function and inherent logic, and does not limit in any way the implementation processes of the embodiments of the present application. Also, in the embodiments of the present application, the terms “downlink,” “uplink,” and “sidelink” are used to describe the direction of signal or data transmission, and in this specification, “downlink” means that the direction of signal or data transmission is a first direction from the station to the user equipment in the cell, “uplink” means that the direction of signal or data transmission is a second direction from the user equipment in the cell to the station, and “sidelink” means that the direction of signal or data transmission is a third direction from user equipment 1 to user equipment 2. For example, “downlink signal” means that the direction of transmission of the signal is the first direction. Also, in the embodiments of the present application, the terms “and / or” describe only the associated relationship and indicate that three relationships may exist. Specifically, A and / or B can represent three cases: when A exists independently, when both A and B exist, and when B exists independently. Furthermore, the symbol " / " in this specification generally indicates that the relationship between the preceding and following related items is "or".

[0247] Based on the embodiments described above, the embodiments of the present application provide a corresponding side-link synchronization device.

[0248] Figure 20 is a schematic diagram of the side link synchronization device provided in the embodiment of the present application, which is applied to a terminal. As shown in Figure 20, the side link synchronization device 2000 is The system includes a transceiver unit 2000 configured to transmit or receive a sidelink synchronization signal block (S-SSB) on a first frequency domain resource, the first frequency domain resource being a subset of the system frequency domain resources.

[0249] In some embodiments, the system frequency domain resources include a plurality of S-SSB frequency domain resources within one sidelink bandwidth part (SL BWP), and the first frequency domain resource is some of the plurality of S-SSB frequency domain resources.

[0250] In some embodiments, the frequency domain positions and / or the number of the plurality of S-SSB frequency domain resources are pre-configured or configured by the network.

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

[0252] In some embodiments, the number of the plurality of S-SSB frequency domain resources is the number of repetitions of one S-SSB in the SL BWP.

[0253] In some embodiments, the system frequency domain resources include a plurality of sub-bandwidths within one SL BWP, at least one of the plurality of sub-bandwidths includes an S-SSB frequency domain resource, the first frequency domain resource is some of the plurality of sub-bandwidths, and the some of the sub-bandwidths include an S-SSB frequency domain resource.

[0254] In some embodiments, for each subbandwidth within the subset of subbandwidths, the frequency domain resources for transmitting S-SSB include all S-SSB frequency domain resources within the subbandwidth or some of the S-SSB frequency domain resources.

[0255] In some embodiments, each subbandwidth within the partial subbandwidth is adjacent in the frequency domain, or each subbandwidth within the partial subbandwidth is not adjacent in the frequency domain, or some subbandwidths within the partial subbandwidth are adjacent in the frequency domain.

[0256] In some embodiments, in subbands containing S-SSB frequency domain resources, the frequency domain locations and / or number of S-SSB frequency domain resources included in each subband are either pre-configured or configured by a network.

[0257] In some embodiments, when S-SSB frequency domain resources are continuously distributed in a subbandwidth containing S-SSB frequency domain resources, the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth is determined based on the starting position of the first S-SSB frequency domain resource in the subbandwidth and the total length of the S-SSB frequency domain resources in the subbandwidth. When S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in the subbandwidth, or based on the starting position of the first S-SSB frequency domain resource in the subbandwidth, the total length of the S-SSB frequency domain resources in the subbandwidth, and the distance between two adjacent S-SSB frequency domain resources in the subbandwidth.

[0258] In some embodiments, in a subbandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources in each subbandwidth is the number of repetitions of one S-SSB in the subbandwidth, where the number of S-SSB frequency domain resources in different subbandwidths is the same or different.

[0259] In some embodiments, the subbandwidth is a resource blockset, channel, frequency range, or resource pool.

[0260] In some embodiments, when the subbandwidth is a frequency range or resource pool, multiple subbandwidths within the SL BWP may or may not overlap in the frequency domain. When the subbandwidth is a resource blockset or channel, multiple subbandwidths within the SL BWP do not overlap in the frequency domain.

[0261] In some embodiments, the system frequency domain resource includes a plurality of SL BWPs, at least one of the plurality of SL BWPs includes an S-SSB frequency domain resource, and the first frequency domain resource is a subset of the plurality of SL BWPs, the subset of SL BWPs includes an S-SSB frequency domain resource.

[0262] In some embodiments, for each SL BWP within some of the SL BWPs, the frequency domain resources for transmitting S-SSB include all S-SSB frequency domain resources within the SL BWP or some of the S-SSB frequency domain resources.

[0263] In some embodiments, the SL BWPs within the subset of SL BWPs are adjacent in the frequency domain, or the SL BWPs within the subset of SL BWPs are not adjacent in the frequency domain, or some of the SL BWPs within the subset of SL BWPs are adjacent in the frequency domain.

[0264] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, the frequency domain locations and / or number of S-SSB frequency domain resources included in each SL BWP are either pre-configured or configured by a network.

[0265] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, if 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. If 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 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 distance between two adjacent S-SSB frequency domain resources in the SL BWP.

[0266] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources in each SL BWP is the number of repetitions of one S-SSB in the SL BWP, and the number of S-SSB frequency domain resources in different SL BWPs is the same or different.

[0267] In some embodiments, the system frequency domain resource includes a plurality of carriers, at least one of which includes an S-SSB frequency domain resource, and the first frequency domain resource is a subset of the plurality of carriers, which includes an S-SSB frequency domain resource.

[0268] In some embodiments, for each carrier within the subset of carriers, the frequency domain resources for transmitting S-SSB include all S-SSB frequency domain resources within the carrier or some of the S-SSB frequency domain resources.

[0269] In some embodiments, the carriers within the subset of carriers are adjacent in the frequency domain, or the carriers within the subset of carriers are not adjacent in the frequency domain, or some of the carriers within the subset of carriers are adjacent in the frequency domain.

[0270] In some embodiments, in a carrier containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources included in each carrier are either pre-configured or configured by a network.

[0271] In some embodiments, in a carrier containing S-SSB frequency domain resources, if the S-SSB frequency domain resources are continuously distributed, the frequency domain position of each S-SSB frequency domain resource contained in the 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 resource in the carrier. If the S-SSB frequency domain resources are discontinuously distributed, the frequency domain position of each S-SSB frequency domain resource contained in the carrier is determined based on the starting position and length of each S-SSB frequency domain resource in the carrier, or 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 resource in the carrier, and the distance between two adjacent S-SSB frequency domain resources in the carrier.

[0272] In some embodiments, in a carrier containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources in each carrier is the number of repetitions of one S-SSB in the carrier, and the number of S-SSB frequency domain resources in different carriers is the same or different.

[0273] In some embodiments, the system frequency domain resources further include a second frequency domain resource, the second frequency domain resource being a frequency domain resource other than the first frequency domain resource among the system frequency domain resources, and the second frequency domain resource is used to transmit or receive service data.

[0274] In some embodiments, the second frequency domain resource does not include the S-SSB frequency domain resource.

[0275] In some embodiments, the system frequency domain resource further includes a second frequency domain resource, the second frequency domain resource being a frequency domain resource other than the first frequency domain resource among the system frequency domain resources, and the second frequency domain resource is used to transmit or receive S-SSB if the device 2000 has the capability to transmit or receive S-SSB on the second frequency domain resource.

[0276] Those skilled in the art should understand that the description relating to the side-link synchronization device in the embodiments of this application can be understood by referring to the description relating to the side-link synchronization method in the embodiments of this application.

[0277] Figure 21 is a schematic diagram of the communication device 2100 provided in the embodiment of the present application. The communication device 2100 shown in Figure 21 includes a processor 2110, and the processor 2110 can realize the method in the embodiment of the present application by calling and executing a computer program from memory.

[0278] Optionally, the communication device 2100 may further include a memory 2120, as shown in Figure 21. Here, the processor 2110 can realize the method in the embodiment of the present invention by calling and executing a computer program from the memory 2120.

[0279] Here, the memory 2120 may be a separate device independent of the processor 2110, or it may be integrated into the processor 2110.

[0280] Optionally, as shown in Figure 21, 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 transmit information or data to other devices or to receive information or data transmitted by other devices.

[0281] Here, the transceiver 2130 may include a transmitter and a receiver. The transceiver 2130 may further include one or more antennas.

[0282] The communication device 2100 may also be a terminal in the embodiment of the present application, and the communication device 2100 can perform the corresponding processes realized by the terminal in each method of the embodiment of the present application, which will not be described again here for brevity.

[0283] Figure 22 is a schematic diagram of a chip according to an embodiment of the present application. The chip 2200 shown in Figure 22 includes a processor 2210, and the processor 2210 can realize the method in the embodiment of the present application by calling and executing a computer program from memory. Optionally, as shown in Figure 22, the chip 2200 may further include a memory 2220. Here, the processor 2210 can implement the method in the embodiment of the present invention by calling and executing a computer program from the memory 2220. Here, the memory 2220 may be a separate device independent of the processor 2210, or it may be integrated into the processor 2210.

[0284] Optionally, the chip 2200 may further include an input interface 2230, where the processor 2210 can control the input interface 2230 to communicate with other devices or chips, specifically, to acquire information or data transmitted by other devices or chips.

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

[0286] The chip may be applied to the terminal in the embodiment of the present application, and the chip may perform the corresponding processes implemented by the terminal in each method of the embodiment of the present application, which will not be described again here for brevity.

[0287] It should be understood that the chips referred to in the embodiments of this application may also be called system-level chips, system chips, chip systems, or system-on-a-chip.

[0288] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the embodiments of the above method may be completed by an integrated logic circuit in hardware form or by instructions in software form within the processor. The above processor may 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 device, a discrete gate or transistor logic device, a discrete hardware component, etc. Each method, step and logic block diagram disclosed in the embodiments of this application can be implemented or executed. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application may be executed directly by a hardware decoding processor, or by a combination of hardware and software modules within the decoding processor. The software modules may be located in conventional storage media such as random-access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers, etc. The storage medium is placed in memory, and the processor reads the information in memory and, in combination with its hardware, completes the steps of the embodiment of the above method.

[0289] To ensure clarity, the memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Here, the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM) used as an external cache. To illustrate, in a non-exclusive manner, 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 (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous-connected dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). It should be noted that the memory in the systems and methods described herein includes, but is not limited to, these and any other suitable types of memory.

[0290] It should be understood that, as described in the illustrative but not limiting description, the memory in the embodiments of this application may further include, for example, 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), synchronously connected dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). In other words, the memory in the embodiments of this application is intended to include, but not be limited to, these and any other suitable types of memory.

[0291] Embodiments of the present application further provide a computer-readable storage medium for storing computer programs. The computer-readable storage medium may be applied to a terminal in an embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the terminal in each method of the embodiment of the present application, which will not be described again here for brevity.

[0292] Embodiments of the present application further provide a computer program product including computer program instructions. The computer program product may be applied to the terminal in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the terminal in each method of the embodiment of the present application, which will not be described again here for brevity.

[0293] Embodiments of the present application further provide a computer program. The computer program may be applied to the terminal in the embodiment of the present application, and 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 embodiment of the present application, which will not be described again here for brevity.

[0294] Those skilled in the art will recognize that each example unit and algorithmic step described in relation to the embodiments disclosed herein can be implemented in electronic hardware or in 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. While experts in the art may implement the described functions using different methods for each specific application, such implementations should not be considered beyond the scope of this application.

[0295] Those skilled in the art will clearly understand, for the sake of convenience and brevity of explanation, that the specific operating processes of the above-described systems, apparatuses, and units can be described by referring to the corresponding processes in the embodiments of the methods described above, and will not be described again here.

[0296] In some embodiments provided herein, it should be understood that the disclosed systems, apparatus and methods can be implemented in other ways. For example, the embodiments of the apparatus described above are illustrative only, and the division of the units is merely a division of logical functions; in actual implementation, there may be other methods of division, such as integrating or integrating multiple units or components into another system, or ignoring or not performing some features. In other words, the mutual coupling, direct coupling or communication connection expressed or discussed may be an indirect coupling or communication connection via some interface, apparatus or unit, and may be electrical, mechanical or otherwise.

[0297] The units described as individual parts may or may not be physically separated, and the parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Depending on the actual needs, some or all of these units can be selected to achieve the objectives of the solution in this embodiment.

[0298] Furthermore, each functional unit in each embodiment of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit.

[0299] If the aforementioned functions are implemented in the form of a software function unit and sold or used as an independent product, they may be stored on a computer-readable storage medium. Based on this understanding, an essential part of the technical solution of the present application, i.e., a part that contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a computer software product, which is stored on a storage medium and includes several instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The storage medium includes various media capable of storing program code, such as USB memory, portable hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0300] The above description is merely an embodiment of the present application, and the scope of protection of this application is not limited thereto. All modifications or substitutions that a person skilled in the art could easily conceive of within the technical scope disclosed herein should be included within the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A side link synchronization method applied to a terminal, A sidelink synchronization method comprising transmitting or receiving a sidelink synchronization signal block (S-SSB) on a first frequency domain resource, wherein the first frequency domain resource is a portion of the system frequency domain resources.

2. The system frequency domain resource includes multiple S-SSB frequency domain resources within one sidelink bandwidth portion (SL BWP), The first frequency domain resource is a portion of the multiple S-SSB frequency domain resources. The side link synchronization method according to claim 1.

3. The frequency domain locations and / or number of the plurality of S-SSB frequency domain resources are either pre-configured or configured by a network. The side link synchronization method according to claim 2.

4. When the plurality of S-SSB frequency domain resources are distributed continuously, the frequency domain positions of the plurality of 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 plurality of S-SSB frequency domain resources. When the plurality of S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of the plurality of S-SSB frequency domain resources is determined based on the starting position and length of each S-SSB frequency domain resource, or based on the starting position of the first S-SSB frequency domain resource, the total length of the plurality of S-SSB frequency domain resources, and the distance between two adjacent S-SSB frequency domain resources. The side link synchronization method according to claim 2 or 3.

5. The number of the multiple S-SSB frequency domain resources is the number of repetitions of one S-SSB in the SL BWP. The side link synchronization method according to any one of claims 2 to 4.

6. The system frequency domain resource includes multiple subbandwidths within one SL BWP, and at least one of the multiple subbandwidths includes an S-SSB frequency domain resource. The first frequency domain resource is a portion of the subbandwidths among the plurality of subbandwidths, and the portion of the subbandwidths includes an S-SSB frequency domain resource. The side link synchronization method according to claim 1.

7. For each subbandwidth within the aforementioned subbandwidth, the frequency domain resources for transmitting the S-SSB include all S-SSB frequency domain resources within the subbandwidth or some of the S-SSB frequency domain resources. The side link synchronization method according to claim 6.

8. Each of the subbandwidths within the aforementioned subbandwidths is adjacent in the frequency domain, or Each of the subbandwidths within the aforementioned subbandwidths is not adjacent in the frequency domain, or Some of the aforementioned subbandwidths are adjacent in the frequency domain. The side link synchronization method according to claim 6 or 7.

9. In a subbandwidth containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources included in each subbandwidth are either pre-configured or configured by a network. The side link synchronization method according to any one of claims 6 to 8.

10. In a subbandwidth containing S-SSB frequency domain resources, if the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth is determined based on the starting position of the first S-SSB frequency domain resource within the subbandwidth and the total length of the S-SSB frequency domain resources within the subbandwidth. When S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth is determined based on the starting position and length of each S-SSB frequency domain resource within the subbandwidth, or based on the starting position of the first S-SSB frequency domain resource within the subbandwidth, the total length of the S-SSB frequency domain resources within the subbandwidth, and the distance between two adjacent S-SSB frequency domain resources within the subbandwidth. The side link synchronization method according to any one of claims 6 to 9.

11. In a subbandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources included in each subbandwidth is the number of repetitions of one S-SSB in the subbandwidth, and the number of S-SSB frequency domain resources included in different subbandwidths is the same or different. The side link synchronization method according to any one of claims 6 to 10.

12. The subbandwidth is a resource blockset, channel, frequency range, or resource pool. The side link synchronization method according to any one of claims 6 to 11.

13. If the subbandwidth is a frequency range or a resource pool, the multiple subbandwidths within the SL BWP may overlap or not overlap in the frequency domain. If the subbandwidth is a resource blockset or channel, the multiple subbandwidths within the SL BWP do not overlap in the frequency domain. The side link synchronization method according to claim 12.

14. The system frequency domain resource includes a plurality of SL BWPs, and at least one of the plurality of SL BWPs includes an S-SSB frequency domain resource. The first frequency domain resource is a portion of the plurality of SL BWPs, and the portion of the SL BWPs includes an S-SSB frequency domain resource. The side link synchronization method according to claim 1.

15. For each SL BWP within the aforementioned partial SL BWP, the frequency domain resources for transmitting the S-SSB include all S-SSB frequency domain resources within the SL BWP or some of the S-SSB frequency domain resources. The side link synchronization method according to claim 14.

16. The SL BWPs within the aforementioned partial SL BWPs are adjacent in the frequency domain, or The SL BWPs within the aforementioned partial SL BWPs are not adjacent in the frequency domain, or Some of the aforementioned SL BWPs are adjacent in the frequency domain. The side link synchronization method according to claim 14 or 15.

17. In an SL BWP containing S-SSB frequency domain resources, the frequency domain locations and / or number of S-SSB frequency domain resources included in each SL BWP are either pre-configured or configured by a network. The side link synchronization method according to any one of claims 14 to 16.

18. In an SL BWP containing S-SSB frequency domain resources, if 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 S-SSB frequency domain resources are distributed discontinuously, 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 within the SL BWP, or based on the starting position of the first S-SSB frequency domain resource within the SL BWP, the total length of the S-SSB frequency domain resources within the SL BWP, and the distance between two adjacent S-SSB frequency domain resources within the SL BWP. The side link synchronization method according to any one of claims 14 to 17.

19. In an SL BWP containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources included in each SL BWP is the number of repetitions of one S-SSB in the SL BWP, and the number of S-SSB frequency domain resources included in different SL BWPs is the same or different. The side link synchronization method according to any one of claims 14 to 18.

20. The system frequency domain resource includes a plurality of carriers, and at least one of the plurality of carriers includes an S-SSB frequency domain resource. The first frequency domain resource is a subset of the plurality of carriers, and the subset of carriers includes an S-SSB frequency domain resource. The side link synchronization method according to claim 1.

21. For each carrier within the aforementioned partial carrier, the frequency domain resources for transmitting the S-SSB include all S-SSB frequency domain resources within the carrier or some of the S-SSB frequency domain resources. The side link synchronization method according to claim 20.

22. Each of the carriers within the aforementioned subset of carriers is adjacent in the frequency domain, or Each of the carriers within the aforementioned subset of carriers is not adjacent in the frequency domain, or Some of the carriers within the aforementioned some carriers are adjacent in the frequency domain. The side link synchronization method according to claim 20 or 21.

23. In a carrier containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources included in each carrier are either pre-configured or configured by the network. The side link synchronization method according to any one of claims 20 to 22.

24. In a carrier containing S-SSB frequency domain resources, if the S-SSB frequency domain resources are continuously distributed, the frequency domain position of each S-SSB frequency domain resource contained 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 S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of an S-SSB frequency domain resource contained in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource within the carrier, or based on the starting position of the first S-SSB frequency domain resource within the carrier, the total length of the S-SSB frequency domain resources within the carrier, and the distance between two adjacent S-SSB frequency domain resources within the carrier. The side link synchronization method according to any one of claims 20 to 23.

25. In a carrier containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources in each carrier is the number of repetitions of one S-SSB in the carrier, and the number of S-SSB frequency domain resources in different carriers is the same or different. A side link synchronization method according to any one of claims 20 to 24.

26. The system frequency domain resource further includes a second frequency domain resource, the second frequency domain resource being a frequency domain resource other than the first frequency domain resource among the system frequency domain resources. The second frequency domain resource is used to transmit or receive service data. The side link synchronization method according to any one of claims 1 to 25.

27. The aforementioned second frequency domain resource does not include an S-SSB frequency domain resource. The side link synchronization method according to claim 26.

28. The system frequency domain resource further includes a second frequency domain resource, the second frequency domain resource being a frequency domain resource other than the first frequency domain resource among the system frequency domain resources. If the terminal has the capability to transmit or receive S-SSB on a second frequency domain resource, the second frequency domain resource is used to transmit or receive S-SSB. The side link synchronization method according to any one of claims 1 to 26.

29. Side link synchronization device, A sidelink synchronization device comprising a transceiver unit configured to transmit or receive a sidelink synchronization signal block (S-SSB) on a first frequency domain resource, wherein the first frequency domain resource is a portion of the system frequency domain resources.

30. The system frequency domain resource includes multiple S-SSB frequency domain resources within one sidelink bandwidth portion (SL BWP), The first frequency domain resource is a portion of the S-SSB frequency domain resources among the plurality of S-SSB frequency domain resources. The side link synchronization device according to claim 29.

31. The frequency domain locations and / or number of the plurality of S-SSB frequency domain resources are either pre-configured or configured by a network. The side link synchronization device according to claim 30.

32. When the plurality of S-SSB frequency domain resources are distributed continuously, the frequency domain positions of the plurality of 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 plurality of S-SSB frequency domain resources. When the plurality of S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of the plurality of S-SSB frequency domain resources is determined based on the starting position and length of each S-SSB frequency domain resource, or based on the starting position of the first S-SSB frequency domain resource, the total length of the plurality of S-SSB frequency domain resources, and the distance between two adjacent S-SSB frequency domain resources. The side link synchronization device according to claim 30 or 31.

33. The number of the multiple S-SSB frequency domain resources is the number of repetitions of one S-SSB in the SL BWP. A side link synchronization device according to any one of claims 30 to 32.

34. The system frequency domain resource includes multiple subbandwidths within one SL BWP, and at least one of the multiple subbandwidths includes an S-SSB frequency domain resource. The first frequency domain resource is a portion of the subbandwidths among the plurality of subbandwidths, and the portion of the subbandwidths includes an S-SSB frequency domain resource. The side link synchronization device according to claim 29.

35. For each subbandwidth within the aforementioned subbandwidth, the frequency domain resources for transmitting the S-SSB include all S-SSB frequency domain resources within the subbandwidth or some of the S-SSB frequency domain resources. The side link synchronization device according to claim 34.

36. Each of the subbandwidths within the aforementioned subbandwidths is adjacent in the frequency domain, or Each of the subbandwidths within the aforementioned subbandwidths is not adjacent in the frequency domain, or Some of the aforementioned subbandwidths are adjacent in the frequency domain. The side link synchronization device according to claim 34 or 35.

37. In a subbandwidth containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources included in each subbandwidth are either pre-configured or configured by a network. A side link synchronization device according to any one of claims 34 to 36.

38. In a subbandwidth containing S-SSB frequency domain resources, if the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth is determined based on the starting position of the first S-SSB frequency domain resource within the subbandwidth and the total length of the S-SSB frequency domain resources within the subbandwidth. When S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of the S-SSB frequency domain resources included in each subbandwidth is determined based on the starting position and length of each S-SSB frequency domain resource within the subbandwidth, or based on the starting position of the first S-SSB frequency domain resource within the subbandwidth, the total length of the S-SSB frequency domain resources within the subbandwidth, and the distance between two adjacent S-SSB frequency domain resources within the subbandwidth. A side link synchronization device according to any one of claims 34 to 37.

39. In a subbandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources included in each subbandwidth is the number of repetitions of one S-SSB in the subbandwidth, and the number of S-SSB frequency domain resources included in different subbandwidths is the same or different. A side link synchronization device according to any one of claims 34 to 38.

40. The subbandwidth is a resource blockset, channel, frequency range, or resource pool. A side link synchronization device according to any one of claims 34 to 39.

41. If the subbandwidth is a frequency range or a resource pool, the multiple subbandwidths within the SL BWP may overlap or not overlap in the frequency domain. If the subbandwidth is a resource blockset or channel, the multiple subbandwidths within the SL BWP do not overlap in the frequency domain. The side link synchronization device according to claim 40.

42. The system frequency domain resource includes a plurality of SL BWPs, and at least one of the plurality of SL BWPs includes an S-SSB frequency domain resource. The first frequency domain resource is a portion of the plurality of SL BWPs, and the portion of the SL BWPs includes an S-SSB frequency domain resource. The side link synchronization device according to claim 29.

43. For each SL BWP within the aforementioned partial SL BWP, the frequency domain resources for transmitting the S-SSB include all S-SSB frequency domain resources within the SL BWP or some of the S-SSB frequency domain resources. The side link synchronization device according to claim 42.

44. The SL BWPs within the aforementioned partial SL BWPs are adjacent in the frequency domain, or The SL BWPs within the aforementioned partial SL BWPs are not adjacent in the frequency domain, or Some of the aforementioned SL BWPs are adjacent in the frequency domain. The side link synchronization device according to claim 42 or 43.

45. In an SL BWP containing S-SSB frequency domain resources, the frequency domain locations and / or number of S-SSB frequency domain resources included in each SL BWP are either pre-configured or configured by a network. A side link synchronization device according to any one of claims 42 to 44.

46. In an SL BWP containing S-SSB frequency domain resources, if 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 S-SSB frequency domain resources are distributed discontinuously, 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 within the SL BWP, or based on the starting position of the first S-SSB frequency domain resource within the SL BWP, the total length of the S-SSB frequency domain resources within the SL BWP, and the distance between two adjacent S-SSB frequency domain resources within the SL BWP. A side link synchronization device according to any one of claims 42 to 45.

47. In an SL BWP containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources included in each SL BWP is the number of repetitions of one S-SSB in the SL BWP, and the number of S-SSB frequency domain resources included in different SL BWPs is the same or different. A side link synchronization device according to any one of claims 42 to 46.

48. The system frequency domain resource includes a plurality of carriers, and at least one of the plurality of carriers includes an S-SSB frequency domain resource. The first frequency domain resource is a subset of the plurality of carriers, and the subset of carriers includes an S-SSB frequency domain resource. The side link synchronization device according to claim 29.

49. For each carrier within the aforementioned partial carrier, the frequency domain resources for transmitting the S-SSB include all S-SSB frequency domain resources within the carrier or some of the S-SSB frequency domain resources. The side link synchronization device according to claim 48.

50. Each of the carriers within the aforementioned subset of carriers is adjacent in the frequency domain, or Each of the carriers within the aforementioned subset of carriers is not adjacent in the frequency domain, or Some of the carriers within the aforementioned some carriers are adjacent in the frequency domain. The side link synchronization device according to claim 48 or 49.

51. In a carrier containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources included in each carrier are either pre-configured or configured by the network. A side link synchronization device according to any one of claims 48 to 50.

52. In a carrier containing S-SSB frequency domain resources, if the S-SSB frequency domain resources are continuously distributed, the frequency domain position of each S-SSB frequency domain resource contained 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 S-SSB frequency domain resources are distributed discontinuously, the frequency domain position of an S-SSB frequency domain resource contained in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource within the carrier, or based on the starting position of the first S-SSB frequency domain resource within the carrier, the total length of the S-SSB frequency domain resources within the carrier, and the distance between two adjacent S-SSB frequency domain resources within the carrier. A side link synchronization device according to any one of claims 48 to 51.

53. In a carrier containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources in each carrier is the number of repetitions of one S-SSB in the carrier, and the number of S-SSB frequency domain resources in different carriers is the same or different. A side link synchronization device according to any one of claims 48 to 52.

54. The system frequency domain resource further includes a second frequency domain resource, the second frequency domain resource being a frequency domain resource other than the first frequency domain resource among the system frequency domain resources. The second frequency domain resource is used to transmit or receive service data. A side link synchronization device according to any one of claims 29 to 53.

55. The aforementioned second frequency domain resource does not include an S-SSB frequency domain resource. The side link synchronization device according to claim 54.

56. The system frequency domain resource further includes a second frequency domain resource, the second frequency domain resource being a frequency domain resource other than the first frequency domain resource among the system frequency domain resources. If the device has the capability to transmit or receive S-SSB on a second frequency domain resource, the second frequency domain resource is used to transmit or receive S-SSB. A side link synchronization device according to any one of claims 29 to 54.

57. It is a terminal, A terminal comprising a processor and memory, wherein the memory is configured to store computer programs, and the processor is configured to perform the method according to any one of claims 1 to 28 by calling and executing the computer programs stored in the memory.

58. It's a tip, A chip comprising a processor that causes a device on which the chip is mounted to perform the method according to any one of claims 1 to 28 by calling and executing a computer program from memory.

59. A computer-readable storage medium storing a computer program that causes a computer to perform the method described in any one of claims 1 to 28.

60. A computer program product comprising a computer program instruction causing a computer to perform the method described in any one of claims 1 to 28.

61. A computer program that causes a computer to perform the method described in any one of claims 1 to 28.

Images