Method and apparatus in node for wireless communication

Abstract

The present application provides a method and apparatus in a node for wireless communication. The method comprises: receiving one or more sidelink synchronization signal blocks, wherein the one or more sidelink synchronization signal blocks comprise a first sidelink synchronization signal block; and on the basis of a target priority group sequence, determining whether a sending node for the first sidelink synchronization signal block is selected as a synchronization reference, wherein the target priority group sequence is either one of a first priority group sequence and a second priority group sequence, at least one of whether the first sidelink synchronization signal block is configured for a first operation, whether the first sidelink synchronization signal block carries a first-type identifier, and whether the first sidelink synchronization signal block occupies a first-type resource is used for determining the target priority group sequence, and the first operation comprises at least one of initial beam pairing, sidelink unicast link establishment and sidelink beam management.

Description

Method and apparatus in a node for wireless communication Technical Field

[0001] The present application relates to the field of communication technology, and more particularly, to a method and apparatus in a node for wireless communication. Background Art

[0002] In sideline communications, using a sideline synchronization signal block or a modified format of a sideline synchronization signal block as a reference signal for initial beam pairing has become an optional solution. When the sending node performing initial beam pairing can serve as a synchronization reference source, if the receiving node has multiple synchronization reference sources, the sending node may not be selected as the synchronization reference, resulting in the sending node being unable to perform initial beam pairing. Therefore, how to perform initial beam pairing based on the sideline synchronization signal block is a technical problem that needs to be solved. Furthermore, after the introduction of 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 technical problems that need to be solved.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a method and apparatus in a node for wireless communication. The following introduces various aspects of the present application.

[0005] In a first aspect, a method is provided in a first node for wireless communication, comprising: receiving one or more side synchronization signal blocks, the one or more side synchronization signal blocks including a first side synchronization signal block; determining whether a sending node of the first side synchronization signal block is selected as a synchronization reference according to a target priority group order, the target priority group order being one of a first priority group order and a second priority group order; wherein at least one of whether the first side synchronization signal block is configured for a first operation, whether the first side synchronization signal block carries a first type of identifier, and whether the first side synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation includes at least one of initial beam pairing, side unicast link establishment, and side beam management.

[0006] In a second aspect, a method is provided in a second node for wireless communication, comprising: sending a first side synchronization signal block; wherein, at least one of whether the first side synchronization signal block is configured for the first operation, whether the first side synchronization signal block carries the first type of identifier, and whether the first side synchronization signal block occupies the first type of resource is used by the receiving node of the first side synchronization signal block to determine a target priority group order; the first operation includes at least one of initial beam pairing, side unicast link establishment and side beam management; the target priority group order is used to determine whether the second node is selected by the receiving node as a synchronization reference; the target priority group order is one of the first priority group order and the second priority group order.

[0007] According to a third aspect, a first node for wireless communication is provided, comprising: a first receiver for receiving one or more side synchronization signal blocks, the one or more side synchronization signal blocks including a first side synchronization signal block; a first processor for determining whether a sending node of the first side synchronization signal block is selected as a synchronization reference according to a target priority group order, the target priority group order being one of a first priority group order and a second priority group order; wherein at least one of whether the first side synchronization signal block is configured for a first operation, whether the first side synchronization signal block carries a first type of identifier, and whether the first side synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation comprises at least one of initial beam pairing, side unicast link establishment, and side beam management.

[0008] In a fourth aspect, a second node for wireless communication is provided, comprising: a first transmitter for sending a first side synchronization signal block; wherein, at least one of whether the first side synchronization signal block is configured for the first operation, whether the first side synchronization signal block carries the first type of identifier, and whether the first side synchronization signal block occupies the first type of resource is used by the receiving node of the first side synchronization signal block to determine a target priority group order; the first operation includes at least one of initial beam pairing, side unicast link establishment and side beam management; the target priority group order is used to determine whether the second node is selected by the receiving node as a synchronization reference; the target priority group order is one of the first priority group order and the second priority group order.

[0009] In a fifth aspect, a first node used for wireless communication is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the first node executes the method described in the first aspect.

[0010] In the sixth aspect, a second node used for wireless communication is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, 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, the system including the first node and / or the second node described above. In another possible design, the system may also include other devices that interact with the first node or the second node in the solution provided in the embodiment of the present application.

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

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

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

[0015] In an embodiment of the present application, after a first node receives one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, it can determine the priority group corresponding to the first sidelink synchronization signal block based on at least one of whether the first sidelink synchronization signal block is configured for a first operation, whether it carries a first type of identifier, and whether it occupies a first type of resource. The first type of identifier and the first type of resource are related to a first operation, and the first operation includes at least one of initial beam pairing, sidelink unicast link establishment, and beam management. Determining the priority of the sending node based on whether the first sidelink synchronization signal block is used for the first operation helps to achieve effective initial beam pairing before the sidelink unicast link is established.

[0016] In an embodiment of the present application, the first node acts as a receiving node, determines a target priority group order based on the situation of the first side synchronization signal block, and determines whether the sending node of the first side synchronization signal block is selected as a synchronization reference based on the target priority group order. The target priority group order is one of two priority group orders. That is, the first side synchronization signal block is configured for the first operation and is not configured for the first operation, and different priority group orders will be used to determine the priority respectively. Therefore, whether the first side synchronization signal block is used to establish a side unicast link is taken into account in this synchronization priority rule. In addition, the two priority group orders include a traditional priority group order and a priority group order related to the initial beam pairing, thereby optimizing the synchronization priority of the sending node of the initial beam pairing.

[0017] In this embodiment of the present application, any two nodes in sideline communication perform initial beam pairing before establishing a sideline unicast link. Using paired beams to establish a unicast link can expand the link range between the sending and receiving nodes, enabling more nodes to realize advanced business use cases.

[0018] In an embodiment of the present application, by performing initial beam pairing before establishing a side unicast link, the sending 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] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application is applicable.

[0020] FIG2 is a schematic diagram of the time slot structure of the side synchronization signal block.

[0021] FIG3 is a schematic diagram showing the distribution of multiple S-SSBs in one cycle.

[0022] FIG4 is a schematic flow chart of a method in a first node for wireless communication provided in an embodiment of the present application.

[0023] FIG5 is a schematic flow chart of an implementation method of initial beam pairing in the first operation.

[0024] FIG6 is a flowchart illustrating another implementation of initial beam pairing in the first operation.

[0025] FIG7 is a flow chart showing an implementation method of establishing a side unicast link in the first operation.

[0026] FIG8 is a flow chart of a possible implementation of the method shown in FIG4 .

[0027] FIG9 is a flowchart of another possible implementation of the method shown in FIG4 .

[0028] FIG. 10 is a flowchart illustrating a method for selecting a synchronization reference according to the result of step S930 in FIG. 9 .

[0029] FIG11 is a schematic structural diagram of a first node for wireless communication provided in an embodiment of the present application.

[0030] FIG12 is a schematic structural diagram of a second node for wireless communication provided in an embodiment of the present application.

[0031] FIG13 is a schematic structural diagram of the device provided in an embodiment of the present application.

[0032] FIG14 is a schematic diagram of the hardware modules of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0034] Figure 1 is a diagram illustrating a 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 geographic area and may communicate with terminals within the coverage area.

[0035] In some implementations, user equipment (UE) can communicate with other user devices via a sidelink (SL). Sidelink communication may also be referred to as proximity-based services (ProSe) communication, unilateral communication, sidelink communication, device-to-device (D2D) communication, etc.

[0036] In other words, sidelink data is transmitted between user equipments via a sidelink. The sidelink data may include data and / or control signaling. In some implementations, 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] The following describes several common sidelink communication scenarios with reference to Figure 1. Sidelink communication can be categorized into three scenarios, depending on whether the user device in the sidelink is within the coverage of the network device. Scenario 1: The user device conducts sidelink communication within the coverage of the network device. Scenario 2: Some user devices conduct sidelink communication within the coverage of the network device. Scenario 3: The user device conducts sidelink communication outside the coverage of the network device.

[0038] As shown in Figure 1, in scenario 1, user equipments 121-122 can communicate via a sidelink, and user equipments 121-122 are all within the coverage of network device 110, or in other words, user equipments 121-122 are all within the coverage of the same network device 110. In this scenario, network device 110 can send configuration signaling to user equipments 121-122, and accordingly, user equipments 121-122 communicate via the sidelink based on the configuration signaling.

[0039] As shown in Figure 1, in scenario 2, user equipment 123-124 can communicate via a sidelink, and user equipment 123 is within the coverage of network device 110, while user equipment 124 is outside the coverage of network device 110. In this scenario, user equipment 123 receives configuration information from network device 110 and communicates via the sidelink based on the configuration signaling. However, for user equipment 124, since user equipment 124 is outside the coverage of network device 110, it cannot receive the configuration information of network device 110. In this case, user equipment 124 can obtain the configuration of the sidelink communication based on pre-configuration configuration information and / or configuration information sent by user equipment 123 within the coverage area, so as to communicate with user equipment 123 via the sidelink based on the obtained configuration.

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

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

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

[0043] It should be noted that Figure 1 exemplarily shows a network device and multiple user devices. Optionally, the wireless communication system 100 may include multiple network devices and the coverage range of each network device may include other numbers of user devices. This embodiment of the present application does not limit this.

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

[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: fifth generation (5G) system or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0046] The user equipment in the embodiment 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, 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 embodiment of the present application may be a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as a handheld device with a wireless connection function, a vehicle-mounted device, etc. The user equipment in the embodiment of the present application may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, 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 may act as a base station. For example, a user device can act as a dispatching entity, providing sidelink signals between user devices in vehicle-to-everything (V2X) or D2D networks. For example, a cell phone and a car can communicate with each other using sidelink data. A cell phone and a smart home device can also communicate with each other without relaying the communication signal through a base station.

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

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

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

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

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

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

[0053] It should be understood that the interpretation of the terminology in the embodiments of the present application can refer to the specification protocols TS36 series, TS37 series and TS38 series of the 3rd Generation Partnership Project (3GPP), but can also refer to the specification protocols of the Institute of Electrical and Electronics Engineers (IEEE).

[0054] With the development of communication technology, technical research and standardization of sideline communication are gradually being carried out. The sideline 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 2 (SA2) Working Group specifically studies and standardizes 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 sideline communication, the Radio Access Network Working Group 1 (RAN1) and RAN2 developed power saving technologies (such as partial sensing, discontinuous reception (DRX) and inter-UE coordination (IUC) technology).

[0055] The application areas of side-by-side communication are also gradually expanding. For example, although NR SL was originally developed to support V2X applications, the industry is increasingly keen to expand NR SL to more commercial use cases. For example, highly automated driving technology requires sharing a large amount of sensor information between vehicles.

[0056] The continuous expansion of sidelink communication applications is placing higher demands on NR SL. These requirements include two key requirements: increasing sidelink data rates and supporting more new carriers on the sidelink. Adding more new carriers expands the transmission bandwidth, further increasing the data rate.

[0057] According to 3GPP project RP-222806, the research on supporting new carriers in the NR SL evolution of Rel-18 focuses on sidelink beam management (SL BM). Sidelink beam management typically includes initial beam-pairing, beam maintenance, and beam failure recovery (BFR).

[0058] The relationship between PC5 / sidelink unicast link establishment and sidelink initial beam pairing includes the following three candidate procedures:

[0059] Alternative process 1: Perform initial beam pairing before establishing the sidelink unicast link between UE1 and UE2;

[0060] Alternative process 2: Perform initial beam pairing during the sidelink unicast link establishment process between UE1 and UE2;

