Method and apparatus in a node for wireless communication

Abstract

The invention provides a method and a device in a node for wireless communication, which are used for realizing initial beam pairing based on a side synchronization signal block. The method comprises: receiving one or more sideline synchronization signal blocks, the one or more sideline synchronization signal blocks comprising a first sideline synchronization signal block, the first sideline synchronization signal block being configured for a first operation, and / or the first sideline synchronization signal block carrying a first type of identification, and / or the first type of identification being configured for a second operation; the first side row synchronization signal block occupies a first type of resources; selecting a synchronization reference according to the first priority group sequence; wherein the first operation comprises at least one of initial beam pairing, sideward unicast link establishment and sideward beam management; the first priority group sequence is related to the first operation and / or the sideline synchronization signal block carrying the first type identifier and / or the sideline synchronization signal block occupying the first type resource.

Description

[0001] This application is a divisional application of the case with the application number 202380011760.X, the application date of September 18, 2023, and the invention title "Method and apparatus in a node for wireless communication". Technical Field

[0002] This application relates to the field of communication technologies, and more particularly, to a method and an apparatus in a node for wireless communication. Background Art

[0003] In sidelink communication, it has become an optional solution to use a sidelink synchronization signal block or a modified format of the sidelink synchronization signal block as a reference signal for initial beam pairing. When the transmitting node for initial beam pairing can be used as a synchronization reference source, if the receiving node has multiple synchronization reference sources, it may not select this transmitting node as the synchronization reference, resulting in the transmitting node being unable to perform initial beam pairing. Therefore, how to perform initial beam pairing based on the sidelink synchronization signal block is a technical problem to be solved. Moreover, after introducing initial beam pairing, how to redesign the synchronization priority rules and how to determine the priority when the node performing initial beam pairing is used as a synchronization reference are both technical problems to be solved. Summary of the Invention

[0004] Embodiments of this application provide a method and an apparatus in a node for wireless communication. The following introduces various aspects related to this application.

[0005] In a first aspect, a method in a first node for wireless communication is provided, including: receiving one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or, the first sidelink synchronization signal block carrying a first type of identifier, and / or, the first sidelink synchronization signal block occupying a first type of resource; selecting a synchronization reference according to a first priority group order; where the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management; and the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0006] In a second aspect, a method in a second node for wireless communication is provided, including: transmitting a first sidelink synchronization signal block, where the first sidelink synchronization signal block is configured for a first operation, and / or, the first sidelink synchronization signal block carries a first type of identifier, and / or, the first sidelink synchronization signal block occupies a first type of resource; wherein, the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management; a receiving node of the first sidelink synchronization signal block selects a synchronization reference according to a first priority group order; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0007] In a third aspect, a first node for wireless communication is provided, including: a first receiver configured to receive one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, where the first sidelink synchronization signal block is configured for a first operation, and / or, the first sidelink synchronization signal block carries a first type of identifier, and / or, the first sidelink synchronization signal block occupies a first type of resource; a first processor configured to select a synchronization reference according to a first priority group order; wherein, the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0008] In a fourth aspect, a second node for wireless communication is provided, including: a first transmitter configured to transmit a first sidelink synchronization signal block, where the first sidelink synchronization signal block is configured for a first operation, and / or, the first sidelink synchronization signal block carries a first type of identifier, and / or, the first sidelink synchronization signal block occupies a first type of resource; wherein, the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management; a receiving node of the first sidelink synchronization signal block selects a synchronization reference according to a first priority group order; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0009] In a fifth aspect, a first node for use in wireless communication is provided, including a transceiver, a memory, and a processor, where the memory is configured to store a program, and the processor is configured to call the program in the memory and control the transceiver to receive or transmit signals, so that the first node performs the method described in the first aspect.

[0010] In a sixth aspect, a second node for use in wireless communication is provided, including a transceiver, a memory, and a processor. The memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals, so that the second node executes the method described in the second aspect.

[0011] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned first node and / or second node. In another possible design, the system may further include other devices that interact with the first node or the second node in the solution provided by 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 computer to execute some or all of the steps in the methods of the above-mentioned various aspects.

[0013] In a ninth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable a computer to execute some or all of the steps in the methods of the above-mentioned various aspects. In some implementation manners, the computer program product may be a software installation package.

[0014] In a 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-mentioned various aspects.

[0015] In an embodiment of the present application, after receiving one or more sidelink synchronization signal blocks, the first node can determine whether one or more sidelink synchronization signal blocks include a first sidelink synchronization signal block related to initial beam pairing, etc., according to at least one of the configuration of the sidelink synchronization signal block, the carried identifier, and the occupied resources, so as to effectively implement initial beam pairing through the first sidelink synchronization signal block before establishing a sidelink unicast link.

[0016] In an embodiment of the present application, the first node, as a receiving node, selects a synchronization reference according to the first priority group order. Among them, the synchronization priority rule of the first priority group order is related to initial beam pairing, sidelink unicast link establishment, beam management, and the identifier carried by the sidelink synchronization signal block, the resources occupied by the sidelink synchronization signal block, etc. Therefore, whether the sending node establishes a sidelink unicast link is considered in the new synchronization priority rule. In addition, the first priority group order optimizes the traditional synchronization priority rule, so the synchronization priority of the sending node for initial beam pairing is optimized.

[0017] In the embodiments of the present application, any two nodes of sidelink communication perform initial beam pairing before establishing a sidelink unicast link. Establishing a unicast link using the paired beams can expand the link range between the transmitting node and the receiving node, enabling more nodes to implement advanced commercial use cases.

[0018] In the embodiments of the present application, by performing initial beam pairing before establishing a sidelink unicast link, the transmitting node can effectively avoid sending direct communication request messages with high resource overhead on all beams through beam scanning, thereby significantly reducing resource waste. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a schematic diagram of the system architecture of a wireless communication system applicable to the embodiments of the present application.

[0020] Figure 2 It is a schematic diagram of the time slot structure of a sidelink synchronization signal block.

[0021] Figure 3 It is a schematic diagram of the distribution of multiple S-SSBs in one period.

[0022] Figure 4 It is a schematic flowchart of a method in a first node for wireless communication provided by the embodiments of the present application.

[0023] Figure 5 It is a schematic flowchart of an implementation manner of beam initial pairing in the first operation.

[0024] Figure 6 It is a schematic flowchart of another implementation manner of beam initial pairing in the first operation.

[0025] Figure 7 It is a schematic flowchart of an implementation manner of sidelink unicast link establishment in the first operation.

[0026] Figure 8 For Figure 4 It is a schematic diagram of a possible implementation manner of the method shown.

[0027] Figure 9 It is a schematic flowchart of another method in a first node for wireless communication provided by the embodiments of the present application.

[0028] Figure 10 For Figure 9 It is a schematic diagram of a possible implementation manner of the method shown.

[0029] Figure 11 It is a schematic diagram of the structure of a first node for wireless communication provided by the embodiments of the present application.

[0030] Figure 12Schematic structural diagram of a second node for wireless communication provided by an embodiment of the present application.

[0031] Figure 13 Schematic structural diagram of the device provided by an embodiment of the present application.

[0032] Figure 14 Schematic diagram of the hardware module of the communication device provided by an embodiment of the present application. Detailed implementation manners

[0033] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. For the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0034] Figure 1 It is a schematic diagram of the system architecture of a wireless communication system 100 applicable to an embodiment of the present application. The wireless communication system 100 may include a network device 110 and user devices 121 to 129. The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminals located within the coverage area.

[0035] In some implementation manners, user equipment (UE) may communicate with each other through a sidelink (SL). Sidelink communication may also be referred to as proximity-based services (ProSe) communication, one-way communication, sidechain communication, device-to-device (D2D) communication, etc.

[0036] Or rather, sidelink data is transmitted between user equipment through the sidelink. The sidelink data may include data and / or control signaling. In some implementation manners, the sidelink data may be, for example, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a PSCCH demodulation reference signal (DMRS), a PSSCH DMRS, a physical sidelink feedback channel (PSFCH), etc.

[0037] As described below in conjunction with Figure 1Introduce several common sidelink communication scenarios. In sidelink communication, according to whether the user equipment in the sidelink is within the coverage of the network equipment, it can be divided into three scenarios. Scenario 1: The user equipment conducts sidelink communication within the coverage of the network equipment. Scenario 2: Some user equipment conducts sidelink communication within the coverage of the network equipment. Scenario 3: The user equipment conducts sidelink communication outside the coverage of the network equipment.

[0038] As Figure 1 shown in the figure, in Scenario 1, user equipments 121 to 122 can communicate through the sidelink, and user equipments 121 to 122 are all within the coverage of network equipment 110. Or rather, user equipments 121 to 122 are all within the coverage of the same network equipment 110. In this scenario, network equipment 110 can send configuration signaling to user equipments 121 to 122. Correspondingly, user equipments 121 to 122 communicate through the sidelink based on the configuration signaling.

[0039] As Figure 1 shown in the figure, in Scenario 2, user equipments 123 to 124 can communicate through the sidelink. User equipment 123 is within the coverage of network equipment 110, and user equipment 124 is outside the coverage of network equipment 110. In this scenario, user equipment 123 receives the configuration information of network equipment 110 and communicates through the sidelink based on the configuration of the configuration signaling. However, for user equipment 124, since user equipment 124 is outside the coverage of network equipment 110 and cannot receive the configuration information of network equipment 110, at this time, user equipment 124 can obtain the configuration of sidelink communication according to the pre-configured configuration information and / or the configuration information sent by user equipment 123 located within the coverage, so as to communicate with user equipment 123 through the sidelink based on the obtained configuration.

[0040] In some cases, user equipment 123 can send the above configuration information to user equipment 124 through the physical sidelink broadcast channel (PSBCH) to configure user equipment 124 to communicate through the sidelink.

[0041] As Figure 1 shown in the figure, in Scenario 3, user equipments 125 to 129 are all outside the coverage of network equipment 110 and cannot communicate with network equipment 110. In this case, the user equipments can all conduct sidelink communication based on the pre-configured information.

[0042] In some cases, user equipments 127 to 129 located outside the coverage of a network device can form a communication group, and the user equipments 127 to 129 within the communication group can communicate with each other. Additionally, the user equipment 127 within the communication group can serve as a central control node, also known as a cluster header (CH). Correspondingly, the user equipments in other communication groups can be referred to as "cluster members".

[0043] It should be noted that Figure 1 Exemplarily, a network device and multiple user equipments are shown. Optionally, the wireless communication system 100 may include multiple network devices, and the coverage of each network device may include other numbers of user equipments. The embodiments of the present application do not make any limitations thereto.

[0044] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity. The embodiments of the present application do not make any limitations thereto.

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

[0046] The user equipment in the embodiments of the present application may also be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. The user equipment in the embodiments of the present application may be a device that provides voice and / or data connectivity to users and can be used to connect people, things, and machines. For example, it can be a handheld device with a wireless connection function, a vehicle-mounted device, etc. The user equipment in the embodiments of the present application may be a mobile phone, a tablet computer (Pad), a laptop computer, a palmtop computer, a mobile internet device (MID), a wearable device, a vehicle, 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 user equipment can act as a base station. For example, the user equipment can act as a scheduling entity that provides sidelink signals between user equipments in vehicle-to-everything (V2X) or D2D, etc. For instance, a cellular phone and a car communicate with each other using sidelink data. A cellular phone communicates with a smart home device without relaying the communication signal through a base station.

[0047] The network device in the embodiments of the present application can be a device for communicating with a user equipment. This network device can also be referred to as an access network device or a radio access network device. For example, the network device can be a base station. The network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) that connects a user equipment to a wireless network. The base station can be generally covered by various names below, or replaced with the following names, such as: Node B, evolved Node B (eNB), next generation Node B (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), access point (AP), master eNB, secondary eNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The 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. The base station can also refer to a communication module, a modem or a chip disposed in the foregoing device or apparatus. The base station can also be a mobile switching center and a device that undertakes the base station function in D2D, V2X, machine-to-machine (M2M) communication, a network-side device in a 6G network, a device that undertakes the base station function in a future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the network device.

[0048] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the position of the mobile base station. In other examples, a helicopter or a drone can be configured to be used as a device for communicating with another base station.

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

[0050] Network devices and user devices can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed on aircraft, balloons, and satellites in the air. In the embodiments of the present application, the scenarios where the network devices and user devices are located are not limited.

[0051] It should be understood that all or part of the functions of the communication devices in the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform).

[0052] For the sake of easy understanding, some relevant technical knowledge involved in the embodiments of the present application will be introduced first. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0053] It should be understood that the explanations of the terms in the embodiments of the present application can refer to the specification protocols of the 3rd generation partnership project (3GPP) series TS36, TS37, and TS38, but can also refer to the specification protocols of the Institute of Electrical and Electronics Engineers (IEEE).

[0054] With the development of communication technologies, the technical research and standardization of sidelink communication are gradually being carried out. The sidelink communication developed in the RAN of 5G NR Release-16 (Rel-16) is mainly used to support advanced V2X applications. In Rel-17, the System Architecture Working Group 2 (SA2) specifically conducts research and standardization on ProSe including public safety and commercial related services. As part of Rel-17, in order to save power consumption for battery-constrained users and improve the reliability of sidelink communication, the Radio Access Network Working Group 1 (RAN1) and RAN2 have developed power saving technologies (such as partial sensing, discontinuous reception (DRX), and Inter-UE coordination (IUC) technologies).

[0055] The application fields of sidelink communication are also gradually expanding. Exemplarily, although the original intention of NR SL development was to support V2X applications, the industry is increasingly enthusiastic about expanding NR SL to more commercial use cases. For example, highly automated driving technology requires sharing a large amount of sensor information between vehicles.

