Lateral synchronization method and device, terminal, chip and storage medium

Abstract

The embodiment of the invention provides a sidelink synchronization method. The method comprises the following steps: a terminal sends or receives a sidelink synchronization signal block (S-SSB) on a first frequency domain resource; wherein the first frequency domain resource is a part of frequency domain resources in the system frequency domain resources. According to the method, the S-SSB is sent or received by using part of frequency domain resources in the system frequency domain resources, so that the S-SSB can be sent or received on a relatively small bandwidth, terminals with different capabilities in the same communication system can be considered, and all the terminals can be ensured to be synchronized.

Description

[0001] Case Analysis

[0002] This application is a divisional application of Chinese Patent No. 202380093181.4, filed on July 14, 2023, entitled "A Side-by-Side Synchronization Method, Apparatus, Terminal, Chip and Storage Medium". Technical Field

[0003] This application relates to the field of communication technology, specifically to a side-by-side synchronization method, apparatus, terminal, chip, and storage medium. Background Technology

[0004] Sidelink (SL) synchronization is a crucial step in SL systems, occurring before SL communication. Existing SL technologies assume all terminals in the system have identical capabilities, such as supporting the same bandwidth and transmit power. Therefore, in current technologies, the frequency domain resources and locations for transmitting / receiving Sidelink Synchronization Signal Blocks (S-SSBs) are supported by all terminals. For example, in current Sidelink Over Unlicensed Spectrum (SL-U) systems, if there are multiple sets of Resource Blocks (RBs) in the frequency domain, and S-SSBs need to be transmitted on multiple sets of RBs, then the terminal also needs to attempt to detect and receive S-SSBs on multiple sets of RBs.

[0005] However, with technological advancements, supporting multiple terminals with different communication capabilities within the same communication system has become an unavoidable issue. If we continue to assume all terminals possess the same communication capabilities, it will create difficulties in the SL synchronization process between terminals with different capabilities. Therefore, ensuring SL synchronization between terminals with different capabilities when they coexist in a system is a pressing problem that needs to be solved. Summary of the Invention

[0006] This application provides a side-by-side synchronization method, apparatus, terminal, chip, and storage medium.

[0007] In a first aspect, embodiments of this application provide a sidelink synchronization method applied to a terminal. The method includes: 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.

[0008] Secondly, embodiments of this application provide a sidelink synchronization device, which includes: 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 resource.

[0009] Thirdly, embodiments of this application provide a terminal, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the aforementioned side-by-side synchronization method.

[0010] Fourthly, embodiments of this application provide a chip for implementing the aforementioned side-line synchronization method. Specifically, the chip includes a processor for retrieving and running a computer program from a memory, causing a device equipped with the chip to execute the aforementioned side-line synchronization method.

[0011] Fifthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that causes a computer to perform the aforementioned side-by-side synchronization method.

[0012] Sixthly, embodiments of this application provide a computer program product, including computer program instructions that cause a computer to execute the above-described side-by-side synchronization method.

[0013] In a seventh aspect, embodiments of this application provide a computer program that, when run on a computer, causes the computer to execute the aforementioned side-by-side synchronization method.

[0014] This method uses a portion of the system's frequency domain resources to transmit or receive S-SSBs, enabling S-SSB transmission or reception to be performed on a relatively small bandwidth. This allows it to accommodate terminals with different capabilities within the same communication system, thereby ensuring that all terminals can achieve synchronization. Attached Figure Description

[0015] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0016] Figure 1 This is a schematic diagram of side-by-side communication within network coverage provided in an embodiment of this application;

[0017] Figure 2 This is a schematic diagram of side-by-side communication within a portion of the network coverage provided in an embodiment of this application;

[0018] Figure 3 This is a schematic diagram of side-by-side communication outside network coverage provided in an embodiment of this application;

[0019] Figure 4 This is a schematic diagram of side-by-side communication with a central control node provided in an embodiment of this application;

[0020] Figure 5 This is a schematic diagram of the unicast transmission method provided in the embodiments of this application;

[0021] Figure 6 This is a schematic diagram of the multicast transmission method provided in the embodiments of this application;

[0022] Figure 7 This is a schematic diagram of the broadcast transmission method provided in the embodiments of this application;

[0023] Figure 8 This is a schematic diagram of the time slot structure in NR-V2X provided in the embodiments of this application;

[0024] Figure 9 This is a schematic diagram provided by an embodiment of the present application, showing that the available OFDM symbols for a PSSCH change in different transmissions within the same time slot;

[0025] Figure 10 This is a schematic diagram of the second-order SCI mapping method provided in the embodiments of this application;

[0026] Figure 11 This is a schematic diagram of the time-frequency domain location of the PSCCH DMRS provided in the embodiments of this application;

[0027] Figure 12 This is a schematic diagram of the time-domain location of the four DMRS symbols when the PSSCH has 13 symbols, as provided in the embodiments of this application.

[0028] Figure 13 This is a schematic diagram of single-symbol DMRS frequency domain type 1 provided in an embodiment of this application;

[0029] Figure 14 This is a schematic diagram of the time-frequency location of the SL CSI-RS provided in the embodiments of this application;

[0030] Figure 15 This is a schematic diagram illustrating an example of channel occupancy time and channel occupancy provided in an embodiment of this application;

[0031] Figure 16 This is a schematic diagram of frequency domain resource allocation provided in an embodiment of this application;

[0032] Figure 17 This is a schematic flowchart of the side-line synchronization method provided in the embodiments of this application;

[0033] Figure 18 This is a schematic diagram of the frequency domain resource design scheme for S-SSB provided in the embodiments of this application. Figure 1 ;

[0034] Figure 19 This is a schematic diagram of the frequency domain resource design scheme for S-SSB provided in the embodiments of this application. Figure 2 ;

[0035] Figure 20 This is a schematic diagram of the structural composition of the side-tracking synchronization device provided in the embodiments of this application;

[0036] Figure 21 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0037] Figure 22 This is a schematic structural diagram of the chip according to an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0039] The technical solutions of the embodiments of this application can be applied to various side-link communication systems. To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0040] 1. Side-to-side communication under different network coverage environments

[0041] In side-channel communication, based on the network coverage of the communicating terminal, it can be divided into side-channel communication within network coverage, side-channel communication with partial network coverage, side-channel communication outside network coverage, and side-channel communication with a central control node, as follows: Figure 1 , Figure 2 , Figure 3 and Figure 4 As shown.

[0042] like Figure 1 As shown, in side-link communication within network coverage, all terminals conducting side-link communication are within the coverage area of ​​the same base station. Therefore, all of these terminals can conduct side-link communication based on the same side-link configuration by receiving configuration signaling from the base station.

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

[0044] like Figure 3 As shown, for side communication outside network coverage, all terminals conducting side communication are located outside the network coverage area, and all terminals determine the side configuration and conduct side communication based on the pre-configuration information.

[0045] like Figure 4 As shown, for side-by-side communication with a central control node, multiple terminals form a communication group, which contains a central control node, such as... Figure 4 UE1 in this context. The central control node, also known as the cluster head (CH), has at least one of the following functions: establishing a communication group; handling the joining and leaving of group members; coordinating resources, allocating sideline transmission resources to other terminals, and receiving sideline feedback information from other terminals; and coordinating resources with other communication groups.

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

[0047] Device-to-device communication (D2D) is a sidelink transmission technology that differs from the traditional cellular system's data transmission method, which relies on base stations. Therefore, it offers higher spectral efficiency and lower transmission latency. Vehicle-to-everything (V2X) systems employ direct terminal-to-terminal communication, and the 3rd Generation Partnership Project (3GPP) defines two transmission modes: Mode 1 and Mode 2.

[0048] In the first mode, the terminal's transmission resources are allocated by the base station, and the terminal transmits data on the side link according to the resources allocated by the base station. The base station can allocate resources for a single transmission or for semi-static transmission. For example... Figure 1 In this scenario, the terminal is located within the network coverage area, and the network allocates transmission resources for the terminal to use for side-by-side transmission.

[0049] Second mode: The terminal selects a resource from the resource pool for data transmission. For example... Figure 3 In this case, the terminal is located outside the cell coverage area, and the terminal autonomously selects transmission resources from the pre-configured resource pool for side-channel transmission; or in Figure 1 In this process, the terminal autonomously selects transmission resources from the resource pool configured in the network for side-by-side transmission.

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

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

[0052] LTE-V2X supports broadcast transmission, while NR-V2X introduces unicast and multicast transmission methods. For unicast transmission, there is only one receiving terminal, such as... Figure 5 In this context, UE1 and UE2 communicate via unicast; for multicast transmission, the receiving end is all terminals within a communication group, or all terminals within a certain transmission distance, such as... Figure 6 As shown, UE1, UE2, UE3, and UE4 form a communication group, where UE1 transmits data, and the other terminal devices in the group are all receiving terminals. For broadcast transmission, the receiving terminal is any terminal surrounding the transmitting terminal, such as... Figure 7 As shown, UE1 is the sending terminal, and the other terminals around it, UE2 to UE6, are all receiving terminals.