[0061] Alternative process three: Initial beam pairing starts after the sidelink unicast link between UE1 and UE2 is established.

[0062] Among them, alternative process one can expand the transmission range of sidelink communications and improve resource utilization. Specifically, the advantage of performing initial beam pairing before the sidelink unicast link is established is that the paired beams can be fully utilized to expand the transmission range, so that sidelink unicast links can be established between more UEs, thereby providing more advanced business use case services. These UEs are, for example, high-performance audio-visual equipment in stadiums, large event venues, and concerts. Furthermore, the advantage of performing initial beam pairing before the sidelink unicast link is established is that the direct communication request (DCR) message used to establish the unicast link only needs to be sent on the paired beam through the physical sidelink shared channel (PSSCH), thereby avoiding the use of beam sweeping to send DCR multiple times on the resources occupied by multiple transmit beams, thereby significantly improving resource utilization efficiency.

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

[0064] UE1 sends multiple S-SSBs using beam sweeping.

[0065] UE2 performs reference signal received power (RSRP) measurement on the sidelink synchronization signal (SLSS) and / or PSBCH, and UE2 determines the transmit beam of UE1 and the receive beam of UE2 based on the measured RSRP;

[0066] For the determined transmitting beam of UE1, UE2 reports the associated beam.

[0067] Traditional S-SSB design

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

[0069] For ease of understanding, the structure of a time slot of S-SSB is exemplarily illustrated below in conjunction with Figure 2. Referring to Figure 2, in a time slot of S-SSB, there are S-PSS and S-SSS, PSBCH, and the last guard symbol, which occupy two symbols respectively. In the structure shown in Figure 2, in an S-SSB time slot of 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 S-PSS, the fourth and fifth symbols are used to carry S-SSS, the last symbol is used as a guard symbol, and the other symbols are used to carry PSBCH.

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

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

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

[0073] Table 1

[0074] The distribution of multiple S-SSBs within a fixed period 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.

[0075] For ease of understanding, the following example illustrates the distribution of multiple S-SSBs within a fixed period, with reference to Figure 3. In the example of Figure 3, the fixed period, also known as the S-SSB period, is 16 radio frames. When 16 radio frames are grouped together, each period starts with the first time slot of the current group of radio frames and ends with the first time slot of the next group of radio frames.

[0076] In Figure 3, there are four S-SSBs within a fixed period. The time interval between the time slot of the first S-SSB and the start of the fixed period is called the time offset. The time interval between two consecutive S-SSBs is called the time interval.

[0077] Traditional NR SL synchronization priority design

[0078] 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 rule. That is, when the UE searches for two or more synchronization sources, the UE can select the synchronization source with the highest priority as the synchronization reference; when the UE searches for two or more synchronization sources with the same priority, the SyncRefUE with the highest PSBCH-RSRP result is selected as its synchronization reference. The NR SL synchronization priority rules include GNSS-based synchronization priority rules and gNB / eNB-based synchronization priority rules, as shown in Table 2.

[0079] Table 2

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

[0081] Since the traditional (e.g., Re1-16 / 17) S-SSB is not designed for initial beam pairing, the traditional S-SSB only carries the SLSSID, so the receiving UE (i.e., UE2) cannot identify the sending user of the S-SSB (i.e., UE1) through the received S-SSB; and the traditional S-SSB is used for broadcast rather than unicast, so the target receiving UE (i.e., UE2) cannot be identified through the traditional S-SSB, let alone the beam information.

[0082] As mentioned above, the process of performing initial beam pairing before establishing a side unicast link will be introduced in the new NR SL system (such as Rel-18 / 19), and S-SSB has become an alternative solution as a reference signal for initial beam pairing. In some scenarios, in order to facilitate UE2 to identify UE1 that sends the S-SSB from multiple UEs, UE1 needs to indicate at least one of its own user identification (UE ID) information (or source identification), transmission beam information, and receiving user identification (or destination identification) by sending an enhanced S-SSB (enhanced S-SSB, eS-SSB). When the UE that sends the eS-SSB can be used as a synchronization reference source, the receiving user can select a synchronization reference from multiple synchronization reference sources through the traditional NR SL synchronization priority rules.

[0083] However, as shown in Table 2, the traditional NR SL synchronization priority group sorting does not take into account the eS-SSB used for initial beam pairing. According to the traditional synchronization priority group sorting, the UE sending the eS-SSB (i.e., UE1) may belong to a lower priority group. If the UE sending the eS-SSB belongs to a lower priority group, the UE (i.e., UE1) may not be able to perform initial access pairing and thus cannot establish a side unicast link. If the base station or UE configures the side unicast link establishment or initial beam pairing based on specific requirements, the traditional synchronization priority group sorting method may not meet the specific requirements for establishing the side unicast link.

[0084] In summary, how to effectively perform initial beam pairing using S-SSB before establishing a sidelink unicast link is a technical issue that needs to be addressed. Furthermore, the introduction of the new feature of initial beam pairing in the NR SL system will lead to the need to redesign the synchronization priority rules. Furthermore, establishing a synchronization reference for the sidelink unicast link is also a technical issue that needs to be addressed. Furthermore, the priority of the UE performing initial beam pairing as the synchronization reference is also a technical issue that needs to be addressed.

[0085] Based on this, 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 side synchronization signal blocks including a first side synchronization signal block, it can first select the target priority group order corresponding to the sending node in the two priority group orders according to the first side synchronization signal block, and then determine whether the sending node is selected as a synchronization reference. Among them, the basis for selecting the target priority group order includes whether the first side synchronization signal block is related to the first operation such as initial beam pairing, side unicast link establishment, beam management, or the first type of identification, the first type of resource. That is, the present application introduces a new synchronization priority group order to determine the synchronization priority group order to which the sending UE of the S-SSB / eS-SSB belongs according to the purpose of the side synchronization signal block.

[0086] 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 and sidelink beam pairing.

[0087] It should be noted that the beam 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 consistent, and the embodiments of the present application do not distinguish between them.

[0088] The following describes a detailed description of the method embodiment of the present application in conjunction with the accompanying drawings. Figure 4 is a schematic flow chart of a method for wireless communication in a first node provided in an embodiment of the present application. The method shown in Figure 4 includes steps S410 and S420. It should be understood that the method shown in Figure 4 can be performed by the first node.

[0089] In some implementations, the first node can be any of the user devices described above for sidewalk communication. For example, the first node can be a vehicle in V2X or a V2X infrastructure. In some implementations, the first node can be located within or outside the network coverage area. When within the network coverage area, the first node can perform sidewalk communication based on the configuration of the network device.

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

[0091] As an embodiment, the first node may be a user equipment, for example, the user equipments 121 to 129 shown in FIG1 .

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

[0093] 4 , in step S410 , one or more sideline synchronization signal blocks are received.

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

[0095] In some embodiments, the one or more sending nodes may be user equipment interacting with the first node, or may be network equipment, which is not limited here.

[0096] As an embodiment, one or more side synchronization signal blocks include the S-SSB in the traditional NR Rel-16 and Rel-17, and also include a new S-SSB different from the traditional S-SSB.

[0097] As an embodiment, one or more sideline synchronization signal blocks include an enhanced sideline synchronization signal block, i.e., eS-SSB.

[0098] As an embodiment, one or more side synchronization signal blocks include an S-SSB in a modified format.

[0099] The one or more sideline synchronization signal blocks include a first sideline synchronization signal block. Alternatively, the first sideline synchronization signal block may be any sideline synchronization signal block among the one or more sideline synchronization signal blocks received by the first node. Alternatively, the receiving node of the first sideline synchronization signal block includes the first node. For simplicity, the term "S-SSB" will be used hereinafter to represent a sideline synchronization signal block. Therefore, the first sideline synchronization signal block may be referred to as a first S-SSB.

[0100] As an embodiment, the first S-SSB is any S-SSB among the one or more S-SSBs.

[0101] As an embodiment, the first S-SSB is any side row synchronization signal block among the multiple S-SSBs.

[0102] The sending node of the first S-SSB is the second node. The second node is any node that can interact with the first node, or any node that wants to communicate with the first node.

[0103] As an embodiment, the second node is a user equipment that wishes to perform operations such as initial beam pairing, sidelink unicast link establishment, or beam pairing with the first node.

[0104] The second node may send the first S-SSB by broadcasting, by multicasting, or by unicasting.

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

[0106] The first S-SSB may be any of the aforementioned S-SSBs. For example, the first S-SSB may be a traditional S-SSB or a new S-SSB. For example, the first S-SSB may be an eS-SSB or a non-eS-SSB. For example, the first S-SSB may or may not use an improved format.

[0107] Exemplarily, the eS-SSB (or the new S-SSB) is configured for a first operation, and / or the eS-SSB carries a first type of identifier, and / or the first type of resources is used for the eS-SSB. The first operation includes at least one of initial beam pairing, sidewalk unicast link establishment, and sidewalk beam management, which will be exemplarily described below with reference to Figures 5 to 7.

[0108] In some embodiments, the first operation includes initial beam pairing, where the initial beam pairing is sideways initial beam pairing. When the first S-SSB is configured for sideways initial beam pairing, the first node may match a transmit beam and a receive beam with a transmitting node of the first S-SSB to determine an optimal beam pair.

[0109] As an embodiment, the process of side-by-side initial beam pairing can refer to the pairing process of other communication systems (for example, NR), and the relevant process can also be improved according to the characteristics of the side-by-side communication system.

[0110] As an embodiment, the process of the side-by-side initial beam pairing includes two processes: coarse beam pairing and fine beam pairing.

[0111] For ease of understanding, the initial beam pairing process including coarse pairing and fine pairing is exemplarily described below with reference to Figure 5. As shown in Figure 5, the sideline receive beam of UE1 is initially paired with the sideline transmit beam of UE2.

[0112] 5 , in step S510 , a rough pairing is completed between UE2 transmitting beam A and UE1 receiving beam 2 .

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

[0114] Subsequently, UE1 selects a narrow beam as a receiving beam for UE2's transmitting beam A based on the measurement result.

[0115] As an embodiment, the initial beam pairing process includes coarse beam pairing.

[0116] For ease of understanding, the following illustrative example illustrates the initial beam pairing process, including coarse pairing, with reference to Figure 6. As shown in Figure 6, UE1's sideways transmit beam is initially paired with UE2's sideways receive beam. Referring to Figure 6, UE1 transmits four beams using beam scanning. UE2 measures each of UE1's four transmit beams using two receive beams. Based on the measurement results, UE2 determines the matching UE1 transmit beam and UE2 receive beam and notifies UE1 of the matching pair.

[0117] In some embodiments, the first operation includes establishing a sidelink unicast link. When the first S-SSB sent by the second node is configured for establishing a sidelink unicast link, the first node establishes the sidelink unicast link with the second node through the first S-SSB.

[0118] For ease of understanding, the following describes an implementation process of establishing a sidelink unicast link by taking UE1 and UE2 in FIG. 7 as an example.

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

[0120] 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 the sidelink unicast link.

[0121] As an embodiment, the sidewalk unicast link establishment process may include initial beam pairing. For example, when the initial beam pairing is performed before the unicast link is established, the sidewalk unicast link establishment process may be considered to include performing the initial beam pairing.

[0122] In some embodiments, the first operation includes side beam management. When the first S-SSB sent by the second node is configured for side beam management, the first node performs beam management with the second node by receiving the first S-SSB.

[0123] Exemplarily, the first node can perform side beam management with the sending node of the first S-SSB by receiving the first S-SSB. As mentioned above, side beam management includes processes such as initial beam pairing, beam maintenance, and beam failure recovery. Multiple processes in side beam management can enable the first node to perform stable side 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), and the relevant processes can also be improved according to the characteristics of the side communication system.

