Method and apparatus for use in node for wireless communication

Abstract

The present application provides a method and apparatus for use in a node for wireless communication, so as to achieve initial beam pairing based on a sidelink synchronization signal block. 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, the first sidelink synchronization signal block is configured for a first operation, and / or the first sidelink synchronization signal block carries a first-type identifier, and / or the first sidelink synchronization signal block occupies a first-type resource; and on the basis of a first priority group sequence, selecting a synchronization reference, wherein the first operation comprises at least one of initial beam pairing, sidelink unicast link establishment, and sidelink beam management, and the first priority group sequence is related to the first operation and / or a sidelink synchronization signal block carrying the first-type identifier and / or a sidelink synchronization signal block occupying the first-type resource.

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 sidelink synchronization signal blocks, the one or more sidelink synchronization signal blocks including a first sidelink synchronization signal block, the first sidelink synchronization signal block being configured for a first operation, and / or the first sidelink synchronization signal block carries a first type of identifier, and / or the first sidelink synchronization signal block occupies a first type of resource; selecting a synchronization reference according to a first priority group order; wherein the first operation includes at least one of initial beam pairing, sidelink unicast link establishment and sidelink beam management; the first priority group order is related to the first operation and / or the sidelink synchronization signal block carrying the first type of identifier and / or the sidelink synchronization signal block occupying the first type of resource.

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

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

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

[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 the first node receives one or more side synchronization signal blocks, it can determine whether the one or more side synchronization signal blocks include a first side synchronization signal block related to initial beam pairing, etc. based on at least one of the configuration of the side synchronization signal block, the identifier carried, and the occupied resources, thereby achieving effective initial beam pairing through the first side synchronization signal block before the side unicast link is established.

[0016] In an embodiment of the present application, the first node, acting as a receiving node, selects a synchronization reference according to a first priority group sequence. The synchronization priority rules of the first priority group sequence are related to initial beam pairing, sidelink unicast link establishment, beam management, the identifier carried by the sidelink synchronization signal block, and the resources occupied by the sidelink synchronization signal block. Therefore, the new synchronization priority rules take into account whether the sending node establishes a sidelink unicast link. Furthermore, the first priority group sequence optimizes the traditional synchronization priority rules, thereby optimizing the synchronization priority of the sending node in 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 schematic diagram of a possible implementation of the method shown in FIG4 .

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

[0028] FIG10 is a schematic diagram of a possible implementation of the method shown in FIG9 .

[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 a 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, transmission 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 set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in 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 device.

[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 includes 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) so that surrounding UEs 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] As mentioned above, the process of performing initial beam pairing before the sidelink unicast link is established has been introduced into the NR SL system, and S-SSB or a modified format of S-SSB will be used as the reference signal for the initial beam pairing.

[0082] In some scenarios, in order to facilitate UE2 to identify UE1 sending 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 (eS-SSB). When the UE sending the eS-SSB can be used as a synchronization reference source, the receiving user can select a synchronization reference from multiple synchronization reference sources according to the traditional NR SL synchronization priority rules.

[0083] However, if the UE sending the eS-SSB belongs to a lower priority group, the UE may not be able to perform initial access pairing and thus cannot establish a sidelink unicast link. However, for UEs sending eS-SSBs, they are not only used to maintain synchronization but also need to establish a sidelink unicast link. Therefore, traditional synchronization priority rules cannot meet the requirement for performing initial beam pairing to establish a sidelink 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] In order to solve the above problems, an embodiment of the present application proposes a method for a first node in wireless communication. Through this method, when the first node receives one or more sideline signal blocks including a first sideline synchronization signal block, it selects a synchronization reference according to a first priority group order. The first sideline synchronization signal block and the first priority group order are both related to first operations such as initial beam pairing, sideline unicast link establishment, and beam management, or first-class identifiers and first-class resources. In other words, the present application introduces a new synchronization priority group order related to the first operation, etc., so that the receiving node can select a synchronization reference according to the configuration of the sideline synchronization signal block, the identifier it carries, or the resources it occupies.

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

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

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

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

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

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

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

[0103] In one embodiment, the first S-SSB is used for the first operation. For example, the first S-SSB is used for initial beam pairing. In another example, the first S-SSB is used for sidewalk unicast link establishment. In another example, the first S-SSB is used for sidewalk beam management. In another example, the first S-SSB is used for initial beam pairing before establishing a sidewalk unicast link to establish the sidewalk unicast link.

[0104] Exemplarily, the first S-SSB is configured for sideways initial beam pairing, so that the first node can match the transmit beam and receive beam with the transmitting node of the first S-SSB to determine the optimal beam pair.

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

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

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

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

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

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

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

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

[0113] Exemplarily, the first S-SSB is configured for side unicast link establishment, so the first node can establish a side unicast link with the sending node of the first S-SSB by receiving the first S-SSB.

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

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

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

[0117] In some embodiments, 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.

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

[0119] In some embodiments, the first S-SSB may also be used for a conventional synchronization reference, or may also be used for conventional sideline communication or sideline discovery.

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

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

[0122] In some embodiments, the first S-SSB may be configured for multiple operations. For example, the first S-SSB may be used for both the first operation and the conventional operation.

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

[0124] As an embodiment, the first S-SSB is used for the first operation, and the first S-SSB is also used for sideline communication or sideline discovery.

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

[0126] Exemplarily, the first type of identifier can be used to identify the relevant information of the carrier. As an embodiment, 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 carrying the S-SSB. Taking the first S-SSB as an example, the first type of identifier carried by the first S-SSB can be the identifier of the second node sending the first S-SSB (source identifier), or the identifier of the first node receiving the first S-SSB (destination identifier), or the beam identifier carrying the first S-SSB.

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

[0128] As an embodiment, the first S-SSB belongs to the S-SSB carrying the first type of identifier.

[0129] As an embodiment, the S-SSB carrying the first type of identifier includes the first S-SSB.