[0056] Due to the continuous expansion of the application fields of sidelink communication, higher requirements are imposed on NR SL. These requirements include two key needs: increasing the sidelink data rate and supporting more new carriers on the sidelink. By adding more new carriers, the transmission bandwidth can be expanded, thereby further increasing the data rate.

[0057] It can be seen from 3GPP project RP-222806 that the research on the evolution of Rel-18 NR SL for supporting new carriers mainly focuses on sidelink beam management (SL BM). Sidelink beam management generally includes initial beam-pairing, beam maintenance, and beam failure recovery (BFR), etc.

[0058] Regarding the relationship between PC5 / sidelink unicast link establishment and sidelink initial beam-pairing, there are the following three candidate procedures:

[0059] Candidate procedure 1: Execute initial beam-pairing before the sidelink unicast link establishment between UE1 and UE2;

[0060] Candidate procedure 2: Execute initial beam-pairing during the sidelink unicast link establishment between UE1 and UE2;

[0061] Candidate procedure 3: Start initial beam-pairing only after the sidelink unicast link establishment between UE1 and UE2.

[0062] Among them, alternative process 1 can expand the transmission range of sidelink communication and improve resource utilization. Specifically, the advantage of performing initial beam pairing before establishing a sidelink unicast link is that it can make full use of the paired beams to expand the transmission range, enabling more UEs to establish sidelink unicast links, thereby providing more advanced commercial use case services. These UEs are, for example, high-performance audio-visual devices in stadiums, large event venues, and concerts. Further, the advantage of performing initial beam pairing before establishing a sidelink unicast link is also that the direct communication request (DCR) message used to establish the unicast link only needs to be sent on the paired beams through the physical sidelink shared channel (PSSCH), thus avoiding multiple transmissions of the DCR on the resources occupied by multiple transmission beams using the beam sweeping method. Therefore, the resource utilization efficiency can be significantly improved.

[0063] For the reference signal adopted by alternative process 1, the 3GPP RAN1 meeting has agreed to adopt the sidelink synchronization signal / physical sidelink broadcast channel block (S-SS / PSBCH block, S-SSB) or a modified format based on the S-SSB as an alternative. Among them, the sidelink synchronization signal / physical sidelink broadcast channel block can also be replaced by the sidelink-synchronization signal block (S-SSB). That is to say, the S-SSB in this article can represent the sidelink synchronization signal / physical sidelink broadcast channel block or the sidelink-synchronization signal block, and the embodiments of this application do not limit this. As an example, the operation process of alternative process 1 using the S-SSB as the reference signal to perform initial beam pairing can be as follows:

[0064] UE1 sends multiple S-SSBs through the beam sweeping method;

[0065] UE2 performs reference signal received power (RSRP) measurements on the sidelink synchronization signal (SLSS) and / or PSBCH. UE2 determines the transmission beam of UE1 and the reception beam of UE2 according to the measured RSRP.

[0066] For the determined transmission beam of UE1, UE2 performs associated beam reporting.

[0067] Traditional S-SSB Design

[0068] In the traditional NR S-SSB design, the S-SSB consists of a sidelink primary synchronization signal (S-PSS), a sidelink secondary synchronization signal (S-SSS), and PSBCH. Generally, the S-SSB occupies one time slot in the time domain. The numerology configured by the SL bandwidth part (BWP) adopted by the S-SSB includes the subcarrier spacing and the cyclic prefix (CP) length, etc. In a SL BWP, the transmission of the S-SSB cannot be frequency division multiplexed (FDM) with the transmission of other sidelink physical channels. Therefore, the transmission of invalid S-SSB(s) will not only increase resource consumption but also seriously affect the available resources of other physical SL channels / signals.

[0069] For ease of understanding, the following will be combined with Figure 2 to give an exemplary description of the structure of one time slot of the S-SSB. Refer to Figure 2 , in one time slot of the S-SSB, it includes the S-PSS and S-SSS that each occupy two symbols, PSBCH, and the final guard symbol. In the Figure 2 shown structure, for an S-SSB time slot with a normal CP, the first symbol (i.e., the first PSBCH symbol) can be used for automatic gain control (AGC), the second and third symbols are used to carry the S-PSS, the fourth and fifth symbols are used to carry the S-SSS, the last symbol is used for the guard symbol, and the other symbols are used to carry PSBCH.

[0070] As Figure 2 shown, the S-SSB spans 11 common resource blocks (Common RBs) in a SL BWP in the frequency domain, that is, 132 subcarriers. Among them, the S-PSS and S-SSS occupy 127 subcarriers. The frequency domain position of the S-SSB in the SL BWP is pre-configured or configured. Therefore, the receiving UE of the S-SSB (including UE1) does not need to perform blind detection in the frequency domain to find the S-SSB.

[0071] UE sends S-SSB to expand the coverage of synchronization reference source. Specifically, in NR SL, global navigation satellite system (GNSS), gNB / eNB and NR SL UE (i.e. synchronization reference UE, SyncRefUE) can all be used as synchronization reference source for a UE. SyncRefUE can send synchronization information (e.g., S-SSB) so that surrounding UEs have the same timing reference.

[0072] In the design of traditional S-SSB, one or more S-SSBs are sent in a fixed period (i.e., 160ms, 16 radio frames). In an S-SSB period, the number of multiple S-SSBs is preconfigured or configurable, depending on the subcarrier spacing (SCS) and the frequency range, as shown in Table 1. Table 1 shows the number of S-SSBs sent in an S-SSB period.

[0073] Table 1

[0074]

[0075] In a fixed period, the distribution of multiple S-SSBs depends on two parameters: one is the slot offset from the start of the S-SSB period to the first S-SSB, and the other is the slot interval between two consecutive S-SSBs.

[0076] For ease of understanding, the following Figure 3 The distribution of multiple S-SSBs within a fixed period is exemplified. Figure 3 In the example of , the fixed period, that is, the S-SSB period, is 16 radio frames. When 16 radio frames are taken as a group, each period starts at the first time slot of the current group of radio frames and ends at the first time slot of the next group of radio frames.

[0077] Figure 3 There are 4 S-SSBs in a fixed period. The time period between the time slot where the first S-SSB is located and the start position of the fixed period is the time offset. The time period between two adjacent S-SSBs is the time interval.

[0078] Traditional NRSL Synchronization Priority Design

[0079] NR SL has two major synchronization reference sources, namely the Global Navigation Satellite System (GNSS) and base stations (including gNB / eNB). In addition, the UE can also select a Synchronization Reference UE (SyncRefUE) as its synchronization reference source. The UE selects or reselects the synchronization reference according to the NR SL synchronization priority rules. That is to say, when the UE detects two or more synchronization sources, the UE can select the synchronization source with the highest priority as the synchronization reference; when the UE detects two or more synchronization sources with the same priority, it selects the SyncRefUE with the highest PSBCH-RSRP result as its synchronization reference. The NR SL synchronization priority rules include the synchronization priority rules based on GNSS and the synchronization priority rules based on gNB / eNB, as shown in Table 2.

[0080] Table 2

[0081]

[0082] In Table 2, SLSSID is the sidelink synchronization signal identity; InC is the InCoverage in the Master Information Block Sidelink (or sidelink master information block, S-MIB). Among them, InC (InCoverage indication) can be used to indicate whether the UE sending this S-MIB is within the network coverage. In the synchronization priority group based on GNSS, when the value of InC is true, it indicates that the UE sending this S-MIB is within the network coverage, or this UE selects GNSS timing as its synchronization reference source.

[0083] As mentioned above, the process of performing initial beam pairing before the establishment of a sidelink unicast link has been introduced into the NR SL system, and the S-SSB or the improved format of the S-SSB will be used as the reference signal for initial beam pairing.

[0084] In some scenarios, in order to facilitate UE2 to identify UE1 that sends this S-SSB from multiple UEs, UE1 needs to indicate at least one of its user identification (UE ID) information (or source identification), transmission beam information, and receiving user identification (or destination identification) by sending an enhanced S-SSB (eS-SSB). When the UE sending the eS-SSB can be used as a synchronization reference source, the receiving user can select the synchronization reference from multiple synchronization reference sources according to the traditional NR SL synchronization priority rules.

[0085] However, if the UE that transmits the eS-SSB belongs to a lower-priority group, the UE may not be able to perform initial access pairing all the time, and thus cannot establish a sidelink unicast link. However, for the UE that transmits the eS-SSB, it is not only used to maintain synchronization, but also has the requirement to establish a sidelink unicast link. Therefore, the traditional synchronization priority rules cannot meet the requirement of performing initial beam pairing for establishing a sidelink unicast link.

[0086] In summary, how to effectively perform initial beam pairing before establishing a sidelink unicast link through S-SSB is a technical problem to be solved. Moreover, introducing a new feature of initial beam pairing in the NR SL system will lead to the problem that the synchronization priority rules need to be redesigned. Moreover, the synchronization reference for establishing a sidelink unicast link is also a technical problem to be solved. Moreover, the priority of the UE that performs initial beam pairing as a synchronization reference is also a technical problem to be solved.

[0087] To solve the above problems, an embodiment of the present application proposes a method in a first node for wireless communication. Through this method, when the first node receives one or more sidelink signal blocks including a first sidelink synchronization signal block, it selects a synchronization reference according to a first priority group order. The first sidelink synchronization signal block and the first priority group order are both related to a first operation such as initial beam pairing, sidelink unicast link establishment, beam management, or a first type of identifier and a first type of resource. That is to say, the present application introduces a new synchronization priority group order related to the first operation and the like, so that the receiving node can select a synchronization reference according to the configuration of the sidelink synchronization signal block, the carried identifier, or the occupied resource.

[0088] It should be noted that the initial beam pairing mentioned in the embodiment of the present application may include or be replaced by at least one of the following: sidelink initial beam pairing, sidelink beam pairing.

[0089] It should be noted that the beams mentioned in the embodiments of the present application may include or be replaced by at least one of the following: beam, physical beam, logical beam, spatial filter, spatial parameter, spatial domain filter, spatial domain transmission filter, spatial domain reception filter, antenna port. The meanings of these expressions may be the same, and the embodiments of the present application do not distinguish them.

[0090] The method embodiments of the present application will be introduced in detail below with reference to the accompanying drawings. Figure 4 It is a schematic flowchart of the method in the first node for wireless communication provided by the embodiments of the present application. Figure 4 The method shown includes step S410 and step S420. It should be understood that Figure 4 the method shown can be executed by the first node.

[0091] In some implementation manners, the first node may be any one of the aforementioned user equipments for sidelink communication. For example, the first node may be a vehicle in V2X or a basic communication facility in V2X. In some implementation manners, the first node may be within the network coverage or outside the network coverage. When within the network coverage, the first node may perform sidelink communication based on the configuration of the network device.

[0092] As an embodiment, the first node may be a network-controlled repeater (NCR).

[0093] As an embodiment, the first node may be a user equipment, for example, Figure 1 the user equipments 121 to 129 shown.

[0094] As an embodiment, the first node may be a relay, such as a relay terminal.

[0095] Referring to Figure 4 , in step S410, receive one or more sidelink synchronization signal blocks.

[0096] One or more sidelink synchronization signal blocks come from one or more transmitting nodes. The sidelink synchronization signal block may include at least two of S-PSS, S-SSS, and PSBCH. The sidelink synchronization signal block may include S-PSS and S-SSS. The sidelink synchronization signal block may not include PSBCH.

[0097] In some embodiments, one or more transmitting nodes may be user equipment interacting with a first node or network equipment, which is not limited herein.

[0098] One or more sidelink synchronization signal blocks include a first sidelink synchronization signal block, which can be replaced with that the first sidelink synchronization signal block is any one of the one or more sidelink synchronization signal blocks received by the first node. In other words, the receiving node of the first sidelink synchronization signal block includes the first node. For simplicity, S-SSB is used to represent the sidelink synchronization signal block hereinafter. Therefore, the first sidelink synchronization signal block can be represented as the first S-SSB.

[0099] As an embodiment, the first S-SSB is a new S-SSB, which is different from the S-SSBs in traditional NR Rel-16 and Rel-17.

[0100] As an embodiment, the first S-SSB is an enhanced sidelink synchronization signal block, i.e., eS-SSB.

[0101] As an embodiment, the first S-SSB adopts a modified format of the traditional S-SSB.

[0102] The transmitting node of the first S-SSB is a second node. The second node may be user equipment that hopes to perform operations such as initial beam pairing and sidelink unicast link establishment with the first node.

[0103] In some embodiments, the first S-SSB may be one S-SSB, any multiple S-SSBs in a group of S-SSBs, or multiple S-SSBs, which is not limited herein.

[0104] In some embodiments, the first S-SSB is configured for a first operation. The first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management. Among them, the initial beam pairing may be sidelink initial beam pairing.

[0105] As an embodiment, the first S-SSB is used for the first operation. For example, the first S-SSB is used for initial beam pairing. For another example, the first S-SSB is used for sidelink unicast link establishment. For another example, the first S-SSB is used for sidelink beam management. For another example, the first S-SSB is used for initial beam pairing before sidelink unicast link establishment to establish a sidelink unicast link.

[0106] Exemplarily, the first S-SSB is configured for sidelink initial beam pairing. Therefore, the first node can match the transmit beam and receive beam with the transmit node of the first S-SSB to determine the optimal beam pair.

[0107] As an embodiment, the process of sidelink initial beam pairing can refer to the pairing process of other communication systems (e.g., NR), or the relevant process can be improved according to the characteristics of the sidelink communication system.