[0124] In some embodiments, the first S-SSB sent by the second node may also be used for a traditional synchronization reference (eg, sideline synchronization), or may also be used for traditional sideline communication or sideline discovery.

[0125] In some embodiments, the first S-SSB can be configured for multiple operations. For example, the first S-SSB can be used for both the first operation and the traditional operation. For example, when the first S-SSB is used for the first operation, it can also be used for sideline synchronization. For another example, when the first S-SSB is used for the first operation, it can also be used for sideline communication or sideline discovery.

[0126] The above describes three possible operations when the S-SSB is configured for the first operation. It should be understood that these three operations are described as examples, and the first operation may also include other operations performed through the first S-SSB.

[0127] For the first operation, the S-SSB carrying the first type of identifier or occupying the first type of resources can also be used to indicate that the S-SSB is used for the first operation. That is, the S-SSB is configured for the first operation, the S-SSB carries the first type of identifier, and the S-SSB occupies the first type of resources are interchangeable. For example, 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 resources. The three expressions can be interchangeable.

[0128] Taking the first S-SSB as an example, the resources occupied by the first S-SSB or the identifier carried indicates the purpose of the first S-SSB.

[0129] As an embodiment, whether the first S-SSB occupies the first type of resources corresponds to whether the first S-SSB is configured for the first operation.

[0130] As an embodiment, whether the first S-SSB occupies the first type of resources is used to determine whether the first S-SSB is configured for the first operation.

[0131] As an embodiment, whether the first S-SSB is configured for the first operation is used to determine whether the first S-SSB occupies the first type of resources.

[0132] As an embodiment, the first S-SSB is configured for the first operation corresponding to the first S-SSB occupying the first type of resources.

[0133] As an embodiment, the first S-SSB is not configured for the first operation and the first S-SSB does not occupy the first type of resources.

[0134] As an embodiment, whether the first S-SSB carries the first type of identifier corresponds to whether the first S-SSB is configured for the first operation.

[0135] As an embodiment, whether the first S-SSB carries a first type of identifier is used to determine whether the first S-SSB is configured for a first operation.

[0136] As an embodiment, whether the first S-SSB is configured for the first operation is used to determine whether the first S-SSB carries the first type of identifier.

[0137] As an embodiment, the first S-SSB is configured for a first operation corresponding to the first S-SSB carrying the first type of identifier.

[0138] As an embodiment, the first S-SSB is not configured for the first operation and the first S-SSB does not carry the first type of identifier.

[0139] As an embodiment, the first type of identifier is used to determine whether S-SSB is used for the first operation.

[0140] As an embodiment, when the S-SSB is used for the first operation, the S-SSB carries the first type of identifier; when the S-SSB is not used for the first operation, the S-SSB does not carry the first type of identifier.

[0141] As an embodiment, the first type of resources is configured for the first operation.

[0142] As an embodiment, when S-SSB is used for the first operation, the S-SSB occupies the first type of resources; when S-SSB is not used for the first operation, the S-SSB does not occupy the first type of resources.

[0143] In some embodiments, the first type of identifier is related to the sending 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 transmitting the S-SSB.

[0144] As an embodiment, the first type of identifier includes at least one of a source identifier, a destination identifier, and a beam identifier. Accordingly, the source identifier is the identifier of the S-SSB sending node; the destination identifier is the identifier of the S-SSB receiving node; and the beam identifier is the identifier of the beam used to transmit the S-SSB.

[0145] As an embodiment, the first type of identifier is related to the sending node of the S-SSB, and the first type of identifier is used to identify the sending node of the S-SSB.

[0146] As an embodiment, the first type of identifier is a source ID.

[0147] As an embodiment, the first type of identifier is an L1 source identifier.

[0148] As an embodiment, the first type of identifier carried by the first S-SSB is used to identify the sending node of the first S-SSB. For example, the first type of identifier carried by the first S-SSB can identify the second node. For another example, the first type of identifier is a source identifier, and the first S-SSB carries the source identifier to indicate that the sending node is the second node corresponding to the source identifier.

[0149] As an embodiment, the first type of identifier is related to the receiving node of the S-SSB, and the first type of identifier is used to identify the target receiving node of the S-SSB.

[0150] As an embodiment, the first type of identifier is a destination ID.

[0151] As an embodiment, the first type of identifier is an L1 destination identifier.

[0152] In one embodiment, the first type of identifier carried by the first sidelink synchronization signal block is used to identify a target receiving node of the first sidelink synchronization signal block. For example, the first type of identifier carried by the first S-SSB may identify a first node. In another example, the first type of identifier is a destination identifier, and the first S-SSB carries the destination identifier to indicate that the receiving node includes the first node corresponding to the destination identifier.

[0153] As an embodiment, the first type of identifier is related to the beam transmitting the sideline synchronization signal block, and the first type of identifier is used to identify the beam transmitting the sideline synchronization signal block.

[0154] As an embodiment, the first type of identifier is a beam identifier.

[0155] As an embodiment, the first type of identifier is a beam index.

[0156] As an embodiment, the first type of identification includes beam information.

[0157] As an embodiment, the first type of identification is related to beam information.

[0158] In some embodiments, the first type of resources is related to the first operation. Exemplarily, the first type of resources is configured to perform the first operation.

[0159] As an embodiment, the first type of resources are time-frequency resources used for the first operation.

[0160] As an embodiment, the first type of resource is used to transmit a first type of S-SSB, and the first type of S-SSB carries the first type of identifier. That is, when the S-SSB carries the first type of identifier, the S-SSB is transmitted through the first type of resource.

[0161] As an embodiment, the first type of resources includes time domain resources and / or frequency domain resources.

[0162] As an embodiment, the first type of resources includes at least one time-frequency resource.

[0163] As an embodiment, the first type of resources includes at least one time domain resource.

[0164] As an embodiment, the time domain resources include one or more sideline time slots, or one or more sideline multi-carrier symbols, which are not limited here.

[0165] As an embodiment, the first type of resources includes at least one time slot.

[0166] As an embodiment, the first type of resources includes at least one sideline time slot.

[0167] As an embodiment, the first type of resources includes at least one frequency domain resource.

[0168] As an embodiment, the frequency domain resources include one or more subcarriers, or one or more RBs, or one or more PRBs, or one or more subchannels, which are not limited here.

[0169] As an embodiment, the first type of resources includes a positive integer number of resource elements (RE).

[0170] As an embodiment, the first type of resources is used to send an S-SSB configured for the first operation, or an S-SSB carrying the first type of identifier.

[0171] As an embodiment, resources used to transmit S-SSB but different from the first type of resources are called second type of resources.

[0172] As an embodiment, the second type of resources includes at least one time-frequency resource.

[0173] As an embodiment, the second type of resources includes at least one time domain resource.

[0174] As an embodiment, the second type of resources includes at least one time slot.

[0175] As an embodiment, the second type of resources includes at least one sideline time slot.

[0176] As an embodiment, the second type of resources includes at least one frequency domain resource.

[0177] As an embodiment, the second type of resources includes a positive integer number of REs.

[0178] As an embodiment, the second type of resources is used to send S-SSB for sideline synchronization, or used to send S-SSB for sideline communication or sideline discovery.

[0179] Exemplarily, the time domain locations of the first type of resources and the second type of resources are different.

[0180] As an embodiment, at least one time domain resource included in the first category of resources is different from any time domain resource included in the second category of resources.

[0181] As an embodiment, the second type of resource is the time slot indicated by sl-SSB-TimeAllocation3, and the first type of resource is the time slot indicated by sl-SSB-TimeAllocationX, where X is a positive integer greater than 3.

[0182] Exemplarily, the frequency domain positions of the first type of resources and the second type of resources are different.

[0183] As an embodiment, at least one frequency domain resource included in the first category of resources is different from any frequency domain resource included in the second category of resources.

[0184] As an embodiment, at least one RE included in the first category of resources is different from any RE included in the second category of resources.

[0185] As an embodiment, the second type of resources are frequency domain resources indicated by sl-SSB-FrequencyAllocationY1, and the first type of resources are frequency domain resources indicated by sl-SSB-FrequencyAllocationY2. Y1 and Y2 are positive integers with different values.

[0186] As an embodiment, the second type of resources are resource blocks (RBs) indicated by sl-SSB-FrequencyAllocationY1, and the first type of resources are RBs indicated by sl-SSB-FrequencyAllocationY2.

[0187] Exemplarily, the first type of resources and the second type of resources have the same time domain position but different frequency domain positions.

[0188] As an embodiment, the second type of resource is a time slot indicated by sl-SSB-TimeAllocation3, and the first type of resource is a frequency domain resource indicated by sl-SSB-FrequencyAllocationY, and the frequency domain resource indicated by sl-SSB-FrequencyAllocationY does not overlap with the time slot indicated by sl-SSB-TimeAllocation3 in the frequency domain, but overlaps in the time domain. Wherein Y is a positive integer.

[0189] As an embodiment, the first type of resources are different from the resources occupied by the S-SSB used for side synchronization.

[0190] As an embodiment, the first type of resources are different from the resources occupied by S-SSB used for sideline communication or sideline discovery.

[0191] As an embodiment, the first type of resources and the second type of resources are orthogonal in the time domain or the frequency domain.

[0192] In some embodiments, the second node sending the first S-SSB may determine the purpose or type of the sent first S-SSB based on the received indication information. The indication information may be referred to as first information. Exemplarily, the first information may be used to indicate whether the first S-SSB is configured for a first operation, and / or whether the first S-SSB carries a first type of identifier, and / or whether the first S-SSB occupies a first type of resource.

[0193] Exemplarily, the second node may receive first information sent by a higher layer to determine the purpose of the first S-SSB.

[0194] As an embodiment, when the first information indicates that the first S-SSB is used for the first operation, the second node can configure the first S-SSB for the first operation, or the first S-SSB carries the first type of identifier, or sends the first S-SSB on the first type of resource, so as to facilitate the first node to determine.

[0195] As an embodiment, when the first information indicates that the first S-SSB is not used for the first operation, the second node may not configure the first S-SSB for the first operation, or carry the first type of identifier on the first S-SSB, or send the first S-SSB on the first type of resources, so as to facilitate the first node to determine.

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

[0197] 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 S-SSB among the multiple S-SSBs except the first S-SSB. The second S-SSB is different from the first S-SSB. For example, the first S-SSB is configured for the first operation, and the second S-SSB is not configured for the first operation. For another example, the first S-SSB carries a first-class identifier, and the second S-SSB does not carry the first-class identifier. For another example, the first S-SSB occupies first-class resources, and the second S-SSB does not occupy first-class resources.

[0198] 4 , in step S420 , it is determined whether the sending node of the first S-SSB is selected as the synchronization reference according to the target priority group order. In other words, the first node selects the synchronization reference according to the target priority group order.

[0199] The first node selects a synchronization reference, which means the first node selects a reference source for sidetrack synchronization from among multiple synchronization reference sources. For example, multiple S-SSBs received by the first node correspond to multiple available synchronization reference sources, and the first node may determine the synchronization reference source according to a certain synchronization priority rule.

[0200] As described above, the one or more S-SSBs received by the first node may include an S-SSB with specific requirements or specific configurations. When the first node receives the S-SSB, it can identify the requirements or purpose of the S-SSB so as to increase (or adjust) the synchronization priority of the sending node with specific requirements. For example, the first node can identify whether the first S-SSB is used to establish a side unicast link to meet the special requirements of the UE to establish a side unicast link.