[0053] 4. NR-V2X System Frame Structure

[0054] The time slot structure in NR-V2X is as follows Figure 8 As shown:

[0055] Figure 8 Figure (a) in the figure is a schematic diagram of the time slot structure excluding the Physical Sidelink Feedback Channel (PSFCH); Figure 8 Figure (b) in the figure is a schematic diagram of the time slot structure including the PSFCH channel.

[0056] In NR-V2X, the Physical Sidelink Control Channel (PSCCH) occupies 2 or 3 Orthogonal Frequency Division Multiplexing (OFDM) symbols in the time domain, starting from the second sidelink symbol of the time slot. In the frequency domain, it can occupy {10, 12, 15, 20, 25} Physical Resource Blocks (PRBs). To reduce the complexity of blind detection of the PSCCH by the User Equipment (UE), only one number of PSCCH symbols and PRBs can be configured within a resource pool. Furthermore, because the sub-channel is the smallest granularity for allocating PSSCH resources in NR-V2X, the number of PRBs occupied by the PSCCH must be less than or equal to the number of PRBs contained in a sub-channel within the resource pool, to avoid imposing additional restrictions on PSSCH resource selection or allocation. In the time domain, PSSCH also begins with the second sideline symbol of the time slot. The last time-domain symbol in this time slot is the Guard Period (GP) symbol, and the remaining symbols map to PSSCH. The first sideline symbol in this time slot is a repetition of the second sideline symbol. Typically, the receiving terminal uses the first sideline symbol as the Automatic Gain Control (AGC) symbol, and the data on this symbol is usually not used for data demodulation. In the frequency domain, PSSCH occupies K sub-channels, and each sub-channel consists of N consecutive PRBs.

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

[0058] 5. Side Link PSSCH

[0059] In NR-V2X, the PSSCH is used to carry second-order sidelink control information (SCI) (SCI 2-A or SCI 2-B) and data. The second-order SCI uses polar coding and is always modulated using Quadrature Phase Shift Keying (QPSK). The data portion of the PSSCH uses low-density parity check (LDPC) codes, supporting a maximum modulation order of 256QAM.

[0060] In NR-V2X, the PSSCH supports a maximum of two streams and uses a unit precoding matrix to map data from the two layers to two antenna ports. Only one transport block (TB) can be transmitted in a single PSSCH. However, unlike the transmission method of the PSSCH data portion, when the PSSCH uses a dual-stream transmission method, the modulation symbols transmitted by the second-order SCI on both streams are exactly the same. This design ensures the reception performance of the second-order SCI in highly correlated channels.

[0061] Since the maximum retransmission count for a PSSCH in NR-V2X is 32, if a PSFCH resource exists in the resource pool and its configuration period is 2 or 4, the available OFDM symbols for a PSSCH may change within different time slots of different transmissions. Figure 9 As shown. If calculated based on the actual number of OFDM symbols within a time slot... The number of symbols available for PSSCH transmission within a time slot may differ, leading to variations in Q′. SCI2 Different, and Q′ SCI2 Changes in this process will cause changes in the size of the transfer block size (TBS) carried by the PSSCH. To ensure that the transfer block size (TBS) remains constant across multiple PSSCH transmissions, the calculation... The actual number of PSFCH symbols was not used at that time, and in the calculation At the same time, the number of resource elements (REs) occupied by the PSSCH demodulation reference signal (DMRS) and the number of REs occupied by the phase-tracking reference signal (PT-RS), which may change during retransmission, are not taken into account.

[0062] The code rate of the second-order SCI can be dynamically adjusted within a certain range. The specific code rate used is indicated by the first-order SCI, so even after the code rate changes, the receiver does not need to perform blind detection on the second-order SCI. The modulation symbols of the second-order SCI begin mapping from the symbol containing the first PSSCH DMRS using a frequency-domain-first, time-domain-later approach. On the OFDM symbol containing the DMRS, the second-order SCI is mapped to the REs not occupied by the DMRS, such as... Figure 10 As shown.

[0063] Within a resource pool, the data portion of the PSSCH can employ multiple different Modulation and Coding Scheme (MCS) tables, including the standard 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 in the first-order SCI. To control the Peak to Average Power Ratio (PAPR), the PSSCH must be transmitted using consecutive PRBs. Since the subchannel is the smallest frequency domain resource granularity of the PSSCH, this requires the PSSCH to occupy consecutive subchannels.

[0064] 6. Side-transfer block size

[0065] The PSSCH adopts the Transport Block Size (TBS) determination mechanism from the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) in New Radio (NR). Specifically, it determines the TBS based on a reference value for the number of Repeatable Engines (REs) used for the PSSCH within the PSSCH time slot, thus ensuring the actual bit rate is as close as possible to the target bit 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 remains constant during PSSCH retransmissions, thereby maintaining the same determined TBS size. To achieve this, the reference value N for the number of REs used by the PSSCH during the TBS determination process is used. RE Determine according to formula (1):

[0066]

[0067] Where n PRB This represents the number of PRBs occupied by PSSCH. This refers to the number of REs occupied by the first-order SCI (including the REs occupied by the DMRS of PSCCH). N′ represents the number of REs occupied by the second-order SCI. RE The number of reference REs available for PSSCH within a PRB is determined by formula (2):

[0068]

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

[0070] Table 1. Permitted DMRS patterns within the resource pool and Correspondence

[0071]

[0072] 7. Side Link DMRS

[0073] In NR-V2X, the DMRS pattern of the PSCCH is the same as that of the NR Physical Downlink Control Channel (PDCCH), meaning that the DMRS exists on the OFDM symbol of each PSCCH, and in the frequency domain, it is located in the {#1, #5, #9} REs of a PRB, such as... Figure 11 As shown. The DMRS sequence of PSCCH is generated by formula (3):

[0074]

[0075] The pseudo-random sequence c(m) is derived from... Initialization is performed, where l is the index of the OFDM symbol containing the DMRS within the time slot. This is the index of the time slot where DMRS is located within the system frame. N represents the number of OFDM symbols within a time slot. ID ∈{0,1,…,65535}, N in a resource pool ID The specific value is determined by network configuration or pre-configuration.

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

[0077] Table 2. Number and position of DMRS symbols under different numbers of PSSCH and PSCCH symbols.

[0078]

[0079] If multiple time-domain DMRS patterns are configured within the resource pool, the specific time-domain DMRS pattern used is selected by the transmitting UE and indicated in the first-order SCI. This design allows high-speed moving UEs to select high-density DMRS patterns, thereby ensuring the accuracy of channel estimation, while low-speed moving UEs can use low-density DMRS patterns, thereby improving spectral efficiency.

[0080] The generation method of PSSCH DMRS sequences is almost identical to that of PSCCH DMRS sequences. The only difference lies in the initialization formula of the pseudo-random sequence c(m). init middle, p i The i-th bit of the PSCCH for scheduling this PSSCH is the Cyclic Redundancy Check (CRC), where L = 24, representing the number of bits in the PSCCH CRC.

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

[0082] 8. Side Link Channel State Information Reference Signal (CSI-RS)

[0083] To better support unicast communication, NR-V2X supports SL CSI-RS, which will only be sent when the following three conditions are met:

[0084] 1) The UE sends the corresponding PSSCH, meaning the UE cannot only send SL CSI-RS;

[0085] 2) Higher-level signaling activated side-line CSI reporting;

[0086] 3) When sideline CSI reporting is activated by higher-layer signaling, the corresponding bits in the second-order SCI sent by the UE trigger sideline CSI reporting.

[0087] The maximum number of ports supported by SL CSI-RS is 2. With two ports, SL CSI-RS from different ports are multiplexed using code division on two adjacent REs of the same OFDM symbol. Within a PRB, each port has 1 SL CSI-RS, meaning the density is 1. Therefore, within a PRB, SL CSI-RS will appear 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 PSCCH and second-order SCI, SL CSI-RS cannot be located on the same OFDM symbol as PSCCH and second-order SCI. Since the channel estimation accuracy of the OFDM symbol containing PSSCH DMRS is high, and SL CSI-RS from two ports will occupy two consecutive REs in the frequency domain, SL CSI-RS cannot be transmitted on the same OFDM symbol as PSSCH DMRS. The location of the OFDM symbol containing SL CSI-RS is indicated by the sl-CSI-RS-FirstSymbol parameter in the PC5 RRC.

