Wireless communication method, terminal device, and network device

Abstract

The present application provides a wireless communication method, a terminal device, and a network device. The wireless communication method comprises: if a terminal device fails to execute listen-before-talk (LBT) on some or all of resource block (RB) sets of a first sidelink synchronization signal block (S-SSB) slot, the terminal device executes a first operation. The present application specifies a behavior (i.e., the first operation) of the terminal device when the terminal device fails to execute the LBT on some or all of the RB sets of the first S-SSB slot, thereby avoiding the problem of a synchronization performance anomaly between the terminal device and another device to a certain extent.

Description

Wireless communication method, terminal device, and network device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art

[0002] If the terminal device successfully performs listen-before-talk (LBT) on the sidelink synchronization signal block (S-SSB) time slot, the terminal device can map and send the S-SSB on the S-SSB time slot. However, if LBT fails on some or all resource block (RB) sets in the S-SSB time slot, the behavior of the terminal device is unclear, which may affect the synchronization performance of the terminal device in the sidelink, and thus cause the terminal device to be unable to synchronize with other terminal devices.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method, terminal device, and network device. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for wireless communication is provided, including: if a terminal device fails to perform listen-before-talk (LBT) on part or all of the resource block (RB) sets in a first S-SSB time slot, the terminal device performs a first operation.

[0006] In a second aspect, a method for wireless communication is provided, including: a network device sends configuration information to a terminal device; wherein the configuration information is used to configure one or more of the following information: first information, used to indicate the frequency domain position of a target resource block RB set, the target RB set being the RB set in the S-SSB time slot in which the terminal device preferentially performs listen-before-talk LBT; a first interval, used to indicate the interval between first-class S-SSB time slots; a second interval, used to indicate the interval between first-class S-SSB time slots and second-class S-SSB time slots, the second-class S-SSB time slots being supplementary candidate time slots for the first-class S-SSB time slots; and a third interval, used to indicate the interval between multiple second-class S-SSB time slots corresponding to the same first-class S-SSB time slot.

[0007] According to a third aspect, a terminal device is provided, comprising: an execution unit for performing a first operation if the terminal device fails to perform listen-before-talk (LBT) on part or all of the resource block (RB) sets in the first S-SSB time slot.

[0008] In a fourth aspect, a network device is provided, including: a sending unit for sending configuration information to a terminal device; wherein the configuration information is used to configure one or more of the following information: first information for indicating the frequency domain position of a target resource block RB set, the target RB set being the RB set in the S-SSB time slot in which the terminal device preferentially performs listen-before-talk LBT; a first interval for indicating the interval between first-class S-SSB time slots; a second interval for indicating the interval between first-class S-SSB time slots and second-class S-SSB time slots, the second-class S-SSB time slots being supplementary candidate time slots for the first-class S-SSB time slots; and a third interval for indicating the interval between multiple second-class S-SSB time slots corresponding to the same first-class S-SSB time slot.

[0009] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0010] In a sixth aspect, a network device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the method of the second aspect.

[0011] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided in the embodiment of the present application.

[0012] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a terminal device and / or a network device to execute part or all of the steps in the methods of the above aspects.

[0013] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a terminal device and / or a network device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0014] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0015] This application clarifies the behavior of the terminal device when it fails to perform LBT on part or all of the RB sets in the first S-SSB time slot (i.e., the first operation), thereby avoiding the problem of abnormal synchronization performance between the terminal device and other devices to a certain extent. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.

[0017] FIG2 is an example diagram of a side communication scenario within network coverage.

[0018] FIG3 is an example diagram of a side communication scenario with partial network coverage.

[0019] FIG4 is an example diagram of a side communication scenario outside network coverage.

[0020] FIG5 is a diagram illustrating an example of a side communication scenario with a central control node.

[0021] FIG6 is an example diagram of a sideline communication method based on broadcasting.

[0022] FIG7 is an example diagram of a unicast-based sideline communication method.

[0023] FIG8 is an example diagram of a side communication method based on multicast.

[0024] FIG9 is a diagram showing an example of a time slot structure of certain side-by-side communication systems (e.g., an NR-V2X system).

[0025] FIG10 is an example diagram showing changes in the available OFDM symbols for the PSSCH in different time slots.

[0026] FIG11 is an example diagram of time-frequency resources occupied by the second-order SCI in a time slot.

[0027] FIG12 is a schematic diagram of a DMRS pattern of a PSCCH.

[0028] FIG13 is a schematic diagram of the time domain positions of four DMRS symbols when the number of PSSCH symbols is 14.

[0029] FIG14 is an example diagram of a single-symbol DMRS frequency domain type 1. FIG.

[0030] FIG15 is an example diagram of the time-frequency position of an SL CSI-RS.

[0031] FIG16 is an example diagram showing a channel occupancy time obtained by a communication device after successful LBT on a channel of an unlicensed spectrum, and signal transmission using resources within the channel occupancy time.

[0032] FIG17 is an example diagram of COT sharing.

[0033] FIG18 is an example diagram of the division of sidelink frequency domain resources in the unlicensed spectrum.

[0034] Figure 19A is an example diagram of S-SSB time domain resource configuration.

[0035] FIG19B is a diagram showing an example of the time-frequency structure of S-SSB.

[0036] Figure 20 is an example diagram of S-SSB mapping.

[0037] Figure 21 is a schematic flowchart of a wireless communication method provided in an embodiment of the present application.

[0038] Figure 22 is an example diagram of a wireless communication method provided in an embodiment of the present application.

[0039] Figure 23 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0040] Figure 24 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0041] Figure 25 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0042] Figure 26A is a schematic diagram of the arrangement of a first type of S-SSB time slot and a second type of S-SSB time slot provided in an embodiment of the present application.

[0043] Figure 26B is a schematic diagram of the arrangement of another type of first S-SSB time slots and second type S-SSB time slots provided in an embodiment of the present application.

[0044] Figure 26C is a schematic diagram of the arrangement of another type of first S-SSB time slots and second type S-SSB time slots provided in an embodiment of the present application.

[0045] Figure 27 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0046] Figure 28 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0047] Figure 29 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0048] Figure 30 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0049] Figure 31 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0050] Figure 32 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

[0051] Figure 33 is a schematic structural diagram of a network device provided in an embodiment of the present application.

[0052] Figure 34 is a schematic structural diagram of a device for communication provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The technical solution in this application will be described below with reference to the accompanying drawings.

[0054] Communication System

[0055] Figure 1 is a diagram illustrating the system architecture of a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 located within the coverage area.

[0056] Optionally, the wireless communication system 100 may include multiple network devices and the coverage area of ​​each network device may include other numbers of terminal devices, which is not limited in this embodiment of the present application.

[0057] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0058] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0059] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity that provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communication. For example, a cellular phone and a car communicate with each other using sidelink signals. Cell phones and smart home devices can communicate with each other without relaying the communication signal through a base station. Optionally, the terminal device can be used to act as a base station.

[0060] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, a modem or a chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device (D2D), vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, and a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form adopted by the network equipment.

[0061] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0062] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0063] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0064] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0065] Sideline communication under different network coverage conditions

[0066] Sidelink communication (or sidelink transmission) refers to a communication technology based on sidelink (SL). Sidelink communication can be, for example, D2D or V2X. Sidelink communication supports direct communication and data transmission between terminal devices. Direct communication data transmission between terminal devices can achieve higher spectrum efficiency and lower transmission latency. For example, the Internet of Vehicles system uses sidelink communication technology.

[0067] In side communication, according to the network coverage of the terminal device, side communication can be divided into side communication within the network coverage, side communication with partial network coverage, side communication outside the network coverage and side communication controlled by the central node.

[0068] Figure 2 illustrates an example scenario for sidelink communication within network coverage. In the scenario shown in Figure 2, both terminal devices 120a are within the coverage of network device 110. Therefore, both terminal devices 120a can receive configuration signaling from network device 110 (configuration signaling in this application can also be replaced by configuration information) and determine the sidelink configuration based on the configuration signaling from network device 110. After both terminal devices 120a have configured their sidelinks, sidelink communication can proceed on the sidelink.

[0069] Figure 3 is an example diagram of a sidelink communication scenario with partial network coverage. In the scenario shown in Figure 3, terminal device 120a performs sidelink communication with terminal device 120b. Terminal device 120a is located within the coverage range of network device 110, so terminal device 120a can receive the configuration signaling of network device 110 and determine the sidelink configuration based on the configuration signaling of network device 110. Terminal device 120b is located outside the network coverage and cannot receive the configuration signaling of network device 110. In this case, terminal device 120b can determine the sidelink configuration based on pre-configuration information and / or information carried in the physical sidelink broadcast channel (PSBCH) sent by terminal device 120a within the network coverage. After both terminal device 120a and terminal device 120b perform sidelink configuration, sidelink communication can be performed on the sidelink.

[0070] Figure 4 illustrates an example scenario for sidelink communication outside of network coverage. In the scenario shown in Figure 4, both terminal devices 120b are outside of network coverage. In this scenario, both terminal devices 120b can determine the sidelink configuration based on pre-configured information. After both terminal devices 120b have configured their sidelinks, sidelink communication can proceed over the sidelink.

[0071] Figure 5 illustrates an example scenario for sideline communication with a central control node. In the scenario shown in Figure 5, multiple terminal devices 120b may constitute a communication group. This communication group may include a central control node. In some cases, the central control node may serve as a cluster header (CH) terminal device. The central control node may have one or more of the following functions: establishing the communication group, managing the joining and leaving of group members, coordinating resources, allocating sideline transmission resources to other terminal devices, receiving sideline feedback information from other terminal devices, and coordinating resources with other communication groups.

[0072] Sideline communication mode

[0073] Certain standards or protocols (such as the 3rd Generation Partnership Project (3GPP)) define two sideline communication modes (or transmission modes): a first mode and a second mode.

[0074] In the first mode, the resources of the terminal device (the resources mentioned in this application may also be referred to as transmission resources, time-frequency resources) are allocated by the network device. The terminal device can send data on the side link according to the resources allocated by the network device. The network device can allocate resources for a single transmission to the terminal device, or it can allocate resources for semi-static transmission to the terminal device. This first mode can be applied to scenarios covered by a network device, such as the scenario shown in Figure 2 above. In the scenario shown in Figure 2, the terminal device 120a is within the network coverage of the network device 110, so the network device 110 can allocate resources used in the side transmission process to the terminal device 120a.

[0075] In the second mode, the terminal device can autonomously select one or more resources from a resource pool (RP). The terminal device can then perform side transmission based on the selected resources. For example, in the scenario shown in FIG4 , the terminal device 120b is located outside the cell coverage area. Therefore, the terminal device 120b can autonomously select resources from a pre-configured resource pool for side transmission. Alternatively, in the scenario shown in FIG2 , the terminal device 120a can also autonomously select one or more resources from a resource pool configured by the network device 110 for side transmission.

[0076] Data transmission method of side communication

[0077] Some sidewalk communication systems (such as LTE-V2X) support broadcast-based data transmission (hereinafter referred to as broadcast transmission). For broadcast transmission, the receiving terminal device can be any terminal device around the transmitting terminal device. Taking Figure 6 as an example, terminal device 1 is the transmitting terminal device, and the receiving terminal device corresponding to the transmitting terminal device is any terminal device around terminal device 1, such as terminal devices 2 to terminal devices 6 in Figure 6.

[0078] In addition to broadcast transmission, some communication systems also support unicast-based data transmission (hereinafter referred to as unicast transmission) and / or multicast-based data transmission (hereinafter referred to as multicast transmission). For example, NR-V2X aims to support autonomous driving. Autonomous driving places higher requirements on data exchange between vehicles. For example, data exchange between vehicles requires higher throughput, lower latency, higher reliability, wider coverage, and more flexible resource allocation. Therefore, to improve the performance of data exchange between vehicles, NR-V2X introduces unicast and multicast transmission.

[0079] For unicast transmission, there is typically only one receiving terminal device. For example, in Figure 7, unicast transmission occurs between terminal devices 1 and 2. Terminal device 1 can be the sending terminal device, and terminal device 2 can be the receiving terminal device, or alternatively, terminal device 1 can be the receiving terminal device, and terminal device 2 can be the sending terminal device.

[0080] For multicast transmission, the receiving terminal device can be a terminal device within a communication group, or it can be a terminal device within a certain transmission distance. Taking Figure 7 as an example, terminal devices 1, 2, 3, and 4 form a communication group. If terminal device 1 sends data, the other terminal devices in the group (terminal devices 2 through 4) can all be receiving terminal devices.

[0081] Sideline communication system frame structure

[0082] A timeslot may include channels such as the physical sidelink control channel (PSCCH), the physical sidelink shared channel (PSSCH), and the physical sidelink feedback channel (PSFCH). These channels will be described in detail below and will not be repeated here.

[0083] Figure 9 shows an example of a time slot structure for certain sidelink communication systems (e.g., NR-V2X systems). Figure 9(a) shows an example of a time slot structure in which the physical sidelink feedback channel (PSFCH) is not included in the time slot. Figure 9(b) shows an example of a time slot structure in which the PSFCH is included in the time slot.

[0084] As shown in Figure 9, in the time domain, the PSCCH can start from the second sidelink symbol of the time slot and occupy 2 or 3 orthogonal frequency division multiplexing (OFDM) symbols. In the frequency domain, it can occupy {10, 12 15, 20, 25} physical resource blocks (PRBs). In order to reduce the complexity of blind detection of PSCCH by terminal devices, only one number of PSCCH symbols and PRBs can be configured in a resource pool. In addition, the subchannel is the minimum granularity of PSSCH resource allocation in some sidelink communication systems (such as NR-V2X systems). Therefore, the number of PRBs occupied by PSCCH must be less than or equal to the number of PRBs contained in a subchannel in the resource pool to avoid additional restrictions on PSSCH resource selection or allocation.

[0085] In the time domain, the PSSCH can start from the second side symbol of the time slot. The last time domain symbol in the time slot is the guard period (GP) symbol (also called the gap (GAP) symbol), and the remaining symbols can be mapped to the PSSCH. The first side symbol in the time slot can be a repetition of the second side symbol. The receiving terminal device can use the first side symbol as an automatic gain control (AGC) symbol, and the data on this symbol is usually not used for data demodulation. As shown in Figure 9(a), the PSSCH can occupy K subchannels in the frequency domain, and each subchannel can include N consecutive PRBs. K can be an integer greater than 0, and N can be an integer greater than 0.

[0086] As shown in FIG9( b ), when a time slot includes a PSFCH channel, the second to last and third to last symbols in the time slot can be used for PSFCH channel transmission, and a time domain symbol before the PSFCH channel can be used as a GP symbol.

[0087] PSSCH

[0088] In some sidelink communication systems (such as NR-V2X systems), PSSCH can be used to carry second-order sidelink control information (SCI). The second-order SCI can include SCI 2-A or SCI 2-B. The second-order SCI can use Polar coding. The second-order SCI can be fixedly modulated with QPSK. The data part of PSSCH can use low-density parity check (LDPC). The highest modulation order that the data part of PSSCH can support is 256QAM.

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