[0201] In order to facilitate the improvement (or adjustment) of the priority of the sending node with specific needs, the embodiment of the present application uses different priority group orders (also called priority group sorting) to respectively determine the priority corresponding to the sending node of different types of S-SSB. When there are multiple priority group orders, the first node can determine the priority group order corresponding to the first S-SSB sending node based on the relevant information of the received first S-SSB, that is, the target priority group order. That is to say, after receiving the first S-SSB, the first node can determine the target priority group order corresponding to the sending node of the first S-SSB, and then determine whether the sending node of the first S-SSB is selected as the priority reference based on the target priority group order.

[0202] In some embodiments, two priority group orders are used to correspond to sending nodes with specific requirements and sending nodes without specific requirements. For example, the first node can determine the synchronization priority group order to which the sending node of the S-SSB / eS-SSB belongs based on the purpose of the S-SSB or eS-SSB. For example, whether the UE needs to establish a side unicast link and / or whether the UE sends an S-SSB or eS-SSB is used to determine the synchronization priority group order adopted by the UE.

[0203] As an embodiment, the first node may identify the needs of the sending node to determine the priority ranking. For example, whether the UE needs to establish a sidelink unicast link is used to determine the synchronization priority ranking adopted by the UE as a SyncRefUE.

[0204] As an embodiment, the first node may identify whether one or more S-SSBs belong to eS-SSBs and determine the synchronization priority group order to be adopted. For example, the UE sending an S-SSB or an eS-SSB is used to determine the synchronization priority order adopted by the UE as a SyncRefUE.

[0205] In some embodiments, the first node may identify one or more S-SSBs by their configuration, carried identifiers, or occupied resources, and determine the order of the target priority groups. Taking the first S-SSB as an example, at least one of whether the first S-SSB is configured for the first operation, whether the first S-SSB carries a first-class identifier, and whether the first S-SSB occupies the first-class resources is used to determine the order of the target priority groups.

[0206] As an embodiment, whether the first S-SSB is an eS-SSB is used to determine the target priority group order.

[0207] Exemplarily, the second node may determine how to send the first S-SSB based on the first information, and the first node may determine the target priority group order corresponding to the second node based on the first S-SSB. As an embodiment, the first information is used to determine the target priority group order corresponding to the sending node of the first side synchronization signal block.

[0208] Exemplarily, the first node selects a target priority group order from multiple priority group orders based on the first S-SSB. For the sake of brevity, the following description will take two priority group orders as an example. When the two priority group orders are a first priority group order and a second priority group order, the target priority group order is one of the first priority group order and the second priority group order.

[0209] In one embodiment, the first sidelink synchronization signal block is used to determine the target priority group order from the first priority group order and the second priority group order. For example, when the first S-SSB is an eS-SSB, the target priority group order is the first priority group order; when the first S-SSB is a traditional S-SSB, the target priority group order is the second priority group order.

[0210] In some embodiments, when 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 at least one of the first type of resources, the target priority group order is the first priority group order; when the first S-SSB is not configured for the first operation, the first S-SSB does not carry the first type of identifier, and the first S-SSB does not occupy at least one of the first type of resources, the target priority group order is the second priority group order.

[0211] For ease of understanding, the following is an exemplary description with reference to the flowchart shown in Figure 8. The method shown in Figure 8 is executed by the first node. Figure 8 shows a method for the first node to determine the order of target priority groups after receiving the first S-SSB.

[0212] Referring to Figure 8, in step S810, after receiving a first S-SSB, the first node needs to identify the purpose or related information of the first S-SSB. The first node needs to determine whether the first S-SSB is configured for a first operation, carries a first-class identifier, or occupies a first-class resource. If the first S-SSB is at least one of the three, step S820 is executed; if not, step S830 is executed.

[0213] In step S820, it is determined that the target priority group order is the first priority group order.

[0214] In step S830, it is determined that the target priority group order is the second priority group order.

[0215] As can be seen from Figures 4 to 8, the embodiments of the present application use different priority group orders to determine the priority group corresponding to the sending node of the S-SSB for different uses of the S-SSB. That is, the one or more S-SSBs received by the first node include S-SSBs used for the first operation and S-SSBs not used for the first operation. For one or more S-SSBs used for the first operation, one priority group order is used to determine whether the sending node is used as a synchronization reference; for one or more S-SSBs not used for the first operation, another priority group order is used to determine whether the sending node is used as a synchronization reference.

[0216] In some embodiments, the first priority group order is the order of multiple first-class priority groups, and the second priority group order is the order of multiple second-class priority groups; the sending node of the first S-SSB corresponds to the target priority group, and the target priority group is one of the multiple first-class priority groups, or the target priority group is one of the multiple second-class priority groups.

[0217] As an embodiment, the multiple first-class priority groups are determined based on at least two of the SLSSID, InC, first-class identifier carried by the S-SSB, and time-frequency resources occupied by the S-SSB.

[0218] As an embodiment, the multiple first-class priority groups are determined based on at least one of the coverage indication carried by the S-SSB, the first-class identifier, and the time-frequency resources occupied by the S-SSB, and the SLSSID carried by the S-SSB.

[0219] As an embodiment, the multiple first-class priority groups are related to at least two of the four: SLSSID, InC, first-class identifier and time-frequency resources occupied by S-SSB carried by S-SSB; the multiple second-class priority groups are related to at least two of the three: side synchronization signal identifier, InC and time-frequency resources occupied by S-SSB carried by S-SSB.

[0220] Exemplarily, when the target priority group order is the first priority group order, multiple first-class priority groups include the target priority group corresponding to the sending node of the first S-SSB, and the target priority group can be determined based on at least one of the InC carried by the first S-SSB, the first-class identifier, and the time-frequency resources occupied by the first S-SSB.

[0221] As an embodiment, the target priority group is determined based on at least two of the SLSSID, InC, first type identifier carried by the first S-SSB and the time-frequency resources occupied by the first S-SSB.

[0222] As an embodiment, the target priority group is determined based on at least one of the InC carried by the first S-SSB, the first type identifier, the time-frequency resources occupied by the first S-SSB, and the SLSSID carried by the first S-SSB.

[0223] As an embodiment, the SLSSID, InC carried by the first S-SSB and the first type of identifier carried by the first S-SSB are used to determine the target priority group.

[0224] As an example, when the SLSSID carried by the first S-SSB is 0, InC is true, and the first type identifier identifies the first node, the target priority group is priority group 1.

[0225] As an example, when the SLSSID carried by the first S-SSB is 337, InC is false, and the first type identifier identifies the first node, the target priority group is priority group 2.

[0226] As an example, when the SLSSID∈{0,1,...,335} carried by the first S-SSB, InC=true, and the first type identifier identifies the first node, the target priority group is priority group 4.

[0227] As an example, when the SLSSID∈{0,1,...,335} carried by the first S-SSB, InC=false, and the first type identifier identifies the first node, the target priority group is priority group 5.

[0228] As an embodiment, the SLSSID carried by the first S-SSB and the first type of resources occupied by the first S-SSB are used to determine the target priority group. The first type of resources are, for example, the time slot indicated by sl-SSB-TimeAllocation4 or the frequency indicated by sl-SSB-FrequencyAllocation1.

[0229] As an example, when the SLSSID carried by the first S-SSB is 0 and the sidelink synchronization signal (SLSS) is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, or when the SLSSID is 0 and the SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1, the target priority group is priority group 1.

[0230] As an embodiment, the SLSSID and InC carried by the first S-SSB and the first type of resources occupied by the first S-SSB are used to determine the target priority group. The first type of resources are, for example, the time slot indicated by sl-SSB-TimeAllocation4 or the frequency indicated by sl-SSB-FrequencyAllocation1.

[0231] As an example, when the SLSSID carried by the first S-SSB is 0, the SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC is false, or when SLSSID is 0, the SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1, and InC is false, or when SLSSID is 337, the SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC is false, or when SLSSID is 337, the SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC is false, the target priority group is priority group 2.

[0232] As an example, when the first S-SSB carries SLSSID∈{0,1,...,335}, InC=true, and SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, or when SLSSID∈{0,1,...,335}, InC=true, and SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, the target priority group is priority group 4.

[0233] As an example, when the first S-SSB carries SLSSID∈{0,1,...,335}, InC=false, and SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, or when SLSSID∈{0,1,...,335}, InC=false, and SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, the target priority group is priority group 5.

[0234] As an embodiment, the SLSSID and InC carried by the first S-SSB, the first type of identifier carried by the first S-SSB, and the first type of resources occupied by the first S-SSB are used to determine the target priority group.

[0235] As an example, when the first S-SSB carries SLSSID=0, InC=false, the first type identifier identifies the first node, and the SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3, the target priority group is priority group 2.

[0236] In order to improve communication efficiency, the first node may determine whether to increase the priority of the sending node of the S-SSB based on the information carried by the S-SSB or the resources occupied. For example, when the first node finds that the sending node of the S-SSB wants to communicate with it based on the information of the S-SSB, it may establish communication with the sending node in a timely manner.

[0237] In some embodiments, the first type of identifier is a destination identifier, and whether the first type of identifier carried by the first S-SSB is used to identify the first node is used to determine the position of the target priority group in the first priority group sequence. The first type of identifier carried by the first S-SSB is used to identify the first node, and can be replaced by the first type of identifier carried by the first S-SSB being the same as the identifier of the first node. For example, when the first type of identifier carried by the S-SSB is used to identify the first node, the target priority group of the sending node of the S-SSB is located first in the target priority group sequence. That is to say, the first node can raise the priority of the sending node to the highest level, establish a side unicast link or other first operations with the sending node of the S-SSB, thereby improving communication efficiency.

[0238] In some embodiments, the first type of identifier is a destination identifier, and the multiple S-SSBs received by the first node also include a second S-SSB. When the first type of identifier carried by the first S-SSB is used to identify the first node and the first type of identifier carried by the second S-SSB is not used to identify the first node, the sending node of the first S-SSB (the second node) is preferentially selected as a synchronization reference over the sending node of the second S-SSB.

[0239] In some embodiments, the multiple S-SSBs received by the first node also include a second S-SSB. When the first S-SSB occupies the first type of resources and the second S-SSB does not occupy the first type of resources, the sending node of the first S-SSB is preferentially selected as a synchronization reference rather than the sending node of the second S-SSB to improve communication efficiency.

[0240] As an embodiment, the sending node of the first S-SSB belongs to the target priority group.

[0241] Exemplarily, at least one of the multiple first-class priority groups includes a sending node of an S-SSB for a first operation, and any second-class priority group among the multiple second-class priority groups does not include a sending node of an S-SSB for the first operation; or, at least one of the multiple first-class priority groups includes a sending node of an S-SSB carrying a first-class identifier, and any second-class priority group among the multiple second-class priority groups does not include a sending node of an S-SSB carrying a first-class identifier; or, at least one of the multiple first-class priority groups includes a sending node of an S-SSB occupying first-class resources, and any second-class priority group among the multiple second-class priority groups does not include a sending node of an S-SSB occupying first-class resources.

[0242] As an embodiment, at least one of the multiple first-class priority groups is related to the first operation and / or the S-SSB carrying the first-class identifier and / or the S-SSB occupying the first-class resources; any second-class priority group among the multiple second-class priority groups is not related to the first operation, the S-SSB carrying the first-class identifier, and the S-SSB occupying the first-class resources.

[0243] As an embodiment, the sending node of the S-SSB configured for the first operation belongs to one of multiple first-class priority groups.

[0244] As an embodiment, the sending node of the S-SSB carrying the first type identifier belongs to one of the multiple first type priority groups.

[0245] As an embodiment, the sending node of the S-SSB occupying the first type of resources belongs to one of the multiple first type priority groups.