[0088] The location of the first RE occupied by the SL CSI-RS within a PRB is indicated by the sl-CSI-RS-FreqAllocation parameter in the PC5 RRC. If the SL CSI-RS is a single port, this parameter is a bitmap of length 12, corresponding to 12 REs within a PRB. If the SL CSI-RS is a two-port port, this parameter is a bitmap of length 6. In this case, the SL CSI-RS occupies two REs, 2f(1) and 2f(1)+1, where f(1) represents the index of the bit with a value of 1 in the bitmap. The frequency domain location of the SL CSI-RS is also determined by the transmitting terminal, but the determined frequency domain location of the SL CSI-RS cannot conflict with the PT-RS. Figure 14 A time-frequency location diagram of SL CSI-RS is given. Figure 14 In this configuration, the number of SL CSI-RS ports is 2, the number of sl-CSI-RS-FirstSymbols is 8, and the sl-CSI-RS-FreqAllocation is [b5,b4,b3,b2,b1,b0] = [0,0,0,1,0,0].

[0089] 9. 5G unlicensed (NR-U) spectrum communication

[0090] The NR system, introduced in 3GPP Release 15, is a communication technology for use on both existing and new licensed spectrum. NR systems enable seamless cellular network coverage, high spectral efficiency, high peak data rates, and high reliability. In Long Term Evolution (LTE) systems, unlicensed spectrum (or unlicensed spectrum) has been implemented as a supplementary band to licensed spectrum for cellular networks. Similarly, NR systems can also use unlicensed spectrum as part of 5G cellular network technology to provide services to users. The 3GPP Release 16 standard discusses NR systems for unlicensed spectrum, referred to as NR-unlicensed (NR-U).

[0091] The NR-U system supports two networking modes: licensed spectrum-assisted access and unlicensed spectrum-independent access. The former requires access to the network via licensed spectrum, with unlicensed spectrum used as a secondary carrier; the latter allows for independent networking via unlicensed spectrum, allowing the UE to directly access the network. The unlicensed spectrum used by the NR-U system introduced in 3GPP Release 16 is concentrated in the 5GHz and 6GHz bands, such as 5925-7125MHz in the US or 5925-6425MHz in Europe. In Release 16, a new band 46 (5150MHz-5925MHz) was defined for use as unlicensed spectrum.

[0092] Unlicensed spectrum refers to spectrum allocated by a country or region for use in wireless communication. This spectrum is generally considered shared spectrum, meaning that communication equipment can use it as long as it meets the regulatory requirements set by the country or region for that spectrum, without needing to apply for a proprietary spectrum license from the country or region's dedicated spectrum management agency. Because the use of unlicensed spectrum requires compliance with the specific regulations of each country and region, such as the "Listen Before Talk" (LBT) principle, NR technology needs to be enhanced to adapt to the regulatory requirements of unlicensed frequency bands while efficiently utilizing unlicensed spectrum to provide services. The 3GPP Release 16 standard primarily standardized the following aspects of NR-U technology: channel listening procedures; initial access procedures; control channel design; Hybrid Automatic Repeat Request (HARQ) and scheduling; and scheduling-free licensed transmission.

[0093] 10. Channel Monitoring: LBT

[0094] To ensure the amicable coexistence of various communication systems using unlicensed spectrum, some countries and regions have stipulated regulatory requirements for using unlicensed spectrum. For example, according to European regulations, when communicating on unlicensed spectrum, communication devices must adhere to the "LBT" principle. This means that before transmitting signals through a channel on unlicensed spectrum, the device must first perform an LBT, or channel listening. Only if the channel listening result is that the channel is idle, or the LBT is successful, can the communication device transmit signals through that channel. If the channel listening result is that the channel is busy, or the LBT fails, then the communication device cannot transmit signals through that channel. Furthermore, to ensure fairness in the use of shared spectrum resources, if a communication device successfully performs an LBT on a channel on unlicensed spectrum, the duration for which the device can use that channel for communication transmission cannot exceed a certain limit. This mechanism, by limiting the maximum communication duration after a successful LBT, allows different communication devices to have the opportunity to access the shared channel, thus enabling different communication systems to coexist amicably on the shared spectrum.

[0095] Although channel sensing is not a global regulatory requirement, it is a necessary feature for communication equipment in unlicensed NR systems because it provides benefits such as interference avoidance and amicable coexistence between communication systems on shared spectrum. From a network deployment perspective, channel sensing includes two mechanisms: load-based equipment (LBE) LBT, also known as dynamic channel sensing or dynamic channel occupancy, and frame-based equipment (FBE) LBT, also known as semi-static channel sensing or semi-static channel occupancy.

[0096] 11. Dynamic channel monitoring

[0097] Dynamic channel sensing (DLS) can also be considered a channel-by-bits (LBT) method based on level-of-behind (LBE). Its channel sensing principle is that the communication equipment performs LBT on an unlicensed spectrum carrier after the service arrives, and begins signal transmission on that carrier after a successful LBT. Dynamic channel sensing LBT methods include Type 1 and Type 2 channel access methods. Type 1 channel access is a multi-slot channel detection method with random backoff based on contention window size adjustment. The corresponding channel access priority class (CAPC)p can be selected according to the priority of the service to be transmitted. Type 2 channel access is a channel access method based on fixed-length listening slots. Type 2 channel access includes Type 2A, Type 2B, and Type 2C channel access. Type 1 channel access is mainly used for communication equipment to initiate channel occupancy, while Type 2 channel access is mainly used for communication equipment to share channel occupancy. A special case that needs to be explained is that when a base station initiates channel occupancy for a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block within a Discover Reference Symbol (DRS) window, and the DRS window does not include unicast data transmission from the UE, if the length of the DRS window does not exceed 1ms and the duty cycle of the DRS window transmission does not exceed 1 / 20, then the base station can use the Type 2A channel to access and initiate channel occupancy.

[0098] Figure 15 The document provides an example of a communication device obtaining a channel occupancy time after a successful LBT on an unlicensed spectrum channel, and using the resources within that channel occupancy time for signal transmission.

[0099] 12. Base station default channel access method: Type 1 channel access

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

[0101] If the channel access process is complete, the base station can use the channel to transmit the intended service. The maximum duration for which the base station can use the channel for transmission cannot exceed T. mcot,p .

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

[0103]

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

[0105] When a base station initiates a Channel Occupancy Time (COT), it can use the resources within that COT for downlink transmission and also share those resources with the UE for uplink transmission. When sharing COT resources with the UE for uplink transmission, the UE can use one of three channel access methods: Type 2A, Type 2B, or Type 2C. Type 2A, Type 2B, and Type 2C are all channel access methods based on fixed-length listening time slots.

[0106] Type 2A channel access:

[0107] The UE uses a 25μs single-slot channel detection method. Specifically, under Type 2A channel access, the UE can perform a 25μs channel sniff before transmission begins, and transmit after successful channel sniffing.

[0108] Type 2B channel access:

[0109] The UE uses a 16μs single-slot channel detection method. Specifically, under Type 2B channel access, the UE can perform a 16μs channel listening before transmission begins, and transmit after successful channel listening. The gap between the start position of this transmission and the end position of the previous transmission is 16μs.

[0110] Type 2C channel access:

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

[0112] 14. Channel Access Parameter Indication (including Cyclic Prefix Extension (CPE))

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

[0114] In specific instructions, the base station can explicitly indicate channel access parameters such as CPE length, channel access method, or channel access priority to the UE through joint coding. The characteristics of the indication methods for channel access parameters introduced under different DCI formats are described below.

[0115] 1) Backoff uplink grant for scheduling PUSCH transmissions (DCI format 0_0):

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

[0117] 2) Downlink rollback grant for scheduling PDSCH transmissions (DCI format 1_0):

[0118] The standard pre-defined set of channel access mode and CPE length joint indications is shown in Table 4. The downlink grant includes 2 bits of LBT indication information, which is used to indicate the jointly coded channel access mode and CPE length from the set shown in Table 4. This channel access mode and CPE length are used for PUCCH transmission, where the PUCCH can carry either an ACK or a NACK corresponding to the PDSCH. If the channel access mode is Type 1 channel access, the UE determines the channel access priority CAPC = 1 for PUCCH transmission.

[0119] Table 4. Joint Indicator Set of Channel Access Method and CPE Length

[0120] LBT indication Channel access method CPE length 0 Type2C Channel Access C2* symbol length - 16μs - TA 1 Type 2A Channel Access C3* Symbol length - 25μs - TA 2 Type 2A Channel Access C1* symbol length - 25μs 3 Type 1 Channel Access 0

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

[0122] 3) Non-backoff uplink grant for scheduling PUSCH transmissions (DCI format 0_1):

[0123] The higher-layer configuration includes an LBT parameter indication set, which contains at least one jointly coded channel access mode, CPE length, and CAPC. The non-backoff uplink grant includes LBT indication information, which is used to indicate the jointly coded channel access mode, CPE length, and CAPC from the aforementioned LBT parameter indication set. This channel access mode, CPE length, and CAPC are used for PUSCH transmission. If the indicated channel access mode is Type 2 channel access, the indicated CAPC is the CAPC used by the base station when obtaining the COT. The LBT indication information includes a maximum of 6 bits.

[0124] 4) Non-backoff downlink grant for scheduling PDSCH transmissions (DCI format 1_1):