[0090] In some sideline communication systems (such as NR-V2X systems), the maximum number of retransmissions of a PSSCH is 32 times. If there are PSFCH resources in the resource pool and the configuration period of the PSFCH resources is 2 or 4, the OFDM symbols available in the time slot where different transmissions of a PSSCH are located may change. Figure 10 is an example diagram of the change in the available OFDM symbols of the PSSCH in different time slots. As shown in Figure 10, due to the existence of PSFCH resources, the number of OFDM symbols available for the nth transmission and the n+1th transmission of the PSSCH is different. If the number of symbols transmitted by the PSSCH is calculated according to the actual number of OFDM symbols in a time slot The difference in the number of symbols available for PSSCH transmission in a time slot may cause Q′ SCI2 Different, and Q′ SCI2 The change of will lead to the change of the size of the TB carried by PSSCH, as described below. In order to ensure that the transmission block size (TBS) remains unchanged during multiple transmissions of PSSCH, The actual number of PSFCH symbols is not used. The number of resource elements (REs) occupied by the PSSCH demodulation reference signal (DMRS) and the number of REs occupied by the phase-tracking reference signal (PT-RS), which may change during the retransmission process, are not taken into account.

[0091] The code rate of the second-order SCI can be dynamically adjusted within a certain range, and the specific code rate used can be indicated by the first-order SCI. Therefore, even after the code rate changes, the receiver does not need to perform blind detection on the second-order SCI. Figure 11 shows an example of the time-frequency resources occupied by the second-order SCI in a time slot. As shown in Figure 11, the modulation symbols of the second-order SCI can be mapped starting from the symbol where the first PSSCH DMRS is located, using a frequency domain first and then a time domain mapping. In the OFDM symbol where the DMRS is located, the second-order SCI can be mapped to REs not occupied by the DMRS.

[0092] Within a resource pool, the data portion of the PSSCH can use multiple different modulation and coding scheme (MCS) tables. For example, one or more of the following tables can be used: the conventional 64QAM MCS table, the 256QAM MCS table, and the low spectrum efficiency 64QAM MCS table. In a transmission, the specific MCS table used for the data portion of the PSSCH can be indicated by the "MCS table indication" field in the first-order SCI. In order to control the PAPR, the PSSCH must be sent using continuous PRBs. Since the subchannel is the minimum frequency domain resource granularity of the PSSCH, the PSSCH must occupy continuous subchannels.

[0093] Sidelink TBS

[0094] PSSCH follows the TBS determination mechanism of the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH), that is, the TBS can be determined based on the reference value of the number of REs used for PSSCH in the time slot where PSSCH is located, so that the actual code rate is as close to the target code rate as possible. It should be noted that the purpose of using the reference value of the number of REs instead of the actual number of REs is to ensure that the number of REs used to determine the TBS remains unchanged during the PSSCH retransmission process, so that the determined TBS size is the same. In order to achieve this goal, the reference value N of the number of REs occupied by PSSCH in the TBS determination process is used. RE It can be determined according to the following formula:

[0095] Among them, n PRB is the number of PRBs occupied by PSSCH, is the number of REs occupied by the first-order SCI (including the REs occupied by the DMRS of the PSCCH), is the number of REs occupied by the second-order SCI (as described above), N′ REIndicates the number of reference REs that can be used for PSSCH in a PRB. N' RE It can be determined by the following formula:

[0096] in, It can represent the number of subcarriers in a PRB, for example, Indicates the number of symbols available for sidelink in a time slot, which may not include the last GP symbol and the first symbol used for AGC. = A reference value indicating the number of symbols occupied by the PSFCH, for example, or 3. The specific value can be indicated by the "PSFCH symbol number" field in the first-order SCI. It can represent the reference value of the number of REs occupied by PT-RS and channel state information-reference signal (CSI-RS), and can be configured by radio resource control (RRC) layer parameters. It can represent the average number of DMRS REs in a time slot, which is related to the DMRS pattern allowed in the resource pool. Table 1 shows the DMRS pattern allowed in the resource pool and The corresponding relationship.

[0097] Table 1

[0098] Sidelink DMRS