[0108] As an embodiment, the process of sidelink initial beam pairing includes two processes: beam rough pairing and fine pairing.

[0109] For ease of understanding, the initial beam pairing process including rough pairing and fine pairing will be described exemplarily below in conjunction with Figure 5 As shown, the sidelink receive beam of UE1 performs initial beam pairing with the sidelink transmit beam of UE2. Figure 5 As shown, the sidelink receive beam of UE1 performs initial beam pairing with the sidelink transmit beam of UE2.

[0110] Refer to Figure 5 , in step S510, rough pairing is completed between the transmit beam A of UE2 and the receive beam 2 of UE1.

[0111] In step S520, UE1 uses three narrower beams, beam 2-1, beam 2-2, and beam 2-3, to receive the signals transmitted by beam A and performs measurements for fine pairing. UE1 configures three narrow beams in beam 2, and UE2 transmits signals multiple times.

[0112] Subsequently, UE1 selects a narrow beam as the receive beam for the transmit beam A of UE2 according to the measurement results.

[0113] As an embodiment, the process of the initial beam pairing includes beam rough pairing.

[0114] For ease of understanding, the initial beam pairing process including rough pairing will be described exemplarily below in conjunction with Figure 6 As shown, the sidelink transmit beam of UE1 performs initial beam pairing with the sidelink receive beam of UE2. Refer to Figure 6 As shown, the sidelink transmit beam of UE1 performs initial beam pairing with the sidelink receive beam of UE2. Refer to Figure 6 , UE1 transmits four beams by means of beam scanning. UE2 measures the four transmit beams of UE1 through two receive beams respectively. UE2 determines the matching transmit beam of UE1 and receive beam of UE2 according to the measurement results and notifies UE1.

[0115] Exemplarily, the first S-SSB is configured for sidelink unicast link establishment. Therefore, the first node can establish a sidelink unicast link with the transmit node of the first S-SSB by receiving the first S-SSB.

[0116] For ease of understanding, taking UE1 and UE2 in Figure 7 as an example, the process of an implementation manner of establishing a sidelink unicast link is illustrated by way of example.

[0117] Referring to Figure 7 , in step S710, UE1 sends a DCR to UE2. UE1 requests to establish a sidelink unicast link from UE2 through the DCR.

[0118] In step S720, UE2 feeds back a direct communication accept to UE1. According to the feedback from UE2, UE1 and UE2 complete the process of establishing a sidelink unicast link.

[0119] In some embodiments, the process of establishing a sidelink unicast link may include initial beam pairing. For example, when the initial beam pairing is performed before the unicast link is established, the process of establishing a sidelink unicast link can be considered to include performing initial beam pairing.

[0120] Exemplarily, the first node may perform sidelink beam management with the sending node of the first S-SSB by receiving the first S-SSB. As described above, sidelink beam management includes processes such as initial beam pairing, beam maintenance, and beam failure recovery. Multiple processes in sidelink beam management can enable the first node to perform stable sidelink communication within a larger link range. Among them, processes such as beam maintenance and beam failure recovery can refer to the implementation processes of other communication systems (for example, NR), or can also improve relevant processes according to the characteristics of the sidelink communication system.

[0121] In some embodiments, the first S-SSB can also be used for traditional synchronization reference, or can also be used for traditional sidelink communication or sidelink discovery.

[0122] As an embodiment, the first S-SSB is used for sidelink synchronization.

[0123] As an embodiment, the first S-SSB is used for sidelink communication or sidelink discovery.

[0124] In some embodiments, the first S-SSB can be configured for multiple operations. For example, the first S-SSB can be used for a first operation while also being used for traditional operations.

[0125] As an embodiment, the first S-SSB is used for the first operation, and the first S-SSB is also used for sidelink synchronization.

[0126] As an example, the first S-SSB is used for the first operation, and the first S-SSB is also used for sidelink communication or sidelink discovery.

[0127] In some embodiments, the first S-SSB carries a first type of identifier. The first type of identifier may indicate node information or beam information related to the first S-SSB.

[0128] Exemplarily, the first type of identifier may be used to identify relevant information of the carrier. As an example, the first type of identifier is related to the transmitting node of the S-SSB, or the first type of identifier is related to the receiving node of the S-SSB, or the first type of identifier is related to the beam carrying the S-SSB. Taking the first S-SSB as an example, the first type of identifier carried by the first S-SSB may be the identifier of the second node that transmits the first S-SSB (source identifier), or the identifier of the first node that receives the first S-SSB (destination identifier), or the beam identifier carrying the first S-SSB.

[0129] Exemplarily, the S-SSBs carrying the first type of identifier may be multiple S-SSBs, and are distinguished from other S-SSBs by the first type of identifier. Therefore, the S-SSBs carrying the first type of identifier may be a type of S-SSB.

[0130] As an example, the first S-SSB belongs to the S-SSBs carrying the first type of identifier.

[0131] As an example, the S-SSBs carrying the first type of identifier include the first S-SSB.

[0132] Exemplarily, the first S-SSB may indicate that it is used for the first operation by carrying the first type of identifier. Therefore, the first S-SSB being configured for the first operation may also be expressed as the first S-SSB carrying the first type of identifier.

[0133] As an example, when the S-SSB carries the first type of identifier, the transmitting node of the S-SSB supports sidelink initial beam pairing and / or sidelink unicast link establishment and / or sidelink beam management based on the S-SSB.

[0134] In some embodiments, the first S-SSB occupies a first type of resource. The first type of resource may be time-frequency resources reserved or dynamically scheduled by the system for the first operation between any two nodes. In some embodiments, the first type of resource is a resource different from traditional sidelink synchronization. That is to say, the first type of resource is independent of the resources traditionally used for synchronization. If the first S-SSB occupies the first type of resource, the first type of S-SSB is used for the first operation; if the first S-SSB does not occupy the first type of resource, the first type of S-SSB is used for traditional operations.

[0135] As an embodiment, the first type of resource is different from the resource occupied by the traditional S-SSB for synchronization. That is to say, the first type of resource is configured separately relative to the resource for synchronization. For example, the first type of resource occupies different time domain resources from the traditional resource for synchronization, or occupies different frequency domain resources in the same time domain.

[0136] Exemplarily, the S-SSB occupying the first type of resource can be multiple S-SSBs, and is distinguished from other S-SSBs by the occupied time-frequency resources. Therefore, the S-SSB occupying the first type of resource can be a type of S-SSB.

[0137] As an embodiment, the first S-SSB belongs to the S-SSB occupying the first type of resource.

[0138] As an embodiment, the S-SSB occupying the first type of resource includes the first S-SSB.

[0139] Exemplarily, the first S-SSB can indicate that it is used for the first operation by occupying the first type of resource. Therefore, the first S-SSB is configured for the first operation, which can also be expressed as the first S-SSB occupying the first type of resource.

[0140] As an embodiment, the S-SSB occupying the first type of resource can carry the first type of identifier, or may not carry the first type of identifier.

[0141] As an embodiment, multiple sidelink signal resources for sending or receiving S-SSB are associated with the first type of identifier, or carry the first type of identifier, or are mapped to the first type of identifier.

[0142] In the embodiments of the present application, the three expressions that the first S-SSB is configured for the first operation, the first S-SSB carries the first type of identifier, and the first S-SSB occupies the first type of resource can be replaced with each other.

[0143] When the first node receives multiple S-SSBs, it may include one first S-SSB or multiple first S-SSBs.

[0144] In some embodiments, the multiple S-SSBs received by the first node may further include a second S-SSB. The second S-SSB may be any one of the multiple S-SSBs other than the first S-SSB. The second S-SSB is different from the first S-SSB. Exemplarily, the first S-SSB is configured for a first operation, and the second S-SSB is not configured for the first operation. Exemplarily, the first S-SSB carries a first type of identifier, and the second S-SSB does not carry the first type of identifier. Exemplarily, the first S-SSB occupies a first type of resource, and the second S-SSB does not occupy the first type of resource.

[0145] Continue to refer to Figure 4 , in step S420, select a synchronization reference according to the first priority group order.

[0146] The first node selecting a synchronization reference means that the first node selects a reference source for sidelink synchronization among multiple synchronization reference sources. For example, the multiple S-SSBs received by the first node correspond to multiple available synchronization reference sources, and the first node can determine the synchronization reference source according to a certain synchronization priority rule.

[0147] The first node selects a synchronization reference according to the first priority group order. To improve the synchronization priority of the node performing the first operation, the first priority group order is introduced as a new synchronization priority rule. The first node selecting a synchronization reference according to the first priority group order means that the first node selects a synchronization reference source according to the new synchronization priority rule. In some embodiments, after receiving one or more S-SSBs, the first node can prioritize the relevant multiple sending nodes according to the first priority group order, so as to facilitate the first node to determine the synchronization reference source.

[0148] The first priority group order is related to the first operation and / or the S-SSB carrying the first type of identifier and / or the S-SSB occupying the first type of resource. That is to say, the first priority group order is different from the priority group order in Table 2 above. Exemplarily, when the first node receives the first S-SSB, the sending node of the first S-SSB will no longer be prioritized according to the priority group order in Table 2 above, so as to avoid the sending node being unable to perform the first operation.

[0149] In some embodiments, the first priority group order is used to determine the priority group to which the sending node of the S-SSB performing the first operation belongs. That is to say, the first priority group order indicates the priority groups corresponding to the sending nodes of the multiple S-SSBs used for the first operation.

[0150] As an embodiment, the first S-SSB is configured for the first operation. The first node can determine the priority group to which the sending node of the first S-SSB belongs according to the configuration information of the first S-SSB.

[0151] As an embodiment, when the sending node of the first S-SSB needs to perform a first operation, the indication information of the first S-SSB can indicate this operation requirement, and the first node can determine the priority of the sending node as a synchronization reference source according to the new synchronization priority rule. When the sending node does not need to perform the first operation, it can send an S-SSB different from the first S-SSB.

[0152] In some embodiments, the first priority group order is used to determine the priority group to which the sending node of the S-SSB carrying the first type of identifier belongs. That is, the first priority group order indicates the priority groups corresponding to the sending nodes of multiple S-SSBs carrying the first type of identifier.

[0153] As an embodiment, the first priority group order is used to determine the priority group to which the sender of the S-SSB carrying the first type of identifier belongs. For example, when the first S-SSB carries the first type of identifier, the priority group corresponding to the sending node of the first S-SSB will be determined according to the first priority group order.

[0154] In some embodiments, the first S-SSB can carry the first type of identifier in multiple ways. Exemplarily, the first type of identifier can be indicated by the SLSSID carried by the first S-SSB, so that the first node can directly determine whether the S-SSB carries the first type of identifier when decoding the SLSSID.

[0155] As an embodiment, the first S-SSB carries the SLSSID, and the SLSSID includes the first type of identifier.

[0156] Exemplarily, the first type of identifier and the SLSSID carried by the first S-SSB can be independently indicated respectively, and the first node can jointly determine the priority group of the sending node according to the first type of identifier and the SLSSID.

[0157] As an embodiment, the first S-SSB carries the SLSSID.

[0158] As an embodiment, the first S-SSB carries the SLSSID and the first type of identifier. Among them, the first type of identifier and the SLSSID are independently indicated respectively.

[0159] As an embodiment, the first type of identifier does not include the SLSSID.

[0160] In some embodiments, the first priority group order is used to determine the priority group to which the sending node of the S-SSB occupying the first type of resource belongs. That is, the first priority group order indicates the priority groups corresponding to the sending nodes of multiple S-SSBs occupying the first type of resource.

[0161] It can be seen from Figure 4 that whether the sending node needs initial beam pairing and / or establish a sidelink unicast link and / or perform sidelink beam management is used to determine the priority of the sending node as a synchronization reference source.

[0162] As described above in connection with Figure 4 the first priority group order considers the priority synchronization rule of whether the sending node needs to perform the first operation. To improve the success probability of the user equipment performing the first operation, it is necessary to increase (or adjust) the synchronization priority of the user equipment that needs to perform the first operation. For ease of understanding, the method for increasing the synchronization priority of the user equipment performing the first operation will be described in detail below in combination with various possible implementation manners of the first priority group order.

[0163] In some embodiments, the first priority group order may be an order of multiple candidate priority groups. Among them, the multiple candidate priority groups may include a target priority group, and the sending node of the first S-SSB corresponds to the target priority group. That is to say, the target priority group is the priority group corresponding to the sending node of the first S-SSB, and the multiple priority groups in the first priority group order may directly include the target priority group.

[0164] Exemplarily, the target priority group may be the first candidate priority group among the multiple candidate priority groups. Therefore, in the first priority group order, the target priority group is located at the highest priority position. In this case, when the multiple S-SSBs received by the first node include the first S-SSB, regardless of which priority group the sending node of the first S-SSB corresponds to in Table 2, the sending node will be preferentially selected by the first node as the synchronization reference.

[0165] As an embodiment, when the sending node of the first S-SSB needs to perform the first operation, regardless of the priority group of the sending node, the first node selects the sending node as the synchronization reference. For example, assume that UE1 is a UE that needs to establish a sidelink unicast link. When UE2 detects multiple synchronization sources, regardless of whether UE1 is regarded as a SyncRefUE, it still needs to detect the eS-SSBs sent from UE1 for initial beam pairing. Therefore, UE2 can regard UE1 as a SyncRefUE, thereby avoiding detecting the S-SSBs sent from other UEs.

[0166] Exemplarily, the target priority group may be a candidate priority group at any position among the multiple candidate priority groups.

[0167] As an embodiment, in the first priority group order, the target priority group may be any one of the multiple candidate priority groups.