[0130] Exemplarily, the first S-SSB may indicate that it is used for the first operation by carrying a first type of identifier. Therefore, the first S-SSB is configured for the first operation, which can also be represented as the first S-SSB carrying the first type of identifier.

[0131] As an embodiment, when the S-SSB carries the first type of identifier, the sending node of the S-SSB supports S-SSB-based side initial beam pairing and / or side unicast link establishment and / or side beam management.

[0132] In some embodiments, the first S-SSB occupies first-class resources. The first-class resources may be time-frequency resources reserved or dynamically scheduled by the system for performing the first operation between any two nodes. In some embodiments, the first-class resources are resources distinct from traditional sideline synchronization. That is, the first-class resources are independent of traditional resources used for synchronization. If the first S-SSB occupies the first-class resources, the first-class S-SSB is used for the first operation; if the first S-SSB does not occupy the first-class resources, the first-class S-SSB is used for traditional operations.

[0133] As an embodiment, the first type of resources differ from the resources occupied by the conventional S-SSB used for synchronization. In other words, the first type of resources are configured separately from the resources used for synchronization. For example, the first type of resources and the conventional resources used for synchronization occupy different time domain resources, or they occupy different frequency domain resources in the same time domain.

[0134] Exemplarily, the S-SSB occupying the first type of resources may be a plurality of S-SSBs, and is distinguished from other S-SSBs by the occupied time-frequency resources. Therefore, the S-SSB occupying the first type of resources may be a type of S-SSB.

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

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

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

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

[0139] As an embodiment, multiple side signal resources used to send or receive S-SSB are associated with the first type of identifier, or carry the first type of identifier, or are mapped to the first type of identifier.

[0140] In an embodiment of the present application, the first S-SSB is configured for a first operation, the first S-SSB carries a first type of identifier, and the first S-SSB occupies a first type of resource. The three expressions can be interchangeable.

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

[0142] 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. Exemplarily, the first S-SSB is configured for the first operation, and the second S-SSB is not configured for the first operation. Exemplarily, the first S-SSB carries a first-category identifier, and the second S-SSB does not carry the first-category identifier. Exemplarily, the first S-SSB occupies first-category resources, and the second S-SSB does not occupy first-category resources.

[0143] Continuing to refer to FIG. 4 , in step S420 , a synchronization reference is selected according to the first priority group sequence.

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

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

[0146] The first priority group order is related to the first operation and / or the S-SSB carrying the first type of identifier and / or the S-SSB occupying the first type of resources. In other words, the first priority group order is different from the priority group order in Table 2 above. Exemplarily, when the first node receives the first S-SSB, the sending node of the first S-SSB will no longer prioritize according to the priority group order in Table 2 above to avoid the sending node being unable to perform the first operation.

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

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

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

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

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

[0152] In some embodiments, the first S-SSB may carry the first type of identifier in a variety of ways. For example, the first type of identifier may be indicated by the SLSSID carried by the first S-SSB, so that the first node can directly determine whether the S-SSB carries the first type of identifier when decoding the SLSSID.

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

[0154] Exemplarily, the first type of identifier and the SLSSID carried by the first S-SSB can be independently indicated, and the first node can jointly determine the priority group of the sending node based on the first type of identifier and the SLSSID.

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

[0156] As an embodiment, the first S-SSB carries the SLSSID and the first type identifier, wherein the first type identifier and the SLSSID are independently indicated.

[0157] As an embodiment, the first type of identification does not include SLSSID.

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

[0159] As can be seen from FIG4 , whether the sending node requires initial beam pairing and / or establishing a side unicast link and / or performing side beam management is used to determine the priority of the sending node as a synchronization reference source.

[0160] The above description, combined with FIG4 , describes a priority synchronization rule for the first priority group sequence, which considers whether the sending node needs to perform the first operation. To increase the probability of the user device successfully executing the first operation, it is necessary to increase (or adjust) the synchronization priority of the user device that needs to perform the first operation. For ease of understanding, the following describes a method for increasing the synchronization priority of the user device that performs the first operation in detail, combined with various possible implementations of the first priority group sequence.

[0161] In some embodiments, the first priority group sequence may be a sequence of multiple candidate priority groups. The multiple candidate priority groups may include a target priority group, to which the transmitting node of the first S-SSB corresponds. That is, the target priority group is the priority group corresponding to the transmitting node of the first S-SSB, and the multiple priority groups in the first priority group sequence may directly include the target priority group.

[0162] Exemplarily, the target priority group may be the first candidate priority group among the plurality of candidate priority groups. Thus, in the first priority group order, the target priority group is at the highest priority position. In this case, when the first node receives a plurality of S-SSBs including the first S-SSB, regardless of which priority group the sending node of the first S-SSB corresponds to in Table 2, the sending node will be preferentially selected by the first node as the synchronization reference.

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

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

[0165] As an embodiment, in the first priority group sequence, the target priority group may be any one of the plurality of candidate priority groups.

[0166] As an embodiment, the target priority group includes UE(s) that need to perform a first operation, or UE(s) whose side synchronization signal blocks carry a first type of identifier, or UE(s) whose side synchronization signal blocks occupy a first type of resources.

[0167] As an embodiment, UE(s) that need to perform the first operation, or UE(s) whose side synchronization signal block carries the first type of identifier, or UE(s) whose side synchronization signal block occupies the first type of resources belongs to the target priority group.

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

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

[0170] As an embodiment, the multiple candidate priority groups include 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.

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

[0172] As an embodiment, the multiple candidate priority groups include 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.

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

[0174] As an embodiment, the multiple candidate priority groups include 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.

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

[0176] As an embodiment, the UE(s) that needs to perform the first operation belongs to one candidate priority group among the multiple candidate priority groups.

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

[0178] As an embodiment, the UE(s) directly synchronized to the GNSS belongs to one candidate priority group among the multiple candidate priority groups.