[0125] The higher-layer configuration includes an LBT parameter indication set, which contains at least one jointly coded channel access mode and CPE length. The non-backoff downlink grant includes LBT indication information, which indicates the jointly coded channel access mode and CPE length from the aforementioned LBT parameter indication set. This channel access mode and CPE length are used for PUCCH transmission, where the PUCCH can carry ACK or NACK information corresponding to the PDSCH. If the channel access mode is Type 1 channel access, the UE determines the channel access priority CAPC for PUCCH transmission to be 1. The LBT indication information includes a maximum of 4 bits.

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

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

[0128] The frequency domain resource allocation for the side link is similar to that for Uu, such as... Figure 16As shown. When there are multiple carriers in the frequency domain, the terminal and system need to support carrier aggregation. Alternatively, the system can support only a single carrier scenario, in which case carrier aggregation is not required. A carrier's frequency resource can be divided into one or more Band Width Parts (BWPs). Currently, when multiple BWPs exist in the frequency domain, only one BWP can be active at a time. Furthermore, in the SL system, the system currently only supports one sideband bandwidth part (SL BWP). In the NR-U (Unlicensed Band) system, a BWP is divided into multiple RB sets, each RB set being 20MHz in size. An RB set serves as the smallest unit of the LBT (Local Band Adapter). For example, in... Figure 16 In this context, BWP 1 is divided into RB set 0 to RB set 4.

[0129] The above provides a brief explanation of the relevant technologies / terms involved in the embodiments of this application, which will not be repeated in the following embodiments.

[0130] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of this application can be implemented by pre-storing the corresponding code, table or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method.

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

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

[0133] With technological advancements, supporting multiple terminal devices with varying communication capabilities within the same communication system has become an unavoidable issue. If we continue to assume all terminals possess the same communication capabilities, it will create difficulties for less capable terminals (smartwatches, fitness trackers, AR / VR glasses, etc.). For example, less capable terminals typically cannot support bandwidths as large as those of mobile phones. A mobile phone might support 100MHz bandwidth, while a smartwatch communicating with it might only support a maximum of 5MHz or 20MHz. Consequently, in real-world communication scenarios, this mismatch in terminal capabilities (bandwidth) will lead to the following problems:

[0134] 1) When communicating between a fully capable terminal (such as a mobile phone) and a less capable terminal, if the communication bandwidth of the fully capable terminal is reduced in order to ensure the normal communication of the less capable terminal, it will lead to system bandwidth congestion and waste of bandwidth resources.

[0135] 2) If fully capable terminals still use full-bandwidth communication, then less capable terminals will not be able to participate. For example, if fully capable terminals send data via broadcast or multicast, a less capable terminal, as the receiver, will not be able to receive the data on the full bandwidth.

[0136] The SL synchronization process, a crucial component and step in the SL system, occurs prior to SL communication. Developing a solution for the synchronization process and the transmission / reception of S-SSBs to address communication issues between terminals with varying capabilities is highly efficient. This is because the synchronization process is simple, involves relatively little data transmission and reception, and consumes minimal resources. Therefore, operating the transmission / reception of S-SSBs on a smaller bandwidth allows for simultaneous support of terminal devices with different capabilities, ensuring synchronization across all devices. Subsequent communication processes, due to differences in service type and data volume, can be discussed separately from the solution presented in this application.

[0137] In view of this, this application provides a side-by-side synchronization method, apparatus, terminal, chip, and storage medium. The method can be executed by the terminal, or by a chip, chip system, or circuit configured in the terminal; the embodiments of this application do not limit this. For ease of description, the following explanation uses execution by the terminal as an example.

[0138] In this method, the terminal can transmit or receive S-SSBs on a first frequency domain resource, which is a portion of the system's frequency domain resources. By using a portion of the system's frequency domain resources for S-SSB transmission or reception, this method allows S-SSB transmission or reception to occur within a relatively small bandwidth, thus accommodating terminals with different capabilities within the same communication system and ensuring that all terminals can achieve synchronization.

[0139] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0140] Figure 17 This is a flowchart illustrating the side-by-side synchronization method provided in an embodiment of this application. For example... Figure 17 As shown, the side-line synchronization method may include the following steps:

[0141] S1701, the terminal transmits or receives S-SSB on the first frequency domain resource; wherein, the first frequency domain resource is a portion of the system frequency domain resources.

[0142] The first frequency domain resource can be determined, for example, through definition, pre-configuration, or network configuration. This first frequency domain resource can serve as a common frequency domain resource among different terminals in the communication system for the transmission or reception of S-SSBs. In other words, each terminal must transmit or receive S-SSBs on at least the first frequency domain resource.

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

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

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

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

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

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

[0149] As an example, when multiple (e.g., N) S-SSB frequency domain resources are consecutively distributed, the frequency domain positions of these multiple S-SSB frequency domain resources can be determined based on the starting position of the first S-SSB frequency domain resource and the total length of the multiple S-SSB frequency domain resources. In other words, given the starting position of the first S-SSB frequency domain resource and the total length of all S-SSB frequency domain resources, the frequency domain positions of the multiple consecutively distributed S-SSB frequency domain resources can be determined.

[0150] As another example, when the multiple (e.g., N) S-SSB frequency domain resources are not discontinuously distributed, the frequency domain positions of these multiple S-SSB frequency domain resources can be determined based on the starting position and length of each S-SSB frequency domain resource. That is, if the starting position and length of each S-SSB frequency domain resource are determined, the frequency domain positions of the multiple discontinuously distributed S-SSB frequency domain resources can be determined.

[0151] As another example, when multiple (e.g., N) S-SSB frequency domain resources are not discontinuously distributed, the frequency domain positions of these multiple S-SSB frequency domain resources can be determined based on the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval between two adjacent S-SSB frequency domain resources. That is, once the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval between two adjacent S-SSB frequency domain resources are determined, the frequency domain positions of the multiple discontinuously distributed S-SSB frequency domain resources can be determined. The total length of the multiple S-SSB frequency domain resources can refer to the length between the starting position of the first S-SSB frequency domain resource and the ending position of the last S-SSB frequency domain resource, or it can refer to the sum of the lengths of each individual S-SSB frequency domain resource.

[0152] For example, the interval between two adjacent S-SSB frequency domain resources can be indicated by the number of sub-channels or resource blocks between them. For instance, an interval of G between two adjacent S-SSB frequency domain resources can indicate that the interval is G sub-channels or G resource blocks. Here, G is an integer greater than or equal to 0. For example, when G > 0, it indicates that the interval between two adjacent S-SSB frequency domain resources is G sub-channels or G resource blocks; when G = 0, it indicates that there is no interval or the interval is 0 between two adjacent S-SSB frequency domain resources, meaning that the two adjacent S-SSB frequency domain resources are continuous in the frequency domain.

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

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

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

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

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

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

[0159] For example, assuming this sub-bandwidth includes sub-bandwidth #1, then the frequency domain resources for transmitting S-SSBs in sub-bandwidth #1 may include all or part of the S-SSB frequency domain resources in sub-bandwidth #1. When the frequency domain resources for transmitting S-SSBs include all the S-SSB frequency domain resources in sub-bandwidth #1, it means that the terminal needs to fully utilize all the S-SSB frequency domain resources in sub-bandwidth #1 for S-SSB transmission; when the frequency domain resources for transmitting S-SSBs include part of the S-SSB frequency domain resources in sub-bandwidth #1, it means that the terminal does not need to fully utilize all the S-SSB frequency domain resources in sub-bandwidth #1 for S-SSB transmission.

[0160] As an example, whether a terminal needs to fully utilize all S-SSB frequency domain resources in the sub-bandwidth for S-SSB transmission can be determined based on network configuration. For instance, when the network configuration requires the terminal to fully utilize all S-SSB frequency domain resources in the sub-bandwidth for S-SSB transmission, the terminal can transmit S-SSBs on all S-SSB frequency domain resources in the sub-bandwidth based on the network configuration. As another example, the terminal can independently determine whether to fully utilize all S-SSB frequency domain resources in the sub-bandwidth for S-SSB transmission. For instance, when the terminal's capabilities support its ability to fully utilize all S-SSB frequency domain resources in the sub-bandwidth for S-SSB transmission, the terminal can transmit S-SSBs on all S-SSB frequency domain resources in the sub-bandwidth. As yet another example, the sending terminal can also determine whether to fully utilize all S-SSB frequency domain resources in the sub-bandwidth for S-SSB transmission based on instructions from other terminals in the communication system. For example, a weak terminal in a communication system can instruct the sending terminal to occupy all S-SSB frequency domain resources in the sub-bandwidth to transmit S-SSBs, thereby simplifying the complexity of the weak terminal when detecting S-SSBs. In this case, the sending terminal can transmit S-SSBs on all S-SSB frequency domain resources in the sub-bandwidth.

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