[0099] In some sideline communication systems (such as NR-V2X systems), the DMRS pattern of the PSCCH can be the same as that of the physical downlink control channel (PDCCH). That is, the DMRS can exist on each OFDM symbol of the PSCCH and can be located in the {#1, #5, #9} REs of a PRB in the frequency domain. Figure 12 is a schematic diagram of a DMRS pattern of the PSCCH. The DMRS sequence of the PSCCH is generated by the following formula:

[0100] Among them, the pseudo-random sequence c(m) can be obtained by Initialize. Wherein, l can represent the index of the OFDM symbol where the DMRS is located in the time slot, It can represent the index of the time slot where the DMRS is located in the system frame. It can represent the number of OFDM symbols in a time slot, N ID∈{0,1,…,65535}, in a resource pool N ID The specific value is configured or pre-configured by the network.

[0101] Some sideline communication systems (such as NR-V2X systems) use multiple time-domain PSSCH DMRS patterns, which draws on the design of the Uu interface of the NR system. Within a resource pool, the number of available DMRS patterns can be 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 13 shows the time-domain position of four DMRS symbols when the PSSCH has 14 symbols.

[0102] Table 2

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

[0104] The generation method of the PSSCH DMRS sequence is almost identical to that of the PSCCH DMRS sequence. The only difference is the initialization formula c(m) of the pseudo-random sequence. init middle, Among them, p i The ith CRC bit of the PSCCH that schedules the PSSCH. L may be the number of bits of the PSCCH CRC, for example, L=24.

[0105] In the NR communication system, PDSCH and PUSCH support two frequency domain DMRS patterns, namely DMRS frequency domain type 1 and DMRS frequency domain type 2. For each frequency domain type, there are two different types: single DMRS symbol and double DMRS symbol. Single-symbol DMRS frequency domain type 1 supports 4 DMRS ports, and single-symbol DMRS frequency domain type 2 can support 6 DMRS ports. In the case of double DMRS symbols, the number of supported ports is doubled. However, in sideline communication systems (such as NR-V2X), since PSSCH only needs to support two DMRS ports at most, only single-symbol DMRS frequency domain type 1 can be supported. Figure 14 is an example diagram of a single-symbol DMRS frequency domain type 1.

[0106] Sidelink CSI-RS

[0107] The sidelink communication system can support sidelink CSI-RS (SL CSI-RS) to better support unicast communication. SL CSI-RS can be transmitted when the following three conditions are met: the terminal device transmits the corresponding PSSCH (that is, the terminal device cannot only transmit SL CSI-RS); higher-layer signaling activates SL CSI-RS reporting; when higher-layer signaling activates SL CSI-RS reporting, the corresponding bit in the second-order SCI sent by the terminal device triggers SL CSI-RS reporting.

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

[0109] The position of the first RE occupied by SL CSI-RS in a PRB can be indicated by the sl-CSI-RS-FreqAllocation parameter in PC5RRC. If SL CSI-RS is one port, the parameter can be a bitmap with a length of 12, corresponding to 12 REs in one PRB. If SL CSI-RS is two ports, the parameter is a bitmap with a length of 6. In this case, SL CSI-RS can occupy two REs, 2f(1) and 2f(1)+1. Among them, f(1) can represent the index of the bit with a value of 1 in the above bitmap. The frequency domain position of SL CSI-RS can also be determined by the transmitting terminal device. The determined frequency domain position of SL CSI-RS cannot conflict with PT-RS. Figure 15 is an example diagram of the time-frequency position of SL CSI-RS. In FIG15 , the number of SL CSI-RS ports is 2, the sl-CSI-RS-FirstSymbol is 8, and the sl-CSI-RS-FreqAllocation is [b5, b4, b3, b2, b1, b0] = [0, 0, 0, 1, 0, 0].

[0110] Unlicensed spectrum communications

[0111] Unlicensed spectrum is spectrum designated by countries and regions for use by radio equipment. This spectrum is generally considered shared spectrum, meaning that as long as communications equipment meets national or regional regulatory requirements for the spectrum, it can use it without having to apply for exclusive spectrum authorization from the national or regional spectrum management agency. Unlicensed spectrum may also be referred to as shared spectrum, unlicensed spectrum, unlicensed frequency band, or unlicensed frequency band.

[0112] In LTE systems, unlicensed spectrum has been used as a supplementary frequency band to licensed spectrum for cellular networks. NR systems can achieve seamless cellular network coverage, high spectral efficiency, high peak rates, and high reliability. 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 the use of NR systems in unlicensed spectrum, referred to as NR unlicensed (NR-U) systems.

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

[0114] The use of unlicensed spectrum needs to meet the specific regulatory requirements of each country and region. For example, communication equipment can use unlicensed spectrum to access channels on unlicensed spectrum through channel monitoring to avoid conflicts with other communication equipment or other communication systems (such as WiFi systems). As an implementation method, communication equipment can use unlicensed spectrum in accordance with the principle of LBT. Therefore, for NR-U, NR technology needs to be enhanced accordingly to adapt to the regulatory requirements of unlicensed frequency bands, while efficiently utilizing unlicensed spectrum to provide services. In the 3GPP R16 standard, the standardization of NR-U technology in the following aspects was mainly completed: channel monitoring process; initial access process; control channel design; HARQ and scheduling; scheduling-free authorization transmission, etc.

[0115] LBT

[0116] The LBT principle may include: before a communication device uses a channel on an unlicensed spectrum to send a signal, it must first perform LBT. In the case of a successful LBT, the result of the channel monitoring is that the channel is idle. Only when the channel is idle can the communication device send a signal through the channel. If the channel monitoring result of the communication device on the channel is that the channel is busy or LBT fails, then the communication device cannot send a signal through the channel. In addition, in order to ensure fairness in the use of spectrum resources of the shared spectrum, if a communication device succeeds in LBT on a channel on an unlicensed spectrum, the duration for which the communication device can use the channel for communication transmission cannot exceed a certain duration. By limiting the maximum duration for communication after a successful LBT, this mechanism can give different communication devices the opportunity to access the shared channel, thereby allowing different communication systems to coexist in a friendly manner on the shared spectrum.

[0117] Signal transmission in unlicensed spectrum involves concepts related to channel occupancy, such as channel occupancy time (COT), maximum channel occupancy time (MCOT), the COT of network devices (such as base stations), and the COT of terminal devices.

[0118] MCOT refers to the maximum duration a communication device is allowed to transmit signals using unlicensed spectrum channels if LBT is successful. It should be understood that MCOT refers to the duration of signal transmission. Different communication devices with different channel access priorities may have different MCOT values. For example, the maximum MCOT value can be set to 10ms.

[0119] FIG16 is an example diagram showing a channel occupancy time obtained by a communication device after successful LBT on a channel of an unlicensed spectrum, and signal transmission using resources within the channel occupancy time.

[0120] Although channel sensing is not a global regulatory requirement, it can provide interference avoidance and coexistence benefits for communication systems on shared spectrum. Therefore, during the design of NR systems on unlicensed spectrum, channel sensing is a feature that communication equipment in the system must support.

[0121] Unlicensed spectrum channel access method

[0122] Some communication systems (such as the NR-U system) introduce a channel access method using LBT.

[0123] From a system networking perspective, LBT can be implemented in two ways: load-based equipment (LBE) LBT, also known as dynamic channel monitoring or dynamic channel occupancy; and frame-based equipment (FBE) LBT, also known as semi-static channel monitoring or semi-static channel occupancy. The principle of dynamic channel monitoring LBT is that a communication device performs LBT on a carrier in unlicensed spectrum upon service arrival and begins transmitting signals on that carrier after successful LBT.

[0124] The LBT mode of dynamic channel monitoring may include a Type 1 (Type 1) channel access mode and a Type 2 (Type 2) channel access mode.

[0125] The following describes the details of channel monitoring or channel access using a network device as an example. It is understood that the process of channel monitoring or channel access for other communication devices, such as terminal devices, is similar.

[0126] Type 1 channel access is also known as multi-slot channel detection with random backoff based on contention window size adjustment. In Type 1, a channel access priority class (CAPC) p is selected based on the priority of the service to be transmitted. The communication device can initiate channel occupation with a length of Tmcot based on the channel access priority class p.

[0127] If a network device uses Type 1 channel access, in addition to transmitting its own data during the channel occupancy period, it can also share its COT with terminal devices. Sharing the COT with a terminal device means allowing the terminal device to transmit data during the duration of the COT (i.e., the COT obtained by the network device through channel access). Accordingly, if a terminal device uses Type 1 channel access, in addition to transmitting its own data during the channel occupancy period, it can also share its COT with the network device.

[0128] When the resources within the COT are shared with the terminal device for uplink transmission, the terminal device can use the channel access method of type 2A, the channel access method of type 2B or the channel access method of type 2A for channel access (channel access, CA). Among them, the channel access method of type 2A, the channel access method of type 2B or the channel access method of type 2A are all channel access methods based on fixed-length monitoring time slots. Figure 17 is an example diagram of COT sharing. As shown in Figure 17, terminal device 1 (UE1) can perform LBT within Td+Ts1, thereby using the shared COT through channel access. Terminal device 2 (UE2) can use the shared COT through the channel access method of type 2A before time slot n+2.

[0129] Table 3 shows the channel access priority and its corresponding parameters when the terminal device performs type 1 channel access.

[0130] Table 3

[0131] The default channel access mode on the network device side is type 1 channel access mode. The channel access parameters corresponding to the channel access priority p are shown in Table 3. In Table 3, m p It can refer to the number of fallback slots corresponding to the channel access priority p, CW pIt can refer to the contention window (CW) size corresponding to the channel access priority p. min,p It can refer to the CW corresponding to the channel access priority p p Minimum value, CW max,p It can refer to the CW corresponding to the channel access priority p p The maximum value, T mcot,p It refers to the maximum channel occupancy time corresponding to the channel access priority p.

[0132] Type 2 channel access is also known as a channel access method based on fixed-length channel monitoring time slots. Type 2 channel access methods include Type 2A, Type 2B, and Type 2C. When resources within a COT are shared with other communication devices, these other devices can use Type 2 channel access.

[0133] In Type 2A channel access, a communication device can use a single-slot detection of the channel every 25 us. This means that the communication device can begin channel detection 25 us before starting to send data. This 25 us channel detection can include one 16 us channel detection and one 9 us channel detection. If both detection results indicate that the channel is idle, the channel is considered idle and channel access can be performed.

[0134] In the Type 2B channel access method, the communication device can use a 16-us single-slot channel detection process. During the channel detection process, if the communication device detects that the channel is idle for more than 4 us within the last 9 us, it can be considered that the channel is idle.

[0135] In the Type 2C channel access method, communication devices can transmit data directly over the channel without performing channel detection. In the Type 2C channel access method, the time difference between the current transmission and the previous transmission is less than or equal to 16us. In other words, if the time difference between two transmissions is less than or equal to 16us, they can be considered to be the same transmission and channel detection is not required. It should be noted that in the Type 2C channel access method, the transmission time of communication devices is limited and generally cannot exceed 584us.

[0136] A special case that needs to be explained is that when the network device initiates channel occupancy to transmit the synchronizing signal / PBCH block (SSB) within the discovery reference signal (DRS) window and the DRS window does not include unicast data transmission of the terminal device, 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 network device can use type 2A channel access to initiate channel occupancy.

[0137] Channel access parameter indication

[0138] In some communication systems based on unlicensed spectrum (such as NR-U systems), when a terminal device is scheduled to transmit PUSCH or physical uplink control channel (PUCCH), the network device can indicate the channel access method corresponding to the PUSCH or PUCCH by carrying downlink control information (DCI) of uplink grant (UL grant) or downlink grant (DL grant). In addition, since some channel access methods need to meet the gap requirements of 16μs or 25μs, the terminal device can ensure the gap size between two transmissions by transmitting a cyclic prefix extension (CPE). Accordingly, the network device can indicate the CPE length of the first symbol of the uplink transmission of the terminal device.

[0139] When specifically indicating, the network device can explicitly indicate channel access parameters such as CPE length, channel access mode, or channel access priority to the terminal device through joint coding. The following describes the characteristics of the channel access parameter indication methods introduced in different DCI formats.

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

[0141] The standard predefines a set of channel access mode and CPE length joint indications, as shown in Table 4. The fallback uplink grant includes 2-bit LBT indication information. This 2-bit LBT indication information 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 terminal device can select the CAPC based on the service priority.

[0142] Table 4

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

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

[0145] The standard presets a set of joint indications of channel access mode and CPE length, and the set is shown in Table 4. The fallback downlink grant includes 2-bit LBT indication information, and the 2-bit LBT indication information is used to indicate the jointly coded channel access mode and CPE length from the set shown in Table 4. The channel access mode and CPE length are used for PUCCH transmission, wherein the PUCCH can carry acknowledgment (ACK) or negative acknowledgment (NACK) information corresponding to the PDSCH. If the channel access mode is type 1 channel access, the terminal device can determine that the CAPC used to transmit the PUCCH is 1.

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

[0147] The high layer configures the LBT parameter indication set. The LBT parameter indication set includes at least one joint coding. The joint coding is used to indicate the channel access method, CPE length and CAPC. The non-fallback uplink authorization includes LBT indication information. The LBT indication information is used to indicate the jointly coded channel access method, CPE length and CAPC from the above-mentioned LBT parameter indication set. The channel access method, CPE length and CAPC are used for PUSCH transmission. If the indicated channel access method is type 2 channel access, the CAPC indicated at the same time is the CAPC used by the network device when obtaining the COT. In addition, the LBT indication information includes a maximum of 6 bits.

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

[0149] The high layer configures the LBT parameter indication set. The LBT parameter indication set includes at least one joint coding. The joint coding is used to indicate the channel access method and CPE length. The non-fallback downlink authorization includes LBT indication information. The LBT indication information is used to indicate the channel access method and CPE length of the joint coding from the above-mentioned LBT parameter indication set. The channel access method and CPE length are used for PUCCH transmission. Among them, the PUCCH can carry the ACK or NACK information corresponding to the PDSCH. If the channel access method is type 1 channel access, the terminal device can determine that the CAPC used to transmit the PUCCH is 1. In addition, the LBT indication information includes a maximum of 4 bits.

[0150] In addition to the above explicit indications, the network device can also implicitly indicate the channel access method within the COT. For example, when the terminal device receives an uplink authorization or downlink authorization sent by the base station indicating that the channel access type corresponding to the PUSCH or PUCCH is type 1 channel access, if the terminal device can determine that the PUSCH or PUCCH belongs to the COT of the network device, for example, the terminal device receives a DCI format 2_0 sent by the network device, and determines that the PUSCH or PUCCH belongs to the COT of the network device based on the DCI format 2_0, then the terminal device can update the channel access type corresponding to the PUSCH or PUCCH to type 2A channel access instead of using type 1 channel access.

[0151] SL frequency domain resource allocation

[0152] The frequency domain resource division of SL communication is similar to that of Uu communication. Figure 18 shows an example of sidelink frequency domain resource division.

[0153] As shown in Figure 18, when there are multiple carriers in the frequency domain resources, the terminal device and the system can support the function of multi-carrier communication (such as carrier aggregation). Of course, the system can also only support single-carrier scenarios. In this case, the system and the terminal device may not need to support the function of multi-carrier communication. The frequency resources of a carrier can be divided into one or more BWPs. In the related art, when there are multiple BWPs in the frequency domain, only one BWP is supported for activation at the same time. In the SL system, the related art only supports one SL BWP. In some unlicensed spectrum communication systems (such as the NR-U system), a BWP is divided into multiple RB sets (RB sets). The size of each RB set can be 20MHz. An RB set can be used as the minimum unit of LBT.

[0154] S-SSB time domain resource allocation

[0155] In some sideline communication systems, S-SSB is allocated in the time domain with time slots as the minimum granularity. The S-SSB synchronization period (hereinafter referred to as period or S-SSB period) can be 160ms. Depending on the subcarrier spacing, the number of S-SSB time slots in each period is different. For example, a subcarrier spacing of 15kHz can correspond to 1 S-SSB time slot in a period; a subcarrier spacing of 30kHz corresponds to a configurable parameter of S-SSB time slots in a period of {1, 2}; a subcarrier spacing of 60kHz corresponds to a configurable parameter of S-SSB time slots in a period of {1, 2, 4}, etc. Figure 19A is an example diagram of S-SSB time domain resource configuration. As shown in Figure 19A, two sets of S-SSBs are included in one period (160ms), namely synchronization resource group 1 and synchronization resource group 2. Among them, one set of S-SSBs can be used for sending, and the other set of S-SSBs can be used for receiving. In Figure 19A, each set of S-SSBs contains 4 S-SSB time slots. For ease of description and understanding, the embodiments provided in this application are all described using a set of S-SSBs as an example. It is understandable that the methods provided in the embodiments of this application can also be applied to another set of S-SSBs.

[0156] Figure 19B shows an example of the time-frequency structure of S-SSB. As shown in Figure 19B, an S-SSB timeslot contains 14 OFDM symbols. Each symbol is used to carry the PSBCH, S-PSS, and S-SSS. In the frequency domain, the PSBCH can occupy 132 subcarriers, and the S-PSS / S-SSS sequence can occupy 127 subcarriers.

[0157] S-SSB time-frequency domain mapping

[0158] As mentioned above, the frequency domain resources corresponding to an S-SSB time slot may include multiple RB sets. The terminal device may attempt to map or transmit the S-SSB on one or more RB sets of an S-SSB time slot. If the terminal device attempts to map or transmit the S-SSB on an RB set, LBT may be performed on the RB set. If LBT is successfully performed on the RB set, that is, it is detected that the RB set is not occupied (or available), the S-SSB may be mapped or sent on this RB set. If the terminal device attempts to map or transmit the S-SSB on multiple RB sets, LBT may be performed on each of the multiple RB sets, and whether the S-SSB can be mapped or sent on the corresponding RB set may be determined based on the LBT results on each RB set.

[0159] Within an RB set, S-SSBs are repeatedly mapped in the frequency domain. In multiple RB sets corresponding to a time slot, S-SSBs are also repeatedly mapped within each RB set.

[0160] The following uses Figure 20 as an example to illustrate the mapping of S-SSB. As shown in Figure 20, the frequency domain resources corresponding to an S-SSB time slot include four RB sets. If these four RB sets are all configured to transmit S-SSB, the terminal device can perform LBT on each of these four RB sets. As shown in Figure 20, if the terminal device successfully performs LBT on RB set 0, RB set 1, and RB set 2 of the first S-SSB time slot, the S-SSB is mapped or sent on these three RB sets. As can be seen from Figure 20, the S-SSB is repeatedly mapped three times within one RB set.

[0161] S-SSB time slots may include first-category S-SSB time slots and second-category S-SSB time slots. The second-category S-SSB time slots may be supplementary candidate time slots for the first-category S-SSB time slots. The first-category S-SSB time slots may be, for example, S-SSB time slot resources in the R16 / R17 sidelink configuration, and the second-category S-SSB time slots are additional S-SSB time slot resources newly defined in R18.

[0162] A first-class S-SSB time slot may correspond to or be associated with K second-class S-SSB time slots. The spacing between S-SSB time slots may be configured or preconfigured. Continuing with FIG. 20 , one first-class S-SSB time slot corresponds to three second-class S-SSB time slots. The spacing between these four S-SSB time slots is shown in FIG. 20 .

[0163] The transmission of S-SSB was discussed in some meetings. The following examples illustrate the discussion of S-SSB transmission in some meetings.

[0164] Conference RAN1#109-e

[0165] Agreement

[0166] For S-SSB and synchronization in SL-U:

[0167] Further study (FFS) is needed on the time domain locations of S-SSB resources, e.g., whether / how to introduce more candidate occasions compared with R16 / R17 NR SL design, etc.

[0168] Down-selection at least one of the following solutions to meet OCB and PSD requirement for S-SSB transmission.

[0169] Option 1: Using interlaced RB transmission.

[0170] Option 2: S-SSB multiplexing with other SL transmissions in the same slot.

[0171] Option 3: Repetition of S-PSS / S-SSS / PSBCH in frequency domain.

[0172] Option 4: S-PSS / S-SSS / PSBCH with wider bandwidth.

[0173] Further study is needed: whether to support 4 symbols S-SSB.

[0174] Note: 4 symbols S-SSB can be considered with options 1 / 2 / 3 / 4 above.

[0175] Further study is needed: whether the temporary exemption of OCB requirement is applicable for S-SSB transmission.

[0176] Further study is needed: whether there are any changes to R16 / R17 NR SL synchronization procedure.

[0177] Conference RAN1#110

[0178] Agreement

[0179] If RAN1 decides that LBT is performed for S-SSB transmission, in addition to the S-SSB occasions in R16 / R17 NR SL design, support additional candidate S-SSB occasions.

[0180] Further study is needed: the number and locations of additional candidate S-SSB occasions.

[0181] Further study is needed on when a UE transmits S-SSB on such additional candidate S-SSB occasions, and the related Rx UE's behavior.

[0182] Agreement

[0183] For S-SSB and synchronization in SL-U: No changes on R16NR SL S-PSS / S-SSS sequence generation; Continue studying the 4 options from the previous agreement and whether / how temporary exemption of OCB requirement is applicable for S-SSB transmission, e.g., how to meet the minimum of 2MHz requirement under 15kHz SCS.

[0184] Conference RAN1#110bis-e

[0185] Agreement

[0186] To meet OCB and PSD requirement for S-SSB transmission, down-select between the followings for 15kHz and 30kHz SCS.

[0187] Option 1: Using interlaced RB transmission for S-PSS / S-SSS / PSBCH.

[0188] Option 3: Repetition of S-PSS / S-SSS / PSBCH in frequency domain.

[0189] Further study is required on whether / how the above options apply to all or subset of channel type of S-PSS / S-SSS / PSBCH.

[0190] Note: RAN1 further study the relationship between the above options and temporary OCB exemption, and the discussion on temporary OCB exemption can continue even if option 1 or option 3 is supported.

[0191] Further study is needed on how to handle 60kHz SCS (if needed, not limited to option 1 or option 3).

[0192] Agreement

[0193] Regarding usage of PRBs within intra-cell guard band of two adjacent RB sets:

[0194] Such PRBs can be used for PSSCH transmission if and only if a UE can transmit on the respective LBT channels after performing channel access procedure in multi-channel case and the UE uses both of these two RB sets for PSSCH transmission.

[0195] FFS details, e.g., handling of potential unequal sub-channel size, for interlaced RB based transmission, whether the PRB(s) in the intra-cell guard band have the same interlace index(s) as the PRBs for PSSCH transmission in these two RB sets, require further study.

[0196] Such PRBs are not used for PSCCH transmission.

[0197] Further study is needed: whether or not such PRBs are used for PSFCH / S-SSB transmission.

[0198] Agreement

[0199] At least R16 / R17 NR SL S-SSB slots are excluded from SL resource pool.

[0200] Note: Whether or not additional candidate S-SSB occasions are excluded from the resource pool will be discussed after the details of additional candidate S-SSB occasions are clearer.

[0201] Agreement

[0202] Regarding additional candidate S-SSB occasions: their number and time domain locations are (pre-)configured or predefined.

[0203] Conference RAN1#111

[0204] Agreement

[0205] For S-SSB transmission, down-select one or more of the following for 15kHz and 30kHz SCS.

[0206] Option 1-1: Using interlaced RB transmission for all of S-PSS / S-SSS / PSBCH.

[0207] Option 1-2: Using interlaced RB transmission for PSBCH only, and apply OCB exemption to S-PSS and S-SSS.

[0208] Option 3-1: Repeat S-PSS / S-SSS / PSBCH N times in frequency domain, and there is a gap between the repetition(s) to meet OCB requirement.

[0209] Details that require further study include, for example, that the length of the gap is (pre-)configured or pre-defined, with a value of N (eg, N=2).

[0210] Further study needed: gap of 0.

[0211] Option 3-2: Repeat only S-PSS / S-SSS K times in frequency domain, and PSBCH is rate matched. There is a gap between the repetition(s) to meet OCB requirement.

[0212] Details that require further study include, for example, the length of gap is (pre-)configured or pre-defined, value of K.

[0213] Further study needed: gap of 0.

[0214] Further study is needed: PSBCH resource.

[0215] Option 3-3: keep the legacy S-PSS / S-SSS / PSBCH while repeating PSBCH N times in frequency domain and rate-matching PSBCH to S-PSS / S-SSS symbols,and there is a gap between the PSBCH repetition(s)to meet OCB requirements.

[0216] Details that require further study include, for example, the length of gap is (pre-)configured or pre-defined, value of N.

[0217] Option A: Apply OCB exemption to all of S-PSS / S-SSS / PSBCH.

[0218] For Option 1-1 and 1-2 above.

[0219] Further study is needed on whether / how to handle the case when each interlace has only 10PRBs in a RB set.

[0220] Further research is needed on whether a transient period issue exists and whether / how to address it.

[0221] Agreement

[0222] Regarding the number and location(s) of additional candidate S-SSB occasions, RAN1 further study the followings.

[0223] Option 1: Reuse legacy NR SL design, and increase the available values ​​in sl-NumSSB-WithinPeriod for each SCS.

[0224] Option 2: Each R16 / R17 NR SL S-SSB slot has K corresponding additional candidate S-SSB occasion, and the gap between them is (pre-)configured.

[0225] Further details such as the value of K, details on gap length, etc. need to be studied.

[0226] Option 3: The number and location(s) of additional candidate S-SSB occasions are separately (pre-)configured.

[0227] Option 4: Introduce M contiguous candidate S-SSB occasions in one S-SSB period.

[0228] Option 5: the number of candidate S-SSB occasions is (pre-)configured, and locations are determined based on the (pre-)configured number.

[0229] Agreement

[0230] Regarding additional candidate S-SSB occasions

[0231] During the same S-SSB period, RAN1 further studied the followings.

[0232] 1. Only when R16 / R17 S-SSB transmission fails, the terminal equipment will attempt to transmit on all or some of the additional candidate S-SSB occasion(s) only when it fails to transmit on R16 / R17 S-SSB occasion(s)

[0233] 2. The terminal device attempts to transmit on all additional candidate S-SSB occasion(s)regardless of whether or not it transmitted on R16 / R17 S-SSB occasion(s)

[0234] 3. The terminal device can attempt to transmit on all or some of additional candidate S-SSB occasion(s)regardless of whether or not it transmitted on R16 / R17 S-SSB occasion(s).

[0235] 4. Upon LBT failure on a (candidate) S-SSB occasion, a UE attempts to transmit on the subsequent additional candidate S-SSB occasion if within a period S-SSB transmission has not been transmitted in any prior occasions.

[0236] Agreement

[0237] Regarding S-SSB, RAN1 further study the following:

[0238] How to transmit S-SSB when a SL BWP contains multiple RB sets.

[0239] RAN1#112

[0240] Agreement

[0241] For S-SSB transmission within 1 RB set, down-select to one or more of the following for 15kHz and 30kHz SCS.

[0242] Option 1-1: Using interlaced RB transmission for all of S-PSS / S-SSS / PSBCH.

[0243] Further study is needed: whether / how to handle the case when each interlace has only 10PRBs in a RB set, egwhether 1 or 2 interlaces will be used for S-SSB.

[0244] Option 3-1: Transmit S-PSS / S-SSS / PSBCH N times by repetition in frequency domain, and there is a gap between the repetition(s) to meet OCB requirement.

[0245] Details that require further study include, for example, whether the length of gap between repetitions is (pre-)configured or pre-defined, value of N (eg, N=2), how to reduce PAPR, etc.

[0246] Further study needed: gap of 0.

[0247] Option A: Apply OCB exemption to all of S-PSS / S-SSS / PSBCH.

[0248] Continue studying how to meet the minimum 2MHz requirements under 15kHz SCS.

[0249] Agreement

[0250] Support one or more of the following options (Down-select one or support both of the followings:).

[0251] Option 1: Additional candidate S-SSB occasions are excluded from resource pool.

[0252] Option 2: Additional candidate S-SSB occasions belong to resource pool.

[0253] Note: Companies are encouraged to consider aspects including: S-SSB resource overhead, Tx / Rx UE behavior (eg, whether any blind detection in Option 2), applicable scenarios, etc.

[0254] Agreement

[0255] RAN1 further study the followings.

[0256] Whether / how to maintain a COT when the COT contains multiple RB sets and includes S-SSB slot(s), e.g., whether to transmit S-SSB repetitions in more than one RB set, etc.

[0257] RAN1#112bis-e

[0258] Working assumption

[0259] Additional candidate S-SSB occasions are excluded from the resource pool.

[0260] Agreement

[0261] When the SL-BWP contains multiple RB sets, study the followings.

[0262] When UE attempts to transmit S-SSB in a S-SSB occasion (eg, R16 / 17 S-SSB occasion, R18 additional candidate S-SSB occasion)

[0263] UE may transmit S-SSB repetition in more than one RB set (Alt 1: UE may transmit S-SSB repetition in more than one RB set).

[0264] Details such as the location of such S-SSB repetition(s) (eg, (pre-)configured and / or pre-defined), whether / how to address potential power reduction and / or potential fluctuation of PSBCH-RSRP require further study.

[0265] Further study is needed: the relationship with UE's COT.

[0266] Further study is needed: the scenario that UE may or may not transmit S-SSB repetition in more than one RB set.

[0267] Note: whether UE can transmit S-SSBs over non-contiguous RB sets is subject to RAN4's reply, details can be found in RAN1's ​​LS to RAN4 in R1-2304218.

[0268] Agreement

[0269] For S-SSB transmission within 1RB set, for 15kHz and 30kHz SCS, Alt6 is supported.

[0270] Alt 6: Support both Option 3-1 (revised) and Option B, and enable one of them by (pre-)configuration.

[0271] Note: the options are as below.

[0272] Option 1-1: Using interlaced RB transmission for all of S-PSS / S-SSS / PSBCH.

[0273] Further study is needed: whether / how to handle the case when each interlace has only 10PRBs in a RB set, egwhether 1 or 2 interlaces will be used for S-SSB.

[0274] Option 3-1 (revised): Transmit legacy S-PSS / S-SSS / PSBCH N times by repetition in frequency domain, and there is a gap between the repetition(s) to meet OCB requirement.

[0275] Further study is needed on whether the length of gap between repetitions is (pre-)configured or pre-defined, value of N (eg, N=2), whether / how to reduce PAPR.

[0276] Further study needed: gap of 0.

[0277] Option A: Legacy S-SSB.

[0278] Continue studying how to meet the minimum 2MHz requirements under 15kHz SCS for OCB exemption.

[0279] Option B: Legacy S-SSB.

[0280] RAN1 does not pursue further study on how to meet the minimum 2MHz requirements under 15kHz SCS for OCB exemption.

[0281] Note: Option A and B are applicable in region with no OCB requirement, or with OCB exemption.

[0282] Conclusion

[0283] Regarding additional candidate S-SSB occasions, in the same S-SSB period, UE can attempt to transmit on additional candidate S-SSB occasion(s)regardless of whether or not it transmitted on R16 / R17 S-SSB occasion(s)

[0284] RAN1#113

[0285] Agreement

[0286] When the SL-BWP contains multiple RB sets, support the followings.

[0287] When UE attempts to transmit S-SSB in a S-SSB occasion (eg, R16 / 17 S-SSB occasion, R18 additional candidate S-SSB occasion), UE may transmit S-SSB repetition in more than one RB set

[0288] In RAN1#114, you can select one of the following options.

[0289] Alt 1: At least the power for S-SSB transmission on anchor RB set does not change due to the number of used RB sets

[0290] Details that require further study include whether this can be satisfied by (pre-)configuration, whether the power for S-SSB transmission on other RB set(s)also does not change due to the number of used RB sets, etc.

[0291] Alt 2: The power for S-SSB transmission on each RB set does not change due to the number of used RB sets.

[0292] Details such as whether this can be satisfied by (pre-)configuration, etc. require further investigation.

[0293] Further study is needed: The locations of S-SSB repetitions in each RB set are the same as the locations of S-SSB repetitions in the anchor RB set.

[0294] Further research is needed: how to (pre)configure resources for the S-SSB repetitions

[0295] Note: anchor RB set refers to the RB set where S-SSB indicated by sl-AbsoluteFrequencySSB-r16 locates

[0296] Note: whether the UE can transmit S-SSBs over non-contiguous RB sets is subject to RAN4's reply, details can be found in RAN1's ​​LS to RAN4 in R1-2304218, R1-2306198.

[0297] Agreement

[0298] Regarding “Option 3-1(revised):Transmit legacy S-PSS / S-SSS / PSBCH N times by repetition in frequency domain,and there is a gap between the repetition(s)to meet OCB requirement”

[0299] Support

[0300] Alt 3: the value of gap is (pre-)configured, and the value of N is (pre-)configured.

[0301] What needs further study: the value range for gap and N.

[0302] Further research is needed to determine whether N for different RB sets can be different.

[0303] For further study: whether to apply any restriction on sl-AbsoluteFrequencySSB-r16 for 60kHz.

[0304] Further study is needed: whether / how to support reducing PAPR of S-SSB transmission, at least considering the following options.

[0305] Option 1: Use different S-SSB repeats in different To determine the initial scrambling seed of PSBCH and the sequence shift of S-SSS and S-PSS (Option 1: use different across the different S-SSB repetitions to determine the initial scrambling seed of PSBCH, and the sequence shift for S-SSS and S-PSS).

[0306] Option 2: phase adjustment among repetitions.

[0307] Option 3: no specification impact to reduce PAPR.

[0308] Option 4: use S-SSB repetition index to scramble different S-SSB repetition(s).

[0309] Agreement

[0310] Regarding the number and location(s) of additional candidate S-SSB occasions, support, the following options are supported.

[0311] Option 2(12): Each R16 / R17 NR SL S-SSB slot has K corresponding additional candidate S-SSB occasion(s)in different time slot(s), and the gap between them is (pre-)configured.

[0312] Further details are needed for FFS, such as value of K, details on gap length (including possibility of being 0), etc.

[0313] As described above, if the terminal device successfully performs LBT on the S-SSB time slot, the terminal device can map and send S-SSB on the S-SSB time slot. However, in the case of failure to perform LBT on the S-SSB time slot, the behavior of the terminal device is unclear, which may affect the synchronization performance of the side link, and thus cause the terminal device to be unable to synchronize with other terminal devices. For example, if the S-SSB time slot is a first-class S-SSB time slot, and the terminal device does not attempt to send S-SSB on the second-class S-SSB time slot corresponding to the first-class S-SSB time slot, then during the current S-SSB period, the terminal device may not send S-SSB, resulting in the terminal device being unable to synchronize with other terminal devices.

[0314] It should be noted that the failure to perform LBT on the S-SSB time slot may include: the failure to perform LBT on all RB sets of the S-SSB time slot, or the failure to perform LBT on a specific RB set of the S-SSB time slot, or the failure to perform LBT on any one or more RB sets of the S-SSB time slot.

[0315] FIG21 is a schematic flow chart of a wireless communication method provided by an embodiment of the present application to solve the above problem. The method shown in FIG21 can be executed by a terminal device. The method shown in FIG21 can include step S2110.

[0316] Step S2110: If the terminal device fails to perform LBT on part or all of the RB sets in the first S-SSB time slot, the terminal device performs the first operation.

[0317] The first S-SSB time slot may be a resource for transmitting an S-SSB. The first S-SSB time slot may be a first-type S-SSB time slot or a second-type S-SSB time slot. Furthermore, the S-SSB time slot may be an opportunity for transmitting an S-SSB. Therefore, the term "S-SSB time slot" in this application may also be replaced by "S-SSB transmission opportunity." In other words, the first S-SSB time slot may also be replaced by the first S-SSB transmission opportunity.

[0318] The first S-SSB time slot may be any one of a plurality of S-SSB time slots within an S-SSB cycle. Alternatively, the first S-SSB time slot may be a specific S-SSB time slot within an S-SSB cycle. For example, the first S-SSB time slot may be the first S-SSB time slot within the S-SSB cycle. Alternatively, the first S-SSB time slot may be the last S-SSB time slot within the S-SSB cycle.

[0319] It should be noted that all RB sets in the first S-SSB time slot may refer to all RB sets in the first time slot that are configured to be capable of LBT; or, all RB sets contained in the first S-SSB time slot.

[0320] In the event that LBT fails to be performed on part or all of the RB sets of the first S-SSB time slot, the terminal device cannot send S-SSB on part or all of the RB sets of the first S-SSB time slot, which may cause synchronization abnormality. The present application clarifies the behavior of the terminal device (i.e., the first operation), thereby avoiding the problem of abnormal synchronization performance between the terminal device and other devices to a certain extent.

[0321] In some embodiments, if the terminal device fails to perform LBT on all or part of the RB sets in the first S-SSB time slot, the first operation may include: performing LBT on the second S-SSB time slot. Here, performing LBT on the second S-SSB time slot may refer to performing LBT on part or all of the RB sets in the second S-SSB time slot.

[0322] The second S-SSB time slot may be a time slot associated with the first S-SSB time slot. For example, the second S-SSB time slot may be an S-SSB time slot that belongs to the same S-SSB period as the first S-SSB time slot. For another example, the second S-SSB time slot may be a second-type S-SSB time slot corresponding to the first S-SSB time slot. Optionally, the first S-SSB time slot may be a first-type S-SSB time slot, and the second S-SSB time slot may be any second-type S-SSB time slot corresponding to the first S-SSB time slot or a specific second-type S-SSB time slot. Optionally, the first S-SSB time slot may be a second-type S-SSB time slot, and the second S-SSB time slot may also be a second-type S-SSB time slot, and the first S-SSB time slot and the second S-SSB time slot may correspond to the same first-type S-SSB time slot. For example, the second S-SSB time slot may have a time relationship with the first S-SSB time slot. For example, the second S-SSB time slot may be the S-SSB time slot closest to the first S-SSB time slot.

[0323] It should be noted that, when the second S-SSB time slot is a second-type S-SSB time slot, the second S-SSB time slot may be any second-type S-SSB time slot or a specific second-type S-SSB time slot within the S-SSB period. Exemplarily, the second S-SSB time slot may be the first or last second-type S-SSB time slot corresponding to the first-type S-SSB time slot.

[0324] It can be seen from this that based on the present application, when LBT fails to be performed on the first type of S-SSB time slot LBT, the terminal device can perform LBT on one or more S-SSB time slots in the second type of S-SSB time slot.

[0325] It should be noted that if the terminal device successfully performs LBT on the second S-SSB time slot, the terminal device can decide whether to perform LBT on the remaining part or all of the second-type S-SSB time slots based on the implementation.

[0326] In the related art, if the terminal device fails to perform LBT on the first type of S-SSB time slot, that is, the terminal device cannot successfully send S-SSB on the first type of S-SSB time slot, then it is unclear whether the terminal device performs LBT on the second type of S-SSB time slot corresponding to the first type of S-SSB time slot, which may cause some problems. For example, if the terminal device decides not to perform LBT on the second type of S-SSB time slot, the terminal device will not send S-SSB during the current S-SSB cycle, which will directly affect the synchronization performance of the side link, resulting in the terminal device being unable to synchronize with other terminal devices. Based on the present application, in the event that LBT fails to be performed on part or all of the RB sets on the first S-SSB time slot, the terminal device may decide to continue to perform LBT on the second type of S-SSB time slot (i.e., the second S-SSB time slot) corresponding to the first S-SSB time slot, thereby achieving the transmission of S-SSB within the S-SSB cycle as much as possible, and then achieving synchronization of the terminal device with other terminal devices as much as possible.

[0327] It should be noted that if the terminal device performs LBT on part or all of the RB sets in the second S-SSB time slot and multiple RB sets are available, the terminal device can occupy multiple RB sets to send S-SSB in a repeated mapping manner.

[0328] The following describes in detail the technical solution for the terminal device to perform LBT on the second S-SSB time slot when the terminal device fails to perform LBT on all RB sets of the first S-SSB time slot in combination with the example shown in Figure 22. In Figure 22, according to the system configuration / pre-configuration, the frequency domain resources include a total of 4 RB sets, and the IDs of these 4 RB sets are 0, 1, 2, and 3, respectively (represented by RB set 0, RB set 1, RB set 2, and RB set 3 in Figure 22). Among them, the terminal device can send S-SSB on RB set 0, RB set 1, and RB set 2, and there is no transmission and / or reception of S-SSB on RB set 3. That is, RB set 3 is configured not to send S-SSB. In the time domain, an S-SSB cycle contains two sets of S-SSB time slot resources, one set for sending S-SSB and the other for receiving S-SSB.

[0329] It should be noted that all embodiments provided in this application are based on one of the two sets of S-SSB time slot resources. It is understandable that the methods provided in the embodiments of this application can also be implemented for the other set of S-SSB time slot resources.

[0330] As shown in Figure 22, time slot s1 is a first-type S-SSB time slot, and time slots s2, s3, and s4 are second-type S-SSB time slots. In Figure 22, time slot s1 can be the first S-SSB time slot, and time slots s2, s3, or s4 can be the second S-SSB time slot. By default, the terminal device must attempt to send S-SSB in the first-type S-SSB time slot. That is, the terminal device needs to perform LBT on RB set 0, RB set 1, and RB set 2 of time slot s1 to detect whether the resources are available. In Figure 22, the three RB sets of time slot s1 are all occupied / unavailable. Therefore, the terminal device cannot send S-SSB in any RB set corresponding to time slot s1.

[0331] Since the terminal device does not transmit an S-SSB in time slot s1, it can attempt to transmit an S-SSB in at least one of the second-category S-SSB time slots corresponding to time slot s1. The terminal device can first perform LBT on each of the three RB sets in the second-category S-SSB time slot s2. As shown in Figure 22, after detection, the terminal device finds that all three RB sets in time slot s2 are available. It then uses the three RB sets in a repeated mapping manner to transmit an S-SSB in time slot s2.

[0332] The terminal device has already sent an S-SSB on a second-class S-SSB time slot, making up for the loss of not sending an S-SSB in time slot s1. For subsequent second-class S-SSB time slots s3 and s4, the terminal device can decide whether to continue sending S-SSB based on the implementation. For example, the terminal device can continue to try to send S-SSB on time slots s3 and s4. The terminal device can first perform LBT on the three RB sets corresponding to each time slot, and determine whether the corresponding RB set is available based on the LBT detection result, and then map and send S-SSB on the available RB set. Alternatively, the terminal device can decide not to attempt to send any S-SSB on time slots s3 and s4. Then, the terminal device can try to send S-SSB without performing any LBT operation on these two time slots.

[0333] In some embodiments, the terminal device may preferentially perform LBT on the target RB set of the first S-SSB time slot. In other words, the terminal device may preferentially attempt to map and send the S-SSB on the target RB set of the first S-SSB time slot. Alternatively, the terminal device needs to at least attempt to map and send the S-SSB on the target RB set of the first S-SSB time slot. That is, if the S-SSB is successfully sent on the target RB set of the first S-SSB time slot, the terminal device may not perform LBT on other RB sets other than the target RB set in the first S-SSB time slot.

[0334] In some embodiments, the terminal device may preferentially send the S-SSB on the target RB set of the first S-SSB time slot. In other words, the terminal device needs to at least map and send the S-SSB on the target RB set. For example, the terminal device may perform LBT on all RB sets of the first S-SSB time slot. If LBT is successfully performed on the target RB set, the S-SSB is sent on the target RB set. For RB sets other than the target RB set, if LBT is successfully performed, the S-SSB may be sent on the RB set; if LBT fails, it may not be sent on the RB set. Whether to send S-SSB on other RB sets can be decided by the terminal device based on implementation.

[0335] For example, on the frequency domain resources corresponding to time slot s1, the frequency domain resources include N (N>1) RB sets. The terminal device needs to send S-SSB on at least the target RB set. If after performing LBT on the target RB set, it is determined that S-SSB can be sent on the target RB set, then for other RB sets other than the target RB set in the first time slot, the terminal device can perform the following two operations. First, the terminal device performs LBT on at least one RB set in the other RB sets. If the terminal device detects that at least one RB set for performing LBT is available, it sends S-SSB on the at least one RB set. Second, the terminal device performs LBT on any RB set in the other RB sets. If this RB set is not available, the terminal device does not send S-SSB on this RB set.

[0336] The frequency domain position of the target RB set may be known to both the receiver and the sender of the S-SSB. Therefore, the receiver of the S-SSB may also preferentially receive the S-SSB on the target RB set. Optionally, the frequency domain position of the target RB set satisfies one or more of the following: network device configuration, pre-configuration, and pre-setting. That is, the receiver and sender of the S-SSB may determine the position of the target RB set by means of pre-configuration and / or preset values. In some embodiments, the target RB set may also be referred to as an anchor RB set.

[0337] Optionally, the method shown in Figure 21 may further include step S2103. Step S2103 may be performed by the network device and the terminal device.

[0338] In step S2103, the network device sends configuration information to the terminal device, wherein the configuration information can be used to configure or indicate the frequency domain position of the target RB set.

[0339] For the receiving terminal device of S-SSB, since it is not known on which RB set or sets the sending terminal device of S-SSB has sent S-SSB, the receiving terminal device may need to detect / receive S-SSB on all RB sets. On the one hand, this leads to higher power consumption of the receiving terminal, and on the other hand, it also requires the receiving terminal device to have the ability to support full-bandwidth reception. Based on the present application, on the one hand, the receiving terminal device of S-SSB can give priority to receiving S-SSB on the target RB set, thereby avoiding the high power consumption problem caused by the terminal device trying to detect or receive S-SSB on all RB sets. On the other hand, as long as the receiving terminal device has at least the bandwidth receiving capability corresponding to the target RB set, it can detect / receive S-SSB in most scenarios. In other words, based on the present application, low-capability terminal devices (supporting part of the bandwidth in the full bandwidth) can know in advance that they need to receive S-SSB on the target RB set in order to accurately receive S-SSB, thereby achieving synchronization with other terminal devices and further realizing side communication.

[0340] It should be noted that the present application does not limit the frequency domain location of the target RB set. For example, the target RB set may be an RB set located at the center frequency point.

[0341] It should be noted that the target RB set may include one or more RB sets, and this application does not impose any limitation on this.

[0342] In step S2110, some or all of the RB sets in which LBT fails in the first S-SSB time slot may include a target RB set. That is, if LBT fails on the target RB set, the terminal device may perform the first operation. For example, the frequency domain resources corresponding to the first S-SSB time slot may include N RB sets. N is an integer greater than 1. The terminal device needs to at least attempt to send an S-SSB on the target RB set. If LBT fails on the target RB set, the terminal device may perform the first operation.

[0343] It should be noted that when the terminal device successfully performs LBT on the target RB set of the first S-SSB time slot, the terminal device may decide whether to perform the first operation based on the implementation. Take the first operation including performing LBT on the second S-SSB time slot as an example. The terminal device may perform LBT on the second S-SSB time slot or not. Whether to perform LBT on the second S-SSB time slot may depend on the implementation of the terminal device.

[0344] The target RB set is described below in conjunction with Figure 23. In Figure 23, according to the system configuration / pre-configuration, the frequency domain resources include a total of 4 RB sets, and the IDs of these 4 RB sets are 0, 1, 2, and 3, respectively (represented by RB set 0, RB set 1, RB set 2, and RB set 3 in Figure 23). Among them, the terminal device can send S-SSB on RB set 0, RB set 1, and RB set 2, and there is no S-SSB transmission and / or reception on RB set 3. That is, RB set 3 is configured not to send S-SSB.

[0345] The first S-SSB time slot may be time slot s1. As shown in Figure 23, the target RB set is RB set 1 in each S-SSB time slot. The terminal device preferentially performs LBT on RB set 1 in time slot s1. In Figure 23, the terminal device fails to perform LBT on RB set 0 and RB set 2 in time slot s1. The terminal device may decide whether to perform LBT on one or more of time slots s2, s3, and s4, depending on its implementation.

[0346] In some embodiments, LBT may fail to be performed on the target RB set of the first S-SSB time slot, i.e., the terminal device detects that the target RB set of the first S-SSB time slot is unavailable or occupied. That is, some or all of the RB sets described in step S2110 may include the target RB set. In this case, the first operation performed by the terminal device may include performing LBT on one or more RB sets other than the target RB set in the first S-SSB time slot.

[0347] It is understandable that if LBT fails to be performed on the target RB set, the terminal device may perform LBT on one or more RB sets outside the target RB set of the same S-SSB time slot to increase the probability of successful S-SSB transmission. For example, if LBT is successfully performed on a second RB set outside the target RB set of the first S-SSB time slot, the terminal device may send the S-SSB on the second RB set. Alternatively, if LBT fails on the second RB set, the terminal device may not send the S-SSB on the second RB set. This solution is described below in conjunction with Figure 24.

[0348] In Figure 24, according to the system configuration / pre-configuration, the frequency domain resources include a total of four RB sets, and the IDs of these four RB sets are 0, 1, 2, and 3, respectively (represented by RB set 0, RB set 1, RB set 2, and RB set 3 in Figure 24). Among them, the terminal device can send S-SSBs on RB set 0, RB set 1, and RB set 2, and no S-SSBs are sent and / or received on RB set 3. That is, RB set 3 is configured not to send S-SSBs.

[0349] The first S-SSB slot may be slot s1. As shown in Figure 24, the target RB set is RB set 1 in each S-SSB slot. The terminal device fails to perform LBT on RB set 1 in the first S-SSB slot. Therefore, the terminal device performs LBT on RB set 0 and RB set 2 in the first S-SSB slot. As shown in Figure 24, LBT is successful on the RB sets, and the terminal device maps and transmits the S-SSB on RB set 0 in slot s1.

[0350] In some embodiments, LBT is successfully performed on the target RB set of the first S-SSB time slot, but LBT fails on some or all RB sets in the first S-SSB time slot except the target RB set. That is, the some or all RB sets described in step S2110 do not include the target RB set. In this case, the first operation may be determined by the implementation of the terminal device. For example, the terminal device may not perform LBT on other S-SSB time slots of the S-SSB cycle in which the first S-SSB time slot is located. Alternatively, the terminal device may perform LBT on some or all S-SSBs in the other S-SSBs of the S-SSB cycle.

[0351] In some embodiments, if LBT fails to be performed on the target RB set in the first S-SSB time slot, the first operation may include performing LBT on the second S-SSB time slot. For example, even if LBT is successfully performed on RB sets other than the target RB set in the first S-SSB time slot, the terminal device may still perform LBT on the second S-SSB time slot.

[0352] In some embodiments, if LBT fails to be performed on the target RB set in the first S-SSB time slot, but LBT is successfully performed on one or more RB sets in the first S-SSB time slot other than the target RB set (or mapped and sent S-SSB), the terminal device does not need to perform LBT on the second S-SSB time slot. For example, the terminal device may decide whether to perform LBT on the second S-SSB time slot based on implementation.

[0353] Continuing to refer to Figure 24, time slot s1 is the first S-SSB time slot, and time slot s2 can be the second S-SSB time slot. As shown in Figure 24, the terminal device fails LBT on the target RB set of time slot s1. In some embodiments, the terminal device performs LBT on at least one of all RB sets in time slot s2. As shown in Figure 24, since the terminal device performs LBT on time slot s2 and sends S-SSB on 3 RB sets, for time slot s3 and time slot s4, the terminal device can decide whether to perform LBT on time slot s3 and time slot s4 based on implementation. In some embodiments, since the terminal device sends S-SSB on RB set 0 of time slot s1, the terminal device can decide whether to attempt to send S-SSB on time slots s2, s3, and s4 based on implementation.

[0354] In some implementations, the terminal device may preferentially perform LBT on the target RB set of the second S-SSB time slot. For example, as long as the terminal device fails to perform LBT on the target RB set of the first S-SSB time slot, the terminal device needs to perform LBT on the target RB set of the second S-SSB time slot. That is, even if the terminal device successfully performs LBT on RB sets other than the target RB set of the first S-SSB time slot, but fails to perform LBT on the target RB set of the first S-SSB time slot, the terminal device may perform LBT on the target RB set of the second time slot. In other words, the terminal device may send the S-SSB on the target RB set of the S-SSB time slot within the S-SSB period as much as possible. As described above, both the transmitting terminal device and the receiving terminal device of the S-SSB know the time domain position of the target RB set. If the target RB set of the first S-SSB time slot fails to perform LBT, the transmitting terminal device may also perform LBT on the target RB set of the second S-SSB time slot to try to send the S-SSB, thereby facilitating the receiving terminal device to receive the S-SSB on the target RB set of the second S-SSB time slot.

[0355] It should be noted that if the terminal device successfully performs LBT on the target RB set in the second S-SSB time slot, the terminal device can decide whether to perform LBT on other RB sets in the second S-SSB time slot except the target RB set based on the implementation.

[0356] Continuing with reference to FIG24 , time slot s1 is the first S-SSB time slot, and time slot s2 may be the second S-SSB time slot. As shown in FIG24 , the terminal device fails LBT on the target RB set in time slot s1. Therefore, the terminal device preferentially performs LBT on the target RB set in time slot s2 (i.e., RB set 1 in time slot s2). For RB sets other than the target RB set in time slot s2, the terminal device may decide whether to perform LBT on RB set 2 and / or RB set 3 based on the implementation. FIG24 shows that the terminal device decides to perform LBT on RB set 2 and RB set 3.

[0357] In the related art, for the terminal devices with lower capabilities described above, the RB set (i.e., the target RB set) where the receiving terminal device that needs to receive the S-SSB currently resides may not have an S-SSB sent. For the terminal device that sends the S-SSB, the S-SSB may have been sent on an RB set other than the RB set where the receiving terminal device resides. Based on this, the sending terminal device may consider that the S-SSB has been sent in the current S-SSB time slot. Therefore, the receiving terminal device may decide not to send the S-SSB on other S-SSB time slots (e.g., the second type of S-SSB time slots) within the S-SSB cycle. This will result in the receiving terminal device no longer being able to receive the S-SSB within the current S-SSB cycle, thereby having a greater impact on the synchronization performance of the low-capability terminal. In the present application, the terminal device can perform LBT on the target RB set on each S-SSB time slot within the S-SSB cycle to send the S-SSB, thereby making it more likely that the low-capability receiving terminal device will receive the S-SSB on the target RB set, thereby avoiding the degradation of the synchronization performance of the low-capability terminal device as much as possible.

[0358] If LBT fails to be performed on the target RB set of the second S-SSB time slot, the terminal device may perform the first operation on the second S-SSB time slot as the first S-SSB time slot described above. For example, the terminal device may perform LBT on at least one RB set in other RB sets other than the target RB set in the second S-SSB time slot. If LBT is successfully performed on at least one RB set in other RB sets, S-SSB may be sent on the at least one RB set. If LBT fails to be performed on at least one RB set in other RB sets, S-SSB may not be sent on the at least one RB set. Alternatively, the terminal device may perform LBT on a third S-SSB time slot associated with the second S-SSB time slot. In the third S-SSB time slot, the terminal device may also preferentially perform LBT on the target RB set.

[0359] If LBT is successfully performed on the target RB set of the second S-SSB time slot, the terminal device may determine whether to perform LBT on the remaining S-SSB time slots in the S-SSB cycle according to the implementation.

[0360] The following is a detailed description using FIG25 as an example.

[0361] In Figure 25, according to the system configuration / pre-configuration, the frequency domain resources include a total of four RB sets, and the IDs of these four RB sets are 0, 1, 2, and 3, respectively (represented by RB set 0, RB set 1, RB set 2, and RB set 3 in Figure 25). Among them, the terminal device can send S-SSBs on RB set 0, RB set 1, and RB set 2, and no S-SSBs are sent and / or received on RB set 3. That is, RB set 3 is configured not to send S-SSBs. RB set 1 is the target RB set.

[0362] In Figure 25, time slot s1 can be the first S-SSB time slot, and time slot s2 can be the second S-SSB time slot. In some of the above cases, the terminal device performs LBT on RB set 1 of time slot s2. However, performing LBT on RB set 1 of time slot s2 fails. In this case, time slot s2 can be used as the first S-SSB time slot, and time slot s3 can be used as the second S-SSB time slot. In some embodiments, when performing LBT on RB set 1 of time slot s2 fails, the terminal device can perform LBT on time slot s3. Further, the terminal device can preferentially perform LBT on RB set 1 of time slot s3. Since the terminal device successfully performs LBT on RB set 1 of s3, the terminal device can determine whether to perform LBT on time slot s4 according to the implementation. In some embodiments, although LBT fails to be performed on RB set1 of time slot s2, the terminal device successfully performs LBT on RB set0 and RB set1 of time slot s2 and sends S-SSB, that is, the terminal device successfully sends S-SSB on time slot s2, then the terminal device can decide whether to perform LBT on time slot s3 and / or s4 through implementation.

[0363] The number of S-SSB time slots associated with the second S-SSB time slot may be one or more. For example, the second S-SSB time slot may be associated with a first S-SSB time slot set. The first S-SSB time slot set may include one or more S-SSB time slots. For example, the second S-SSB time slot may belong to a first S-SSB period, and the first S-SSB time slot set may include S-SSB time slots preceding the second S-SSB time slot within the first S-SSB period.

[0364] The present application does not limit the type of S-SSB time slots included in the first S-SSB time slot set. For example, in the case where a first-class S-SSB time slot can correspond to K second-class S-SSB time slots, the first S-SSB time slot set can include the first-class S-SSB time slot and part or all of the K second-class S-SSB time slots, and the second time slot can be any one of the K second-class S-SSB time slots. Exemplarily, the first S-SSB time slot set can include the first-class S-SSB time slot; or, the first S-SSB time slot set can include the first-class S-SSB time slot and the second-class S-SSB time slot. The second-class S-SSB time slot included in the first S-SSB time slot set can be the second-class S-SSB time slot that precedes the second S-SSB time slot.

[0365] Whether to perform LBT on the second S-SSB time slot can be determined based on the LBT situation of the first S-SSB time slot set associated with the second S-SSB time slot. For example, if the terminal device fails to perform LBT on part or all of the RB sets of each S-SSB time slot in the first S-SSB time slot set, the terminal device can perform LBT on the second S-SSB time slot. In other words, when all S-SSB time slots in the first S-SSB time slot set have LBT failures, the terminal device can perform LBT on the second S-SSB time slot. Alternatively, if the terminal device fails to perform LBT on part or all of the RB sets of any S-SSB time slot in the first S-SSB time slot set, the terminal device can perform LBT on the second S-SSB time slot. In other words, if any S-SSB time slot in the first S-SSB time slot set has LBT failures, the terminal device can perform LBT on the second S-SSB time slot. For example, if the terminal device fails LBT on the first type of S-SSB time slot in the first S-SSB time slot set, the terminal device can perform LBT on the second S-SSB time slot.

[0366] For example, an S-SSB synchronization cycle may include time slot s1, time slot s2, time slot s3, and time slot s4. Time slot s2, s3, or s4 may be used as the second S-SSB time slot. If the second S-SSB time slot is time slot s3, the terminal device may determine whether to perform LBT on time slot s3 and send S-SSB according to the following implementation method. As an implementation method, the first S-SSB time slot may be time slot s1, and the terminal device may determine whether to perform LBT on time slot s3 based on whether the LBT performed on time slot s1 is successful. As another implementation method, the first S-SSB time slot may be time slot s2, and the terminal device may determine whether to perform LBT on time slot s3 based on whether the LBT performed on time slot s1 is successful. As another implementation method, the first S-SSB time slot set may include time slot s1 and time slot s2, and the terminal device may determine whether to perform LBT on time slot s3 based on whether the LBT performed on the first S-SSB time slot set is successful. If the second S-SSB time slot is time slot s4, the terminal device may perform operations similar to those for time slot s3. As an implementation, whether to perform LBT on time slot s4 may be determined based on whether LBT was successfully performed on time slot s1. As another implementation, the first S-SSB time slot set may include time slot s1, time slot s2, and time slot s3, and the terminal device may determine whether to perform LBT on time slot s4 based on whether LBT was successfully performed on time slots s1, time slots s2, and time slots s3. The terminal device may also determine whether to perform LBT and S-SSB transmission on time slots s3 or s4, depending on the implementation.

[0367] Exemplarily, if LBT fails on all RB sets of each S-SSB time slot in the first S-SSB time slot set, the terminal device may perform LBT on the second S-SSB time slot. That is, if LBT fails on all RB sets of each S-SSB time slot in all S-SSB time slots in the first S-SSB time slot set, the terminal device may perform LBT on the second S-SSB time slot.

[0368] Exemplarily, if the LBT of the target RB set of each S-SSB time slot in the first S-SSB time slot set fails, the terminal device may perform LBT on the second S-SSB time slot. That is, as long as the LBT of the target RB set of all S-SSB time slots in the first S-SSB time slot set fails, the terminal device may perform LBT on the second S-SSB time slot. That is, whether to perform LBT on the second S-SSB time slot may not take into account the LBT results of other RB sets other than the target RB set on the S-SSB time slots in the first S-SSB time slot set.

[0369] In some embodiments, the second S-SSB time slot may belong to a second S-SSB time slot set. The S-SSB time slots in the second S-SSB time slot set may all be second-category S-SSB time slots. The above-mentioned performing LBT on the second S-SSB time slot may include: performing LBT on one or more S-SSB time slots in the second S-SSB time slot set. In other words, in the case where LBT needs to be performed on the second S-SSB time slot, the terminal device may perform LBT on one or more S-SSB time slot sets in the second S-SSB time slot set.

[0370] It should be noted that the first S-SSB time slot set and the second S-SSB time slot set may belong to the same S-SSB period.

[0371] The technical solutions related to the first S-SSB time slot set and the second S-SSB time slot set can be implemented in combination. For example, an S-SSB cycle may include L+H S-SSB time slots. L may indicate the number of S-SSB time slots in the first S-SSB time slot set; H may indicate the number of S-SSB time slots in the second S-SSB time slot set. Alternatively, the first S-SSB time slot set and the second S-SSB time slot set may form an S-SSB time slot set group, and the same S-SSB cycle may include P groups of S-SSB time slot set groups. That is, an S-SSB cycle may include P×(L+H) S-SSB time slots. L may indicate the number of S-SSB time slots in the first S-SSB time slot set in an S-SSB time slot set group; H may indicate the number of S-SSB time slots in the second S-SSB time slot set in an S-SSB time slot set group; and P may indicate the number of S-SSB time slot set groups.

[0372] The first S-SSB time slot set and the second S-SSB time slot set are described below with reference to Figures 26A and 26B.

[0373] As shown in FIG26A , the first S-SSB cycle includes four S-SSB time slot set groups, i.e., P=4. One S-SSB time slot set group includes one first-type S-SSB time slot and two second-type S-SSB time slots. For example, in one S-SSB time slot set group, the first S-SSB time slot set may include one first-type S-SSB time slot; the second S-SSB time slot set may include two second-type S-SSB time slots, i.e., L=1 and H=2. Alternatively, in one S-SSB time slot set group, the first S-SSB time slot set may include one first-type S-SSB time slot and one second-type S-SSB time slot; the second S-SSB time slot set may include another second-type S-SSB time slot, i.e., L=2 and H=1.

[0374] As shown in Figure 26B, the first S-SSB cycle includes four S-SSB time slot set groups, i.e., P = 4. One S-SSB time slot set group includes two first-type S-SSB time slots and one second-type S-SSB time slot. This one second-type S-SSB time slot corresponds to two first-type S-SSB time slots. Exemplarily, in one S-SSB time slot set group, the first S-SSB time slot set may include two first-type S-SSB time slots; the second S-SSB time slot set may include one second-type S-SSB time slot, i.e., L = 2 and H = 1.

[0375] In some embodiments, within an S-SSB cycle, the terminal device can decide whether to send S-SSB (or attempt to send LBT) in the next H S-SSB time slots based on whether S-SSB is successfully sent in the first L S-SSB time slots. For example, if no S-SSB is sent in the first L S-SSB time slots (LBT is performed to detect that there are no available resources), the terminal device needs to send S-SSB in at least one time slot within the next H time slots (LBT is performed to detect whether S-SSB can be sent). Alternatively, if S-SSB is successfully sent in at least one time slot within the first L S-SSB time slots, the terminal device can decide whether to send S-SSB in the next H time slots based on the implementation. Continuing to refer to Figure 26B, the terminal device can decide whether to send S-SSB in the next H = 1 S-SSB time slot based on whether S-SSB is successfully sent in the first L = 2 S-SSB time slots in a group of S-SSB time slot sets.

[0376] In some embodiments, the interval between first-type S-SSB time slots may be indicated by a first interval. The interval between a first-type S-SSB time slot and a second-type S-SSB time slot may be indicated by a second interval. The interval between multiple second-type S-SSB time slots of the same first-type S-SSB time slot may be indicated by a third interval. One or more of the first interval, the second interval, and the third interval may be configured, preconfigured, or pre-set by the network device. For example, the configuration information in step S2103 may be used to configure one or more of the first interval, the second interval, and the third interval.

[0377] It should be noted that the second interval and the third interval can be the same, that is, the second interval can be represented by the third interval; or the third interval can be represented by the second interval.

[0378] It should be noted that the second interval and / or the third interval may be greater than or equal to 0. For example, the second interval and / or the third interval may be an integer greater than or equal to 0.

[0379] It should be noted that this application does not limit the size of the first interval, the second interval, and the third interval. For example, the first interval can be larger than the second interval or the third interval. Alternatively, the first interval can be smaller than the second interval or the third interval.

[0380] The following describes the first, second, and third intervals using Figures 26A, 26B, and 26C. In Figures 26A and 26C, a set of S-SSB time slot resources in an S-SSB cycle includes four first-class S-SSB time slots, with each first-class S-SSB time slot correspondingly configured / preconfigured with two second-class S-SSB time slots. The second and third intervals are both represented by interval G2, and one interval is represented by interval G1. In Figure 26B, a set of S-SSB time slot resources in an S-SSB cycle includes four first-class S-SSB time slots, with each two first-class S-SSB time slots correspondingly configured / preconfigured with one second-class S-SSB time slot. The second and third intervals are both represented by interval G2. The first interval includes interval G12 between multiple first-class S-SSB time slots corresponding to the same second-class S-SSB time slot, and interval G1 between multiple first-class S-SSB time slots corresponding to different second-class S-SSB time slots.

[0381] When configuring / preconfiguring the second-type S-SSB time slot, it is necessary to configure, preconfigure, or preset parameters 1 and 2. Parameter 1 can be used to indicate that one first-type S-SSB time slot corresponds to Q second-type S-SSB time slots. Parameter 2 can be used to indicate the interval G2 between the first-type S-SSB time slot and its corresponding second-type S-SSB time slot. Parameter 2 can indicate 0 or a non-zero number. In Figures 26A, 26B, and 26C, a set of S-SSB resources within an S-SSB period includes four first-type S-SSBs, and the interval between the first-type S-SSB time slot and its corresponding second-type S-SSB time slot is G2.

[0382] As shown in FIG26A , interval G1 is greater than interval G2. A first-type S-SSB time slot and a second-type S-SSB time slot corresponding to the first-type S-SSB time slot may be continuous. A second-type S-SSB time slot may be interspersed between first-type S-SSB time slots.

[0383] As shown in Figure 26C, interval G1 is smaller than interval G2. The first type S-SSB time slot and the second type S-SSB time slot corresponding to the first type S-SSB time slot may be discontinuous. That is, other first type S-SSB time slots may exist between the first type S-SSB time slot and the second type S-SSB time slot corresponding to the first type S-SSB time slot. No second type S-SSB time slot may be interspersed between the first type S-SSB time slots. The second type S-SSB time slot may be located in the time domain after all the first type S-SSB time slots in the same S-SSB period.

[0384] In some embodiments, the terminal device may perform the first operation based on one or more of the following information: the scenario the terminal device is in; the type of service the terminal device is performing. For example, the terminal device may determine the first operation based on the scenario and / or service type.

[0385] Optionally, the terminal device may decide whether to send S-SSB on the second S-SSB time slot (i.e., perform LBT) based on implementation.

[0386] In some embodiments, the first S-SSB time slot may belong to a first S-SSB synchronization period. The first S-SSB synchronization period may include a COT. The first S-SSB synchronization period including the COT may include: the first S-SSB synchronization period partially or completely overlaps with the COT.

[0387] The terminal device may send or attempt to send an S-SSB on the first RB set included in the COT. For example, the terminal device may perform LBT on the first RB set. If LBT is successful, the terminal device may send an S-SSB on the first RB set.

[0388] It should be noted that the present application does not limit the type of S-SSB time slot to which the first RB set belongs. For example, the first RB set may belong to a first type of S-SSB time slot or a second type of S-SSB time slot.

[0389] As shown in Figure 27, COT1 includes time slot s1 in the time domain. COT1 includes RB set 0 and RB set 1 in the frequency domain. When the terminal device attempts to send an S-SSB in time slot s1, it needs to try to send an S-SSB in at least RB set 0 and RB set 1 in the frequency domain. As shown in Figure 27, in time slot s1, the terminal device plans to try to send an S-SSB in RB set 0, RB set 1, and RB set 2 according to the above embodiment provided by the present application. Therefore, the terminal device only needs to perform LBT on these three RB sets and then send an S-SSB in the original configuration / pre-configuration method.

[0390] As shown in Figure 28, COT1 includes the second type of S-SSB time slot in the time domain. The terminal device has successfully sent an S-SSB on the RB set (including the target RB set) in the first type of S-SSB time slot s1. According to the configuration / pre-configured settings, the terminal device can decide whether to attempt to send an S-SSB on time slots s2, s3, and s4 through implementation. Since COT1 includes time slot s3, the terminal device can attempt to send an S-SSB on time slot s3. Furthermore, since COT1 includes RB set 0 and RB set 1, the terminal device can perform LBT and send an S-SSB on these two RB sets.

[0391] If the terminal device does not send S-SSB on the first RB set, it may cause the COT to be discontinuous in the first RB set. During this discontinuous period, the resources corresponding to the COT may be preempted by devices of other systems, causing the terminal device to lose the resources corresponding to the COT, and thus causing the terminal device to be unable to continue transmitting data. The present application can perform LBT and send S-SSB on the first RB set included in the COT, thereby occupying the resources corresponding to the COT and avoiding preemption of other systems.

[0392] In some embodiments, the first RB set may be an RB set configured or preconfigured not to transmit an S-SSB. Alternatively, the first RB set is not an RB set configured or preconfigured to require the terminal device to attempt to transmit an S-SSB. That is, even if an RB set is configured or preconfigured not to transmit an S-SSB, the terminal device may attempt to transmit an S-SSB on the RB set if the COT includes the RB set.

[0393] It should be noted that, in some embodiments, if the first RB set is configured or pre-configured as an RB set that does not send S-SSB, the terminal device can decide whether to attempt to send S-SSB on the first RB set based on the implementation.

[0394] As shown in Figure 29, when the COT includes time slot s1 in the time domain, but RB set 3 included in the frequency domain is not the RB set that the terminal device is configured / preconfigured to attempt to transmit, in some embodiments, the terminal device may additionally attempt to perform LBT and S-SSB transmission on RB set 3 corresponding to time slot s1. In some embodiments, the terminal device may determine, through implementation, whether to attempt to transmit S-SSB on RB set 3 corresponding to time slot s1.

[0395] In some embodiments, the terminal device may perform LBT on all RB sets included in the COT. For example, the terminal device may perform LBT on all RB sets included in the COT in the first S-SSB synchronization period, thereby avoiding the loss of resources corresponding to the COT in the first S-SSB synchronization period.

[0396] For example, the first RB set may belong to the first BWP. The first BWP may include N RB sets. If the COT includes Q (Q ≤ N) RB sets in the frequency domain, the terminal device may perform LBT on these Q RB sets in the corresponding S-SSB time slot. If it is detected that the resources of the Q RB sets are available, the terminal device may send S-SSB on these Q RB sets corresponding to the time slot. If at least one of the Q RB sets is occupied, the terminal device may send S-SSB on other RB sets where LBT is successful.

[0397] As shown in Figure 30, the terminal device has successfully sent an S-SSB on the RB set (including the target RB set) in the first-class S-SSB time slot s1. According to the configuration / pre-configuration settings, the terminal device can decide whether to attempt to send an S-SSB in time slots s2, s3, and s4 through implementation. Since COT1 includes the second-class S-SSB time slot s3 in the time domain, the terminal device can attempt to send an S-SSB in time slot s3. Furthermore, since COT1 includes RB set 0, RB set 1, RB set 2, and RB set 3, the terminal device can perform LBT and send an S-SSB on these four RB sets.

[0398] As shown in Figure 31, the terminal device has successfully sent an S-SSB on the RB set (including the target RB set) on the first type of S-SSB time slot s1. According to the configuration / pre-configuration settings, the terminal device can decide whether to attempt to send an S-SSB on time slots s2, s3, and s4 through implementation. Since COT1 includes the second type of S-SSB time slots s3 and s4 in the time domain, the terminal device can attempt to send an S-SSB on time slots s3 and s4. In addition, since COT1 includes RB set 0, RB set 1, RB set 2, and RB set 3, the terminal device needs to perform LBT on these four RB sets and send an S-SSB.

[0399] In some embodiments, the first RB set may belong to a first BWP. The terminal device may perform LBT on all RB sets included in the first BWP. The first BWP may also be replaced by the first bandwidth and the first carrier.

[0400] For example, the first BWP may include N RB sets. The COT includes Q RB sets in the first BWP, where Q is less than or equal to N. Both Q and N can be positive integers. On the first BWP, the terminal device can perform LBT on all N RB sets in the first BWP. If resources are available in the N RB sets, the terminal device can send an S-SSB on the corresponding RB set. Alternatively, if at least one of the N RB sets is occupied, the terminal device can send an S-SSB on the remaining RB sets.

[0401] After the terminal device performs LBT on the first S-SSB time slot, if LBT is successfully performed on Y RB sets in the first S-SSB time slot, the terminal device can further determine on which RB set or sets of the Y RB sets to transmit the S-SSB based on the transmit power of the S-SSB transmitted on the Y RB sets. Y can be an integer greater than 1.

[0402] In some embodiments, the terminal device may transmit an S-SSB on some or all of the Y RB sets based on a first power. The first power is the sum of the transmit powers of the S-SSBs transmitted on all Y RB sets. In other words, the first power may be the total power of the S-SSBs planned to be transmitted on the Y RB sets in the first S-SSB time slot.

[0403] The terminal device can determine which one or more of the Y RB sets to send the S-SSB based on the comparison result between the first power and the maximum restricted transmit power. For example, when the first power is less than or equal to the maximum restricted transmit power value, the terminal device can send the S-SSB on all RB sets in the Y RB sets. For another example, when the first power is greater than or equal to the maximum restricted transmit power value, the terminal device can send the S-SSB on some RB sets in the Y RB sets. The sum of the transmit powers of the S-SSBs sent on some RB sets in the Y RB sets is less than or equal to the maximum restricted transmit power value.

[0404] It can be understood that if the first power is greater than or equal to the maximum limited transmit power, the terminal device can discard Q RB sets out of the Y RB sets, that is, not map and send S-SSBs on the Q RB sets, so that the total power of mapping and sending S-SSBs on YQ RB sets is less than or equal to the maximum limited transmit power. Wherein, Q can be a positive integer greater than 0.

[0405] The terminal device can determine whether to discard the RB set based on the priority associated with the RB set. In the case where the priority corresponding to the RB set is higher, the terminal device gives priority to the RB set for mapping and sending S-SSB. In the case where the priority corresponding to the RB set is lower, the terminal device gives priority to discarding the RB set. For example, the terminal device can start discarding the RB set with the lowest priority. If the total transmit power of the remaining RB sets is still greater than or equal to the maximum limit transmit power, the terminal device can continue to select the RB set with the lowest priority from the remaining RB sets to discard until the total transmit power of the remaining RB sets is less than or equal to the maximum limit transmit power. Alternatively, the terminal device can start selecting from the RB set with the highest priority. When the number of selected RB sets has reached YQ, the terminal device can stop selecting and use the selected RB set to map and send S-SSB.

[0406] It should be noted that, for RB sets with the same priority, the terminal device may select or discard the RB set in a random manner, or the terminal device may determine to select or discard the RB set based on other information such as identification information and frequency.

[0407] In some embodiments, the priority may be related to one or more of the following information about the RB set: whether the RB set is a target RB set and whether the RB set belongs to a COT. For example, the priority may satisfy one or more of the following: the priority corresponding to the target RB set is higher than the priority corresponding to a non-target RB set, the priority corresponding to the target RB set is higher than the priority of an RB set belonging to a COT, the priority of an RB set belonging to a COT is higher than the priority of an RB set not belonging to a COT, and the priority of an RB set belonging to a COT is higher than the priority corresponding to the target RB set.

[0408] For example, the priority order from high to low can be: target RB set > RB set belonging to COT > RB set that is neither a target RB set nor a COT. Alternatively, the priority order from high to low can be: target RB set > non-target RB set. Alternatively, the priority order from high to low can be: RB set belonging to COT > RB set not belonging to COT.

[0409] It should be noted that RB sets between the COT and the target RB set can have a higher priority than other RB sets that are neither the target nor the COT. For example, after selecting the COT and target RB sets, a random selection can be made from the remaining RB sets, or an RB set between the COT and target RB sets can be prioritized from the remaining RB sets.

[0410] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, so for parts not described in detail, reference can be made to the above method embodiments.

[0411] 32 is a schematic structural diagram of a terminal device 3200 provided in an embodiment of the present application. The terminal device 3200 may include an execution unit 3210.

[0412] The execution unit 3210 is used to perform a first operation if the terminal device fails to perform LBT on part or all of the RB sets in the first S-SSB time slot.

[0413] In some embodiments, the terminal device is further configured to: preferentially perform LBT on a target RB set of the first S-SSB time slot.

[0414] In some embodiments, the frequency domain position of the target RB set satisfies one or more of the following: network device configuration, pre-configuration, and pre-setting.

[0415] In some embodiments, failure to perform LBT on some or all RB sets in the first S-SSB time slot includes: failure to perform LBT on the target RB set in the first S-SSB time slot; the first operation includes: performing LBT on one or more RB sets other than the target RB set in the first S-SSB time slot.

[0416] In some embodiments, failure to perform LBT on part or all of the RB sets in the first S-SSB time slot includes: failure to perform LBT on the target RB set in the first S-SSB time slot; the first operation includes: performing LBT on the second S-SSB time slot; wherein the second S-SSB time slot is associated with the first S-SSB time slot.

[0417] In some embodiments, performing LBT on the second S-SSB time slot includes: preferentially performing LBT on a target RB set in the second S-SSB time slot.

[0418] In some embodiments, the first S-SSB time slot belongs to a first S-SSB time slot set, the second S-SSB time slot is associated with the first S-SSB time slot set, and the failure to perform LBT on part or all of the RB sets of the first S-SSB time slot includes: the failure to perform LBT on part or all of the RB sets of each S-SSB time slot in the first S-SSB time slot set; or the failure to perform LBT on part or all of the RB sets of any S-SSB time slot in the first S-SSB time slot set.

[0419] In some embodiments, LBT failure of some or all RB sets of each S-SSB time slot includes LBT failure of target RB sets of each S-SSB time slot.

[0420] In some embodiments, the second S-SSB time slot belongs to a second S-SSB time slot set, and performing LBT on the second S-SSB time slot includes: performing LBT on one or more S-SSB time slots in the second S-SSB time slot set.

[0421] In some embodiments, the first set of S-SSB time slots and the second set of S-SSB time slots belong to the same S-SSB synchronization period.

[0422] In some embodiments, the first S-SSB time slot set and the second S-SSB time slot set constitute an S-SSB time slot set group, and the same S-SSB synchronization period includes P groups of S-SSB time slot set groups, where P is a positive integer.

[0423] In some embodiments, the first S-SSB time slot set includes first-class S-SSB time slots; or the first S-SSB time slot set includes first-class S-SSB time slots and second-class S-SSB time slots; and the second S-SSB time slot set includes second-class S-SSB time slots; wherein the second-class S-SSB time slots are supplementary candidate time slots for the first-class S-SSB time slots.

[0424] In some embodiments, the first S-SSB time slot is a first-category S-SSB time slot or a second-category S-SSB time slot; the second S-SSB time slot is a second-category S-SSB time slot; wherein the second-category S-SSB time slot is a supplementary candidate time slot for the first-category S-SSB time slot.

[0425] In some embodiments, one or more of the following parameters are configured, preconfigured or pre-set by the network device: a first interval, used to indicate the interval between first-class S-SSB time slots; a second interval, used to indicate the interval between a first-class S-SSB time slot and a second-class S-SSB time slot corresponding to the first-class S-SSB time slot; and a third interval, used to indicate the interval between multiple second-class S-SSB time slots corresponding to the same first-class S-SSB time slot.

[0426] In some embodiments, the first S-SSB time slot and the second S-SSB time slot belong to the same S-SSB synchronization period.

[0427] In some embodiments, the execution unit 3210 is used to: the terminal device performs the first operation according to one or more of the following information: the scenario in which the terminal device is located; the type of business executed by the terminal device.

[0428] In some embodiments, the first S-SSB time slot belongs to the first S-SSB synchronization period. When the first S-SSB synchronization period includes the channel occupancy time COT, the terminal device is further used to: perform LBT on the first RB set included in the COT.

[0429] In some embodiments, the first RB set is a RB set configured or preconfigured to not send S-SSBs.

[0430] In some embodiments, performing LBT on a first set of RBs included in the COT includes: the terminal device performing LBT on all sets of RBs included in the COT.

[0431] In some embodiments, the first RB set belongs to a first BWP, and performing LBT on the first RB set included in the COT includes: performing LBT on all RB sets included in the first BWP.

[0432] In some embodiments, the terminal device is also used to: if the terminal device successfully performs LBT on Y RB sets in the first S-SSB time slot, then send S-SSB on part or all of the Y RB sets according to the first power; wherein the first power is the sum of the transmission powers of the S-SSBs sent on all Y RB sets, and Y is an integer greater than 1.

[0433] In some embodiments, S-SSB is sent on some or all of the Y RB sets according to the first power, including: when the first power is less than or equal to the maximum restricted transmit power value, the terminal device sends S-SSB on all of the Y RB sets; and / or when the first power is greater than or equal to the maximum restricted transmit power value, S-SSB is sent on some of the Y RB sets; wherein the sum of the transmit powers of the S-SSBs sent on some of the Y RB sets is less than or equal to the maximum restricted transmit power value.

[0434] In some embodiments, sending S-SSB on some RB sets among Y RB sets includes: preferentially sending S-SSB on RB sets with high priority among the Y RB sets; wherein the priority is related to one or more of the following information of the RB set: whether the RB set is a target RB set; whether the RB set belongs to COT.

[0435] In some embodiments, the priority satisfies one or more of the following: the priority corresponding to the target RB set is higher than the priority corresponding to the non-target RB set; the priority corresponding to the target RB set is higher than the priority of the RB set belonging to the COT; and the priority of the RB set belonging to the COT is higher than the priority of the RB set not belonging to the COT.

[0436] In an optional embodiment, the execution unit 3210 may be a processor 3410. The terminal device 3200 may further include a memory 3420 and a transceiver 3430, as specifically shown in FIG34 .

[0437] 33 is a schematic structural diagram of a network device 3300 provided in an embodiment of the present application. The network device 3300 includes a sending unit 3310.

[0438] The sending unit 3310 is used to send configuration information to the terminal device; wherein the configuration information is used to configure one or more of the following information: first information, used to indicate the frequency domain position of the target RB set, the target RB set is the RB set in the S-SSB time slot where the terminal device preferentially performs LBT; a first interval, used to indicate the interval between the first type S-SSB time slots; a second interval, used to indicate the interval between the first type S-SSB time slot and the second type S-SSB time slot, the second type S-SSB time slot is a supplementary candidate time slot for the first type S-SSB time slot; and a third interval, used to indicate the interval between multiple second type S-SSB time slots corresponding to the same first type S-SSB time slot.

[0439] In an optional embodiment, the sending unit 3310 may be a transceiver 3430. The network device 3300 may further include a processor 3410 and a memory 3420, as specifically shown in FIG34 .

[0440] Figure 34 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 34 indicate that the unit or module is optional. Apparatus 3400 may be used to implement the method described in the above method embodiment. Apparatus 3400 may be a chip, a terminal device, or a network device.

[0441] The device 3400 may include one or more processors 3410. The processor 3410 may support the device 3400 to implement the method described in the method embodiment above. The processor 3410 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0442] The apparatus 3400 may further include one or more memories 3420. The memories 3420 store programs that can be executed by the processor 3410, causing the processor 3410 to perform the methods described in the above method embodiments. The memories 3420 may be independent of the processor 3410 or integrated into the processor 3410.