[0179] As an embodiment, one of the plurality of candidate priority groups includes UE(s) directly synchronized to the GNSS.

[0180] As an embodiment, the UE(s) indirectly synchronized to the GNSS belongs to one candidate priority group among the multiple candidate priority groups.

[0181] As an embodiment, one of the plurality of candidate priority groups includes UE(s) that are indirectly synchronized to the GNSS.

[0182] As an embodiment, the gNB / eNB belongs to one candidate priority group among the multiple candidate priority groups.

[0183] As an embodiment, one of the multiple candidate priority groups includes gNB / eNB.

[0184] As an embodiment, the UE(s) directly synchronized to the gNB / eNB belongs to one candidate priority group among multiple candidate priority groups.

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

[0186] As an embodiment, the UE(s) indirectly synchronized to the gNB / eNB belongs to one candidate priority group among multiple candidate priority groups.

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

[0188] As an embodiment, the GNSS belongs to one candidate priority group among the multiple candidate priority groups.

[0189] As an embodiment, one of the plurality of candidate priority groups includes GNSS.

[0190] In some embodiments, the plurality of candidate priority groups may also be indicated based on at least two of the SLSSID, InC, and resources occupied by a sidelink synchronization signal (SLSS) of the UE(s). As an embodiment, the plurality of candidate priority groups include:

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

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

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

[0194] gNB / eNB, or GNSS;

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

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

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

[0198] As an embodiment, the multiple candidate priority groups include:

[0199] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

[0203] gNB / eNB, or GNSS;

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

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

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

[0207] As an embodiment, the multiple candidate priority groups include:

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

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

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

[0211] gNB / eNB, or GNSS;

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

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

[0214] As an embodiment, the multiple candidate priority groups include:

[0215] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

[0219] gNB / eNB, or GNSS;

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

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

[0222] As an embodiment, the UE(s) whose SLSS carries the first category identifier, or the UE(s) whose SLSS occupies the first category resources belongs to one candidate priority group among the multiple candidate priority groups.

[0223] As an embodiment, one of the multiple candidate priority groups includes UE(s) whose SLSS carries a first type of identifier, or UE(s) whose SLSS occupies a first type of resources.

[0224] As an embodiment, 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 belongs to one candidate priority group among the multiple candidate priority groups.

[0225] As an embodiment, one of the multiple candidate priority groups includes 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.

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

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

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

[0229] As an embodiment, the UE(s) with SLSSID=337 and InC=false belongs to one candidate priority group among the multiple candidate priority groups.

[0230] As an embodiment, UE(s) with SLSSID∈{0,1,...,335} and InC=true belongs to one candidate priority group among the multiple candidate priority groups.

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

[0232] As an embodiment, UE(s) with SLSSID∈{0, 1, . . . , 335} and InC=false belongs to one candidate priority group among the multiple candidate priority groups.

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

[0234] Table 3

[0235] It should be understood that the establishment of the sidewalk unicast link in Table 3 can be replaced by performing the first operation. Exemplarily, the establishment of the sidewalk unicast link can also be sidewalk initial beam pairing or sidewalk beam management.

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

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

[0238] For example, the position of the target priority group in the first priority group order can be determined based on any priority group other than the target priority group among the plurality of candidate priority groups. The candidate priority group used to determine the order of the target priority groups can be referred to as a given candidate priority group. For example, the given candidate priority group serves as a reference level group, and the target priority group can be placed before or after the given candidate priority group. Therefore, the order in which the target priority groups are selected will be determined based on the selected given candidate priority group.

[0239] As an embodiment, the plurality of candidate priority groups include a given candidate priority group, and the position of the target priority group in the plurality of candidate priority groups is before the position of the given candidate priority group in the plurality of candidate priority groups. For example, the given candidate priority group may be priority group 2 corresponding to P2 in Table 3. When the position of the target priority group in the plurality of candidate priority groups is before P2, the position of the target priority group may be between P1 and P2, or may be P1.

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

[0241] As an embodiment, the given candidate priority group is any one of the seven candidate priority groups including GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; and the remaining UE(s) excluding the above UEs, and the position of the target priority group in the multiple candidate priority groups is before the position of any of the above priority groups.

[0242] As an embodiment, the given candidate priority group is any one of the seven candidate priority groups: 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, and the position of the target priority group in the multiple candidate priority groups is before the position of any of the above priority groups.

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

[0244] As an embodiment, for a given candidate priority group, the UE(s) is SLSSID=0 and SLSS is not transmitted on the time slot indicated by sl-SSB-TimeAllocation3 and InC=false, the position of the target priority group in multiple candidate priority groups is before the position of the given candidate priority group.

[0245] As an embodiment, given that the candidate priority group is a UE(s) with SLSSID=337 and InC=false, the position of the target priority group in the plurality of candidate priority groups is before the position of the given candidate priority group.

[0246] As an embodiment, the given candidate priority group is a gNB / eNB, or a GNSS, and the position of the target priority group in the multiple candidate priority groups is before the position of the given candidate priority group.

[0247] As an embodiment, given a candidate priority group is a UE(s) with SLSSID∈{0,1,...,335} and InC=true, the position of the target priority group in the plurality of candidate priority groups is before the position of the given candidate priority group.

[0248] As an embodiment, given a candidate priority group is a UE(s) with SLSSID∈{0,1,...,335} and InC=false, the position of the target priority group in the plurality of candidate priority groups is before the position of the given candidate priority group.

[0249] As an embodiment, the given candidate priority group is the remaining UE(s) after removing the above UEs, and the position of the target priority group in the multiple candidate priority groups is before the position of the given candidate priority group.

[0250] As an embodiment, the given candidate priority group corresponds to P2 in Table 3, which is a UE(s) indirectly synchronized to GNSS or a UE(s) indirectly synchronized to gNB / eNB, and the target priority group is located between P1 and P2 among the multiple candidate priority groups.

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