[0246] As an embodiment, the sending node of S-SSB for sideline synchronization belongs to one of the multiple second priority groups.

[0247] As an embodiment, the sending node of the S-SSB for sideline communication or sideline discovery belongs to one of the multiple second priority groups.

[0248] As an embodiment, the multiple second-class priority groups include GNSS or gNB / eNB; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; and the remaining UE(s) excluding the above UEs.

[0249] As an embodiment, the multiple second-class priority groups are: GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; and the remaining UE(s) excluding the above UEs.

[0250] In some embodiments, multiple second-class priority groups can be indicated based on at least two of the SLSSID, InC and resources occupied by SLSS of UE(s); multiple first-class priority groups can be indicated based on at least two of the SLSSID, InC, first-class identification and resources occupied by SLSS of UE(s).

[0251] As an embodiment, the plurality of second priority groups include:

[0252] 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;

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

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

[0255] gNB / eNB, or GNSS;

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

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

[0258] The remaining UE(s) after removing the above UEs.

[0259] As an embodiment, the plurality of second priority groups are:

[0260] 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;

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

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

[0263] gNB / eNB, or GNSS;

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

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

[0266] The remaining UE(s) after removing the above UEs.

[0267] As an embodiment, the multiple first-class priority groups include GNSS or gNB / eNB; 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.

[0268] As an embodiment, the multiple first-class priority groups are: GNSS; 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.

[0269] It should be noted that the S-SSBs sent by UE(s) in multiple first-class priority groups carry first-class identifiers or occupy first-class resources. Conversely, the S-SSBs sent by UE(s) in multiple second-class priority groups do not carry first-class identifiers and do not occupy first-class resources.

[0270] As an embodiment, the plurality of first priority groups include:

[0271] UE(s) with SLSSID=0, InC=true, Destination ID=xx, or with SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, or with SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1;

[0272] UE(s) with SLSSID = 0, Destination ID = xx, SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3, and InC = false; or, SLSSID = 0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC = false; or, SLSSID = 0, SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1, and InC = false;

[0273] UE(s) with SLSSID=337, Destination ID=xx, InC=false, or SLSSID=337, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or SLSSID=337, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0274] gNB / eNB, or GNSS;

[0275] UE(s) with SLSSID∈{0,1,...,335}, Destination ID=xx, InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=true;

[0276] UE(s) with SLSSID∈{0,1,...,335}, Destination ID=xx, InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0277] The remaining UE(s) after removing the above UEs.

[0278] As an embodiment, the plurality of first priority groups are:

[0279] UE(s) with SLSSID=0, InC=true, Destination ID=xx, or with SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, or with SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1;

[0280] UE(s) with SLSSID = 0, Destination ID = xx, SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3, and InC = false; or, SLSSID = 0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC = false; or, SLSSID = 0, SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1, and InC = false;

[0281] UE(s) with SLSSID=337, Destination ID=xx, InC=false, or SLSSID=337, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or SLSSID=337, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0282] gNB / eNB, or GNSS;

[0283] UE(s) with SLSSID∈{0,1,...,335}, Destination ID=xx, InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=true;

[0284] UE(s) with SLSSID∈{0,1,...,335}, Destination ID=xx, InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0285] The remaining UE(s) after removing the above UEs.

[0286] As an embodiment, the plurality of first priority groups are:

[0287] UE(s) with SLSSID∈{0,1,...,335}, InC=true, and Destination ID=xx, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=true;

[0288] UE(s) with SLSSID∈{0,1,...,335}, InC=false, and Destination ID=xx, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0289] gNB / eNB, or GNSS;

[0290] UE(s) with SLSSID=0, Destination ID=xx, InC=true, or, SLSSID=0, Destination ID=xx, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3, or, SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=true, or, SLSSID=0, SLSS is transmitted on the time slot indicated by the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=true, or, SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1;

[0291] UE(s) with SLSSID = 0, Destination ID = xx, SLSS is not transmitted on the timeslot indicated by sl-SSB-TimeAllocation3, and InC = false; or, with SLSSID = 0, SLSS is not transmitted on the timeslot indicated by sl-SSB-TimeAllocation3, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC = false;

[0292] UE(s) with SLSSID=337, Destination ID=xx, InC=false, or SLSSID=337, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or SLSSID=337, SLSS is transmitted on the time slot indicated by the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0293] The remaining UE(s) after removing the above UEs.

[0294] In the above-mentioned first priority group, xx represents the destination identifier of S-SSB, and the frequency indicated by sl-SSB-FrequencyAllocation1 is different from the frequency domain resources occupied by S-SSB in the second priority group.

[0295] The first priority group may be a first priority group based on a cell or GNSS, or a second priority group based on a GNSS or a cell. In some embodiments, the first priority group corresponds to a user device that selects a cell as a synchronization reference, or the first priority group corresponds to a user device that selects a first type of user device as a synchronization reference, and the first type of user device selects a cell as a synchronization reference; the second priority group corresponds to a user device that selects a GNSS as a synchronization reference, or the second priority group corresponds to a user device that selects a second type of user device as a synchronization reference, and the second type of user device selects GNSS as a synchronization reference.

[0296] 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 GNSS as a synchronization reference.

[0297] As an embodiment, the first priority group corresponds to user equipment that selects the 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.

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

[0299] 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 a second type of user equipment as a synchronization reference.

[0300] 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 first type of user equipment as a synchronization reference.

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

[0302] In some embodiments, the position of the first priority group in the plurality of first priority groups is before the position of the second priority group in the plurality of candidate priority groups, or the position of the first priority group in the plurality of first priority groups is after the position of the second priority group in the plurality of candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

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

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

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

[0306] As an embodiment, the first parameter is set to gnss, or gnb / Enb.

[0307] In some embodiments, the first priority group order and the multiple first-class priority groups therein are related to at least one of the first operation, the first-class identifier and the first-class resource mentioned above; on the contrary, the second priority group order and the multiple second-class priority groups therein are not related to at least one of the first operation, the first-class identifier and the first-class resource mentioned above.

[0308] As an embodiment, the order of the first priority group and the order of the second priority group are: 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 are arranged in sequence; however, the identifiers carried by the UE(s) or the resources occupied in the first priority group order and the second priority group order are different.

[0309] As an embodiment, the first priority group order and the second priority group order are both: 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; the remaining UE(s) excluding the above UEs are arranged in sequence; however, the identifiers carried by the UE(s) or the resources occupied in the first priority group order and the second priority group order are different.

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

[0311] UE(s) with SLSSID=0, InC=true, Destination ID=xx, or with SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, or with SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1;

[0312] UE(s) with SLSSID = 0, Destination ID = xx, SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3, and InC = false; or, SLSSID = 0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC = false; or, SLSSID = 0, SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1, and InC = false;

[0313] UE(s) with SLSSID=337, Destination ID=xx, InC=false, or SLSSID=337, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or SLSSID=337, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0314] gNB / eNB;

[0315] UE(s) with SLSSID∈{0,1,...,335}, Destination ID=xx, InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=true;

[0316] UE(s) with SLSSID∈{0,1,...,335}, Destination ID=xx, InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0317] The remaining UE(s) after excluding the above UEs are arranged in seven priority groups.

[0318] As an embodiment, the second priority group order is:

[0319] 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;

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

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

[0322] gNB / eNB;

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

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

[0325] The remaining UE(s) after excluding the above UEs are arranged in seven priority groups.

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

[0327] UE(s) with SLSSID∈{0,1,...,335}, InC=true, and Destination ID=xx, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=true, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=true;

[0328] UE(s) with SLSSID∈{0,1,...,335}, InC=false, and Destination ID=xx, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or with SLSSID∈{0,1,...,335}, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0329] GNSS;

[0330] UE(s) with SLSSID=0, Destination ID=xx, InC=true, or, SLSSID=0, Destination ID=xx, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3, or, SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=true, or, SLSSID=0, SLSS is transmitted on the time slot indicated by the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=true, or, SLSSID=0, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and the frequency indicated by sl-SSB-FrequencyAllocation1;

[0331] UE(s) with SLSSID = 0, Destination ID = xx, SLSS is not transmitted on the timeslot indicated by sl-SSB-TimeAllocation3, and InC = false; or, with SLSSID = 0, SLSS is not transmitted on the timeslot indicated by sl-SSB-TimeAllocation3, SLSS is transmitted on the frequency indicated by sl-SSB-FrequencyAllocation1, and InC = false;

[0332] UE(s) with SLSSID=337, Destination ID=xx, InC=false, or SLSSID=337, SLSS is transmitted on the time slot indicated by sl-SSB-TimeAllocation4, and InC=false, or SLSSID=337, SLSS is transmitted on the time slot indicated by the frequency indicated by sl-SSB-FrequencyAllocation1, and InC=false;

[0333] The remaining UE(s) after excluding the above UEs are arranged in seven priority groups.

[0334] As an embodiment, the second priority group order is:

[0335] 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;

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

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

[0338] gNB / eNB;

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

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

[0341] The remaining UE(s) after excluding the above UEs are arranged in seven priority groups.

[0342] As an embodiment, the order of the second priority groups is shown in Table 2, and the order of the first priority groups is shown in Table 3.

[0343] Table 3

[0344] The differences between the first priority group order and the second priority group order and their multiple priority groups are described above. The first priority group order and the second priority group order are respectively used to prioritize different sending nodes so that the first node can select a synchronization reference.

[0345] To meet the special needs of the sending nodes that need to perform the first operation, the synchronization priority of these sending nodes should be higher than the synchronization priority of the sending nodes that do not need to perform the first operation. As can be seen above, the first priority group order is related to the nodes that perform the first operation, and the second priority group order is the traditional priority group order.

[0346] In some embodiments, the priority of the first priority group at the first position in the first priority group sequence is higher than the priority of the second priority group at the first position in the second priority group sequence. In other words, for two sending nodes at the same position in the first priority group sequence and the second priority group sequence, the priority of the sending node in the first priority group sequence is higher than the priority of the sending node in the second priority group sequence, so as to meet the communication needs of the sending node that needs to perform the first operation.

[0347] As an embodiment, the priority of the first priority group located at the first position in the first priority group order is the priority of the first priority group selected as the synchronization reference.

[0348] As an embodiment, the priority of the second priority group located at the first position in the second priority group order is the priority of the second priority group selected as the synchronization reference.

[0349] As an embodiment, a sending node in a first priority group located at the first position in the first priority group sequence is preferentially selected as a synchronization reference over a sending node in a second priority group located at the first position in the second priority group sequence.

[0350] As an embodiment, the first position is a position in the first priority group order and also a position in the second priority group order.

[0351] As an embodiment, a plurality of first priority groups are respectively located at a plurality of positions in a first priority group sequence, and the first position is one of the plurality of positions.

[0352] As an embodiment, a plurality of second priority groups are respectively located at a plurality of positions in the second priority group sequence, and the first position is one of the plurality of positions.

[0353] As an embodiment, the first position is the Nth position among the multiple positions in the first priority group sequence, and is also the Nth position among the multiple positions in the second priority group sequence, where N is a positive integer.

[0354] As an embodiment, the priority of the first priority group located at the last position in the first priority group sequence is higher than the priority of the second priority group located at the first position in the second priority group sequence.

[0355] As an embodiment, the priority of the first priority group at the first position in the first priority group sequence is equal to the priority of the second priority group at the second position in the second priority group sequence, and the second position is the sum of the first position and the priority group offset.

[0356] As an embodiment, the priority group offset is determined based on the first S-SSB.

[0357] As an embodiment, at least one of whether the first S-SSB is configured for a first operation, whether the first S-SSB carries a first type of identifier, and whether the first S-SSB occupies a first type of resource is used to determine the priority group offset.