[0443] The apparatus 3400 may further include a transceiver 3430. The processor 3410 may communicate with other devices or chips via the transceiver 3430. For example, the processor 3410 may transmit and receive data with other devices or chips via the transceiver 3430.

[0444] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0445] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0446] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0447] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0448] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0449] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0450] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0451] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0452] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0453] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0454] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0455] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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

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

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

[0459] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

Claims

1. A wireless communication method, characterized in that: include: If the terminal device fails to perform listen-before-talk (LBT) on part or all of the resource block RB sets in the first side synchronization signal block S-SSB time slot, the terminal device performs the first operation.

2. The method according to claim 1, characterized in that The method further comprises: The terminal device preferentially performs LBT on the target RB set of the first S-SSB time slot.

3. The method according to claim 2, characterized in that The frequency domain position of the target RB set satisfies one or more of the following: network device configuration, pre-configuration, and pre-setting.

4. The method according to claim 2 or 3, characterized in that: The failure to perform LBT on some or all RB sets of the first S-SSB time slot includes: failure to perform LBT on a target RB set of the first S-SSB time slot; The first operation includes performing LBT on one or more RB sets other than the target RB set on the first S-SSB time slot.

5. The method according to any one of claims 2 to 4, characterized in that: The failure to perform LBT on some or all of the RB sets of the first S-SSB time slot includes: failure to perform LBT on the target RB set of the first S-SSB time slot; The first operation includes: performing LBT on the second S-SSB time slot; The second S-SSB time slot is associated with the first S-SSB time slot.