[0162] In other words, when a terminal transmits S-SSB on this sub-bandwidth, the sub-bandwidths within this sub-bandwidth can be adjacent in the frequency domain. This results in a relatively uniform distribution of frequency domain resources for S-SSB transmission, and a relatively uniform transmission power in the frequency domain, thus helping to avoid impacting communication performance. In some embodiments, the sub-bandwidths within this sub-bandwidth can also be non-adjacent in the frequency domain, or they can be partially adjacent and partially non-adjacent.

[0163] In some embodiments, the frequency domain location and / or number of S-SSB frequency domain resources contained in each sub-bandwidth of the sub-bandwidth containing S-SSB frequency domain resources are pre-configured or network-configured.

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

[0165] As an example, in a sub-bandwidth containing S-SSB frequency domain resources (e.g., in the K2 sub-bandwidths mentioned above), when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position of the first S-SSB frequency domain resource in that sub-bandwidth and the total length of the S-SSB frequency domain resources in that sub-bandwidth. In other words, if the starting position of the first S-SSB frequency domain resource in a sub-bandwidth and the total length of all S-SSB frequency domain resources in that sub-bandwidth are determined, the frequency domain position of the continuously distributed S-SSB frequency domain resources in that sub-bandwidth can be determined.

[0166] As another example, in a sub-bandwidth containing S-SSB frequency domain resources (e.g., in the K2 sub-bandwidths mentioned above), when the S-SSB frequency domain resources are not discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in that sub-bandwidth. In other words, if the starting position and length of each S-SSB frequency domain resource in a certain sub-bandwidth are determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in that sub-bandwidth can be determined.

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

[0168] For example, the interval between two adjacent S-SSB frequency domain resources can be indicated by the number of sub-channels or resource blocks between them. For instance, an interval of G between two adjacent S-SSB frequency domain resources can refer to an interval of G sub-channels or G resource blocks. Here, G is an integer greater than or equal to 0.

[0169] In some embodiments, in a sub-bandwidth containing S-SSB frequency domain resources (e.g., in the K2 sub-bandwidths mentioned above), the frequency domain location of the S-SSB frequency domain resources contained in each sub-bandwidth may be independently configured or pre-configured.

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

[0171] In some embodiments, the aforementioned sub-bandwidth may be a set of resource blocks (RBs), a channel, a frequency range, or a resource pool (frequency domain resource pool). Alternatively, the sub-bandwidth in the embodiments of this application may also be referred to as (or replaced by) a set of resource blocks, a channel, a frequency range, or a resource pool.

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

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

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

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

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

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

[0178] As one example, whether a terminal needs to fully utilize all S-SSB frequency domain resources in the SL BWP for S-SSB transmission can be determined based on network configuration. As another example, the terminal can autonomously determine whether to fully utilize all S-SSB frequency domain resources in the SL BWP for S-SSB transmission. As yet another example, the sending terminal can also determine whether to fully utilize all S-SSB frequency domain resources in the SL BWP for S-SSB transmission based on instructions from other terminals in the communication system. For instance, a weakly capable terminal in the communication system can instruct the sending terminal to fully utilize all S-SSB frequency domain resources in the SL BWP for S-SSB transmission to simplify the complexity of S-SSB detection for that weakly capable terminal. In this case, the sending terminal can transmit S-SSBs on all S-SSB frequency domain resources in the SL BWP.

[0179] In some embodiments, each SL BWP in the portion of SL BWPs (such as the X1 SL BWPs described above) is adjacent in the frequency domain; or, each SL BWP in the portion of SL BWPs is not adjacent in the frequency domain; or, some of the SL BWPs in the portion of SL BWPs are adjacent in the frequency domain.

[0180] In other words, when a terminal transmits an S-SSB on this portion of SL BWPs, the individual SL BWPs within this portion of SL BWPs can be adjacent in the frequency domain. This results in a relatively uniform distribution of frequency domain resources for S-SSB transmission, and a relatively uniform transmission power in the frequency domain, thus helping to avoid impacting communication performance. In some embodiments, the individual SL BWPs within this portion of SL BWPs can also be non-adjacent in the frequency domain, or they can be partially adjacent and partially non-adjacent.

[0181] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources contained in each SL BWP are pre-configured or network-configured.

[0182] For example, suppose that among the X SL BWPs mentioned above, X2 SL BWPs contain (are configured with) S-SSB frequency domain resources. In this scenario, the frequency domain location and / or quantity of the S-SSB frequency domain resources contained in each of the X2 SL BWPs can be pre-configured or network-configured.

[0183] As an example, in a single-level bounding window (SL BWP) containing S-SSB frequency domain resources (e.g., in the aforementioned X2 SL BWPs), when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in that SL BWP and the total length of the S-SSB frequency domain resources in that SL BWP. In other words, given 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 in that SL BWP, the frequency domain position of the continuously distributed S-SSB frequency domain resources in that SL BWP can be determined.

[0184] As another example, in an SL BWP containing S-SSB frequency domain resources (e.g., in the aforementioned X2 SL BWPs), when the S-SSB frequency domain resources are not discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position and length of each S-SSB frequency domain resource in that SL BWP. In other words, if the starting position and length of each S-SSB frequency domain resource in a given SL BWP are determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in that SL BWP can be determined.

[0185] As another example, in an SL BWP containing S-SSB frequency domain resources (e.g., in the aforementioned X2 SL BWPs), when the S-SSB frequency domain resources are not discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in that SL BWP, the total length of the S-SSB frequency domain resources in that SL BWP, and the interval between two adjacent S-SSB frequency domain resources in that SL BWP. In other words, given 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 that SL BWP, and the interval between two adjacent S-SSB frequency domain resources in that SL BWP, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in that SL BWP can be determined. The total length of the S-SSB frequency domain resources in the SL BWP can refer to the length between the starting position of the first S-SSB frequency domain resource and the ending position of the last S-SSB frequency domain resource in the SL BWP, or it can refer to the sum of the lengths of each S-SSB frequency domain resource in the SL BWP.

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

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

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

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

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

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

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

[0193] For example, assuming this portion of the carrier includes carrier #1, then the frequency domain resources for transmitting S-SSBs in carrier #1 may include all or part of the S-SSB frequency domain resources in carrier #1. When the frequency domain resources for transmitting S-SSBs include all the S-SSB frequency domain resources in carrier #1, it means that the terminal needs to occupy all the S-SSB frequency domain resources in carrier #1 for S-SSB transmission; when the frequency domain resources for transmitting S-SSBs include part of the S-SSB frequency domain resources in carrier #1, it means that the terminal does not need to occupy all the S-SSB frequency domain resources in carrier #1 for S-SSB transmission.

[0194] As one example, whether a terminal needs to occupy all S-SSB frequency domain resources in the carrier for S-SSB transmission can be determined based on network configuration. As another example, the terminal can also autonomously determine whether to occupy all S-SSB frequency domain resources in the carrier for S-SSB transmission. As yet another example, the transmitting terminal can also determine whether to occupy all S-SSB frequency domain resources in the carrier for S-SSB transmission based on instructions from other terminals in the communication system. For instance, a weakly capable terminal in the communication system can instruct the transmitting terminal to occupy all S-SSB frequency domain resources in the carrier for S-SSB transmission, simplifying the complexity of S-SSB detection for that weakly capable terminal. In this case, the transmitting terminal can transmit S-SSBs on all S-SSB frequency domain resources in the carrier.

[0195] In some embodiments, each carrier in the partial carrier (such as the Y1 carriers described above) is adjacent in the frequency domain; or, each carrier in the partial carrier is not adjacent in the frequency domain; or, some of the carriers in the partial carrier are adjacent in the frequency domain.

[0196] In other words, when a terminal transmits S-SSB on this portion of carriers, the carriers within this portion of carriers can be adjacent in the frequency domain. This results in a relatively uniform distribution of frequency domain resources for transmitting S-SSBs, and a relatively uniform transmission power in the frequency domain, which helps to avoid impacting communication performance. In some embodiments, the carriers within this portion of carriers can also be non-adjacent in the frequency domain, or they can be partially adjacent and partially non-adjacent.

[0197] 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 contained in each carrier are pre-configured or network-configured.

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

[0199] As an example, in a carrier containing S-SSB frequency domain resources (e.g., in the Y2 carriers mentioned above), when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each carrier is determined based on the starting position of the first S-SSB frequency domain resource in that carrier and the total length of the S-SSB frequency domain resources in that carrier. In other words, given the starting position of the first S-SSB frequency domain resource in a carrier and the total length of all S-SSB frequency domain resources in that carrier, the frequency domain position of the continuously distributed S-SSB frequency domain resources in that carrier can be determined.

[0200] As another example, in carriers containing S-SSB frequency domain resources (e.g., in the Y2 carriers mentioned above), when the S-SSB frequency domain resources are not discontinuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each carrier is determined based on the starting position and length of each S-SSB frequency domain resource in that carrier. In other words, if the starting position and length of each S-SSB frequency domain resource in a certain carrier are determined, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in that carrier can be determined.