[0168] As an example, the target priority group includes the UE(s) that need to perform a first operation, or the UE(s) for which the sidelink synchronization signal block carries a first type of identifier, or the UE(s) for which the sidelink synchronization signal block occupies a first type of resource.

[0169] As an example, the UE(s) that need to perform a first operation, or the UE(s) for which the sidelink synchronization signal block carries a first type of identifier, or the UE(s) for which the sidelink synchronization signal block occupies a first type of resource belong to the target priority group.

[0170] As an example, the multiple candidate priority groups include GNSS; the UE(s) directly synchronized to GNSS; the UE(s) indirectly synchronized to GNSS; gNB / eNB; the UE(s) directly synchronized to gNB / eNB; the UE(s) indirectly synchronized to gNB / eNB; the remaining UE(s) excluding the above UEs.

[0171] As an example, the multiple candidate priority groups include the UE(s) that need to perform a first operation; GNSS; the UE(s) directly synchronized to GNSS; the UE(s) indirectly synchronized to GNSS; gNB / eNB; the UE(s) directly synchronized to gNB / eNB; the UE(s) indirectly synchronized to gNB / eNB; the remaining UE(s) excluding the above UEs.

[0172] As an example, the multiple candidate priority groups include gNB / eNB; the UE(s) directly synchronized to gNB / eNB; the UE(s) indirectly synchronized to gNB / eNB; GNSS; the UE(s) directly synchronized to GNSS; the UE(s) indirectly synchronized to GNSS; the remaining UE(s) excluding the above UEs.

[0173] As an example, the multiple candidate priority groups include the UE(s) that need to perform a first operation; gNB / eNB; the UE(s) directly synchronized to gNB / eNB; the UE(s) indirectly synchronized to gNB / eNB; GNSS; the UE(s) directly synchronized to GNSS; the UE(s) indirectly synchronized to GNSS; the remaining UE(s) excluding the above UEs.

[0174] As an example, the multiple candidate priority groups include the UE(s) directly synchronized to GNSS; the UE(s) indirectly synchronized to GNSS; gNB / eNB; the UE(s) directly synchronized to gNB / eNB; the UE(s) indirectly synchronized to gNB / eNB.

[0175] As an example, the multiple candidate priority groups include the UE(s) that need to perform a first operation; the UE(s) directly synchronized to the GNSS; the UE(s) indirectly synchronized to the GNSS; the gNB / eNB; the UE(s) directly synchronized to the gNB / eNB; the UE(s) indirectly synchronized to the gNB / eNB.

[0176] As an example, the multiple candidate priority groups include the UE(s) directly synchronized to the gNB / eNB; the UE(s) indirectly synchronized to the gNB / eNB; the GNSS; the UE(s) directly synchronized to the GNSS; the UE(s) indirectly synchronized to the GNSS.

[0177] As an example, the multiple candidate priority groups include the UE(s) that need to perform a first operation; the UE(s) directly synchronized to the gNB / eNB; the UE(s) indirectly synchronized to the gNB / eNB; the GNSS; the UE(s) directly synchronized to the GNSS; the UE(s) indirectly synchronized to the GNSS.

[0178] As an example, the UE(s) that need to perform a first operation belong to one of the candidate priority groups among the multiple candidate priority groups.

[0179] As an example, one of the candidate priority groups among the multiple candidate priority groups includes the UE(s) that need to perform a first operation.

[0180] As an example, the UE(s) directly synchronized to the GNSS belong to one of the candidate priority groups among the multiple candidate priority groups.

[0181] As an example, one of the candidate priority groups among the multiple candidate priority groups includes the UE(s) directly synchronized to the GNSS.

[0182] As an example, the UE(s) indirectly synchronized to the GNSS belong to one of the candidate priority groups among the multiple candidate priority groups.

[0183] As an example, one of the candidate priority groups among the multiple candidate priority groups includes the UE(s) indirectly synchronized to the GNSS.

[0184] As an example, the gNB / eNB belongs to one of the candidate priority groups among the multiple candidate priority groups.

[0185] As an example, one of the candidate priority groups among the multiple candidate priority groups includes the gNB / eNB.

[0186] As an example, the UE(s) directly synchronized to the gNB / eNB belong to one of the candidate priority groups among the multiple candidate priority groups.

[0187] As an example, one of the multiple candidate priority groups includes the UE(s) directly synchronized to the gNB / eNB.

[0188] As an example, the UE(s) indirectly synchronized to the gNB / eNB belong to one of the multiple candidate priority groups.

[0189] As an example, one of the multiple candidate priority groups includes the UE(s) indirectly synchronized to the gNB / eNB.

[0190] As an example, GNSS belongs to one of the multiple candidate priority groups.

[0191] As an example, one of the multiple candidate priority groups includes GNSS.

[0192] In some embodiments, the multiple candidate priority groups can also be indicated according to at least two of the SLSSID of the UE(s), InC, and the resources occupied by the sidelink synchronization signal (SLSS). As an example, the multiple candidate priority groups include:

[0193] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3;

[0194] UE(s) with SLSSID = 0, SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false;

[0195] UE(s) with SLSSID = 337 and InC = false;

[0196] gNB / eNB, or GNSS;

[0197] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0198] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0199] The remaining UE(s) excluding the above UEs.

[0200] As an example, the multiple candidate priority groups include:

[0201] UE(s) carrying the first type of identifier by SLSS, or UE(s) occupying the first type of resource by SLSS;

[0202] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitting on the time slot indicated by sl-SSB-TimeAllocation3;

[0203] UE(s) with SLSSID = 0, SLSS not transmitting on the time slot indicated by sl-SSB-TimeAllocation3 and InC = false;

[0204] UE(s) with SLSSID = 337 and InC = false;

[0205] gNB / eNB, or GNSS;

[0206] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0207] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0208] The remaining UE(s) excluding the above UEs.

[0209] As an example, the multiple candidate priority groups include:

[0210] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitting on the time slot indicated by sl-SSB-TimeAllocation3;

[0211] UE(s) with SLSSID = 0, SLSS not transmitting on the time slot indicated by sl-SSB-TimeAllocation3 and InC = false;

[0212] UE(s) with SLSSID = 337 and InC = false;

[0213] gNB / eNB, or GNSS;

[0214] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0215] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false.

[0216] As an example, the multiple candidate priority groups include:

[0217] UE(s) carried by the SLSS with the first type of identifier, or UE(s) that the SLSS occupies the first type of resource;

[0218] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and the SLSS transmits in the time slot indicated by sl-SSB-TimeAllocation3;

[0219] UE(s) with SLSSID = 0, the SLSS does not transmit in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false;

[0220] UE(s) with SLSSID = 337 and InC = false;

[0221] gNB / eNB, or GNSS;

[0222] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0223] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false.

[0224] As an example, UE(s) carried by the SLSS with the first type of identifier, or UE(s) that the SLSS occupies the first type of resource belong to one of the multiple candidate priority groups.

[0225] As an example, one of the multiple candidate priority groups includes UE(s) carried by the SLSS with the first type of identifier, or UE(s) that the SLSS occupies the first type of resource.

[0226] As an example, UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and the SLSS transmits in the time slot indicated by sl-SSB-TimeAllocation3 belong to one of the multiple candidate priority groups.

[0227] As an example, one of the multiple candidate priority groups includes UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and the SLSS transmits in the time slot indicated by sl-SSB-TimeAllocation3.

[0228] As an example, the UE(s) with SLSSID = 0 and SLSS not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and InC = false belong to one of the multiple candidate priority groups.

[0229] As an example, one of the multiple candidate priority groups includes the UE(s) with SLSSID = 0 and SLSS not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and InC = false.

[0230] As an example, one of the multiple candidate priority groups includes the UE(s) with SLSSID = 337 and InC = false.

[0231] As an example, the UE(s) with SLSSID = 337 and InC = false belong to one of the multiple candidate priority groups.

[0232] As an example, the UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true belong to one of the multiple candidate priority groups.

[0233] As an example, one of the multiple candidate priority groups includes the UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true.

[0234] As an example, the UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false belong to one of the multiple candidate priority groups.

[0235] As an example, one of the multiple candidate priority groups includes the UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false. As an example, the target priority group can be set as the highest-priority group P0 among the multiple candidate priority groups. For example, the first candidate priority group can be as shown in Table 3.

[0236] Table 3

[0237]

[0238] It should be understood that establishing a sidelink unicast link in Table 3 can be replaced with performing a first operation. Exemplarily, establishing a sidelink unicast link can also be sidelink initial beam pairing or sidelink beam management.

[0239] As shown in Table 3, when the S-SSB is the first S-SSB, the target priority group is independent of the SLSSID, InCoverage indication carried by the first S-SSB, and the time-frequency resources occupied by the S-SSB. When the S-SSB is not the first S-SSB, the target priority group is jointly determined according to at least two of the SLSSID, InCoverage indication carried by the S-SSB, and the time-frequency resources occupied by the S-SSB.

[0240] Comparing Table 2 and Table 3, it can be seen that Priority Group 0 is introduced in the first priority group order, and the user equipment performing the first operation belongs to Priority Group 0. Therefore, in the synchronization priority rule of Table 3, the user equipment performing the first operation has a high priority.

[0241] Exemplarily, the position of the target priority group in the first priority group order can be determined according to any one of the priority groups in the multiple candidate priority groups except the target priority group. The candidate priority groups used to determine the target priority group order can be referred to as given candidate priority groups. Exemplarily, as a reference group, the target priority group can be before or after the given candidate priority group. Therefore, the order in which the target priority group is selected will be determined according to the selected given candidate priority group.

[0242] As an embodiment, the multiple candidate priority groups include the given candidate priority group, and the position of the target priority group in the multiple candidate priority groups is before the position of the given candidate priority group in the multiple candidate priority groups. For example, the given candidate priority group can be Priority Group 2 corresponding to P2 in Table 3. When the position of the target priority group in the multiple candidate priority groups is before P2, the position of the target priority group can be between P1 and P2, or it can be P1.

[0243] As an embodiment, the position of the target priority in the multiple candidate priority groups is after the position of the given candidate priority group in the multiple candidate priority groups. For example, the given candidate priority group can be Priority Group 2 corresponding to P2 in Table 3. When the position of the target priority group in the multiple candidate priority groups is after P2, the position of the target priority group can be between P2 and P3, or it can be P3.

[0244] As an example, the given candidate priority group is any one of the seven candidate priorities: GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; and the remaining UE(s) excluding the above UEs. The position of the target priority group among the multiple candidate priority groups is before the position of any one of the above priority groups.

[0245] As an example, the given candidate priority group is any one of the seven candidate priorities: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; and the remaining UE(s) excluding the above UEs. The position of the target priority group among the multiple candidate priority groups is before the position of any one of the above priority groups.

[0246] As an example, the given candidate priority group is UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3. The position of the target priority group among the multiple candidate priority groups is before the position of this given candidate priority group.

[0247] As an example, the given candidate priority group is UE(s) with SLSSID = 0, SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false. The position of the target priority group among the multiple candidate priority groups is before the position of this given candidate priority group.

[0248] As an example, the given candidate priority group is UE(s) with SLSSID = 337 and InC = false. The position of the target priority group among the multiple candidate priority groups is before the position of this given candidate priority group.

[0249] As an example, the given candidate priority group is gNB / eNB, or GNSS. The position of the target priority group among the multiple candidate priority groups is before the position of this given candidate priority group.

[0250] As an example, the given candidate priority group is UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true. The position of the target priority group among the multiple candidate priority groups is before the position of this given candidate priority group.

[0251] As an example, for the UE(s) with the given candidate priority group SLSSID ∈ {0, 1,..., 335} and InC = false, the position of the target priority group among the multiple candidate priority groups is before the position of the given candidate priority group.

[0252] As an example, for the remaining UE(s) after removing the above UEs as the given candidate priority group, the position of the target priority group among the multiple candidate priority groups is before the position of the given candidate priority group.

[0253] As an example, the given candidate priority group corresponds to the UE(s) that indirectly synchronize to GNSS or indirectly synchronize to gNB / eNB in Table 3, and the position of the target priority group among the multiple candidate priority groups is between P1 and P2.

[0254] As an example, the given candidate priority group corresponds to the gNB / eNB or GNSS of P3 in Table 3, and the position of the target priority group among the multiple candidate priority groups is between P2 and P3.

[0255] As an example, the given candidate priority group corresponds to the UE(s) that directly synchronize to gNB / eNB or directly synchronize to GNSS of P4 in Table 3, and the position of the target priority group among the multiple candidate priority groups is between P3 and P4.

[0256] As an example, the given candidate priority group corresponds to the UE(s) that indirectly synchronize to gNB / eNB or indirectly synchronize to GNSS of P5 in Table 3, and the position of the target priority group among the multiple candidate priority groups is between P4 and P5.

[0257] As an example, the given candidate priority group corresponds to the remaining UE(s) with the lowest priority of P6 in Table 3, and the position of the target priority group among the multiple candidate priority groups is between P5 and P6. As an example, the multiple candidate priority groups include, in addition to the priority group corresponding to the UE(s) that need to perform the first operation, multiple priority groups corresponding to any combination of UEs of P1 to P6 in Table 3.

[0258] As a sub - example of the above embodiment, the multiple candidate priority groups include the priority group corresponding to the UE(s) that need to perform the first operation, and also include the UE(s) that directly or indirectly synchronize to GNSS or gNB / eNB and the remaining UE(s) with the lowest priority.

[0259] As an example, the first priority group order is a priority group order composed of the priority group including the UE(s) that need to perform the first operation and any other multiple priority groups in Table 3.

[0260] As an example, the first priority group order is the order of multiple priority groups based on GNSS.