6. The method according to any one of claims 5, characterized in that The performing LBT on the second S-SSB time slot comprises: LBT is preferentially performed on the target RB set of the second S-SSB time slot.

7. The method according to claim 5 or 6, characterized in that: The first S-SSB time slot belongs to a first S-SSB time slot set, the second S-SSB time slot is associated with the first S-SSB time slot set, and the failure to perform LBT on part or all of the RB sets of the first S-SSB time slot includes: Performing LBT on part or all of the RB sets of each S-SSB time slot in the first S-SSB time slot set fails; or Performing LBT on part or all of the RB sets of any S-SSB time slot in the first S-SSB time slot set fails.

8. The method according to claim 7, characterized in that The failure of LBT of part or all of the RB sets of each S-SSB time slot includes the failure of LBT of the target RB sets of each S-SSB time slot.

9. The method according to claim 7 or 8, characterized in that: The second S-SSB time slot belongs to a second S-SSB time slot set, and performing LBT on the second S-SSB time slot includes: performing LBT on one or more S-SSB time slots in the second S-SSB time slot set.

10. The method according to claim 9, characterized in that The first S-SSB time slot set and the second S-SSB time slot set belong to the same S-SSB synchronization period.

11. The method according to claim 10, characterized in that The first S-SSB time slot set and the second S-SSB time slot set constitute an S-SSB time slot set group, and the same S-SSB synchronization period includes P groups of the S-SSB time slot set groups, where P is a positive integer.