[0358] As an embodiment, the priority group offset is related to the first operation.

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

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

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

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

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

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

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

[0366] As an embodiment, when the first S-SSB is configured for the first operation, the priority group offset is greater than 0; when the first S-SSB is not configured for the first operation, the priority group offset is equal to 0.

[0367] As an embodiment, when the first S-SSB carries the first category identifier, the priority group offset is greater than 0; when the first S-SSB does not carry the first category identifier, the priority group offset is equal to 0.

[0368] As an embodiment, when the first S-SSB occupies the first type of resources, the priority group offset is greater than 0; when the first S-SSB does not occupy the first type of resources, the priority group offset is equal to 0.

[0369] As an embodiment, the first candidate priority group is one of the multiple first-class priority groups, the second candidate priority group is one of the multiple second-class priority groups, the position of the first candidate priority group in the first priority group order is the same as the position of the second candidate priority group in the second priority group order; the first candidate priority group is selected as a synchronization reference in preference to the second candidate priority group, or the node belonging to the first candidate priority group is selected as a synchronization reference in preference to the node belonging to the second candidate priority group.

[0370] As an embodiment, the first candidate priority group is any first-class priority group among the multiple first-class priority groups, and the second candidate priority group is a second-class priority group among the multiple second-class priority groups that is ranked first according to the second priority group; the first candidate priority group is selected as a synchronization reference in preference to the second candidate priority group, or the node belonging to the first candidate priority group is selected as a synchronization reference in preference to the node belonging to the second candidate priority group.

[0371] To more efficiently select a synchronization reference, the first node may also determine whether one or more transmitting nodes are selected as synchronization references based on measurement results of one or more S-SSBs. For example, the first S-SSB may be measured, and the second node may be determined as the synchronization reference based on the measurement results of the first S-SSB.

[0372] In some embodiments, the node may perform a first signal measurement on the first S-SSB. The relationship between the result of the first signal measurement and the target threshold is used to determine whether the sending node of the first S-SSB is selected as the synchronization reference.

[0373] As an embodiment, the result of the first signal measurement is parameters such as reference signal received power (RSRP), reference signal received quality (RSRQ), and reference signal strength indication (RSSI), which are not limited here.

[0374] As an embodiment, the size relationship between the result of the first signal measurement and the target threshold and the target priority group order are used together to determine whether the sending node of the first S-SSB is selected as the synchronization reference.

[0375] As an embodiment, the result of the first signal measurement is greater than or equal to the target threshold, and the sending node of the first S-SSB determines whether to be selected as a synchronization reference according to the target priority group order.

[0376] As an embodiment, the result of the first signal measurement is greater than or equal to the target threshold, and the sending node of the first S-SSB is one of multiple synchronization references selectable by the first node.

[0377] In one embodiment, if the result of the first signal measurement is less than the target threshold, the transmitting node of the first S-SSB is not selected as a synchronization reference. In other words, based on the measurement result, a portion of nodes serving as synchronization reference sources can be excluded to improve communication efficiency.

[0378] As an embodiment, the result of the first signal measurement is less than the target threshold, and the sending node of the first S-SSB is not any of the multiple synchronization references selectable by the first node.

[0379] As an embodiment, the first signal measurement includes measuring the PSBCH in the first S-SSB.

[0380] In some embodiments, at least one of whether the first S-SSB is configured for a first operation, whether the first S-SSB carries a first type of identifier, and whether the first S-SSB occupies a first type of resource is used to determine the target threshold.

[0381] As an embodiment, the target threshold is one of a first threshold and a second threshold, wherein the first threshold is smaller than the second threshold, or the first threshold is larger than the second threshold.

[0382] As an embodiment, the target threshold is related to whether the first S-SSB is an eS-SSB.

[0383] As an embodiment, whether the first S-SSB is an eS-SSB is used to determine the target threshold.

[0384] As an embodiment, when the first S-SSB is an eS-SSB, the target threshold is the first threshold; when the first S-SSB is a traditional S-SSB, the target threshold is the second threshold.

[0385] As an embodiment, the first S-SSB is configured for the first operation, and / or the first S-SSB carries the first category identifier, and / or the first S-SSB occupies the first category resources, and the target threshold is the first threshold, otherwise, the target threshold is the second threshold.

[0386] As an embodiment, the first S-SSB is configured for the first operation, and the target threshold is the first threshold; the first S-SSB is not configured for the first operation, and the target threshold is the second threshold.

[0387] As an embodiment, the first S-SSB carries the first category identifier, and the target threshold is the first threshold; the first S-SSB does not carry the first category identifier, and the target threshold is the second threshold.

[0388] As an embodiment, the first S-SSB occupies the first type of resources, and the target threshold is the first threshold; the first S-SSB does not occupy the first type of resources, and the target threshold is the second threshold.

[0389] As an embodiment, the first S-SSB is not configured for the first operation, does not carry the first type of identifier, and does not occupy the first type of resources, and the target threshold is the second threshold.

[0390] The preceding article describes how the first node selects a synchronization reference after receiving multiple S-SSBs. The following describes the embodiments of the present application in more detail with reference to the specific examples of Figures 9 and 10. It should be noted that the examples of Figures 4 to 8 are intended only to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated.

[0391] Figure 9 is written from the perspective of the interaction between a first node and a second node. Referring to Figure 9, in step S910, the second node receives first information. The first information may instruct the second node how to send a first S-SSB.

[0392] In step S920, the second node sends a first S-SSB, and the first node receives the first S-SSB.

[0393] In step S930, the first node measures the first S-SSB, and the relationship between the measurement result and the target threshold is used to determine whether the second node is selected as the synchronization reference.

[0394] The method shown in Figure 10 is executed by the first node. The method shown in Figure 10 is a flowchart of a possible implementation method of the first node making a judgment based on the measurement result after executing step S930.

[0395] 10 , in step S1010 , it is determined whether the result of the first signal measurement is greater than the target threshold value. If yes, step S1020 is executed; if not, step S1030 is executed.

[0396] In step S1020, the sending node of the first S-SSB is selected as the synchronization reference. The sending node of the first S-SSB is the second node in FIG9 .

[0397] In step S1030, the sending node of the first S-SSB is not selected as a synchronization reference.

[0398] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 10 . The device embodiment of the present application is described in detail below in conjunction with Figures 11 to 14 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0399] FIG11 is a diagram of a first node for wireless communication provided by an embodiment of the present application. As shown in FIG11 , the first node 1100 includes a first receiver 1110 and a first processor 1120 .

[0400] The first receiver 1110 may be configured to receive one or more sideline synchronization signal blocks, where the one or more sideline synchronization signal blocks include a first sideline synchronization signal block.

[0401] The first processor 1120 can be used to determine whether the sending node of the first sideline synchronization signal block is selected as a synchronization reference according to a target priority group order, and the target priority group order is one of a first priority group order and a second priority group order; wherein, at least one of whether the first sideline synchronization signal block is configured for a first operation, whether the first sideline synchronization signal block carries a first type of identifier, and whether the first sideline synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation includes at least one of initial beam pairing, sideline unicast link establishment and sideline beam management.

[0402] As an embodiment, the order of the first priority groups is the order of multiple first-class priority groups, and the order of the second priority groups is the order of multiple second-class priority groups; the sending node of the first side synchronization signal block corresponds to the target priority group, and the target priority group is one of the multiple first-class priority groups, or the target priority group is one of the multiple second-class priority groups; at least one of the multiple first-class priority groups includes the sending node of the side synchronization signal block used for the first operation, and any second-class priority group among the multiple second-class priority groups does not include the sending node of the side synchronization signal block used for the first operation; or, at least one of the multiple first-class priority groups includes the sending node of the side synchronization signal block carrying the first-class identifier, and any second-class priority group among the multiple second-class priority groups does not include the sending node of the side synchronization signal block carrying the first-class identifier; or, at least one of the multiple first-class priority groups includes the sending node of the side synchronization signal block occupying the first-class resources, and any second-class priority group among the multiple second-class priority groups does not include the sending node of the side synchronization signal block occupying the first-class resources.

[0403] As an embodiment, when the first sideline synchronization signal block is configured for the first operation, the first sideline synchronization signal block carries the first type of identification, and the first sideline synchronization signal block occupies at least one of the first type of resources, the target priority group order is the first priority group order; when the first sideline synchronization signal block is not configured for the first operation, the first sideline synchronization signal block does not carry the first type of identification, and the first sideline synchronization signal block does not occupy at least one of the first type of resources, the target priority group order is the second priority group order.

[0404] As an embodiment, the first type of identifier is related to the sending node of the sideline synchronization signal block, or the first type of identifier is related to the receiving node of the sideline synchronization signal block, or the first type of identifier is related to the beam transmitting the sideline synchronization signal block.

[0405] As an embodiment, the first type of resources are configured for the first operation.

[0406] As an embodiment, the priority of the first priority group located at the first position in the first priority group sequence is higher than the priority of the second priority group located at the first position in the second priority group sequence.

[0407] As an embodiment, the first node 1100 also includes a second processor, which can be used to perform a first signal measurement on the first side synchronization signal block; wherein, the size relationship between the result of the first signal measurement and the target threshold is used to determine whether the sending node of the first side synchronization signal block is selected as the synchronization reference.

[0408] As an embodiment, at least one of whether the first sideline synchronization signal block is configured for the first operation, whether the first sideline synchronization signal block carries the first type of identifier, and whether the first sideline synchronization signal block occupies the first type of resources is used to determine the target threshold.

[0409] As an embodiment, the target priority group order is the first priority group order, the first priority group order is the order of multiple first-class priority groups, and at least one of the coverage indication carried by the first side synchronization signal block, the first-class identifier carried by the first side synchronization signal block, and the time-frequency resources occupied by the first side synchronization signal block is used to determine the target priority group corresponding to the sending node of the first side synchronization signal block, and multiple first-class priority groups include the target priority group.

[0410] As an embodiment, the first type of identifier is a destination identifier, and whether the first type of identifier carried by the first sidelink synchronization signal block is used to identify the first node is used to determine the position of the target priority group in the first priority group sequence.

[0411] As an embodiment, the first type of identifier is a destination identifier, the multiple side synchronization signal blocks also include a second side synchronization signal block, the first type of identifier carried by the first side synchronization signal block is used to identify the first node, and the first type of identifier carried by the second side synchronization signal block is not used to identify the first node; the sending node of the first side synchronization signal block is preferentially selected as a synchronization reference rather than the sending node of the second side synchronization signal block.

[0412] As an embodiment, the multiple side synchronization signal blocks also include a second side synchronization signal block, the first side synchronization signal block occupies the first type of resources, and the second side synchronization signal block does not occupy the first type of resources; the sending node of the first side synchronization signal block is preferentially selected as a synchronization reference than the sending node of the second side synchronization signal block.

[0413] 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, as specifically shown in FIG13 .

[0414] FIG12 is a diagram of a second node for wireless communication provided by an embodiment of the present application. As shown in FIG12 , the second node 1200 includes a first transmitter 1210 .

[0415] The first transmitter 1210 can be used to send a first sidelink synchronization signal block, wherein at least one of whether the first sidelink synchronization signal block is configured for a first operation, whether the first sidelink synchronization signal block carries a first type of identifier, and whether the first sidelink synchronization signal block occupies a first type of resource is used by a receiving node of the first sidelink synchronization signal block to determine a target priority group order; the first operation includes at least one of initial beam pairing, sidelink unicast link establishment and sidelink beam management; the target priority group order is used to determine whether the second node is selected by the receiving node as a synchronization reference; the target priority group order is one of a first priority group order and a second priority group order.