[0201] As another example, in carriers containing S-SSB frequency domain resources (e.g., in the Y2 carriers mentioned above), when the S-SSB frequency domain resources are not discontinuously 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 that carrier, the total length of the S-SSB frequency domain resources in that carrier, and the interval between two adjacent S-SSB frequency domain resources in that carrier. That is, given 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 that carrier, and the interval between two adjacent S-SSB frequency domain resources in that carrier, the frequency domain position of each discontinuously distributed S-SSB frequency domain resource in that carrier can be determined. The total length of the S-SSB frequency domain resources in that carrier can refer to the length between the starting position of the first S-SSB frequency domain resource and the ending position of the last S-SSB frequency domain resource in that carrier, or it can refer to the sum of the lengths of each S-SSB frequency domain resource in that carrier.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0216] According to the method of this embodiment, on the one hand, the terminal uses a portion of the system's frequency domain resources to transmit or receive S-SSBs, enabling the transmission or reception of S-SSBs to be performed on a relatively small bandwidth. This allows for the consideration of terminals with different capabilities within the same communication system, ensuring that all terminals in the communication system can achieve synchronization. On the other hand, in addition to defining, pre-configuring, or network-configuring common frequency domain resources (first frequency domain resources) for transmitting / receiving S-SSBs, additional frequency domain resources (second frequency domain resources) for transmitting / receiving S-SSBs can also be defined, pre-configured, or network-configured as a supplement to prevent LBT failures of certain frequency band resources from causing the terminal to be unable to transmit S-SSBs.

[0217] The above text combined Figure 17 This application introduces a side-to-side synchronization method provided in its embodiments. To facilitate understanding of the embodiments of this application, several possible implementation schemes applicable to the side-to-side synchronization method in the embodiments of this application are described below.

[0218] As an example, frequency domain resource design schemes for S-SSB may include:

[0219] Option 1: A single SL BWP contains N (N is greater than or equal to 1) S-SSB frequency domain resources.

[0220] Option 2: An SL BWP contains K (K is greater than or equal to 1) sub-bandwidths, and at least one of these K sub-bandwidths contains M (M is greater than or equal to 1) S-SSB frequency domain resources.

[0221] For example, the aforementioned sub-bandwidth can also be referred to as (defined as) an RB set, a channel, a frequency range (FR), or a resource pool (frequency domain resource pool).

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

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

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

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

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

[0227] For example, the aforementioned carrier can be a scenario considering carrier aggregation. Here, "carrier" can also be referred to as "subcarrier" or "carrier component".

[0228] It should be noted that the configuration methods of S-SSB frequency domain resources in Schemes 1 to 4 above may include, for example, configuring S-SSB frequency domain resources by the network, or configuring S-SSB frequency domain resources through pre-configuration.

[0229] The configuration of the aforementioned N / M / L / U S-SSB frequency domain resources may include the configuration of the location and number (i.e., N / M / L / U) of the N / M / L / U S-SSB frequency domain resources.

[0230] For example, the location of S-SSB frequency domain resources can be indicated, for instance, by means of method 1, method 2, or method 3:

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

[0232] Method 2: When multiple S-SSB frequency domain resources are not discontinuously distributed, the starting position and length of each S-SSB frequency domain resource can be indicated. That is, based on the starting position and length of each S-SSB frequency domain resource, the location of the multiple discontinuously distributed S-SSB frequency domain resources can be determined.

[0233] Method 3: When multiple S-SSB frequency domain resources are not discontinuously distributed, the starting position of the first S-SSB frequency domain resource, the total length of the multiple S-SSB frequency domain resources, and the interval G between two adjacent S-SSB frequency domain resources 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.

[0234] For example, the aforementioned interval G can refer to an interval of G sub-channels, or it can refer to an interval of G resource blocks. Here, G is an integer greater than or equal to 0. For instance, when G > 0, it indicates that the interval between two adjacent S-SSB frequency domain resources is G sub-channels or G resource blocks; when G = 0, it indicates that there is no interval or the interval is 0 between two adjacent S-SSB frequency domain resources, meaning that the two adjacent S-SSB frequency domain resources are continuous in the frequency domain.

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

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

[0237] Sending method 1:

[0238] This transmission method can be applied, for example, to the frequency domain resource design scheme in Scheme 1 above.

[0239] For example, for the N S-SSB frequency domain resources in Scheme 1, the terminal can transmit S-SSB on at least one of the S-SSB frequency domain resources. For instance, among the N S-SSB frequency domain resources, N1 (1≤N1≤N) S-SSB frequency domain resources must transmit S-SSB, that is, the terminal must transmit S-SSB on at least N1 S-SSB frequency domain resources.

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

[0241] Sending method 2:

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

[0243] For example, for the K sub-bandwidths included in the SL BWP in Scheme 2, the terminal may transmit at least one S-SSB on at least one of the sub-bandwidths. For instance, among the K sub-bandwidths of the SL BWP, K1 (1≤K1≤K) sub-bandwidths must transmit S-SSBs, that is, the terminal must transmit S-SSBs on at least K1 sub-bandwidths.

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

[0245] As another implementation, the terminal can fully utilize all S-SSB frequency domain resources in each of the K1 sub-bandwidths for S-SSB transmission. For example, assuming that each of the K1 sub-bandwidths contains y1 S-SSB frequency domain resources, then the terminal needs to fully utilize y1 S-SSB frequency domain resources in each sub-bandwidth for S-SSB transmission.

[0246] As another implementation, the terminal can fully utilize all S-SSB frequency domain resources in a portion of the K1 sub-bandwidths to transmit S-SSBs, while in another portion of the sub-bandwidths, it does not need to fully utilize all S-SSB frequency domain resources to transmit S-SSBs.

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

[0248] For example, when a terminal transmits S-SSBs on multiple sub-bandwidths, these sub-bandwidths can be adjacent in the frequency domain. This results in a relatively uniform distribution of frequency domain resources for transmitting S-SSBs, and a relatively uniform transmission power in the frequency domain, which helps to avoid impacting communication performance. In some embodiments, the multiple sub-bandwidths for transmitting S-SSBs can also be non-adjacent in the frequency domain, or they can be partially adjacent and partially non-adjacent.

[0249] Sending method 3:

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

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

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

[0253] As another implementation, the terminal can occupy all S-SSB frequency domain resources on each of the X1 SL BWPs for S-SSB transmission. For example, assuming that each of the X1 SL BWPs contains y2 S-SSB frequency domain resources, then the terminal needs to occupy y2 S-SSB frequency domain resources of each SL BWP for S-SSB transmission.

[0254] As another implementation, the terminal can use all the S-SSB frequency domain resources on some of the X1 SL BWPs to transmit S-SSBs, while it can transmit S-SSBs on other SL BWPs without using all the S-SSB frequency domain resources.

[0255] 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.

[0256] For example, when a terminal transmits S-SSB on multiple SL BWPs, these multiple SL BWPs can be adjacent in the frequency domain. In this way, the frequency domain resources for transmitting S-SSBs are relatively evenly distributed, and the transmission power in the frequency domain is also relatively even, which helps to avoid impacting communication performance. In some embodiments, the multiple SL BWPs transmitting S-SSBs can also be non-adjacent in the frequency domain, or they can be partially adjacent and partially non-adjacent.

[0257] Sending method 4:

[0258] This transmission method can be applied, for example, to the frequency domain resource design scheme in Scheme 4 above.

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

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

[0261] As another implementation, the terminal can occupy all S-SSB frequency domain resources on each of the Y1 carriers to transmit S-SSBs. For example, assuming that each of the Y1 carriers contains y3 S-SSB frequency domain resources, then the terminal needs to occupy y3 S-SSB frequency domain resources on each carrier to transmit S-SSBs.

[0262] As another implementation, the terminal can occupy all S-SSB frequency domain resources on some of the Y1 carriers to transmit S-SSB, while it does not need to occupy all S-SSB frequency domain resources on the other carriers to transmit S-SSB.

[0263] 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.

[0264] For example, when a terminal transmits S-SSB on multiple carriers, these multiple carriers can be adjacent in the frequency domain. In this way, the frequency domain resources for transmitting S-SSB are relatively evenly distributed, and the transmission power in the frequency domain is also relatively even, which helps to avoid impacting communication performance. In some embodiments, the multiple carriers transmitting S-SSB can also be non-adjacent in the frequency domain, or they can be partially adjacent and partially non-adjacent.

[0265] It should be noted that the S-SSB frequency domain resources mentioned in transmission methods 1 to 4 that must be transmitted for S-SSB can also be understood as the frequency domain resources for transmitting S-SSB by default / mandatory.

[0266] It should also be noted that the terminals in the above-mentioned transmission methods 1 to 4 can be either type 1 terminals or type 2 terminals.