[0252] As an embodiment, the given candidate priority group corresponds to P4 in Table 3, which is a UE(s) directly synchronized to the gNB / eNB or a UE(s) directly synchronized to the GNSS, and the target priority group is positioned between P3 and P4 among the multiple candidate priority groups.

[0253] As an embodiment, the given candidate priority group corresponds to P5 in Table 3, which is a UE(s) indirectly synchronized to the gNB / eNB or a UE(s) indirectly synchronized to the GNSS, and the target priority group is positioned between P4 and P5 among the multiple candidate priority groups.

[0254] As an embodiment, the given candidate priority group corresponds to the remaining lowest priority UE(s) of P6 in Table 3, and the target priority group is positioned between P5 and P6 among the multiple candidate priority groups. As an embodiment, the multiple candidate priority groups include, in addition to the priority group corresponding to the UE(s) requiring the first operation, multiple priority groups corresponding to any multiple UEs from P1 to P6 in Table 3.

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

[0256] As an embodiment, the first priority group order is a priority group order consisting of a priority group including UE(s) that needs to perform the first operation and any other multiple priority groups in Table 3.

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

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

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

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

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

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

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

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

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

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

[0267] As an embodiment, the order of the first priority groups is: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; the remaining UE(s) excluding the above UEs are arranged in order. Seven candidate priority groups.

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

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

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

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

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

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

[0274] As an embodiment, the order of the first priority groups is: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; UE(s) requiring the first operation; and the remaining UE(s) excluding the above UEs. As an embodiment, the order of the first priority groups is: UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; and UE(s) indirectly synchronized to gNB / eNB. The five candidate priority groups are arranged in sequence.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0292] gNB / eNB;

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

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

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

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

[0297] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

[0301] gNB / eNB;

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

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

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

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

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

[0307] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

[0310] gNB / eNB;

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

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

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

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

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

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

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

[0318] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

[0319] gNB / eNB;

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

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

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

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

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

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

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

[0327] gNB / eNB;

[0328] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

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

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

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

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

[0336] gNB / eNB;

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

[0338] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

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

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

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

[0345] gNB / eNB;

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

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

[0348] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

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

[0353] GNSS;

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

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

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

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

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

[0359] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

[0362] GNSS;

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

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

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

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

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

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

[0369] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

[0371] GNSS;

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

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

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

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

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

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

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

[0379] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

[0380] GNSS;

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

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

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

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

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

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

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

[0388] GNSS;

[0389] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

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

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

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

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

[0397] GNSS;

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

[0399] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

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

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

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

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

[0406] GNSS;

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

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

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

[0410] UE(s) whose SLSS carries the first category identifier, or UE(s) whose SLSS occupies the first category resources;

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

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

[0413] The priority group sequence in Table 3 shows that this implementation method has redefined the synchronization priority rule. Specifically, the above implementation method assigns the user equipment that needs to perform the first operation to a higher priority group, or introduces a new priority group for the user equipment that needs to perform the first operation.

[0414] In some embodiments, the traditional synchronization priority rule is reused. When the user equipment needs to perform the first operation, the synchronization priority of the user equipment is increased by a priority group offset (priority offset) so that the user equipment is preferentially selected. For example, according to the traditional synchronization priority rule (for example, Figure 2), UE1 belongs to priority group 4. When UE1 needs to establish a side unicast link, UE1 is assigned to a new priority group. If the new priority group is, for example, priority group 1, then priority offset = 3. If the new priority group is, for example, priority group 2, then priority offset = 2.

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

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

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

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

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

[0420] For another example, when original priority group - priority offset < 1, new priority group = 1.

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

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

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

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

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

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

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

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

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

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

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

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

[0433] As an embodiment, the time domain resources are represented by time slots or symbols or other time units.

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

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

[0436] For ease of understanding, an implementation manner of determining the target priority group based on the reference priority group and the priority group offset is exemplarily described below with reference to FIG. 8 .

[0437] Referring to Figure 8, the index of the first reference priority group corresponding to the sending node of the first S-SSB is synchronization priority group 4. When the priority group offset is 2, the index of the target priority group corresponding to the sending node is synchronization priority group 2.

[0438] As can be seen from Figure 8, after determining the first reference priority group based on the first S-SSB, the index of the first reference priority group is reduced by 2 to determine the index of the target priority group, thereby improving the priority of the sending node of the first S-SSB.

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

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

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

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

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

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

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

[0446] As an embodiment, the first priority group includes user equipments that select a cell as a synchronization reference, and the second priority group includes user equipments that select a GNSS as a synchronization reference.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0461] As an embodiment, the first priority group includes user equipments that select GNSS as a synchronization reference, and the second priority group includes user equipments that select the second category of user equipments as a synchronization reference.

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

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

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

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

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

[0467] As an embodiment, the first parameter is used to determine the first priority group order from a plurality of priority group orders.

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

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

[0470] As an embodiment, the first node may determine whether the priority group of the sending node of the first S-SSB belongs to the first priority group or the second priority group based on system configuration or pre-configuration.

[0471] For example, the target priority group mentioned above may be the first priority group or the second priority group. For example, the first priority group is a synchronization priority based on GNSS. To improve the priority of the target priority group, the target priority group is positioned before the UE directly synchronized to GNSS among multiple candidate priority groups.

[0472] In the multiple ways of determining the order of the first priority group described above, the one or more S-SSBs received by the first node also include a second S-SSB. Whether the second S-SSB is configured for the first operation, whether the second S-SSB carries a first-category identifier, or whether the second S-SSB occupies first-category resources is used to determine the priority group of the sending node of the first S-SSB.

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

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

[0475] As an embodiment, the first S-SSB occupies the first type of resources, the second S-SSB does not occupy the first type of resources, and the sending node of the first S-SSB is preferentially selected as a synchronization reference over the sending node of the second S-SSB block.