[0261] As an example, the first priority group order is the order of multiple priority groups based on gNB / eNB.

[0262] As an example, the first priority group order is: GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; the remaining UE(s) excluding the above UEs, and the seven candidate priority groups are arranged in sequence.

[0263] As an example, the first priority group order is: UE(s) that need to perform the first operation; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; the remaining UE(s) excluding the above UEs, and the eight candidate priority groups are arranged in sequence.

[0264] As an example, the first priority group order is: GNSS; UE(s) that need to perform the first operation; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; the remaining UE(s) excluding the above UEs, and the eight candidate priority groups are arranged in sequence.

[0265] As an example, the first priority group order is: GNSS; UE(s) directly synchronized to GNSS; UE(s) that need to perform the first operation; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; the remaining UE(s) excluding the above UEs, and the eight candidate priority groups are arranged in sequence.

[0266] As an example, the order of the first priority groups is as follows: GNSS; UEs directly synchronized to GNSS; UEs indirectly synchronized to GNSS; UEs that need to perform the first operation; gNB / eNB; UEs directly synchronized to gNB / eNB; UEs indirectly synchronized to gNB / eNB; the remaining UEs after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0267] As an example, the order of the first priority groups is as follows: GNSS; UEs directly synchronized to GNSS; UEs indirectly synchronized to GNSS; gNB / eNB; UEs that need to perform the first operation; UEs directly synchronized to gNB / eNB; UEs indirectly synchronized to gNB / eNB; the remaining UEs after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0268] As an example, the order of the first priority groups is as follows: GNSS; UEs directly synchronized to GNSS; UEs indirectly synchronized to GNSS; gNB / eNB; UEs directly synchronized to gNB / eNB; UEs that need to perform the first operation; UEs indirectly synchronized to gNB / eNB; the remaining UEs after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0269] As an example, the order of the first priority groups is as follows: GNSS; UEs directly synchronized to GNSS; UEs indirectly synchronized to GNSS; gNB / eNB; UEs directly synchronized to gNB / eNB; UEs indirectly synchronized to gNB / eNB; UEs that need to perform the first operation; the remaining UEs after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0270] As an example, the order of the first priority groups is as follows: gNB / eNB; UEs directly synchronized to gNB / eNB; UEs indirectly synchronized to gNB / eNB; GNSS; UEs directly synchronized to GNSS; UEs indirectly synchronized to GNSS; the remaining UEs after removing the above UEs. The seven candidate priority groups are arranged in sequence.

[0271] As an example, the order of the first priority groups is as follows: UEs that need to perform the first operation; gNB / eNB; UEs directly synchronized to gNB / eNB; UEs indirectly synchronized to gNB / eNB; GNSS; UEs directly synchronized to GNSS; UEs indirectly synchronized to GNSS; the remaining UEs after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0272] As an example, the order of the first priority groups is: gNB / eNB; UE(s) that need to perform the first operation; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; the remaining UE(s) after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0273] As an example, the order of the first priority groups is: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) that need to perform the first operation; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; the remaining UE(s) after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0274] As an example, the order of the first priority groups is: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; UE(s) that need to perform the first operation; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; the remaining UE(s) after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0275] As an example, the order of the first priority groups is: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) that need to perform the first operation; UE(s) indirectly synchronized to GNSS; the remaining UE(s) after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0276] As an example, the order of the first priority groups is: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; UE(s) that need to perform the first operation; the remaining UE(s) after removing the above UEs. The eight candidate priority groups are arranged in sequence.

[0277] As an example, the order of the first priority groups is as follows: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; UE(s) that need to perform the first operation; the remaining UE(s) excluding the above UEs, and the eight candidate priority groups are arranged in sequence. As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB, and the five candidate priority groups are arranged in sequence.

[0278] As an example, the order of the first priority groups is as follows: UE(s) that need to perform the first operation; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB, and the six candidate priority groups are arranged in sequence.

[0279] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to GNSS; UE(s) that need to perform the first operation; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB, and the six candidate priority groups are arranged in sequence.

[0280] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; UE(s) that need to perform the first operation; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB, and the six candidate priority groups are arranged in sequence.

[0281] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) that need to perform the first operation; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB, and the six candidate priority groups are arranged in sequence.

[0282] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) that need to perform the first operation; UE(s) indirectly synchronized to gNB / eNB, and the six candidate priority groups are arranged in sequence.

[0283] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; UE(s) that need to perform the first operation, and the six candidate priority groups are arranged in sequence.

[0284] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS, and the five candidate priority groups are arranged in sequence.

[0285] As an example, the order of the first priority groups is as follows: UE(s) that need to perform the first operation; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS, and the six candidate priority groups are arranged in sequence.

[0286] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to gNB / eNB; UE(s) that need to perform the first operation; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS, and the six candidate priority groups are arranged in sequence.

[0287] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; UE(s) that need to perform the first operation; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS, and the six candidate priority groups are arranged in sequence.

[0288] As an example, the order of the first priority groups is as follows: UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) that need to perform the first operation; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS, and the six candidate priority groups are arranged in sequence.

[0289] As an embodiment, the first priority group order is: UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) that need to perform the first operation; UE(s) indirectly synchronized to GNSS, and the six candidate priority groups are arranged in sequence.

[0290] As an embodiment, the first priority group order is: UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; UE(s) that need to perform the first operation, and the six candidate priority groups are arranged in sequence.

[0291] As an embodiment, the first priority group order is:

[0292] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3

[0293] ;

[0294] UE(s) with SLSSID = 0, SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false;

[0295] UE(s) with SLSSID = 337 and InC = false;

[0296] gNB / eNB;

[0297] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0298] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0299] The remaining UE(s) after removing the above UEs, and the seven candidate priority groups are arranged in sequence.

[0300] As an embodiment, the first priority group order is:

[0301] UE(s) with SLSS carrying the first type of identifier, or UE(s) with SLSS occupying the first type of resources;

[0302] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3

[0303] transmitted on;

[0304] UE(s) with SLSSID = 0 and SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3 and InC = false;

[0305] UE(s) with SLSSID = 337 and InC = false;

[0306] gNB / eNB;

[0307] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0308] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0309] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0310] As an example, the order of the first priority group is:

[0311] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3;

[0312] UE(s) with SLSS carrying the first type of identifier, or UE(s) with SLSS occupying the first type of resources;

[0313] UE(s) with SLSSID = 0 and SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3 and InC = false;

[0314] UE(s) with SLSSID = 337 and InC = false;

[0315] gNB / eNB;

[0316] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0317] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0318] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0319] As an embodiment, the order of the first priority group is:

[0320] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3;

[0321] UE(s) with SLSSID = 0, SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false;

[0322] UE(s) with SLSSID = 337 and InC = false;

[0323] UE(s) with SLSS carrying the first type of identifier, or UE(s) with SLSS occupying the first type of resources;

[0324] gNB / eNB;

[0325] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0326] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0327] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0328] As an embodiment, the order of the first priority group is:

[0329] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3;

[0330] UE(s) with SLSSID = 0, SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false;

[0331] UE(s) with SLSSID = 337 and InC = false;

[0332] gNB / eNB;

[0333] UE(s) with SLSS carrying the first type of identifier, or UE(s) with SLSS occupying the first type of resources;

[0334] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = true;

[0335] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = false;

[0336] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0337] As an example, the order of the first priority group is:

[0338] UE(s) where SLSSID = 0 and InC = true, or UE(s) where SLSSID = 0 and SLSS is transmitted in the time slot indicated by sl - SSB - TimeAllocation3;

[0339] UE(s) where SLSSID = 0, SLSS is not transmitted in the time slot indicated by sl - SSB - TimeAllocation3, and InC = false;

[0340] UE(s) where SLSSID = 337 and InC = false;

[0341] gNB / eNB;

[0342] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = true;

[0343] UE(s) where SLSS carries the first - type identifier, or UE(s) where SLSS occupies the first - type resources;

[0344] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = false;

[0345] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0346] As an example, the order of the first priority group is:

[0347] UE(s) where SLSSID = 0 and InC = true, or UE(s) where SLSSID = 0 and SLSS is transmitted in the time slot indicated by sl - SSB - TimeAllocation3;

[0348] UE(s) where SLSSID = 0, SLSS is not transmitted in the time slot indicated by sl - SSB - TimeAllocation3, and InC = false;

[0349] UE(s) with SLSSID = 337 and InC = false;

[0350] gNB / eNB;

[0351] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0352] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0353] UE(s) where the SLSS carries a first - type identifier, or UE(s) where the SLSS occupies first - type resources;

[0354] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0355] As an example, the order of the first priority group is:

[0356] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0357] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0358] GNSS;

[0359] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and the SLSS transmits in the time slot indicated by sl - SSB - TimeAllocation3;

[0360] UE(s) with SLSSID = 0, the SLSS does not transmit in the time slot indicated by sl - SSB - TimeAllocation3 and InC = false;

[0361] UE(s) with SLSSID = 337 and InC = false;

[0362] The remaining UE(s) after removing the above UEs are arranged in seven candidate priority groups in sequence.

[0363] As an example, the order of the first priority group is:

[0364] UE(s) where the SLSS carries a first - type identifier, or UE(s) where the SLSS occupies first - type resources;

[0365] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0366] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0367] GNSS;

[0368] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl - SSB - TimeAllocation3;

[0369] UE(s) with SLSSID = 0, SLSS not transmitted in the time slot indicated by sl - SSB - TimeAllocation3 and InC = false;

[0370] UE(s) with SLSSID = 337 and InC = false;

[0371] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0372] As an example, the order of the first priority group is:

[0373] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0374] UE(s) with SLSS carrying the first - type identifier, or UE(s) with SLSS occupying the first - type resources;

[0375] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0376] GNSS;

[0377] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl - SSB - TimeAllocation3;

[0378] UE(s) with SLSSID = 0, SLSS not transmitted in the time slot indicated by sl - SSB - TimeAllocation3 and InC = false;

[0379] UE(s) with SLSSID = 337 and InC = false;

[0380] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0381] As an example, the order of the first priority group is:

[0382] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = true;

[0383] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = false;

[0384] UE(s) where the SLSS carries the first type of identifier, or UE(s) where the SLSS occupies the first type of resource;

[0385] GNSS;

[0386] UE(s) where SLSSID = 0 and InC = true, or UE(s) where SLSSID = 0 and the SLSS transmits in the time slot indicated by sl-SSB-TimeAllocation3;

[0387] UE(s) where SLSSID = 0, the SLSS does not transmit in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false;

[0388] UE(s) where SLSSID = 337 and InC = false;

[0389] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0390] As an example, the first priority group order is:

[0391] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = true;

[0392] UE(s) where SLSSID ∈ {0, 1,..., 335} and InC = false;

[0393] GNSS;

[0394] UE(s) where the SLSS carries the first type of identifier, or UE(s) where the SLSS occupies the first type of resource;

[0395] UE(s) where SLSSID = 0 and InC = true, or UE(s) where SLSSID = 0 and the SLSS transmits in the time slot indicated by sl-SSB-TimeAllocation3;

[0396] UE(s) where SLSSID = 0, the SLSS does not transmit in the time slot indicated by sl-SSB-TimeAllocation3, and InC = false;

[0397] UE(s) with SLSSID = 337 and InC = false;

[0398] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0399] As an example, the order of the first priority group is:

[0400] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0401] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0402] GNSS;

[0403] UE(s) with SLSSID = 0 and InC = true, or UE(s) with SLSSID = 0 and SLSS transmitted in the time slot indicated by sl-SSB-TimeAllocation3;

[0404] UE(s) with SLSS carrying the first type of identifier, or UE(s) with SLSS occupying the first type of resources;

[0405] UE(s) with SLSSID = 0 and SLSS not transmitted in the time slot indicated by sl-SSB-TimeAllocation3 and InC = false;

[0406] UE(s) with SLSSID = 337 and InC = false;

[0407] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0408] As an example, the order of the first priority group is:

[0409] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = true;

[0410] UE(s) with SLSSID ∈ {0, 1,..., 335} and InC = false;

[0411] GNSS;

[0412] UE(s) with SLSSID = 0 and InC = true, or, UE(s) with SLSSID = 0 and SLSS transmitted in the time slot

[0413] indicated by sl-SSB-TimeAllocation3;

[0414] UE(s) with SLSSID = 0 and SLSS not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and InC = false;

[0415] UE(s) with SLSSID = 337 and InC = false;

[0416] UE(s) where the SLSS carries a first type of identifier, or UE(s) that occupy first type of resources;

[0417] The remaining UE(s) after removing the above UEs are arranged in eight candidate priority groups in sequence.

[0418] As an embodiment, the first priority group order is a priority group order composed of the priority group corresponding to the UE that needs to perform a first operation and multiple priority groups corresponding to any combination of UEs in Table 3.

[0419] From the priority group order in Table 3, it can be seen that this implementation method redefines the synchronization priority rules. Specifically, the above implementation method assigns the user equipment that needs to perform the first operation to a higher priority group, or introduces a new priority group for the user equipment that needs to perform the first operation.

[0420] In some embodiments, reusing the traditional synchronization priority rules, when the user equipment needs to perform a first operation, the synchronization priority of the user equipment is increased by a priority offset so that the user equipment can be preferentially selected. Exemplarily, according to the traditional synchronization priority rules (for example, Figure 2 ), UE1 belongs to priority group 4. When UE1 needs to establish a sidelink unicast link, UE1 is assigned to a new priority group. The new priority group is, for example, priority group 1, then priority offset = 3. The new priority group is, for example, priority group 2, then priority offset = 2.