[0416] As an embodiment, the second node 1200 also includes a second receiver, which can be used to receive first information, where the first information is used to indicate whether the first side synchronization signal block is configured for the first operation, and / or whether the first side synchronization signal block carries a first type of identifier, and / or whether the first side synchronization signal block occupies a first type of resource.

[0417] As an embodiment, the order of the first priority groups is the order of multiple first-class priority groups, and the order of the second priority groups is the order of multiple second-class priority groups; the second node corresponds to the target priority group, and the target priority group is one of the multiple first-class priority groups, or the target priority group is one of the multiple second-class priority groups; at least one of the multiple first-class priority groups includes a sending node for a side synchronization signal block used for the first operation, and any second-class priority group in the multiple second-class priority groups does not include a sending node for a side synchronization signal block used for the first operation; or, at least one of the multiple first-class priority groups includes a sending node for a side synchronization signal block carrying a first-class identifier, and any second-class priority group in the multiple second-class priority groups does not include a sending node for a side synchronization signal block carrying a first-class identifier; or, at least one of the multiple first-class priority groups includes a sending node for a side synchronization signal block occupying a first-class resource, and any second-class priority group in the multiple second-class priority groups does not include a sending node for a side synchronization signal block occupying a first-class resource.

[0418] As an embodiment, when the first sideline synchronization signal block is configured for the first operation, the first sideline synchronization signal block carries the first type of identification, and the first sideline synchronization signal block occupies at least one of the first type of resources, the target priority group order is the first priority group order; when the first sideline synchronization signal block is not configured for the first operation, the first sideline synchronization signal block does not carry the first type of identification, and the first sideline synchronization signal block does not occupy at least one of the first type of resources, the target priority group order is the second priority group order.

[0419] As an embodiment, the first type of identifier is related to the sending node of the sideline synchronization signal block, or the first type of identifier is related to the receiving node of the sideline synchronization signal block, or the first type of identifier is related to the beam transmitting the sideline synchronization signal block.

[0420] As an embodiment, the first type of resources are configured for the first operation.

[0421] As an embodiment, the priority of the first priority group located at the first position in the first priority group sequence is higher than the priority of the second priority group located at the first position in the second priority group sequence.

[0422] As an embodiment, the target priority group order is the first priority group order, the first priority group order is the order of multiple first-class priority groups, and at least one of the in-coverage indication carried by the first side synchronization signal block, the first-class identifier carried by the first side synchronization signal block, and the time-frequency resources occupied by the first side synchronization signal block is used to determine the target priority group corresponding to the second node, and multiple first-class priority groups include the target priority group.

[0423] As an embodiment, the first type of identifier is a destination identifier, and whether the first type of identifier carried by the first sidelink synchronization signal block is used to identify the first node is used to determine the position of the target priority group in the first priority group sequence.

[0424] As an embodiment, the first type of identifier is a destination identifier, the multiple side synchronization signal blocks also include a second side synchronization signal block, the first type of identifier carried by the first side synchronization signal block is used to identify the first node, and the first type of identifier carried by the second side synchronization signal block is not used to identify the first node; the sending node of the first side synchronization signal block is preferentially selected as a synchronization reference rather than the sending node of the second side synchronization signal block.

[0425] As an embodiment, the multiple side synchronization signal blocks also include a second side synchronization signal block, the first side synchronization signal block occupies the first type of resources, and the second side synchronization signal block does not occupy the first type of resources; the sending node of the first side synchronization signal block is preferentially selected as a synchronization reference than the sending node of the second side synchronization signal block.

[0426] As an embodiment, the first transmitter 1210 may be a transceiver 1330. The second node 1100 may further include a processor 1310 and a memory 1320, as specifically shown in FIG13 .

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

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

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

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

[0431] Figure 14 is a block diagram of a hardware module of a communication device provided in an embodiment of the present application. Specifically, Figure 14 shows a block diagram of a first communication device 1450 and a second communication device 1410 communicating with each other in an access network.

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

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

[0434] During transmission from the second communications device 1410 to the first communications device 1450, at the second communications device 1410, upper layer data packets from the core network or from a data source 1477 are provided to a controller / processor 1475. The core network and data source 1477 represent all protocol layers above the L2 layer. The controller / processor 1475 implements L2 layer functionality. During transmission from the second communications device 1410 to the first communications 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 communications device 1450 based on various priority metrics. The controller / processor 1475 is also responsible for retransmission of lost packets and signaling to the first communications device 1450. The transmit processor 1416 and the multi-antenna transmit processor 1471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 1416 implements coding and interleaving to facilitate forward error correction at the second communication device 1410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying, quadrature phase shift keying, M-phase shift keying, and M-quadrature amplitude modulation). The multi-antenna transmit processor 1471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 1416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 1471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier 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 a different antenna 1420 .

[0435] During transmission from the second communications device 1410 to the first communications device 1450, each receiver 1454 at the first communications device 1450 receives a signal via its corresponding 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, which is provided to the receive processor 1456. The receive processor 1456 and the multi-antenna receive processor 1458 implement various L1 layer signal processing functions. The multi-antenna receive processor 1458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 1454. The receive processor 1456 uses a 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 receive processor 1456 demultiplexes the physical layer data signal and reference signal, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 1458 to recover any spatial streams destined for the first communications device 1450. The symbols on each spatial stream are demodulated and recovered in the receive processor 1456, and soft decisions are generated. The receive processor 1456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 1410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 1459. The controller / processor 1459 implements the functions of the L2 layer. The controller / processor 1459 may be associated with a memory 1460 that stores program codes and data. The memory 1460 may be referred to as a computer-readable medium. During 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, and control signal processing to recover the upper layer data packets from the second communication device 1410. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 layer for L3 processing.

[0436] During transmission from the first communications device 1450 to the second communications device 1410, upper layer data packets are provided to the controller / processor 1459 at the first communications device 1450 using a data source 1467. The data source 1467 represents all protocol layers above the L2 layer. Similar to the transmission functionality at the second communications device 1410 described in the transmission from the second communications device 1410 to the first communications device 1450, the controller / processor 1459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels, implementing L2 layer functions for both the user plane and the control plane. The controller / processor 1459 is also responsible for retransmission of lost packets and signaling to the second communications device 1410. The transmit processor 1468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 1457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 1468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 1457, the stream is provided 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 RF symbol stream before providing it to the antenna 1452.

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

[0438] As an embodiment, the first communication device 1450 apparatus 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 apparatus at least: receives one or more sideline synchronization signal blocks, the one or more sideline synchronization signal blocks including a first sideline synchronization signal block; determines whether the sending node of the first sideline synchronization signal block is selected as a synchronization reference according to a target priority group order, the target priority group order is one of a first priority group order and a second priority group order; wherein at least one of whether the first sideline synchronization signal block is configured for a first operation, whether the first sideline synchronization signal block carries a first type of identifier, and whether the first sideline synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation includes at least one of initial beam pairing, sideline unicast link establishment and sideline beam management.

[0439] As an embodiment, the first communication device 1450 apparatus includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating an action when executed by at least one processor, the action including: receiving one or more side synchronization signal blocks, the one or more side synchronization signal blocks including a first side synchronization signal block; determining whether the sending node of the first side synchronization signal block is selected as a synchronization reference according to a target priority group order, the target priority group order being one of a first priority group order and a second priority group order; wherein at least one of whether the first side synchronization signal block is configured for a first operation, whether the first side synchronization signal block carries a first type of identifier, and whether the first side synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation includes at least one of initial beam pairing, side unicast link establishment, and side beam management.

[0440] As an embodiment, the first communication device 1450 corresponds to the first node in this application.

[0441] As an embodiment, the second communication device 1410 corresponds to the second node in this application.

[0442] As an embodiment, the first communication device 1450 or the second communication device 1410 is a user equipment, and the user equipment can serve as a relay node.

[0443] As an embodiment, the first communication device 1450 or the second communication device 1410 is a user equipment supporting V2X, and the user equipment can serve as a relay node.

[0444] As an embodiment, the first communication device 1450 or the second communication device 1410 is a user equipment supporting D2D, and the user equipment can serve as a relay node.

[0445] As an embodiment, the first communication device 1450 or the second communication device 1410 is a network control relay NCR.

[0446] As an embodiment, the first communication device 1450 or the second communication device 1410 is a relay wireless repeater.

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

[0448] As an embodiment, the antenna 1452, the receiver 1454, the multi-antenna receiving processor 1458, the receiving processor 1456, and the controller / processor 1459 are used to receive one or more side synchronization signal blocks in the present application.

[0449] As an embodiment, the antenna 1420, the transmitter 1418, the multi-antenna transmit processor 1471, the transmit processor 1416, and the controller / processor 1475 are used to send the first sideline synchronization signal block in this application.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method in a first node for wireless communication, characterized in that include: Receiving one or more sideline synchronization signal blocks, wherein the one or more sideline synchronization signal blocks include a first sideline synchronization signal block; Determining whether the sending node of the first sideline synchronization signal block is selected as a synchronization reference according to a target priority group order, wherein the target priority group order is one of a first priority group order and a second priority group order; Among them, at least one of whether the first sideline synchronization signal block is configured for a first operation, whether the first sideline synchronization signal block carries a first type of identifier, and whether the first sideline synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation includes at least one of initial beam pairing, sideline unicast link establishment and sideline beam management.

2. The method according to claim 1, characterized in that The first priority group order is the order of multiple first-class priority groups, and the second priority group order is the order of multiple second-class priority groups; the sending node of the first side synchronization signal block corresponds to a target priority group, and the target priority group is one of the multiple first-class priority groups, or the target priority group is one of the multiple second-class priority groups; at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block used for the first operation, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block used for the first operation; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block carrying the first-class identifier, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block carrying the first-class identifier; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block occupying the first-class resources, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block occupying the first-class resources.

3. The method according to claim 1 or 2, characterized in that: When the first sideline synchronization signal block is configured for the first operation, the first sideline synchronization signal block carries the first category identifier, and the first sideline synchronization signal block occupies at least one of the first category resources, the target priority group order is the first priority group order; when the first sideline synchronization signal block is not configured for the first operation, the first sideline synchronization signal block does not carry the first category identifier, and the first sideline synchronization signal block does not occupy at least one of the first category resources, the target priority group order is the second priority group order.

4. The method according to any one of claims 1 to 3, characterized in that The first type of identifier is related to a sending node of a sideline synchronization signal block, or the first type of identifier is related to a receiving node of a sideline synchronization signal block, or the first type of identifier is related to a beam transmitting a sideline synchronization signal block.

5. The method according to any one of claims 1 to 4, characterized in that The first type of resources are configured for the first operation.

6. The method according to any one of claims 1 to 5, characterized in that The priority of the first priority group at the first position in the first priority group order is higher than the priority of the second priority group at the first position in the second priority group order.

7. The method according to any one of claims 1 to 5, characterized in that include: Performing a first signal measurement on the first sideline synchronization signal block; The relationship between the result of the first signal measurement and the target threshold is used to determine whether the sending node of the first side synchronization signal block is selected as the synchronization reference.

8. The method according to claim 7, characterized in that At least one of whether the first sideline synchronization signal block is configured for the first operation, whether the first sideline synchronization signal block carries the first type of identifier, and whether the first sideline synchronization signal block occupies the first type of resources is used to determine the target threshold.

9. The method according to any one of claims 1 to 8, characterized in that The target priority group order is the first priority group order, the first priority group order is the order of multiple first-class priority groups, at least one of the in-coverage indication carried by the first sideline synchronization signal block, the first-class identifier carried by the first sideline synchronization signal block and the time-frequency resources occupied by the first sideline synchronization signal block is used to determine the target priority group corresponding to the sending node of the first sideline synchronization signal block, and the multiple first-class priority groups include the target priority group.