[0476] As an embodiment, in the first priority group order, the priority group corresponding to the sending node of the second S-SSB is located after the priority group corresponding to the sending node of the first S-SSB. That is, when the first node receives the first S-SSB and the second S-SSB, the priority of the sending node of the first S-SSB is higher than the priority of the sending node of the second S-SSB.

[0477] The above text describes various methods for determining the order of the first priority group and the priority group of the first S-SSB sending node in conjunction with Figures 4 to 8. The above method is mainly used to increase the priority group corresponding to the sending node of the first S-SSB so that the sending node is preferentially selected as a synchronization reference. However, in the above method, there may be a situation where multiple sending nodes are preferentially selected. For example, when multiple sending nodes are in the same priority group, how to select a synchronization reference also becomes a technical problem that needs to be solved.

[0478] To address this issue, embodiments of the present application further provide another method for a first node in wireless communication to prioritize the sending node of a first S-SSB. This method reuses traditional synchronization priority rules (e.g., FIG. 2 ) and adjusts the probability of the user equipment being prioritized based on measurement results when the user equipment needs to perform a first operation.

[0479] Exemplarily, in the same priority group, when a user equipment needs to perform a first operation, the user equipment is preferentially selected among all user equipments in the same priority group based on the measurement result.

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

[0481] For ease of understanding, the method for determining the probability of a transmitting node being preferentially selected based on measurement results is described below in conjunction with FIG9 . It should be understood that FIG9 is also performed by the first node. For the sake of brevity, the terms explained in FIG4 are not repeated in FIG9 .

[0482] 9 , in step S910 , one or more S-SSBs are received, which is the same as step S410 .

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

[0484] The one or more S-SSBs in step S910 may respectively include one or more PSBCHs. That is, each S-SSB may include one PSBCH. For example, the first S-SSB includes the first PSBCH.

[0485] The first node measures the one or more PSBCHs to obtain one or more measurement results. The one or more measurement results are used to determine whether the transmitting node of the first S-SSB is selected as the synchronization reference. The one or more measurement results include a result of the first node measuring the first PSBCH.

[0486] Exemplarily, one or more measurement results may be represented by a plurality of signal quality parameters. The signal quality parameters used to represent the measurement results may be reference signal received power (RSRP), reference signal received quality (RSRQ), reference signal strength indication (RSSI), and the like, and are not limited thereto.

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

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

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

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

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

[0492] As a sub-embodiment of the above embodiment, the second S-SSB is configured for the first operation, and when the measurement result for the first PSBCH is greater than the measurement result for the second PSBCH, the sending node of the first S-SSB is preferentially selected as the synchronization reference rather than the sending node of the second S-SSB; when the measurement result for the first PSBCH is less than the measurement result for the second PSBCH, the sending node of the second S-SSB is preferentially selected as the synchronization reference rather than the sending node of the first S-SSB.

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

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

[0495] As an embodiment, when the second S-SSB occupies the first type of resources, the size relationship between the measurement results for the first PSBCH and the measurement results for the second PSBCH is used to determine whether the sending node of the first S-SSB is selected as a synchronization reference; when 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 over the sending node of the second S-SSB.

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

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

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

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

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

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

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

[0503] For ease of understanding, the following is an exemplary description of a method for determining whether the transmitting node of the first S-SSB is preferentially selected based on the measurement result and the measurement result offset, in conjunction with Figure 10. Figure 10 (a) shows a comparison of multiple measurement results of multiple user equipment without considering the measurement result offset, and (b) shows a comparison of multiple measurement results of multiple user equipment determined based on the measurement result offset.

[0504] Referring to Figures (a) and (b) in Figure 10, UE2 receives three S-SSBs from UE1, UE3, and UE4. UE2 measures the three PSBCHs in each of the three S-SSBs and obtains three PSBCH-RSRPs. UE1 is the user equipment that needs to perform the first operation. The PSBCH-RSRP corresponding to UE1 is increased by an RSRP offset, and then the RSRP is used to determine whether to select UE1 as the synchronization reference.

[0505] Comparing Figures (a) and (b), we can see that in Figure (a), UE1's RSRP is the smallest among the three UEs, while in Figure (b), UE1's RSRP is the largest. Therefore, due to the RSRP offset, UE1 is preferred as the synchronization reference over UE3 and UE4.

[0506] As shown in Figure 10, by increasing the PSBCH-RSRP detected by a user equipment by an RSRP offset, the user equipment has a greater probability of being selected as a SyncRefUE compared to other user equipments in the same priority group. In other words, the probability of the transmitting node of the first S-SSB being preferentially selected can be increased by using the measurement result offset.

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

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

[0509] The first receiver 1110 can be used 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, where the first sideline synchronization signal block is configured for a first operation, and / or the first sideline synchronization signal block carries a first type of identifier, and / or the first sideline synchronization signal block occupies a first type of resource; wherein the first operation includes at least one of initial beam pairing, sideline unicast link establishment, and sideline beam management.

[0510] The first processor 1120 can be used to select a synchronization reference according to a first priority group order; the first priority group order is related to the first operation and / or the side synchronization signal block carrying the first type of identifier and / or the side synchronization signal block occupying the first type of resources.

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

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

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

[0514] As an embodiment, the multiple sideline synchronization signal blocks including the first sideline synchronization signal block also include a second sideline synchronization signal block, the first sideline synchronization signal block is configured for the first operation, and the second sideline synchronization signal block is not configured for the first operation; or, the first sideline synchronization signal block carries the first type of identifier, and the second sideline synchronization signal block does not carry the first type of identifier; or, 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 the synchronization reference than the sending node of the second sideline synchronization signal block.

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

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

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

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