[0421] Exemplarily, the target priority group corresponding to the sending node of the first S-SSB can be determined according to the reference priority group and the priority offset in the first priority group order. Exemplarily, multiple candidate priority groups may include a first reference priority group, and the index of the target priority group is determined according to the index of the first reference priority group and the priority offset.

[0422] As an embodiment, the index of the target priority group is the difference between the index of the first reference priority group and the priority offset. For example, the index of the first reference priority group is 3, the priority offset is 2, and the index of the target priority group is 1.

[0423] As an example, the index of the target priority group is the maximum of 1 and the difference between the index of the first reference priority group and the priority group offset. For example, the index of the first reference priority group is 3, the priority group offset is 3, the difference between the index of the first reference priority group and the priority group offset is 0, and the index of the target priority group is 1.

[0424] As an embodiment, the multiple candidate priority groups include a first reference priority group; the index of the target priority group is the difference between the index of the first reference priority group and the priority group offset, or the index of the target priority group is the maximum of 1 and the difference between the index of the first reference priority group and the priority group offset.

[0425] For example, new priority group = original priority group - priority offset.

[0426] Also, when original priority group - priority offset < 1, new priority group = 1.

[0427] As an embodiment, the index of the target priority group is the index of the target priority group among the multiple candidate priority groups.

[0428] As an embodiment, the index of the first reference priority group is the index of the first reference priority group among the multiple candidate priority groups.

[0429] Exemplarily, at least two of the SLSSID carried by the first S-SSB, the InCoverage indication, and the time-frequency resources occupied by the first S-SSB are jointly used to determine the first reference priority group, and the first sidelink synchronization signal block is used to determine the priority group offset.

[0430] As an embodiment, the first operation is used to determine the priority group offset.

[0431] As an embodiment, the first type of identifier is used to determine the priority group offset.

[0432] As an embodiment, the first type of resource is used to determine the priority group offset.

[0433] As an embodiment, the priority group offset is not less than 0.

[0434] As an embodiment, the priority group offset is a non-negative integer.

[0435] As an embodiment, the priority group offset is not 0.

[0436] As an embodiment, the priority group offset is 0.

[0437] As an example, at least two of the SLSSID carried by the first S-SSB, the InCoverage indication, and the time-frequency resources occupied by the first S-SSB are jointly used to determine the first reference priority group.

[0438] As an example, the time-frequency resources include time-domain resources and / or frequency-domain resources.

[0439] As an example, the time-domain resources are represented by time slots or symbols or other time units.

[0440] As an example, the frequency-domain resources are represented by subcarriers or resource blocks or other frequency band units.

[0441] As an example, the first S-SSB is used to determine the priority group offset.

[0442] For ease of understanding, the implementation manner of determining the target priority group based on the reference priority group and the priority group offset will be exemplarily described below. Figure 8 For ease of understanding, the implementation manner of determining the target priority group according to the reference priority group and the priority group offset will be exemplarily described below.

[0443] See Figure 8 , when the index of the first reference priority group corresponding to the sending node of the first S-SSB is the synchronization priority group 4 and the priority group offset is 2, the index of the target priority group corresponding to the sending node is the synchronization priority group 2.

[0444] From Figure 8 it can be seen that after determining the first reference priority group according to the first S-SSB, subtract 2 from the index of the first reference priority group to determine the index of the target priority group, thereby improving the priority of the sending node of the first S-SSB.

[0445] In some embodiments, the multiple candidate priority groups in the first priority group order may include a first priority group and a second priority group. The first priority group and the second priority group may be two priority groups determined based on different reference sources. The sending node of the first S-SSB corresponds to one of the first priority group and the second priority group.

[0446] As an example, the priority group corresponding to the sending node of the first S-SSB includes the first priority group.

[0447] As an example, the first priority group belongs to the priority group corresponding to the sending node of the first S-SSB.

[0448] As an example, the priority group corresponding to the sending node of the first S-SSB includes the second priority group.

[0449] As an embodiment, the second priority group belongs to the priority group corresponding to the transmitting node of the first S-SSB.

[0450] Exemplarily, the first priority group corresponds to user equipment that selects a cell as a synchronization reference, or the first priority group corresponds to user equipment that selects a first type of user equipment as a synchronization reference; the second priority group corresponds to user equipment that selects GNSS as a synchronization reference, or the second priority group corresponds to user equipment that selects a second type of user equipment as a synchronization reference. Among them, the first type of user equipment selects a cell as a synchronization reference, and the second type of user equipment selects GNSS as a synchronization reference. For example, the first priority group corresponds to the synchronization priority based on the gNB / eNB, and the second priority group corresponds to the synchronization priority based on GNSS.

[0451] As an embodiment, the first priority group corresponds to user equipment that selects a cell as a synchronization reference, and the second priority group corresponds to user equipment that selects GNSS as a synchronization reference.

[0452] As an embodiment, the first priority group includes user equipment that selects a cell as a synchronization reference, and the second priority group includes user equipment that selects GNSS as a synchronization reference.

[0453] As an embodiment, user equipment that selects a cell as a synchronization reference belongs to the first priority group, and user equipment that selects GNSS as a synchronization reference belongs to the second priority group.

[0454] As an embodiment, the first priority group corresponds to user equipment that selects a first type of user equipment as a synchronization reference, and the second priority group corresponds to user equipment that selects GNSS as a synchronization reference.

[0455] As an embodiment, the first priority group includes user equipment that selects a first type of user equipment as a synchronization reference, and the second priority group includes user equipment that selects GNSS as a synchronization reference.

[0456] As an embodiment, user equipment that selects a first type of user equipment as a synchronization reference belongs to the first priority group, and user equipment that selects GNSS as a synchronization reference belongs to the second priority group.

[0457] As an embodiment, the first priority group corresponds to user equipment that selects a cell as a synchronization reference, and the second priority group corresponds to user equipment that selects a second type of user equipment as a synchronization reference.

[0458] As an embodiment, the first priority group includes user equipment that selects a cell as a synchronization reference, and the second priority group includes user equipment that selects a second type of user equipment as a synchronization reference.

[0459] As an example, the user equipment that selects the cell as the synchronization reference belongs to the first priority group, and the user equipment that selects the second type of user equipment as the synchronization reference belongs to the second priority group.

[0460] As an example, the first priority group corresponds to the user equipment that selects the first type of user equipment as the synchronization reference, and the second priority group corresponds to the user equipment that selects the second type of user equipment as the synchronization reference.

[0461] As an example, the first priority group includes the user equipment that selects the first type of user equipment as the synchronization reference, and the second priority group includes the user equipment that selects the second type of user equipment as the synchronization reference.

[0462] As an example, the user equipment that selects the first type of user equipment as the synchronization reference belongs to the first priority group, and the user equipment that selects the second type of user equipment as the synchronization reference belongs to the second priority group.

[0463] As an example, the first priority group corresponds to the user equipment that selects the cell as the synchronization reference, and the second priority group corresponds to the user equipment that selects the first type of user equipment as the synchronization reference.

[0464] As an example, the first priority group includes the user equipment that selects the cell as the synchronization reference, and the second priority group includes the user equipment that selects the first type of user equipment as the synchronization reference.

[0465] As an example, the user equipment that selects the cell as the synchronization reference belongs to the first priority group, and the user equipment that selects the first type of user equipment as the synchronization reference belongs to the second priority group.

[0466] As an example, the first priority group corresponds to the user equipment that selects GNSS as the synchronization reference, and the second priority group corresponds to the user equipment that selects the second type of user equipment as the synchronization reference.

[0467] As an example, the first priority group includes the user equipment that selects GNSS as the synchronization reference, and the second priority group includes the user equipment that selects the second type of user equipment as the synchronization reference.

[0468] As an example, the user equipment that selects GNSS as the synchronization reference belongs to the first priority group, and the user equipment that selects the second type of user equipment as the synchronization reference belongs to the second priority group.

[0469] Exemplarily, the position of the first priority group among the multiple candidate priority groups is before the position of the second priority group among the multiple candidate priority groups, or the position of the first priority group among the multiple candidate priority groups is after the position of the second priority group among the multiple candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

[0470] As an embodiment, the first parameter is sl-SyncPriority.

[0471] As an embodiment, the description of the sl-SyncPriority refers to Sections 5.8.6.2 and 6.3.5 of 3GPP TS38.331.

[0472] As an embodiment, the first parameter is used to indicate the order of the first priority group.

[0473] As an embodiment, the first parameter is used to determine the order of the first priority group from among multiple priority group orders.

[0474] As an embodiment, the first parameter is set to GNSS, or gNB / eNB.

[0475] Exemplarily, the priority group of the sending node of the first S-SSB can be at least one of the first priority group or the second priority group. For example, when the order of the first priority group is the order of multiple first priority groups and multiple second priority groups, the priority group of the sending node of the first S-SSB can be any one of the priority groups.

[0476] As an embodiment, the first node can determine whether the priority group of the sending node of the first S-SSB belongs to the first priority group or the second priority group according to system configuration or pre-configuration.

[0477] Exemplarily, the aforementioned target priority group can be the first priority group or the second priority group. For example, the first priority group is the synchronization priority based on GNSS. To improve the priority of the target priority group, the position of the target priority group among the multiple candidate priority groups is before the UE that is directly synchronized to GNSS.

[0478] Among the various determination methods of the above first priority group order, one or more S-SSBs received by the first node further include a second S-SSB. Whether the second S-SSB is configured for a first operation, or whether the second S-SSB carries a first type of identifier, or whether the second S-SSB occupies a first type of resource is used to determine the priority group of the sending node of the first S-SSB.

[0479] As an example, the first S-SSB is configured for a first operation, the second S-SSB is not configured for the first operation, and the transmitting node of the first S-SSB is preferentially selected as the synchronization reference over the transmitting node of the second S-SSB block.

[0480] As an example, the first S-SSB carries a first type of identifier, the second S-SSB does not carry the first type of identifier, and the transmitting node of the first S-SSB is preferentially selected as the synchronization reference over the transmitting node of the second S-SSB block.

[0481] As an example, the first S-SSB occupies a first type of resource, the second S-SSB does not occupy the first type of resource, and the transmitting node of the first S-SSB is preferentially selected as the synchronization reference over the transmitting node of the second S-SSB block.

[0482] As an example, in the first priority group order, the position of the priority group corresponding to the transmitting node of the second S-SSB is after the position of the priority group corresponding to the transmitting node of the first S-SSB. That is, when the first node receives the first S-SSB and the second S-SSB, the priority of the transmitting node of the first S-SSB is higher than the priority of the transmitting node of the second S-SSB.

[0483] As described above in conjunction with Figures 4 to 8 a variety of determination methods for the first priority group order and the priority group of the transmitting node of the first S-SSB are introduced. The above methods are mainly used to enhance the priority group corresponding to the transmitting node of the first S-SSB so that this transmitting node can be preferentially selected as the synchronization reference. However, there may be a situation where multiple transmitting nodes will be preferentially selected in the above methods. For example, when multiple transmitting nodes are in the same priority group, how to select the synchronization reference also becomes a technical problem that needs to be solved.

[0484] To solve this problem, an embodiment of the present application also proposes another method in the first node for wireless communication to enable the transmitting node of the first S-SSB to be preferentially selected. This method reuses the traditional synchronization priority rules (for example, Figure 2 ) and adjusts the probability that the user equipment is preferentially selected through measurement results when the user equipment needs to perform the first operation.

[0485] Exemplarily, in the same priority group, when the user equipment needs to perform the first operation, the measurement results are used to make the user equipment be preferentially selected among all user equipments in the same priority group.

[0486] Exemplarily, in the same priority group, when a user equipment needs to perform a first operation, the measurement result of the user equipment is improved through measurement result offset, so that the user equipment has a greater probability of being selected as a synchronization reference compared with other user equipments in the same priority group.

[0487] For ease of understanding, the following combines Figure 9 with the method for determining the probability that a sending node is preferentially selected based on measurement results. It should be understood that Figure 9 is also executed by the first node. For the sake of brevity, the terms explained in Figure 4 will not be elaborated again in Figure 9 here.

[0488] Refer to Figure 9 . In step S910, one or more S-SSBs are received. This step is the same as step S410.

[0489] In step S920, one or more physical sidelink broadcast channels (PSBCHs) are measured.

[0490] One or more of the S-SSBs in step S910 may each include one or more PSBCHs respectively. That is to say, each S-SSB may include one PSBCH. For example, the first S-SSB includes the first PSBCH.

[0491] The first node measures the one or more PSBCHs, and one or more measurement results can be obtained. The one or more measurement results are used to determine whether the sending node of the first S-SSB is selected as a synchronization reference. The one or more measurement results include the result of the first node measuring the first PSBCH.

[0492] Exemplarily, one or more measurement results can be represented by various signal quality parameters. The signal quality parameters used to represent the measurement results may be parameters such as reference signal received power (RSRP), reference signal received quality (RSRQ), reference signal strength indication (RSSI), etc., which are not limited herein.

[0493] Exemplarily, one or more measurement results for one or more PSBCHs include the measurement result for the first PSBCH, and the measurement result for the first PSBCH is used to determine whether the sending node of the first S-SSB is selected as a synchronization reference.

[0494] As an example, when the measurement result of the first PSBCH is higher than a certain threshold value, the transmitting node of the first S-SSB is selected as the synchronization reference.

[0495] As an example, when the measurement result of the first PSBCH is the maximum value among multiple measurement results in the same priority group, the transmitting node of the first S-SSB is selected as the synchronization reference.