12. The method according to any one of claims 9 to 11, characterized in that: The first set of S-SSB time slots includes a first type of S-SSB time slots; or The first set of S-SSB time slots includes a first type of S-SSB time slots and a second type of S-SSB time slots; and The second set of S-SSB time slots includes a second type of S-SSB time slots; Among them, the second type of S-SSB time slot is a supplementary candidate time slot for the first type of S-SSB time slot.

13. The method according to any one of claims 5 to 12, characterized in that: The first S-SSB time slot is a first-type S-SSB time slot or a second-type S-SSB time slot; The second S-SSB time slot is the second type S-SSB time slot; Among them, the second type of S-SSB time slot is a supplementary candidate time slot for the first type of S-SSB time slot.

14. The method according to claim 13, characterized in that One or more of the following parameters are network device configuration, preconfigured, or pre-set: A first interval, used to indicate an interval between the first type S-SSB time slots; A second interval, used to indicate an interval between the first type S-SSB time slot and a second type S-SSB time slot corresponding to the first type S-SSB time slot; as well as The third interval is used to indicate the interval between multiple second-type S-SSB time slots corresponding to the same first-type S-SSB time slot.

15. The method according to any one of claims 5 to 14, characterized in that: The first S-SSB time slot and the second S-SSB time slot belong to the same S-SSB synchronization period.