[0519] As an embodiment, the multiple sideline synchronization signal blocks including the first sideline synchronization signal block also include a second sideline synchronization signal block, and the second sideline synchronization signal block includes a second physical sideline broadcast channel; the one or more measurement results for the one or more physical sideline broadcast channels include a measurement result for the second physical sideline broadcast channel; whether the second sideline synchronization signal block is configured for the first operation, whether the second sideline synchronization signal block carries the first type of identifier, and whether the second sideline synchronization signal block occupies the first type of resources, and the size relationship between the measurement results for the first physical sideline broadcast channel and the measurement results for the second physical sideline broadcast channel are used to determine whether the sending node of the first sideline synchronization signal block is selected as the synchronization reference.

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

[0521] As an embodiment, the first type of identifier is related to the sending node of the side synchronization signal block, or the first type of identifier is related to the receiving node of the side synchronization signal block, or the first type of identifier is related to the beam carrying the side synchronization signal block.

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

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

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

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

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

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

[0528] As an embodiment, the multiple sideline synchronization signal blocks received by the receiving node of the first sideline synchronization signal block also include a second sideline synchronization signal block, the first sideline synchronization signal block is configured for the first operation, and the second sideline synchronization signal block is not configured for the first operation; or, the first sideline synchronization signal block carries the first type of identifier, and the second sideline synchronization signal block does not carry the first type of identifier; or, 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 second node is preferentially selected as a synchronization reference over the sending node of the second sideline synchronization signal block.

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

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

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

[0532] As an embodiment, the first type of identifier is related to the sending node of the side synchronization signal block, or the first type of identifier is related to the receiving node of the side synchronization signal block, or the first type of identifier is related to the beam carrying the side synchronization signal block.

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

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

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

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

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

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

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

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

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

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

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

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

[0545] 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 include a first sideline synchronization signal block, the first sideline synchronization signal block is configured for a first operation, and / or the first sideline synchronization signal block carries a first type of identifier, and / or the first sideline synchronization signal block occupies a first type of resource; selects a synchronization reference according to a first priority group order; wherein the first operation includes at least one of initial beam pairing, sideline unicast link establishment and sideline beam management; the first priority group order is related to the first operation and / or the sideline synchronization signal block carrying the first type of identifier and / or the sideline synchronization signal block occupying the first type of resource.

[0546] 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 sideline synchronization signal blocks, the one or more sideline synchronization signal blocks including a first sideline synchronization signal block, the first sideline synchronization signal block being configured for a first operation, and / or the first sideline synchronization signal block carries a first type of identifier, and / or the first sideline synchronization signal block occupies a first type of resource; selecting a synchronization reference according to a first priority group order; wherein the first operation includes at least one of initial beam pairing, sideline unicast link establishment and sideline beam management; the first priority group order is related to the first operation and / or the sideline synchronization signal block carrying the first type of identifier and / or the sideline synchronization signal block occupying the first type of resource.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0564] 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 user equipment and network equipment). The present application does not limit the specific implementation method. For example, pre-defined may refer to information defined in a protocol.

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

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

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

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

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

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

[0571] 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)).

[0572] 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: Receive one or more sideline synchronization signal blocks, wherein the one or more sideline synchronization signal blocks include a first sideline synchronization signal block, wherein the first sideline synchronization signal block is configured for a first operation, and / or the first sideline synchronization signal block carries a first type of identifier, and / or the first sideline synchronization signal block occupies a first type of resource; selecting a synchronization reference according to a first priority group order; Among them, the first operation includes at least one of initial beam pairing, side unicast link establishment and side beam management; the first priority group order is related to the first operation and / or the side synchronization signal block carrying the first type of identifier and / or the side synchronization signal block occupying the first type of resources.

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

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

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

5. The method according to any one of claims 1 to 4, characterized in that The multiple sideline synchronization signal blocks including the first sideline synchronization signal block also include a second sideline synchronization signal block, the first sideline synchronization signal block is configured for the first operation, and the second sideline synchronization signal block is not configured for the first operation; or, the first sideline synchronization signal block carries the first type of identifier, and the second sideline synchronization signal block does not carry the first type of identifier; or, 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.

6. The method according to any one of claims 1 to 5, characterized in that The first priority group order is the order of multiple candidate priority groups, and the multiple candidate priority groups include a first priority group and a second priority group; the sending node of the first side synchronization signal block corresponds to one of the first priority group and the second priority group.

7. The method according to claim 6, characterized in that The first priority group corresponds to user equipment that selects a cell as a synchronization reference, or the first priority group corresponds to user equipment that selects a first type of user equipment as a synchronization reference, and the first type of user equipment selects a cell as a synchronization reference; the second priority group corresponds to user equipment that selects a global navigation satellite system GNSS as a synchronization reference, or the second priority group corresponds to user equipment that selects a second type of user equipment as a synchronization reference, and the second type of user equipment selects GNSS as a synchronization reference.

8. The method according to claim 6 or 7, characterized in that: The position of the first priority group in the multiple candidate priority groups is before the position of the second priority group in the multiple candidate priority groups, or the position of the first priority group in the multiple candidate priority groups is after the position of the second priority group in the multiple candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

9. The method according to any one of claims 1 to 8, characterized in that include: measuring one or more physical sideline broadcast channels; The one or more sideline synchronization signal blocks respectively include the one or more physical sideline broadcast channels, and the one or more measurement results for the one or more physical sideline broadcast channels include the measurement results for the first physical sideline broadcast channel, and the measurement results for the first physical sideline broadcast channel are used to determine whether the sending node of the first sideline synchronization signal block is selected as the synchronization reference.

10. According to the method according to claim 9, the multiple sideline synchronization signal blocks including the first sideline synchronization signal block also include a second sideline synchronization signal block, and the second sideline synchronization signal block includes a second physical sideline broadcast channel; the one or more measurement results for the one or more physical sideline broadcast channels include the measurement results for the second physical sideline broadcast channel; whether the second sideline synchronization signal block is configured for the first operation, whether the second sideline synchronization signal block carries the first type of identifier, and whether the second sideline synchronization signal block occupies the first type of resources, and the size relationship between the measurement results for the first physical sideline broadcast channel and the measurement results for the second physical sideline broadcast channel are used to determine whether the sending node of the first sideline synchronization signal block is selected as the synchronization reference.