[0267] The first type of terminal refers to terminals with full capabilities, or terminals with strong or high capabilities, such as mobile phones. The second type of terminal refers to terminals with weak capabilities, such as smartwatches, fitness trackers, and AR / VR glasses. Typically, the second type of terminal supports relatively small bandwidth for sending / receiving information; in other words, it can support sending / receiving information on a sub-bandwidth, but not on the full bandwidth. Furthermore, in some scenarios, the second type of terminal also has lower transmission power, and its encoding / decoding capabilities may also be limited.

[0268] When the terminal sending S-SSBs is a Type 1 terminal, it must send S-SSBs at the default / mandatory frequency domain resource location. Additionally, in some scenarios, this type of terminal can also send S-SSBs on other frequency domain resources. When the terminal sending S-SSBs is a Type 2 terminal, it can send S-SSBs only at the default / mandatory S-SSB frequency domain resource location; it is not required to send S-SSBs on other frequency domain resources. In some scenarios, if a Type 2 terminal has the capability to send S-SSBs on other frequency domain resources, then it can also send S-SSBs on frequency domain resources other than the default / mandatory S-SSB frequency domain resources.

[0269] In one possible approach, the frequency domain resources for the aforementioned default / mandatory S-SSB transmission can be determined, for example, through definition, configuration, or pre-configuration. These default / mandatory S-SSB frequency domain resources can be used as common frequency domain resources for S-SSB transmission. These common frequency domain resources include, but are not limited to, at least one continuous frequency band in the frequency domain, at least one sub-bandwidth (e.g., K1 sub-bandwidths in transmission mode 2), at least one continuous frequency domain resource within an SL BWP, at least one resource pool, at least one SL BWP (e.g., X1 SL BWPs in transmission mode 3), or at least one carrier (e.g., Y1 carriers in transmission mode 4).

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

[0271] Receiving method 1:

[0272] Corresponding to transmission method 1, this receiving method can be applied, for example, to the frequency domain resource design scheme in Scheme 1 above.

[0273] For example, the terminal can detect / receive S-SSBs at N1 S-SSB frequency domain resource locations (default / mandatory frequency domain resource locations) in transmission mode 1. In some embodiments, the terminal can also detect / receive S-SSBs at other frequency domain resource locations.

[0274] Receiving method 2:

[0275] Corresponding to transmission method 2, this receiving method can be applied, for example, to the frequency domain resource design scheme in Scheme 2 above.

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

[0277] Receiving method 3:

[0278] Corresponding to transmission method 3, this receiving method can be applied, for example, to the frequency domain resource design scheme in Scheme 3 above.

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

[0280] Receiving method 4:

[0281] Corresponding to transmission method 4, this receiving method can be applied, for example, to the frequency domain resource design scheme in scheme 4 above.

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

[0283] It should be noted that the terminals in receiving methods 1 to 4 described above can be either type 1 or type 2 terminals. When the terminal receiving S-SSB is a type 1 or type 2 terminal, it must detect / receive S-SSB at least in the default / mandatory frequency domain resource locations. When the terminal receiving S-SSB is a type 1 terminal, it has full capability and can therefore detect / receive S-SSB in additional frequency domain resource locations. In some scenarios, if a type 2 terminal has the capability to detect / receive S-SSB in other frequency domain resource locations, then the type 2 terminal can also detect / receive S-SSB in frequency domain resource locations other than the default / mandatory frequency domain resources.

[0284] To facilitate understanding, the following will be combined with Figure 18 and Figure 19 This paper introduces a possible implementation flow of the side-line synchronization method applicable to the implementation of this application.

[0285] Figure 18 Figure (a) in the figure is a schematic diagram of a frequency domain resource design scheme for an S-SSB provided in an embodiment of this application. Figure 18 As shown in Figure (a), the system supports one BWP (SL BWP) and multiple S-SSB transmission resources in the frequency domain. Alternatively, the system's frequency domain resources can include multiple S-SSB frequency domain resources within a single BWP. The spacing between these multiple S-SSB frequency domain resources can be defined through configuration / pre-configuration.

[0286] by Figure 18Taking Figure (a) as an example, the system frequency domain resources may include three S-SSB frequency domain resources in a BWP. One or more of these three S-SSB frequency domain resources can be used as default / mandatory frequency domain resources. That is, the transmitting terminal must transmit S-SSBs on at least one or more of these frequency domain resources, and the receiving terminal must receive S-SSBs on at least one or more of these frequency domain resources.

[0287] For example, if a terminal is a Type 1 terminal, then the terminal is capable of transmitting S-SSBs on frequency domain resources other than the default / mandatory frequency domain resources. For instance, the terminal can transmit S-SSBs on all S-SSB frequency domain resources. If a terminal is a Type 2 terminal, then the terminal must transmit S-SSBs on at least the default / mandatory S-SSB resources. For instance, the terminal can transmit S-SSBs only on the default / mandatory resources.

[0288] For example, if a terminal is a Type 1 terminal, then the terminal is capable of receiving S-SSBs on frequency domain resources other than the default / mandatory frequency domain resources. For instance, the terminal can receive S-SSBs on all S-SSB frequency domain resources. If a terminal is a Type 2 terminal, then the terminal needs to receive S-SSBs on at least the default / mandatory frequency domain resources. For instance, the terminal can receive S-SSBs only on the default / mandatory resources.

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

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

[0291] In some scenarios, BWP#1 can serve as an additional frequency domain resource. In this scenario, Type I terminals can choose whether to transmit S-SSBs on BWP#1, and / or how much S-SSB frequency domain resource to occupy for transmitting S-SSBs. Type II terminals, due to capability limitations, are typically unable to transmit / receive S-SSBs on BWP#1.

[0292] Figure 18 Figure (c) in the diagram is a schematic diagram of another S-SSB frequency domain resource design scheme provided in an embodiment of this application. Figure 18As shown in Figure (c), the system is configured to support 2 BWPs (SL BWP).

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

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

[0295] Figure 19 This is a schematic diagram of another S-SSB frequency domain resource design scheme provided in the embodiments of this application.

[0296] exist Figure 19 In this example, the entire frequency domain resources can be divided into multiple sub-bandwidths, or in other words, the system frequency domain resources can include multiple sub-bandwidths within a single SL BWP. These multiple sub-bandwidths can be, for example, multiple frequency ranges, multiple resource pools, multiple RB sets, or multiple channels.

[0297] As an example, these multiple sub-bandwidths can be multiple frequency ranges, such as... Figure 19 The frequency range is from #0 to #2. These frequency ranges may or may not overlap.

[0298] Another example is that the multiple sub-bandwidths can be multiple resource pools, such as... Figure 19 Resource pools #0 to #2 are included. These resource pools may or may not overlap.

[0299] Another example is that these multiple sub-bandwidths can be multiple sets of RBs, such as... Figure 19 The RB sets are #0 to #2. There is no overlap between the RB sets. In some embodiments, a protection interval can also be configured between two adjacent RB sets.

[0300] Another example is that these multiple sub-bandwidths can be multiple channels ( Figure 19 (Not shown in the diagram), and there is no overlap between the channels.

[0301] In some scenarios, sub-bandwidth #1 (such as frequency range #1, resource pool #1, or RB set #1) can serve as a default / mandatory frequency domain resource (default / mandatory frequency band), or in other words, as a common frequency domain resource. In this scenario, the terminal must at least transmit / receive S-SSB within sub-bandwidth #1.

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

[0303] Understandably, in Figure 19 In the example shown, sub-bandwidth #2 (such as frequency range #2, resource pool #2, or RB set #2) does not contain S-SSB frequency domain resources, so no terminal will send / receive S-SSB on sub-bandwidth #2.

[0304] This application presents a method for designing frequency domain resources for sidelink synchronization signals. In this method, to support communication and coexistence between terminals with different capabilities within the same system, and to ensure the completion of the sidelink synchronization process, a small frequency band resource (frequency domain resource) can be defined / configured in the frequency domain for transmitting / receiving S-SSBs. This small frequency band resource can be used as a common frequency domain resource dedicated to transmitting system messages such as synchronization, thus primarily ensuring synchronization among all terminals in the sidelink. Furthermore, this method supports additional frequency band resources for transmitting additional S-SSBs, which can supplement the synchronization signal transmission / reception between fully capable terminals. In some embodiments, for less capable terminals, the synchronization process and service data communication process can be performed on different frequency band resources through BWP handover, thereby utilizing frequency domain resources more efficiently.

[0305] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0306] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0307] Based on the foregoing embodiments, this application provides a corresponding side-tracking synchronization device.

[0308] Figure 20 This is a schematic diagram of the structural composition of the side-link synchronization device provided in an embodiment of this application, which is applied to a terminal. For example... Figure 20 As shown, the side-track synchronization device 2000 includes:

[0309] The transceiver unit 2000 is used to transmit or receive side-link synchronization signal blocks S-SSB on the first frequency domain resource; wherein, the first frequency domain resource is a portion of the system frequency domain resource.

[0310] In some embodiments, the system frequency domain resources include a plurality of S-SSB frequency domain resources in a sideband 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.

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