10. The method according to claim 9, characterized in that The first type of identifier is a destination identifier, and whether the first type of identifier carried by the first side synchronization signal block is used to identify the first node is used to determine the position of the target priority group in the first priority group sequence.

11. The method according to claim 9, characterized in that The first type of identifier is a destination identifier, and the multiple side synchronization signal blocks also include a second side synchronization signal block. The first type of identifier carried by the first side synchronization signal block is used to identify the first node, and the first type of identifier carried by the second side synchronization signal block is not used to identify the first node; the sending node of the first side synchronization signal block is preferentially selected as a synchronization reference rather than the sending node of the second side synchronization signal block.

12. The method according to claim 9, characterized in that The multiple sideline synchronization signal blocks also include a second sideline synchronization signal block, the first sideline synchronization signal block occupies the first type of resources, and the second sideline synchronization signal block does not occupy the first type of resources; the sending node of the first sideline synchronization signal block is preferentially selected as a synchronization reference than the sending node of the second sideline synchronization signal block.

13. A method in a second node for wireless communication, characterized in that: include: Sending a first sideline synchronization signal block; Among them, at least one of whether the first sidewalk synchronization signal block is configured for the first operation, whether the first sidewalk synchronization signal block carries the first type of identifier, and whether the first sidewalk synchronization signal block occupies the first type of resources is used by the receiving node of the first sidewalk synchronization signal block to determine the target priority group order; the first operation includes at least one of initial beam pairing, sidewalk unicast link establishment and sidewalk beam management; the target priority group order is used to determine whether the second node is selected by the receiving node as a synchronization reference; the target priority group order is one of the first priority group order and the second priority group order.

14. The method according to claim 13, characterized in that The method further comprises: Receive first information, where the first information is used to indicate whether the first side synchronization signal block is configured for the first operation, and / or whether the first side synchronization signal block carries the first type of identifier, and / or whether the first side synchronization signal block occupies the first type of resources.

15. The method according to claim 13 or 14, characterized in that The first priority group order is the order of multiple first-class priority groups, and the second priority group order is the order of multiple second-class priority groups; the second node corresponds to a target priority group, and the target priority group is one of the multiple first-class priority groups, or the target priority group is one of the multiple second-class priority groups; at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block used for the first operation, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block used for the first operation; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block carrying the first-class identifier, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block carrying the first-class identifier; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block occupying the first-class resources, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block occupying the first-class resources.

16. The method according to any one of claims 13 to 15, characterized in that When the first sideline synchronization signal block is configured for the first operation, the first sideline synchronization signal block carries the first category identifier, and the first sideline synchronization signal block occupies at least one of the first category resources, the target priority group order is the first priority group order; when the first sideline synchronization signal block is not configured for the first operation, the first sideline synchronization signal block does not carry the first category identifier, and the first sideline synchronization signal block does not occupy at least one of the first category resources, the target priority group order is the second priority group order.

17. The method according to any one of claims 13 to 16, characterized in that The first type of identifier is related to a sending node of a sideline synchronization signal block, or the first type of identifier is related to a receiving node of a sideline synchronization signal block, or the first type of identifier is related to a beam transmitting a sideline synchronization signal block.

18. The method according to any one of claims 13 to 17, characterized in that: The first type of resources are configured for the first operation.

19. The method according to any one of claims 13 to 18, characterized in that: The priority of the first priority group at the first position in the first priority group order is higher than the priority of the second priority group at the first position in the second priority group order.

20. The method according to any one of claims 13 to 19, characterized in that The target priority group order is the first priority group order, the first priority group order is the order of multiple first-class priority groups, at least one of the in-coverage indication carried by the first sideline synchronization signal block, the first-class identifier carried by the first sideline synchronization signal block and the time-frequency resources occupied by the first sideline synchronization signal block is used to determine the target priority group corresponding to the second node, and the multiple first-class priority groups include the target priority group.

21. A first node for wireless communication, characterized in that: include: A first receiver, configured to receive one or more sideline synchronization signal blocks, wherein the one or more sideline synchronization signal blocks include a first sideline synchronization signal block; a first processor, configured to determine whether a sending node of the first sideline synchronization signal block is selected as a synchronization reference according to a target priority group order, wherein the target priority group order is one of a first priority group order and a second priority group order; Among them, at least one of whether the first sideline synchronization signal block is configured for a first operation, whether the first sideline synchronization signal block carries a first type of identifier, and whether the first sideline synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation includes at least one of initial beam pairing, sideline unicast link establishment and sideline beam management.

22. The first node according to claim 21, characterized in that The first priority group order is the order of multiple first-class priority groups, and the second priority group order is the order of multiple second-class priority groups; the sending node of the first side synchronization signal block corresponds to a target priority group, and the target priority group is one of the multiple first-class priority groups, or the target priority group is one of the multiple second-class priority groups; at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block used for the first operation, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block used for the first operation; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block carrying the first-class identifier, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block carrying the first-class identifier; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block occupying the first-class resources, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block occupying the first-class resources.

23. The first node according to claim 21 or 22, characterized in that: When the first sideline synchronization signal block is configured for the first operation, the first sideline synchronization signal block carries the first category identifier, and the first sideline synchronization signal block occupies at least one of the first category resources, the target priority group order is the first priority group order; when the first sideline synchronization signal block is not configured for the first operation, the first sideline synchronization signal block does not carry the first category identifier, and the first sideline synchronization signal block does not occupy at least one of the first category resources, the target priority group order is the second priority group order.

24. The first node according to any one of claims 21 to 23, characterized in that: The first type of identifier is related to a sending node of a sideline synchronization signal block, or the first type of identifier is related to a receiving node of a sideline synchronization signal block, or the first type of identifier is related to a beam transmitting a sideline synchronization signal block.

25. The first node according to any one of claims 21-24, characterized in that: The first type of resources are configured for the first operation.

26. The first node according to any one of claims 21-25, characterized in that: The priority of the first priority group at the first position in the first priority group order is higher than the priority of the second priority group at the first position in the second priority group order.

27. The first node according to any one of claims 21-25, characterized in that: include: A second processor, configured to perform a first signal measurement on the first sideline synchronization signal block; The relationship between the result of the first signal measurement and the target threshold is used to determine whether the sending node of the first side synchronization signal block is selected as the synchronization reference.

28. The first node according to claim 27, characterized in that At least one of whether the first sideline synchronization signal block is configured for the first operation, whether the first sideline synchronization signal block carries the first type of identifier, and whether the first sideline synchronization signal block occupies the first type of resources is used to determine the target threshold.

29. The first node according to any one of claims 21 to 28, characterized in that: The target priority group order is the first priority group order, the first priority group order is the order of multiple first-class priority groups, at least one of the in-coverage indication carried by the first sideline synchronization signal block, the first-class identifier carried by the first sideline synchronization signal block and the time-frequency resources occupied by the first sideline synchronization signal block is used to determine the target priority group corresponding to the sending node of the first sideline synchronization signal block, and the multiple first-class priority groups include the target priority group.

30. The first node according to claim 29, characterized in that The first type of identifier is a destination identifier, and the first type of identifier carried by the first side synchronization signal block is used to identify the first node and is used to determine the position of the target priority group in the first priority group order.

31. The first node according to claim 29, characterized in that The first type of identifier is a destination identifier, and the multiple side synchronization signal blocks also include a second side synchronization signal block. The first type of identifier carried by the first side synchronization signal block is used to identify the first node, and the first type of identifier carried by the second side synchronization signal block is not used to identify the first node; the sending node of the first side synchronization signal block is preferentially selected as a synchronization reference rather than the sending node of the second side synchronization signal block.

32. The first node according to claim 29, characterized in that The multiple sideline synchronization signal blocks also include a second sideline synchronization signal block, the first sideline synchronization signal block occupies the first type of resources, and the second sideline synchronization signal block does not occupy the first type of resources; the sending node of the first sideline synchronization signal block is preferentially selected as a synchronization reference than the sending node of the second sideline synchronization signal block.

33. A second node for wireless communication, characterized in that: include: A first transmitter, configured to send a first sideline synchronization signal block; Among them, at least one of whether the first sidewalk synchronization signal block is configured for the first operation, whether the first sidewalk synchronization signal block carries the first type of identifier, and whether the first sidewalk synchronization signal block occupies the first type of resources is used by the receiving node of the first sidewalk synchronization signal block to determine the target priority group order; the first operation includes at least one of initial beam pairing, sidewalk unicast link establishment and sidewalk beam management; the target priority group order is used to determine whether the second node is selected by the receiving node as a synchronization reference; the target priority group order is one of the first priority group order and the second priority group order.

34. The second node according to claim 33, characterized in that: Also includes: A second receiver is used to receive first information, wherein the first information is used to indicate whether the first side synchronization signal block is configured for the first operation, and / or whether the first side synchronization signal block carries the first type of identification, and / or whether the first side synchronization signal block occupies the first type of resources.

35. The second node according to claim 33 or 34, characterized in that: The first priority group order is the order of multiple first-class priority groups, and the second priority group order is the order of multiple second-class priority groups; the second node corresponds to a target priority group, and the target priority group is one of the multiple first-class priority groups, or the target priority group is one of the multiple second-class priority groups; at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block used for the first operation, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block used for the first operation; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block carrying the first-class identifier, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block carrying the first-class identifier; or, at least one of the multiple first-class priority groups includes a sending node of a side synchronization signal block occupying the first-class resources, and any second-class priority group of the multiple second-class priority groups does not include a sending node of a side synchronization signal block occupying the first-class resources.

36. The second node according to claim 33 or 35, characterized in that: When the first sideline synchronization signal block is configured for the first operation, the first sideline synchronization signal block carries the first category identifier, and the first sideline synchronization signal block occupies at least one of the first category resources, the target priority group order is the first priority group order; when the first sideline synchronization signal block is not configured for the first operation, the first sideline synchronization signal block does not carry the first category identifier, and the first sideline synchronization signal block does not occupy at least one of the first category resources, the target priority group order is the second priority group order.

37. The second node according to any one of claims 33-36, characterized in that: The first type of identifier is related to a sending node of a sideline synchronization signal block, or the first type of identifier is related to a receiving node of a sideline synchronization signal block, or the first type of identifier is related to a beam transmitting a sideline synchronization signal block.

38. The second node according to any one of claims 33-37, characterized in that: The first type of resources are configured for the first operation.

39. The second node according to any one of claims 33-38, characterized in that: The priority of the first priority group at the first position in the first priority group order is higher than the priority of the second priority group at the first position in the second priority group order.

40. The second node according to any one of claims 33-39, characterized in that: The target priority group order is the first priority group order, the first priority group order is the order of multiple first-class priority groups, at least one of the in-coverage indication carried by the first sideline synchronization signal block, the first-class identifier carried by the first sideline synchronization signal block and the time-frequency resources occupied by the first sideline synchronization signal block is used to determine the target priority group corresponding to the second node, and the multiple first-class priority groups include the target priority group.

41. A node used for wireless communication, characterized in that: It includes a transceiver, a memory and a processor, wherein 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 node executes the method as described in any one of claims 1-12 or 13-20.

42. A device, characterized in that It comprises a processor, which is used to call a program from a memory so that the device executes the method as described in any one of claims 1-12 or 13-20.

43. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes the method as described in any one of claims 1-12 or 13-20.

44. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1-12 or 13-20.

45. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method as claimed in any one of claims 1 to 12 or 13 to 20.

46. ​​A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1-12 or 13-20.

Images