11. The method according to claim 9, characterized in that The sum of the measurement result and the measurement result offset for the first physical sideline broadcast channel is used to determine whether the sending node of the first sideline synchronization signal block is selected as a synchronization reference; The first sideline synchronization signal block is used to determine the measurement result offset.

12. The method according to any one of claims 1 to 11, characterized in that The first type of identifier is related to a sending node of a side synchronization signal block, or the first type of identifier is related to a receiving node of a side synchronization signal block, or the first type of identifier is related to a beam carrying a side synchronization signal block.

13. A method in a second node for wireless communication, characterized in that: include: Sending a first sideline synchronization signal block, where the first sideline synchronization signal block is configured for a first operation, and / or the first sideline synchronization signal block carries a first type of identifier, and / or the first sideline synchronization signal block occupies a first type of resource; Among them, the first operation includes at least one of initial beam pairing, sidewalk unicast link establishment and sidewalk beam management; the receiving node of the first sidewalk synchronization signal block selects a synchronization reference according to a first priority group order; the first priority group order is related to the first operation and / or the sidewalk synchronization signal block carrying the first type of identifier and / or the sidewalk synchronization signal block occupying the first type of resources.

14. The method according to claim 13, characterized in that The first priority group order is the order of multiple candidate priority groups; the multiple candidate priority groups include a target priority group, and the second node corresponds to the target priority group.

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

16. The method according to claim 14, characterized in that The multiple candidate priority groups include a first reference priority group; the index of the target priority group is the difference between the index of the first reference priority group and the priority group offset, or the index of the target priority group is the maximum value of the difference between the index of the first reference priority group and the priority group offset and 1; at least two of the sideline synchronization signal identifier carried by the first sideline synchronization signal block, the in-coverage indication and the time-frequency resources occupied by the first sideline synchronization signal block are used together to determine the first reference priority group, and the first sideline synchronization signal block is used to determine the priority group offset.

17. The method according to any one of claims 13 to 16, characterized in that The multiple sideline synchronization signal blocks received by the receiving node of the first sideline synchronization signal block also include a second sideline synchronization signal block, the first sideline synchronization signal block is configured for the first operation, and the second sideline synchronization signal block is not configured for the first operation; or, the first sideline synchronization signal block carries the first type of identifier, and the second sideline synchronization signal block does not carry the first type of identifier; or, 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 second node is preferentially selected as the synchronization reference over the sending node of the second sideline synchronization signal block.

18. The method according to any one of claims 13 to 17, characterized in that: The first priority group order is the order of multiple candidate priority groups, and the multiple candidate priority groups include a first priority group and a second priority group; the sending node of the first side synchronization signal block corresponds to one of the first priority group and the second priority group.

19. The method according to claim 18, characterized in that The first priority group corresponds to user equipment that selects a cell as a synchronization reference, or the first priority group corresponds to user equipment that selects a first type of user equipment as a synchronization reference, and the first type of user equipment selects a cell as a synchronization reference; the second priority group corresponds to user equipment that selects a global navigation satellite system GNSS as a synchronization reference, or the second priority group corresponds to user equipment that selects a second type of user equipment as a synchronization reference, and the second type of user equipment selects GNSS as a synchronization reference.

20. The method according to claim 18 or 19, characterized in that The position of the first priority group in the multiple candidate priority groups is before the position of the second priority group in the multiple candidate priority groups, or the position of the first priority group in the multiple candidate priority groups is after the position of the second priority group in the multiple candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

21. The method according to any one of claims 13 to 20, characterized in that The first type of identifier is related to a sending node of a side synchronization signal block, or the first type of identifier is related to a receiving node of a side synchronization signal block, or the first type of identifier is related to a beam carrying a side synchronization signal block.

22. 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, wherein the first sideline synchronization signal block is configured for a first operation, and / or the first sideline synchronization signal block carries a first type of identifier, and / or the first sideline synchronization signal block occupies a first type of resource; a first processor for selecting a synchronization reference in accordance with a first priority group order; Among them, the first operation includes at least one of initial beam pairing, side unicast link establishment and side beam management; the first priority group order is related to the first operation and / or the side synchronization signal block carrying the first type of identifier and / or the side synchronization signal block occupying the first type of resources.

23. The first node according to claim 22, characterized in that The first priority group order is the order of multiple candidate priority groups; the multiple candidate priority groups include a target priority group, and the sending node of the first side synchronization signal block corresponds to the target priority group.

24. The first node according to claim 23, characterized in that The target priority group is a first candidate priority group among the plurality of candidate priority groups.

25. The first node according to claim 23, characterized in that The multiple candidate priority groups include a first reference priority group; the index of the target priority group is the difference between the index of the first reference priority group and the priority group offset, or the index of the target priority group is the maximum value of the difference between the index of the first reference priority group and the priority group offset and 1; at least two of the sideline synchronization signal identifier carried by the first sideline synchronization signal block, the in-coverage indication and the time-frequency resources occupied by the first sideline synchronization signal block are used together to determine the first reference priority group, and the first sideline synchronization signal block is used to determine the priority group offset.

26. The first node according to any one of claims 22-25, characterized in that: The multiple sideline synchronization signal blocks including the first sideline synchronization signal block also include a second sideline synchronization signal block, the first sideline synchronization signal block is configured for the first operation, and the second sideline synchronization signal block is not configured for the first operation; or, the first sideline synchronization signal block carries the first type of identifier, and the second sideline synchronization signal block does not carry the first type of identifier; or, 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.

27. The first node according to any one of claims 22-26, characterized in that: The first priority group order is the order of multiple candidate priority groups, and the multiple candidate priority groups include a first priority group and a second priority group; the sending node of the first side synchronization signal block corresponds to one of the first priority group and the second priority group.