16. The method according to any one of claims 1 to 15, characterized in that The terminal device performing the first operation includes: The terminal device performs the first operation according to one or more of the following information: The scenario in which the terminal device is located; The type of service executed by the terminal device.

17. The method according to any one of claims 1 to 16, characterized in that The first S-SSB time slot belongs to a first S-SSB synchronization period, and when the first S-SSB synchronization period includes a channel occupancy time COT, the method further includes: The terminal device performs LBT on a first RB set included in the COT.

18. The method according to claim 17, characterized in that The first RB set is a RB set configured or pre-configured not to send S-SSB.

19. The method according to any one of claims 17 or 18, characterized in that The terminal device performing LBT on the first RB set included in the COT includes: The terminal device performs LBT on all RB sets included in the COT.

20. The method according to any one of claims 17 to 19, characterized in that The first RB set belongs to the first bandwidth part BWP, and the terminal device performs LBT on the first RB set included in the COT, including: The terminal device performs LBT on all RB sets included in the first BWP.

21. The method according to any one of claims 1 to 20, characterized in that Also includes: If the terminal device successfully performs LBT on Y RB sets of the first S-SSB time slot, the terminal device sends S-SSB on some or all of the Y RB sets according to the first power; The first power is the sum of the transmission powers of the S-SSBs sent on the Y RB sets, and Y is an integer greater than 1.