[0496] Exemplarily, when the multiple S-SSBs received by the first node include a second S-SSB, and the second S-SSB includes a second PSBCH, one or more measurement results for one or more PSBCHs include the measurement result for the second PSBCH. At least one of whether the second S-SSB is configured for the first operation, whether the second S-SSB carries a first type of identifier, and whether the second S-SSB occupies a first type of resource, and the magnitude relationship between the measurement result for the first PSBCH and the measurement result for the second PSBCH are used to determine whether the transmitting node of the first S-SSB is selected as the synchronization reference.

[0497] As an example, when the second S-SSB is configured for the first operation, the magnitude relationship between the measurement result for the first PSBCH and the measurement result for the second PSBCH is used to determine whether the transmitting node of the first S-SSB is selected as the synchronization reference; when the second S-SSB is not configured for the first operation, the transmitting node of the first S-SSB is preferentially selected as the synchronization reference over the transmitting node of the second S-SSB.

[0498] As a sub-example of the above example, the second S-SSB is configured for the first operation. When the measurement result for the first PSBCH is greater than the measurement result for the second PSBCH, the transmitting node of the first S-SSB is preferentially selected as the synchronization reference over the transmitting node of the second S-SSB; when the measurement result for the first PSBCH is less than the measurement result for the second PSBCH, the transmitting node of the second S-SSB is preferentially selected as the synchronization reference over the transmitting node of the first S-SSB.

[0499] As an example, when the second S-SSB carries the first type of identifier, the magnitude relationship between the measurement result for the first PSBCH and the measurement result for the second PSBCH is used to determine whether the transmitting node of the first S-SSB is selected as the synchronization reference; when the second S-SSB does not carry the first type of identifier, the transmitting node of the first S-SSB is preferentially selected as the synchronization reference over the transmitting node of the second S-SSB.

[0500] As a sub - embodiment of the above - mentioned embodiment, the second S - SSB carries the first - type identifier. When the measurement result for the first PSBCH is greater than the measurement result for the second PSBCH, the transmitting node of the first S - SSB is preferentially selected as the synchronization reference over the transmitting node of the second S - SSB; when the measurement result for the first PSBCH is less than the measurement result for the second PSBCH, the transmitting node of the second S - SSB is preferentially selected as the synchronization reference over the transmitting node of the first S - SSB.

[0501] As an embodiment, when the second S - SSB occupies the first - type resources, the magnitude relationship between the measurement result for the first PSBCH and the measurement result for the second PSBCH is used to determine whether the transmitting node of the first S - SSB is selected as the synchronization reference; when the second S - SSB does not occupy the first - type resources, the transmitting node of the first S - SSB is preferentially selected as the synchronization reference over the transmitting node of the second S - SSB.

[0502] As a sub - embodiment of the above - mentioned embodiment, the second S - SSB occupies the first - type resources. When the measurement result for the first PSBCH is greater than the measurement result for the second PSBCH, the transmitting node of the first S - SSB is preferentially selected as the synchronization reference over the transmitting node of the second S - SSB; when the measurement result for the first PSBCH is less than the measurement result for the second PSBCH, the transmitting node of the second S - SSB is preferentially selected as the synchronization reference over the transmitting node of the first S - SSB.

[0503] Exemplarily, the sum of the measurement result for the first PSBCH and the measurement result offset is used to determine whether the transmitting node of the first S - SSB is selected as the synchronization reference; the first S - SSB is used to determine the measurement result offset.

[0504] As an embodiment, the measurement result for the first PSBCH and the measurement result offset are jointly used to determine whether the transmitting node of the first S - SSB is selected as the synchronization reference.

[0505] As an embodiment, the first S - SSB is used to determine the measurement result offset.

[0506] As an embodiment, the sum of the measurement result for the first PSBCH and the measurement result offset is the maximum value among the one or more measurement results.

[0507] As an example, the sum of the measurement result for the first PSBCH and the measurement result offset is the maximum value among the one or more measurement results, and the transmission node of the first S-SSB is selected as the synchronization reference.

[0508] As an example, the sum of the measurement result for the first PSBCH and the measurement result offset is jointly used to determine whether the transmission node of the first S-SSB is selected as the synchronization reference.

[0509] For ease of understanding, the following combines Figure 10 , and gives an exemplary description of the method for determining whether the transmission node of the first S-SSB is preferentially selected according to the measurement result and the measurement result offset. Figure 10 In (a) of [], it is a comparison of multiple measurement results of multiple user equipments without considering the measurement result offset, and in (b), it is a comparison of multiple measurement results of multiple user equipments determined according to the measurement result offset.

[0510] Refer to Figure 10 In the figures (a) and (b) of [], UE2 receives three S-SSBs from UE1, UE3, and UE4. UE2 measures the three PSBCHs in the three S-SSBs respectively to obtain three PSBCH-RSRPs. Among them, UE1 is the user equipment that needs to perform the first operation, and the PSBCH-RSRP corresponding to UE1 is increased by an RSRP offset, and then it is determined whether to select UE1 as the synchronization reference according to the RSRP.

[0511] Comparing figures (a) and (b), it can be seen that in figure (a), the RSRP of UE1 is the minimum value among the three UEs, and in figure (b), the RSRP of UE1 has become the maximum value among the three UEs. Therefore, under the action of the RSRP offset, UE1 is preferentially selected as the synchronization reference compared with UE3 and UE4.

[0512] From Figure 10 , it can be seen that after increasing the PSBCH-RSRP detected by the user equipment by an RSRP offset, this user equipment has a greater probability of being selected as the SyncRefUE compared with other user equipments in the same priority group. That is to say, the probability that the transmission node of the first S-SSB is preferentially selected can be increased through the measurement result offset.

[0513] Above, the method embodiments of the present application have been described in detail in combination with Figures 1 to 10 , and below, the device embodiments of the present application will be described in detail in combination with Figures 11 to 14 . It should be understood that the description of the method embodiments corresponds to the description of the device embodiments. Therefore, for the parts not described in detail, reference can be made to the previous method embodiments.

[0514] Figure 11 A first node for wireless communication provided by an embodiment of the present application. As Figure 11 shown, the first node 1100 includes a first receiver 1110 and a first processor 1120.

[0515] The first receiver 1110 is configured to receive one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or, the first sidelink synchronization signal block carrying a first type of identifier, and / or, the first sidelink synchronization signal block occupying a first type of resource; wherein, the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management.

[0516] The first processor 1120 is configured to select a synchronization reference according to a first priority group order; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0517] As an embodiment, the first priority group order is an order of multiple candidate priority groups; the multiple candidate priority groups include a target priority group, and the sending node of the first sidelink synchronization signal block corresponds to the target priority group.

[0518] As an embodiment, the target priority group is the first candidate priority group among the multiple candidate priority groups.

[0519] As an embodiment, the multiple candidate priority groups include a first reference priority group; the index of the target priority group is the difference between the index of the first reference priority group and a priority group offset, or, the index of the target priority group is the maximum of the difference between the index of the first reference priority group and the priority group offset and 1; at least two of the sidelink synchronization signal identifier carried by the first sidelink synchronization signal block, the coverage indication, and the time-frequency resource occupied by the first sidelink synchronization signal block are jointly used to determine the first reference priority group, and the first sidelink synchronization signal block is used to determine the priority group offset.

[0520] As an embodiment, multiple sidelink synchronization signal blocks including the first sidelink synchronization signal block further include a second sidelink synchronization signal block. The first sidelink synchronization signal block is configured for the first operation, and the second sidelink synchronization signal block is not configured for the first operation; alternatively, the first sidelink synchronization signal block carries the first type of identifier, and the second sidelink synchronization signal block does not carry the first type of identifier; alternatively, the first sidelink synchronization signal block occupies the first type of resource, and the second sidelink synchronization signal block does not occupy the first type of resource; the sending node of the first sidelink synchronization signal block is preferentially selected as a synchronization reference compared to the sending node of the second sidelink synchronization signal block.

[0521] As an embodiment, the first priority group order is the order of multiple candidate priority groups, and the multiple candidate priority groups include a first priority group and a second priority group; the sending node of the first sidelink synchronization signal block corresponds to one of the first priority group and the second priority group.

[0522] As an embodiment, the first priority group corresponds to a user equipment that selects a cell as a synchronization reference, or the first priority group corresponds to a user equipment that selects a first type of user equipment as a synchronization reference, and the first type of user equipment selects a cell as a synchronization reference; the second priority group corresponds to a user equipment that selects GNSS as a synchronization reference, or the second priority group corresponds to a user equipment that selects a second type of user equipment as a synchronization reference, and the second type of user equipment selects GNSS as a synchronization reference.

[0523] As an embodiment, the position of the first priority group in the multiple candidate priority groups is before the position of the second priority group in the multiple candidate priority groups, or the position of the first priority group in the multiple candidate priority groups is after the position of the second priority group in the multiple candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

[0524] As an embodiment, the first node 1100 further includes a second processor, which can be used to measure one or more physical sidelink broadcast channels; wherein, the one or more sidelink synchronization signal blocks respectively include the one or more physical sidelink broadcast channels, and one or more measurement results for the one or more physical sidelink broadcast channels include a measurement result for a first physical sidelink broadcast channel, and the measurement result for the first physical sidelink broadcast channel is used to determine whether the sending node of the first sidelink synchronization signal block is selected as a synchronization reference.

[0525] As an embodiment, a plurality of sidelink synchronization signal blocks including the first sidelink synchronization signal block further includes a second sidelink synchronization signal block, and the second sidelink synchronization signal block includes a second physical sidelink broadcast channel; one or more measurement results for the one or more physical sidelink broadcast channels include a measurement result for the second physical sidelink broadcast channel; at least one of whether the second sidelink synchronization signal block is configured for the first operation, whether the second sidelink synchronization signal block carries the first type of identifier, and whether the second sidelink synchronization signal block occupies the first type of resource, and the magnitude relationship between the measurement result for the first physical sidelink broadcast channel and the measurement result for the second physical sidelink broadcast channel are used to determine whether the transmitting node of the first sidelink synchronization signal block is selected as the synchronization reference.

[0526] As an embodiment, the sum of the measurement result for the first physical sidelink broadcast channel and the measurement result offset is used to determine whether the transmitting node of the first sidelink synchronization signal block is selected as the synchronization reference; the first sidelink synchronization signal block is used to determine the measurement result offset.

[0527] As an embodiment, the first type of identifier is related to the transmitting node of the sidelink synchronization signal block, or the first type of identifier is related to the receiving node of the sidelink synchronization signal block, or the first type of identifier is related to the beam carrying the sidelink synchronization signal block.

[0528] As an embodiment, the first receiver 1110 may be a transceiver 1330, and the first processor may be a processor 1310. The second node 1100 may further include a memory 1320, specifically as Figure 13 shown.

[0529] Figure 12 A second node for wireless communication provided by an embodiment of the present application. As Figure 12 shown, the second node 1200 includes a first transmitter 1210.

[0530] The first transmitter 1210 is configured to transmit a first sidelink synchronization signal block, the first sidelink synchronization signal block is configured for a first operation, and / or the first sidelink synchronization signal block carries a first type of identifier, and / or the first sidelink synchronization signal block occupies a first type of resource; wherein, the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management; the receiving node of the first sidelink synchronization signal block selects a synchronization reference according to a first priority group order; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0531] As an embodiment, the first priority group order is the order of a plurality of candidate priority groups; the plurality of candidate priority groups includes a target priority group, and the second node corresponds to the target priority group.

[0532] As an embodiment, the target priority group is the first candidate priority group among the plurality of candidate priority groups.

[0533] As an embodiment, the plurality of candidate priority groups includes a first reference priority group; the index of the target priority group is the difference between the index of the first reference priority group and the priority group offset, or the index of the target priority group is the maximum value of the difference between the index of the first reference priority group and the priority group offset and 1; at least two of the sidelink synchronization signal identifier, the coverage indication carried by the first sidelink synchronization signal block, and the time-frequency resources occupied by the first sidelink synchronization signal block are jointly used to determine the first reference priority group, and the first sidelink synchronization signal block is used to determine the priority group offset.

[0534] As an embodiment, the plurality of sidelink synchronization signal blocks received by the receiving node of the first sidelink synchronization signal block further includes a second sidelink synchronization signal block, the first sidelink synchronization signal block is configured for the first operation, and the second sidelink synchronization signal block is not configured for the first operation; or, the first sidelink synchronization signal block carries the first type of identifier, and the second sidelink synchronization signal block does not carry the first type of identifier; or, the first sidelink synchronization signal block occupies the first type of resources, and the second sidelink synchronization signal block does not occupy the first type of resources; the second node is preferentially selected as the synchronization reference over the sending node of the second sidelink synchronization signal block.

[0535] As an embodiment, the first priority group order is the order of a plurality of candidate priority groups, the plurality of candidate priority groups includes a first priority group and a second priority group; the sending node of the first sidelink synchronization signal block corresponds to one of the first priority group and the second priority group.

[0536] As an embodiment, the first priority group corresponds to a user equipment that selects a cell as a synchronization reference, or the first priority group corresponds to a user equipment that selects a first type of user equipment as a synchronization reference, and the first type of user equipment selects a cell as a synchronization reference; the second priority group corresponds to a user equipment that selects GNSS as a synchronization reference, or the second priority group corresponds to a user equipment that selects a second type of user equipment as a synchronization reference, and the second type of user equipment selects GNSS as a synchronization reference.

[0537] As an example, the position of the first priority group among the multiple candidate priority groups is before the position of the second priority group among the multiple candidate priority groups, or the position of the first priority group among the multiple candidate priority groups is after the position of the second priority group among the multiple candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