[0312] In some embodiments, when the plurality of S-SSB frequency domain resources are continuously distributed, the frequency domain position of the plurality of S-SSB frequency domain resources is 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 not continuously distributed, 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, it is 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 interval between two adjacent S-SSB frequency domain resources.

[0313] In some embodiments, the number of the plurality of S-SSB frequency domain resources is: the number of times an S-SSB is repeated in the SL BWP.

[0314] In some embodiments, the system frequency domain resources include multiple sub-bandwidths in an SL BWP, at least one of the multiple sub-bandwidths containing S-SSB frequency domain resources; the first frequency domain resource is a portion of the multiple sub-bandwidths, the portion of the sub-bandwidth containing S-SSB frequency domain resources.

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

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

[0317] In some embodiments, the frequency domain location and / or number of S-SSB frequency domain resources contained in each sub-bandwidth of the sub-bandwidth containing S-SSB frequency domain resources are pre-configured or network-configured.

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

[0319] In some embodiments, in a sub-bandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each sub-bandwidth is: the number of times an S-SSB is repeated within that sub-bandwidth; wherein, the number of S-SSB frequency domain resources contained in different sub-bandwidths may be the same or different.

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

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

[0322] In some embodiments, the system frequency domain resources include a plurality of SL BWPs, at least one of which contains S-SSB frequency domain resources; the first frequency domain resources are a portion of the plurality of SL BWPs, which contain S-SSB frequency domain resources.

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

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

[0325] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources contained in each SL BWP are pre-configured or network-configured.

[0326] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, when the S-SSB frequency domain resources are continuously distributed, the frequency domain position of the S-SSB frequency domain resources contained in each SL BWP is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP and the total length of the S-SSB frequency domain resources in the SL BWP; when the S-SSB frequency domain resources are not 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 and length of each S-SSB frequency domain resource in the SL BWP; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the SL BWP, the total length of the S-SSB frequency domain resources in the SL BWP, and the interval between two adjacent S-SSB frequency domain resources in the SL BWP.

[0327] In some embodiments, in an SL BWP containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each SL BWP is: the number of times an S-SSB is repeated within that SL BWP; wherein, different SL BWPs may contain the same or different numbers of S-SSB frequency domain resources.

[0328] In some embodiments, the system frequency domain resources include a plurality of carriers, at least one of which contains S-SSB frequency domain resources; the first frequency domain resources are a portion of the plurality of carriers, which contain S-SSB frequency domain resources.

[0329] In some embodiments, for each of the carriers in the subset, the frequency domain resources for transmitting S-SSBs include: all or part of the S-SSB frequency domain resources in that carrier.

[0330] In some embodiments, the carriers in the partial carrier are adjacent in the frequency domain; or, the carriers in the partial carrier are not adjacent in the frequency domain; or, a portion of the carriers in the partial carrier are adjacent in the frequency domain.

[0331] 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 contained in each carrier are pre-configured or network-configured.

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

[0333] In some embodiments, in a carrier containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each carrier is: the number of times an S-SSB is repeated in that carrier; wherein, different carriers may contain the same or different numbers of S-SSB frequency domain resources.

[0334] In some embodiments, the system frequency domain resources further include second frequency domain resources, which are frequency domain resources other than the first frequency domain resources in the system frequency domain resources; the second frequency domain resources are used to transmit or receive service data.

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

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

[0337] Those skilled in the art should understand that the description of the side synchronization device in the embodiments of this application can be understood with reference to the description of the side synchronization method in the embodiments of this application.

[0338] Figure 21 This is a schematic structural diagram of a communication device 2100 provided in an embodiment of this application. Figure 21 The communication device 2100 shown includes a processor 2110, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0339] Optionally, such as Figure 21 As shown, the communication device 2100 may further include a memory 2120. The processor 2110 can retrieve and run computer programs from the memory 2120 to implement the methods described in this embodiment.

[0340] The memory 2120 can be a separate device independent of the processor 2110, or it can be integrated into the processor 2110.

[0341] Optionally, such as Figure 21 As shown, the communication device 2100 may also include a transceiver 2130, and the processor 2110 may control the transceiver 2130 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

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

[0343] The communication device 2100 may specifically be a terminal in the embodiments of this application, and the communication device 2100 may implement the corresponding processes implemented by the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0344] Figure 22 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 22 The chip 2200 shown includes a processor 2210, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0345] Optionally, such as Figure 22 As shown, chip 2200 may further include memory 2220. Processor 2210 can retrieve and run computer programs from memory 2220 to implement the methods described in this embodiment.

[0346] The memory 2220 can be a separate device independent of the processor 2210, or it can be integrated into the processor 2210.

[0347] Optionally, the chip 2200 may also include an input interface 2230. The processor 2210 can control the input interface 2230 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

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

[0349] This chip can be applied to the terminal in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0350] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0351] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0352] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can 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 can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0353] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0354] This application also provides a computer-readable storage medium for storing a computer program. This computer-readable storage medium can be applied to the terminal in this application embodiment, and the computer program causes the computer to execute the corresponding processes implemented by the terminal in the various methods of this application embodiment; for brevity, further details are omitted here.

[0355] This application also provides a computer program product, including computer program instructions. This computer program product can be applied to the terminal in this application embodiment, and the computer program instructions cause the computer to execute the corresponding processes implemented by the terminal in the various methods of this application embodiment; for brevity, further details are omitted here.

[0356] This application also provides a computer program. This computer program can be applied to the terminal in this application's embodiments. When the computer program runs on a computer, it causes the computer to execute the corresponding processes implemented by the terminal in the various methods of this application's embodiments. For simplicity, these will not be elaborated further here.

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

[0358] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0359] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0361] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0362] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0363] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A side-by-side synchronization method, applied to a terminal, the method comprising: Transmit or receive a link synchronization signal block S-SSB on a first frequency domain resource; wherein, the first frequency domain resource is part or all of the frequency domain resources in the system frequency domain resources.

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

3. The method according to claim 2, wherein, For each of the sub-bandwidths, the frequency domain resources for transmitting the S-SSB include: all S-SSB frequency domain resources in the sub-bandwidth.

4. The method according to claim 2 or 3, wherein, In a sub-bandwidth containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources contained in each sub-bandwidth are pre-configured or network-configured.

5. The method according to claim 2 or 3, wherein, In a sub-bandwidth containing S-SSB frequency domain resources, where the S-SSB frequency domain resources are not distributed discontinuously, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in the sub-bandwidth; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth and the interval between two adjacent S-SSB frequency domain resources in the sub-bandwidth.

6. The method according to claim 2 or 3, wherein, In a sub-bandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each sub-bandwidth is: the number of times an S-SSB is repeated within the sub-bandwidth; wherein, the number of S-SSB frequency domain resources contained in different sub-bandwidths may be the same or different.

7. The method according to claim 2 or 3, wherein, The sub-bandwidth is a set of resource blocks.

8. A lateral synchronization device, the device comprising: The transceiver unit is used to transmit or receive side-link synchronization signal blocks S-SSB on a first frequency domain resource; wherein, the first frequency domain resource is part or all of the frequency domain resources in the system frequency domain resources.

9. The apparatus according to claim 8, wherein, The system frequency domain resources include multiple sub-bandwidths in an SL BWP, and at least one of the multiple sub-bandwidths contains S-SSB frequency domain resources. The first frequency domain resource is a portion of the multiple sub-bandwidths, and the portion of the sub-bandwidths includes S-SSB frequency domain resources.

10. The apparatus according to claim 9, wherein, For each of the sub-bandwidths, the frequency domain resources for transmitting the S-SSB include: all S-SSB frequency domain resources in the sub-bandwidth.

11. The apparatus according to claim 9 or 10, wherein, In a sub-bandwidth containing S-SSB frequency domain resources, the frequency domain location and / or number of S-SSB frequency domain resources contained in each sub-bandwidth are pre-configured or network-configured.

12. The apparatus according to claim 9 or 10, wherein, In a sub-bandwidth containing S-SSB frequency domain resources, where the S-SSB frequency domain resources are not distributed discontinuously, the frequency domain position of the S-SSB frequency domain resources contained in each sub-bandwidth is determined based on the starting position and length of each S-SSB frequency domain resource in the sub-bandwidth; or, it is determined based on the starting position of the first S-SSB frequency domain resource in the sub-bandwidth and the interval between two adjacent S-SSB frequency domain resources in the sub-bandwidth.

13. The apparatus according to claim 9 or 10, wherein, In a sub-bandwidth containing S-SSB frequency domain resources, the number of S-SSB frequency domain resources contained in each sub-bandwidth is: the number of times an S-SSB is repeated within the sub-bandwidth; wherein, the number of S-SSB frequency domain resources contained in different sub-bandwidths may be the same or different.

14. The apparatus according to claim 9 or 10, wherein, The sub-bandwidth is a set of resource blocks.

15. A terminal, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 7.

16. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 7.

17. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as claimed in any one of claims 1 to 7.

Images