28. The first node according to claim 27, characterized in that The first priority group corresponds to user equipment that selects a cell as a synchronization reference, or the first priority group corresponds to user equipment that selects a first type of user equipment as a synchronization reference, and the first type of user equipment selects a cell as a synchronization reference; the second priority group corresponds to user equipment that selects a global navigation satellite system GNSS as a synchronization reference, or the second priority group corresponds to user equipment that selects a second type of user equipment as a synchronization reference, and the second type of user equipment selects GNSS as a synchronization reference.

29. The first node according to claim 27 or 28, characterized in that: The position of the first priority group in the multiple candidate priority groups is before the position of the second priority group in the multiple candidate priority groups, or the position of the first priority group in the multiple candidate priority groups is after the position of the second priority group in the multiple candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

30. The first node according to any one of claims 22-29, characterized in that: include: a second processor, configured to measure one or more physical sideline broadcast channels; The one or more sideline synchronization signal blocks respectively include the one or more physical sideline broadcast channels, and the one or more measurement results for the one or more physical sideline broadcast channels include the measurement results for the first physical sideline broadcast channel, and the measurement results for the first physical sideline broadcast channel are used to determine whether the sending node of the first sideline synchronization signal block is selected as the synchronization reference.

31. According to the first node according to claim 30, the multiple side synchronization signal blocks including the first side synchronization signal block also include a second side synchronization signal block, and the second side synchronization signal block includes a second physical side broadcast channel; the one or more measurement results for the one or more physical side broadcast channels include the measurement results for the second physical side broadcast channel; whether the second side synchronization signal block is configured for the first operation, whether the second side synchronization signal block carries the first type of identifier and whether the second side synchronization signal block occupies the first type of resources, and the size relationship between the measurement results for the first physical side broadcast channel and the measurement results for the second physical side broadcast channel are used to determine whether the sending node of the first side synchronization signal block is selected as the synchronization reference.

32. The first node according to claim 30, characterized in that The sum of the measurement result and the measurement result offset for the first physical sideline broadcast channel is used to determine whether the sending node of the first sideline synchronization signal block is selected as a synchronization reference; The first sideline synchronization signal block is used to determine the measurement result offset.

33. The first node according to any one of claims 22 to 32, characterized in that: The first type of identifier is related to a sending node of a side synchronization signal block, or the first type of identifier is related to a receiving node of a side synchronization signal block, or the first type of identifier is related to a beam carrying a side synchronization signal block.

34. A second node for wireless communication, characterized in that: include: A first transmitter is used to send a first sideline synchronization signal block, where the first sideline synchronization signal block is configured for a first operation, and / or the first sideline synchronization signal block carries a first type of identifier, and / or the first sideline synchronization signal block occupies a first type of resource; The first operation includes at least one of initial beam pairing, side unicast link establishment and side beam management; The receiving node of the first side synchronization signal block selects a synchronization reference according to a first priority group order; the first priority group order is related to the first operation and / or the side synchronization signal block carrying the first type of identifier and / or the side synchronization signal block occupying the first type of resources.

35. The second node according to claim 34, characterized in that: The first priority group order is the order of multiple candidate priority groups; the multiple candidate priority groups include a target priority group, and the second node corresponds to the target priority group.

36. The second node according to claim 35, characterized in that: The target priority group is a first candidate priority group among the plurality of candidate priority groups.

37. The second node according to claim 35, characterized in that: The multiple candidate priority groups include a first reference priority group; the index of the target priority group is the difference between the index of the first reference priority group and the priority group offset, or the index of the target priority group is the maximum value of the difference between the index of the first reference priority group and the priority group offset and 1; at least two of the sideline synchronization signal identifier carried by the first sideline synchronization signal block, the in-coverage indication and the time-frequency resources occupied by the first sideline synchronization signal block are used together to determine the first reference priority group, and the first sideline synchronization signal block is used to determine the priority group offset.

38. The second node according to any one of claims 34-37, characterized in that: The multiple sideline synchronization signal blocks received by the receiving node of the first sideline synchronization signal block also include a second sideline synchronization signal block, the first sideline synchronization signal block is configured for the first operation, and the second sideline synchronization signal block is not configured for the first operation; or, the first sideline synchronization signal block carries the first type of identifier, and the second sideline synchronization signal block does not carry the first type of identifier; or, 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 second node is preferentially selected as the synchronization reference over the sending node of the second sideline synchronization signal block.

39. The second node according to any one of claims 34-38, characterized in that: The first priority group order is the order of multiple candidate priority groups, and the multiple candidate priority groups include a first priority group and a second priority group; the sending node of the first side synchronization signal block corresponds to one of the first priority group and the second priority group.

40. The second node according to claim 39, characterized in that: The first priority group corresponds to user equipment that selects a cell as a synchronization reference, or the first priority group corresponds to user equipment that selects a first type of user equipment as a synchronization reference, and the first type of user equipment selects a cell as a synchronization reference; the second priority group corresponds to user equipment that selects a global navigation satellite system GNSS as a synchronization reference, or the second priority group corresponds to user equipment that selects a second type of user equipment as a synchronization reference, and the second type of user equipment selects GNSS as a synchronization reference.

41. The second node according to claim 39 or 40, characterized in that: The position of the first priority group in the multiple candidate priority groups is before the position of the second priority group in the multiple candidate priority groups, or the position of the first priority group in the multiple candidate priority groups is after the position of the second priority group in the multiple candidate priority groups, or a first parameter is used to determine the order of the first priority group and the second priority group.

42. The second node according to any one of claims 34 to 41, characterized in that: The first type of identifier is related to a sending node of a side synchronization signal block, or the first type of identifier is related to a receiving node of a side synchronization signal block, or the first type of identifier is related to a beam carrying a side synchronization signal block.

43. 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-21.

44. 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-21.

45. 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-21.

46. ​​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-21.

47. 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 21.

48. 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-21.

Images