[0538] As an example, the first type of identifier is related to the transmitting node of the sidelink synchronization signal block, or the first type of identifier is related to the receiving node of the sidelink synchronization signal block, or the first type of identifier is related to the beam carrying the sidelink synchronization signal block.

[0539] As an example, the first transmitter 1210 may be a transceiver 1330. The second node 1100 may further include a processor 1310 and a memory 1320, specifically as Figure 13 shown.

[0540] Figure 13 is a schematic structural diagram of the communication device according to the embodiment of the present application. Figure 13 The dashed lines in indicate that the unit or module is optional. The device 1300 can be used to implement the method described in the above method embodiment. The device 1300 can be a chip, a user equipment or a network equipment.

[0541] The device 1300 may include one or more processors 1310. The processor 1310 can support the device 1300 to implement the method described in the foregoing method embodiment. The processor 1310 can be a general-purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0542] Device 1300 may further include one or more memories 1320. Programs are stored on the memories 1320 and can be executed by the processor 1310, enabling the processor 1310 to execute the methods described in the foregoing method embodiments. The memories 1320 may be independent of the processor 1310 or integrated in the processor 1310.

[0543] Device 1300 may further include a transceiver 1330. The processor 1310 may communicate with other devices or chips through the transceiver 1330. For example, the processor 1310 may transmit and receive data with other devices or chips through the transceiver 1330.

[0544] Figure 14 This is a schematic diagram of the hardware modules of the communication device provided by the embodiments of the present application. Specifically, Figure 14 A block diagram showing a first communication device 1450 and a second communication device 1410 that communicate with each other in an access network is shown.

[0545] The first communication device 1450 includes a controller / processor 1459, a memory 1460, a data source 1467, a transmitting processor 1468, a receiving processor 1456, a multi-antenna transmitting processor 1457, a multi-antenna receiving processor 1458, a transmitter / receiver 1454, and an antenna 1452.

[0546] The second communication device 1410 includes a controller / processor 1475, a memory 1476, a data source 1477, a receiving processor 1470, a transmitting processor 1416, a multi-antenna receiving processor 1472, a multi-antenna transmitting processor 1471, a transmitter / receiver 1418, and an antenna 1420.

[0547] In the transmission from the second communication device 1410 to the first communication device 1450, at the second communication device 1410, upper layer data packets from the core network or from the data source 1477 are provided to the controller / processor 1475. The core network and the data source 1477 represent all protocol layers above the L2 layer. The controller / processor 1475 implements the functionality of the L2 layer. In the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 1450 based on various priority metrics. The controller / processor 1475 is also responsible for retransmission of lost packets and signaling to the first communication device 1450. The transmit processor 1416 and the multi-antenna transmit processor 1471 implement various signal processing functions for the Ll layer (i.e., the physical layer). The transmit processor 1416 implements encoding and interleaving to facilitate forward error correction at the second communication device 1410, and mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying, quadrature phase shift keying, M-phase shift keying, M-quadrature amplitude modulation). The multi-antenna transmit processor 1471 performs digital space precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. The transmit processor 1416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then uses the inverse fast Fourier transform to generate a physical channel carrying a time-domain multi-carrier symbol stream. Subsequently, the multi-antenna transmit processor 1471 performs transmit analog precoding / beamforming operations on the time-domain multi-carrier symbol stream. Each transmitter 1418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 1471 into a radio frequency stream and then provides it to different antennas 1420.

[0548] In a transmission from the second communication device 1410 to the first communication device 1450, at the first communication device 1450, each receiver 1454 receives signals via its respective antenna 1452. Each receiver 1454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream that is provided to the receive processor 1456. The receive processor 1456 and the multi-antenna receive processor 1458 perform various signal processing functions of the Ll layer. The multi-antenna receive processor 1458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receivers 1454. The receive processor 1456 uses the fast Fourier transform to convert the baseband multi-carrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 1456, where the reference signal will be used for channel estimation, and the data signal recovers any spatial streams destined for the first communication device 1450 after multi-antenna detection in the multi-antenna receive processor 1458. The symbols on each spatial stream are demodulated and recovered in the receive processor 1456, and soft decisions are generated. Subsequently, the receive processor 1456 decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 1410 on the physical channel. Subsequently, the upper layer data and control signals are provided to the controller / processor 1459. The controller / processor 1459 performs the functions of the L2 layer. The controller / processor 1459 may be associated with a memory 1460 that stores program code and data. The memory 1460 may be referred to as a computer-readable medium. In a transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the second communication device 1410. Subsequently, the upper layer data packets are provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing.

[0549] In the transmission from the first communication device 1450 to the second communication device 1410, at the first communication device 1450, an upper layer data packet is provided to the controller / processor 1459 using the data source 1467. The data source 1467 represents all protocol layers above the L2 layer. Similar to the transmission function described at the second communication device 1410 in the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels, and implements L2 layer functions for the user plane and the control plane. The controller / processor 1459 is also responsible for retransmitting lost packets and signaling to the second communication device 1410. The transmit processor 1468 performs modulation mapping and channel coding processing. The multi-antenna transmit processor 1457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Subsequently, the transmit processor 1468 modulates the generated spatial streams into multi-carrier / single-carrier symbol streams, and after the analog precoding / beamforming operation in the multi-antenna transmit processor 1457, provides them to different antennas 1452 via the transmitter 1454. Each transmitter 1454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 1457 into a radio frequency symbol stream and then provides it to the antenna 1452.

[0550] In the transmission from the first communication device 1450 to the second communication device 1410, the function at the second communication device 1410 is similar to the reception function described at the first communication device 1450 in the transmission from the second communication device 1410 to the first communication device 1450. Each receiver 1418 receives a radio frequency signal through its corresponding antenna 1420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna receive processor 1472 and the receive processor 1470. The receive processor 1470 and the multi-antenna receive processor 1472 jointly implement the Ll layer functions. The controller / processor 1475 implements the L2 layer functions. The controller / processor 1475 may be associated with a memory 1476 that stores program code and data. The memory 1476 may be referred to as a computer-readable medium. In the transmission from the first communication device 1450 to the second communication device 1410, the controller / processor 1475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packet from the first communication device 1450. The upper layer data packet from the controller / processor 1475 may be provided to the core network or all protocol layers above the L2 layer, and various control signals may also be provided to the core network or L3 for L3 processing.

[0551] As an example, the first communication device 1450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 1450 is at least configured to: receive one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or, the first sidelink synchronization signal block carrying a first type of identifier, and / or, the first sidelink synchronization signal block occupying a first type of resource; select a synchronization reference according to a first priority group order; wherein, the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management; and the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0552] As an example, the first communication device 1450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receiving one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or, the first sidelink synchronization signal block carrying a first type of identifier, and / or, the first sidelink synchronization signal block occupying a first type of resource; selecting a synchronization reference according to a first priority group order; wherein, the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management; and the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

[0553] As an example, the first communication device 1450 corresponds to the first node in the present application.

[0554] As an example, the second communication device 1410 corresponds to the second node in the present application.

[0555] As an example, the first communication device 1450 or the second communication device 1410 is a user equipment, and the user equipment can be used as a relay node.

[0556] As an example, the first communication device 1450 or the second communication device 1410 is a user equipment supporting V2X, and the user equipment can be used as a relay node.

[0557] As an example, the first communication device 1450 or the second communication device 1410 is a D2D-enabled user equipment, which can act as a relay node.

[0558] As an example, the first communication device 1450 or the second communication device 1410 is a network control relay (NCR).

[0559] As an example, the first communication device 1450 or the second communication device 1410 is a relay repeater.

[0560] As an example, the first communication device 1450 or the second communication device 1410 is a relay.

[0561] As an example, the antenna 1452, the receiver 1454, the multi-antenna reception processor 1458, the reception processor 1456, and the controller / processor 1459 are used to receive one or more sidelink synchronization signal blocks in this application.

[0562] As an example, the antenna 1420, the transmitter 1418, the multi-antenna transmission processor 1471, the transmission processor 1416, and the controller / processor 1475 are used to transmit the first sidelink synchronization signal block in this application.

[0563] An embodiment of this application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the terminal or network device provided in the embodiments of this application, and the program causes the computer to execute the methods performed by the terminal or network device in the various embodiments of this application.

[0564] An embodiment of this application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided in the embodiments of this application, and the program causes the computer to execute the methods performed by the terminal or network device in the various embodiments of this application.

[0565] An embodiment of this application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of this application, and the computer program causes the computer to execute the methods performed by the terminal or network device in the various embodiments of this application.

[0566] It should be understood that the terms "system" and "network" in this application may be used interchangeably. Additionally, the terms used in this application are only for explaining specific embodiments of this application and are not intended to limit this application. Terms such as "first", "second", "third", and "fourth" in the specification, claims, and drawings of this application are used to distinguish different objects rather than to describe a specific order. Furthermore, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion.

[0567] In the embodiments of this application, the "indication" mentioned may be a direct indication, an indirect indication, or may also indicate an associated relationship. For example, A indicates B, which may mean that A directly indicates B. For example, B can be obtained through A; it may also mean that A indirectly indicates B. For example, A indicates C and B can be obtained through C; it may also mean that there is an associated relationship between A and B.

[0568] In the embodiments of this application, "B corresponding to A" means that B is associated with A and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0569] In the embodiments of this application, the term "corresponding" may indicate a direct or indirect corresponding relationship between two parties, may also indicate an associated relationship between two parties, or may also be relationships such as indication and being indicated, configuration and being configured, etc.

[0570] In the embodiments of this application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in a device (for example, including user equipment and network equipment). This application does not limit its specific implementation manner. For example, predefined can refer to being defined in a protocol.

[0571] In the embodiments of this application, the "protocol" may refer to standard protocols in the communication field. For example, it may include LTE protocols, NR protocols, and related protocols applied to future communication systems. This application does not limit this.

[0572] In the embodiments of this application, the term "and / or" is merely a description of the associated relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Additionally, the character " / " in this text generally indicates that the associated objects before and after are in an "or" relationship.

[0573] In various embodiments of this application, the magnitude of the serial numbers of the above processes does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic and should not impose any limitation on the implementation process of the embodiments of this application.

[0574] In several embodiments provided by the present 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 illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, 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 displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0576] In addition, in each embodiment of the present application, the various functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0577] 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 processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, fiber optic, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may 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 integrated available media. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0578] As described above, the above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method in a first node for wireless communication, characterized in that, comprising: receiving one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or the first sidelink synchronization signal block carrying a first type of identifier, and / or the first sidelink synchronization signal block occupying a first type of resource; selecting a synchronization reference according to a first priority group order; wherein the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

2. The method according to claim 1, characterized in that, the first priority group order is an order of a plurality of candidate priority groups; the plurality of candidate priority groups include a target priority group, and the sending node of the first sidelink synchronization signal block corresponds to the target priority group.

3. The method according to claim 2, characterized in that, the target priority group is the first candidate priority group among the plurality of candidate priority groups.

4. The method according to claim 2, characterized in that, the plurality of candidate priority groups include a first reference priority group; the index of the target priority group is the difference between the index of the first reference priority group and a priority group offset, or the index of the target priority group is the maximum of the difference between the index of the first reference priority group and the priority group offset and 1; at least two of the sidelink synchronization signal identifier carried by the first sidelink synchronization signal block, the coverage indication, and the time-frequency resource occupied by the first sidelink synchronization signal block are jointly used to determine the first reference priority group, and the first sidelink synchronization signal block is used to determine the priority group offset.

5. The method according to any one of claims 1-4, characterized in that, the plurality of sidelink synchronization signal blocks including the first sidelink synchronization signal block further include a second sidelink synchronization signal block, the first sidelink synchronization signal block being configured for the first operation and the second sidelink synchronization signal block not being configured for the first operation; or the first sidelink synchronization signal block carrying the first type of identifier and the second sidelink synchronization signal block not carrying the first type of identifier; or the first sidelink synchronization signal block occupying the first type of resource and the second sidelink synchronization signal block not occupying the first type of resource; the sending node of the first sidelink synchronization signal block is preferentially selected as the synchronization reference compared to the sending node of the second sidelink synchronization signal block.

6. A method in a second node for wireless communication, characterized in that, comprising: transmitting a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or the first sidelink synchronization signal block carrying a first type of identifier, and / or the first sidelink synchronization signal block occupying a first type of resource; Among them, the receiving node of the first sidelink synchronization signal block selects a synchronization reference according to the first priority group order; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

7. A method in a first node for wireless communication, Characterized in that, Comprising: Receiving one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block; Among them, the first sidelink synchronization signal block includes a first physical sidelink broadcast channel, and the measurement result of the first physical sidelink broadcast channel is used to determine whether the sending node of the first sidelink synchronization signal block is selected as a synchronization reference.

8. A method in a second node for wireless communication, Characterized in that, Comprising: Sending a first sidelink synchronization signal block; Among them, the first sidelink synchronization signal block includes a first physical sidelink broadcast channel, and the measurement result of the first physical sidelink broadcast channel is used to determine whether the sending node of the first sidelink synchronization signal block is selected as a synchronization reference.

9. A first node for wireless communication, Characterized in that, Comprising: A first receiver, configured to receive one or more sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or, the first sidelink synchronization signal block carrying a first type of identifier, and / or, the first sidelink synchronization signal block occupying a first type of resource; A first processor, configured to select a synchronization reference according to the first priority group order; Among them, the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

10. A second node for wireless communication, Characterized in that, Comprising: A first transmitter, configured to send a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or, the first sidelink synchronization signal block carrying a first type of identifier, and / or, the first sidelink synchronization signal block occupying a first type of resource; Among them, the receiving node of the first sidelink synchronization signal block selects a synchronization reference according to the first priority group order; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

Images