22. The method according to claim 21, characterized in that The terminal device sends the S-SSB on part or all of the Y RB sets according to the first power, including: When the first power is less than or equal to the maximum limited transmit power value, the terminal device transmits S-SSB on all RB sets in the Y RB sets; and / or When the first power is greater than or equal to the maximum limited transmit power value, the terminal device transmits S-SSB on some RB sets in the Y RB sets; Among them, the sum of the transmission powers of S-SSBs sent on some RB sets in the Y RB sets is less than or equal to the maximum limited transmission power value.

23. The method according to claim 21 or 22, characterized in that The terminal device sending the S-SSB on some RB sets in the Y RB sets includes: The terminal device preferentially sends the S-SSB on the RB set with a higher priority among the Y RB sets; The priority is related to one or more of the following information of the RB set: Whether the RB set is a target RB set; Whether the RB set belongs to COT.

24. The method according to claim 23, characterized in that The priority meets one or more of the following: The priority corresponding to the target RB set is higher than the priority corresponding to the non-target RB set; The priority corresponding to the target RB set is higher than the priority of the RB set belonging to the COT; as well as The priority of the RB set belonging to the COT is higher than the priority of the RB set not belonging to the COT.

25. A method of wireless communication, characterized in that: include: The network device sends configuration information to the terminal device; The configuration information is used to configure one or more of the following information: The first information is used to indicate the frequency domain position of the target resource block RB set, where the target RB set is the RB set in the S-SSB time slot where the terminal device preferentially performs listen-before-talk LBT; A first interval, used to indicate an interval between time slots of the first type of synchronization signal blocks S-SSB; a second interval, used to indicate an interval between the first type S-SSB time slot and a second type S-SSB time slot, where the second type S-SSB time slot is a supplementary candidate time slot of the first type S-SSB time slot; and The third interval is used to indicate the interval between multiple second-type S-SSB time slots corresponding to the same first-type S-SSB time slot.

26. A terminal device, characterized in that: include: The execution unit is used to perform the first operation if the terminal device fails to perform the listen-before-talk LBT on part or all of the resource block RB sets in the first side synchronization signal block S-SSB time slot.

27. The terminal device according to claim 26, characterized in that: The terminal device is also used for: LBT is preferentially performed on the target RB set of the first S-SSB time slot.

28. The terminal device according to claim 27, characterized in that: The frequency domain position of the target RB set satisfies one or more of the following: network device configuration, pre-configuration, and pre-setting.

29. The terminal device according to claim 27 or 28, characterized in that: The failure to perform LBT on some or all RB sets of the first S-SSB time slot includes: failure to perform LBT on a target RB set of the first S-SSB time slot; The first operation includes performing LBT on one or more RB sets other than the target RB set on the first S-SSB time slot.

30. The terminal device according to any one of claims 27 to 29, characterized in that: The failure to perform LBT on some or all of the RB sets of the first S-SSB time slot includes: failure to perform LBT on the target RB set of the first S-SSB time slot; The first operation includes: performing LBT on the second S-SSB time slot; The second S-SSB time slot is associated with the first S-SSB time slot.

31. The terminal device according to any one of claims 30, characterized in that: The performing LBT on the second S-SSB time slot comprises: LBT is preferentially performed on the target RB set of the second S-SSB time slot.

32. The terminal device according to claim 30 or 31, characterized in that: The first S-SSB time slot belongs to a first S-SSB time slot set, the second S-SSB time slot is associated with the first S-SSB time slot set, and the failure to perform LBT on part or all of the RB sets of the first S-SSB time slot includes: Performing LBT on part or all of the RB sets of each S-SSB time slot in the first S-SSB time slot set fails; or Performing LBT on part or all of the RB sets of any S-SSB time slot in the first S-SSB time slot set fails.

33. The terminal device according to claim 32, characterized in that: The failure of LBT of part or all of the RB sets of each S-SSB time slot includes the failure of LBT of the target RB sets of each S-SSB time slot.

34. The terminal device according to claim 32 or 33, characterized in that: The second S-SSB time slot belongs to a second S-SSB time slot set, and performing LBT on the second S-SSB time slot includes: performing LBT on one or more S-SSB time slots in the second S-SSB time slot set.

35. The terminal device according to claim 34, characterized in that: The first S-SSB time slot set and the second S-SSB time slot set belong to the same S-SSB synchronization period.

36. The terminal device according to claim 35, characterized in that: The first S-SSB time slot set and the second S-SSB time slot set constitute an S-SSB time slot set group, and the same S-SSB synchronization period includes P groups of the S-SSB time slot set groups, where P is a positive integer.

37. The terminal device according to any one of claims 34 to 36, characterized in that: The first set of S-SSB time slots includes a first type of S-SSB time slots; or The first set of S-SSB time slots includes a first type of S-SSB time slots and a second type of S-SSB time slots; and The second set of S-SSB time slots includes a second type of S-SSB time slots; Among them, the second type of S-SSB time slot is a supplementary candidate time slot for the first type of S-SSB time slot.

38. The terminal device according to any one of claims 30 to 37, characterized in that: The first S-SSB time slot is a first-type S-SSB time slot or a second-type S-SSB time slot; The second S-SSB time slot is the second type S-SSB time slot; Among them, the second type of S-SSB time slot is a supplementary candidate time slot for the first type of S-SSB time slot.

39. The terminal device according to claim 38, characterized in that: One or more of the following parameters are network device configuration, preconfigured, or pre-set: A first interval, used to indicate an interval between the first type S-SSB time slots; A second interval, used to indicate an interval between the first type S-SSB time slot and a second type S-SSB time slot corresponding to the first type S-SSB time slot; as well as The third interval is used to indicate the interval between multiple second-type S-SSB time slots corresponding to the same first-type S-SSB time slot.

40. The terminal device according to any one of claims 30 to 39, characterized in that: The first S-SSB time slot and the second S-SSB time slot belong to the same S-SSB synchronization period.

41. The terminal device according to any one of claims 26 to 40, characterized in that: The execution unit is used for: The first operation is performed according to one or more of the following information: The scenario in which the terminal device is located; The type of service executed by the terminal device.

42. The terminal device according to any one of claims 26 to 41, characterized in that: The first S-SSB time slot belongs to a first S-SSB synchronization period, and when the first S-SSB synchronization period includes a channel occupancy time COT, the terminal device is further used for: LBT is performed on a first set of RBs included in the COT.

43. The terminal device according to claim 42, characterized in that: The first RB set is a RB set configured or pre-configured not to send S-SSB.

44. The terminal device according to any one of claims 42 or 43, characterized in that: The performing LBT on the first RB set included in the COT comprises: LBT is performed on all RB sets included in the COT.

45. The terminal device according to any one of claims 42 to 44, characterized in that: The first RB set belongs to a first bandwidth part BWP, and performing LBT on the first RB set included in the COT includes: LBT is performed on all RB sets included in the first BWP.

46. ​​The terminal device according to any one of claims 26 to 45, characterized in that: The terminal device is also used for: If the terminal device successfully performs LBT on Y RB sets of the first S-SSB time slot, sending S-SSB on some or all of the Y RB sets according to the first power; The first power is the sum of the transmission powers of the S-SSBs sent on the Y RB sets, and Y is an integer greater than 1.

47. The terminal device according to claim 46, characterized in that: The sending the S-SSB on part or all of the Y RB sets according to the first power includes: When the first power is less than or equal to the maximum limited transmit power value, transmitting the S-SSB on all RB sets in the Y RB sets; and / or When the first power is greater than or equal to the maximum limited transmit power value, sending S-SSB on some RB sets in the Y RB sets; Among them, the sum of the transmission powers of S-SSBs sent on some RB sets in the Y RB sets is less than or equal to the maximum limited transmission power value.

48. The terminal device according to claim 46 or 47, characterized in that: The sending of S-SSB on some RB sets in the Y RB sets includes: Preferentially sending the S-SSB on the RB set with a higher priority among the Y RB sets; The priority is related to one or more of the following information of the RB set: Whether the RB set is a target RB set; Whether the RB set belongs to COT.

49. The terminal device according to claim 48, characterized in that: The priority meets one or more of the following: The priority corresponding to the target RB set is higher than the priority corresponding to the non-target RB set; The priority corresponding to the target RB set is higher than the priority of the RB set belonging to the COT; as well as The priority of the RB set belonging to the COT is higher than the priority of the RB set not belonging to the COT.

50. A network device, characterized in that: include: A sending unit, used to send configuration information to a terminal device; The configuration information is used to configure one or more of the following information: The first information is used to indicate the frequency domain position of the target resource block RB set, where the target RB set is the RB set in the S-SSB time slot where the terminal device preferentially performs listen-before-talk LBT; A first interval, used to indicate an interval between time slots of the first type of synchronization signal blocks S-SSB; a second interval, used to indicate an interval between the first type S-SSB time slot and a second type S-SSB time slot, where the second type S-SSB time slot is a supplementary candidate time slot of the first type S-SSB time slot; and The third interval is used to indicate the interval between multiple second-type S-SSB time slots corresponding to the same first-type S-SSB time slot.

51. A terminal device, characterized in that: The method comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal device executes the method according to any one of claims 1 to 24.

52. A network device, characterized in that: It comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the network device executes the method as claimed in claim 25.

53. A device, characterized in that: The device comprises a processor, configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 25.

54. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 25.

55. A computer-readable storage medium, characterized in that: A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 25.

56. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 25.

57. A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1 to 25.

Images