Method and apparatus in a node for wireless communication

Abstract

The invention provides a method and an apparatus in a node for wireless communication. The method comprises: receiving one or more sideline synchronization signal blocks, the one or more sideline synchronization signal blocks comprising a first sideline synchronization signal block; determining whether a sending node of the first side row synchronization signal block is selected as a synchronization reference according to a target priority group sequence, wherein the target priority group sequence is one of a first priority group sequence and a second priority group sequence; wherein at least one of whether the first side row synchronization signal block is configured for a first operation, whether the first side row synchronization signal block carries a first type identifier, and whether the first side row synchronization signal block occupies a first type resource is used for determining the target priority group sequence; the first operation comprises at least one of initial beam pairing, sideward unicast link establishment and sideward beam management.

Description

[0001] This application is a divisional application of the case with application number 202380011750.6, application date September 18, 2023, and invention name “Method and device in a node for wireless communication”. Technical Field

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

[0003] 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 for initial beam pairing can be used 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. Summary of the invention

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

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

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

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

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

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

[0010] In a 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, which includes 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, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute some or all of the steps in the above-mentioned various aspects of the method. In some implementations, the computer program product can 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 including the first side synchronization signal block, the priority group corresponding to the first side synchronization signal block can be determined according to at least one of whether the first side synchronization signal block is configured with the first operation, whether it carries the first type of identification, and whether it occupies the first type of resources. The first type of identification and the first type of resources are related to the first operation, and the first operation includes at least one of initial beam pairing, side unicast link establishment, and beam management. Determining the priority of the sending node according to whether the first side synchronization signal block is used for the first operation helps to achieve effective initial beam pairing before the side unicast link is established.

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

[0017] In the embodiment of the present application, any two nodes in the sideline communication perform initial beam pairing before the sideline unicast link is established. Using paired beams to establish a unicast link can expand the link range between the sending node and the receiving node, so that more nodes can 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] Figure 1 This is an example diagram of the system architecture of a wireless communication system applicable to the embodiments of the present application.

[0020] Figure 2 A schematic diagram of the time slot structure of the sideline synchronization signal block.

[0021] Figure 3 Schematic diagram of the distribution of multiple S-SSBs in one cycle.

[0022] Figure 4 A flowchart of a method in a first node for wireless communication provided in an embodiment of the present application.

[0023] Figure 5 The figure is a flowchart of an implementation method of initial beam pairing in the first operation.

[0024] Figure 6 FIG. 4 is a flow chart of another implementation method of initial beam pairing in the first operation.

[0025] Figure 7 A flowchart of an implementation method for establishing a side unicast link in the first operation.

[0026] Figure 8 for Figure 4 A flowchart of a possible implementation of the method shown.

[0027] Fig. 9 for Figure 4 A flowchart of another possible implementation of the method is shown.

[0028] Fig.10 as a basis Fig. 9 The result of step S930 is a flowchart of a method for selecting a synchronization reference.

[0029] Fig.11 A schematic diagram of the structure of a first node for wireless communication provided in an embodiment of the present application.

[0030] Fig.12 A schematic diagram of the structure of a second node for wireless communication provided in an embodiment of the present application.

[0031] Fig.13 A schematic structural diagram of a device provided in an embodiment of the present application.

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

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

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

[0035] In some implementations, user equipment (UE) and user equipment may communicate 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 equipment and user equipment 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] Combined with the following Figure 1 This section introduces several common sidelink communication scenarios. In sidelink communication, three scenarios can be divided according to whether the user equipment in the sidelink is within the coverage of the network device. Scenario 1: The user equipment performs sidelink communication within the coverage of the network device. Scenario 2: Some user equipment performs sidelink communication within the coverage of the network device. Scenario 3: The user equipment performs sidelink communication outside the coverage of the network device.

[0038] like Figure 1 As shown, in scenario 1, user equipments 121-122 can communicate via a side link, 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 a side link based on the configuration signaling.

[0039] like Figure 1 As shown, in scenario 2, user equipment 123-124 can communicate via the side link, and user equipment 123 is within the coverage of network device 110, and user equipment 124 is outside the coverage of network device 110. In this scenario, user equipment 123 receives the configuration information of network device 110 and communicates via the side link based on the configuration of the configuration signaling. However, for user equipment 124, since user equipment 124 is outside the coverage of network device 110, it is unable to receive the configuration information of network device 110. At this time, user equipment 124 can obtain the configuration of the side link communication according to the pre-configuration configuration information and / or the configuration information sent by user equipment 123 within the coverage, so as to communicate with user equipment 123 via the side link based on the acquired configuration.

[0040] In some cases, the user equipment 123 may send the above 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] like Figure 1 As shown, 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, user equipments can all perform sidelink communication based on preconfigured information.

[0042] In some cases, user devices 127-129 located outside the coverage 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, the user device 127 in the communication group can serve as a central control node, also known as a cluster header (CH), and correspondingly, the user devices in other communication groups can be called "group members".

[0043] It should be noted that Figure 1 A network device and multiple user devices are shown exemplarily. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include another number of user devices within its coverage area, which is not limited in the embodiments of the present application.

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

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

[0046] The user equipment in the embodiment of the present application may also be referred to as terminal equipment, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or 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 handheld devices with wireless connection functions, vehicle-mounted devices, 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 smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the user equipment may act as a base station. For example, the user equipment can act as a dispatching entity that provides sidelink signals between user equipment in vehicle-to-everything (V2X) or D2D, etc. For example, a cell phone and a car communicate with each other using sidelink data. A cell phone and a smart home device communicate with each other without relaying the communication signal through a base station.

[0047] The network device in the embodiment of the present application may be a device for communicating with a user device, and the network device may also be referred to as an access network device or a radio access network device, such as a base station. The network device in the embodiment of the present application may refer to a radio access network (RAN) node (or device) that connects a user device to a wireless network. Base station can broadly cover various names as follows, or replace with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), access point (access point, AP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, a modem or a chip 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 the base station function in D2D, V2X, machine-to-machine (M2M) communication, a network side device in a 6G network, and a device that performs the base station function in a future communication system. The base station can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted 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; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present 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 the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

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

[0053] It should be understood that the interpretation of the terms 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, System Architecture 2 (SA2) is specifically researching and standardizing 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, Radio Access Network Working Group 1 (RAN1) and RAN2 have developed power saving technologies (such as partial sensing, discontinuous reception (DRX) and Inter-UE coordination (IUC) 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] As the application areas of sidelink communication continue to expand, higher requirements are placed on NR SL. These requirements include two key needs: increasing the sidelink data rate and supporting more new carriers on the sidelink. By adding more new carriers, the transmission bandwidth can be expanded, thereby further increasing the data rate.

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

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

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

[0060] Alternative process 2: performing initial beam pairing during the establishment of the sidelink unicast link 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 more UEs can establish sidelink unicast links, 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 a 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 a sidelink synchronization signal block (sidelink-synchronization signal block, S-SSB). That is to say, the S-SSB in this article can represent a sidelink synchronization broadcast signal block or a 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 by beam sweeping.

[0065] UE2 performs reference signal received power (RSRP) measurement on a sideline synchronization signal (SL synchronization signal, SLSS) and / or PSBCH, and UE2 determines a transmit beam of UE1 and a receive beam of UE2 according to 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. Usually, 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 will not only increase resource consumption, but also seriously affect the available resources of other physical SL channels / signals.

[0069] For ease of understanding, the following Figure 2 The structure of a time slot of S-SSB is exemplified. Figure 2 In one time slot of S-SSB, there are S-PSS and S-SSS, which occupy two symbols respectively, PSBCH and the last guard symbol. Figure 2 In the structure shown, 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 protection symbol, and the other symbols are used to carry PSBCH.

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

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

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

[0073] Table 1

[0074]

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

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

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

[0078] Traditional NRSL synchronization priority design

[0079] NR SL has two major synchronization reference sources, namely the Global Navigation Satellite System (GNSS) and base stations (including gNB / eNB). In addition, the UE can also select a synchronization reference UE (SyncRefUE) as its synchronization reference source. The UE selects or reselects a 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.

[0080] Table 2

[0081]

[0082] In Table 2, SLSSID is the sidelink synchronization signal identity; InC is the in-coverage indication (InCoverage) in the sidelink master system information block (Master Information Block Sidelink, 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 in 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 in network coverage, or the UE selects GNSS timing as its synchronization reference source.

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

[0084] As mentioned above, the new NR SL system (such as Rel-18 / 19) will introduce a process for performing initial beam pairing before the sidelink unicast link is established, and S-SSB has become an alternative solution as a reference signal for initial beam pairing. In some scenarios, in order to facilitate UE2 to identify UE1 that sends the S-SSB from multiple UEs, UE1 needs to indicate at least one of its user identification (UE ID) information (or source identification), transmission beam information, and receiving user identification (or destination identification) by sending an enhanced S-SSB (enhanced S-SSB, eS-SSB). When the UE 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 through traditional NR SL synchronization priority rules.

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

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

[0087] Based on this, an embodiment of the present application proposes a method in a first node for wireless communication. Through this method, when the first node receives one or more side synchronization signal blocks including a first side synchronization signal block, it can first select the target priority group order corresponding to the sending node in the two priority group orders according to the first side synchronization signal block, and then determine whether the sending node is selected as a synchronization reference. Among them, the basis for selecting the target priority group order includes whether the first side synchronization signal block is related to the first operation such as initial beam pairing, side unicast link establishment, beam management, or the first type of identification, the first type of resources. That is, the present application introduces a new synchronization priority group order to determine the synchronization priority group order to which the sending UE of the S-SSB / eS-SSB belongs according to the purpose of the side synchronization signal block.

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

[0089] It should be noted that the beam mentioned in the embodiment 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 embodiment of the present application does not distinguish between them.

[0090] The method embodiments of the present application are described in detail below with reference to the accompanying drawings. Figure 4 A schematic flow chart of a method in a first node for wireless communication provided in an embodiment of the present application. Figure 4 The method shown includes step S410 and step S420. It should be understood that Figure 4 The illustrated method may be performed by a first node.

[0091] In some implementations, the first node may be any user device for side-by-side communication as described above. For example, the first node may be a vehicle in V2X or a basic communication facility in V2X. In some implementations, the first node may be located within or outside the network coverage. When located within the network coverage, the first node may perform side-by-side communication based on the configuration of the network device.

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

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

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

[0095] See also Figure 4 , in step S410, one or more sideline synchronization signal blocks are received.

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

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

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

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

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

[0101] The one or more side synchronization signal blocks include a first side synchronization signal block, which can be replaced by the first side synchronization signal block being any side synchronization signal block among the one or more side synchronization signal blocks received by the first node. It can also be said that the receiving node of the first side synchronization signal block includes the first node. For simplicity, S-SSB is used hereinafter to represent the side synchronization signal block. Therefore, the first side synchronization signal block can be expressed as a first S-SSB.

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

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

[0104] The sending node of the first S-SSB is the second node. The second node is any node that can interact with the first node, and can also be any node that wants to communicate with the first node.

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

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

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

[0108] The first S-SSB may be any of the S-SSBs mentioned above. Exemplarily, the first S-SSB may be a traditional S-SSB or a new S-SSB. Exemplarily, the first S-SSB may be an eS-SSB or may not be an eS-SSB. Exemplarily, the first S-SSB may or may not use a modified format.

[0109] Exemplarily, the eS-SSB (or the new S-SSB) is configured for the first operation, and / or the eS-SSB carries the first type of identifier, and / or the first type of resource is used for the eS-SSB. The first operation includes at least one of initial beam pairing, side unicast link establishment, and side beam management. Figures 5 to 7 An exemplary description is given.

[0110] In some embodiments, the first operation includes initial beam pairing, and the initial beam pairing is side-by-side initial beam pairing. When the first S-SSB is configured for side-by-side initial beam pairing, the first node may match the transmit beam and the receive beam with the transmit node of the first S-SSB to determine the best beam pair.

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

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

[0113] For ease of understanding, the following Figure 5 The initial beam pairing process including coarse pairing and fine pairing is exemplified. Figure 5 As shown, the side-row receiving beam of UE1 and the side-row transmitting beam of UE2 are initially beam-paired.

[0114] See also Figure 5 In step S510, a rough pairing is completed between UE2 transmitting beam A and UE1 receiving beam 2.

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

[0116] Subsequently, UE1 selects a narrow beam as a receiving beam for UE2's transmitting beam A according to the measurement result.

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

[0118] For ease of understanding, the following Figure 6 The initial beam pairing process including the rough pairing is exemplified. Figure 6 As shown, the side transmission beam of UE1 and the side reception beam of UE2 are initially paired. Figure 6 UE1 transmits 4 beams by beam scanning. UE2 measures UE1's 4 transmit beams respectively by using 2 receive beams. UE2 determines the matching UE1 transmit beam and UE2 receive beam based on the measurement results and notifies UE1.

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

[0120] For ease of understanding, the following Figure 7 Taking UE1 and UE2 in FIG. 1 as an example, a process of implementing a side unicast link establishment is illustrated.

[0121] See also Figure 7 In step S710, UE1 sends a DCR to UE2. UE1 requests UE2 to establish a side unicast link through the DCR.

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

[0123] As an embodiment, the side 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 side unicast link establishment process may be considered to include performing the initial beam pairing.

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

[0125] 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 described above, side beam management includes processes such as initial beam pairing, beam maintenance, and beam failure recovery. The multiple processes in side beam management can enable the first node to perform stable side beam communication within a larger link range. Among them, processes such as beam maintenance and beam failure recovery can refer to the implementation process of other communication systems (for example, NR), and the relevant processes can also be improved according to the characteristics of the side communication system.

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

[0127] In some embodiments, the first S-SSB may be configured for multiple operations. For example, the first S-SSB may be used for the first operation and also for the conventional operation. For example, when the first S-SSB is used for the first operation, it is also used for side synchronization. For another example, when the first S-SSB is used for the first operation, it is also used for side communication or side discovery.

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

[0129] For the first operation, the S-SSB carrying the first type of identification or occupying the first type of resources can also be used to indicate that the S-SSB is used for the first operation. That is to say, the S-SSB is configured for the first operation, the S-SSB carries the first type of identification, and the S-SSB occupies the first type of resources. For example, the first S-SSB is configured for the first operation, the first S-SSB carries the first type of identification, and the first S-SSB occupies the first type of resources. The three expressions can be interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0145] In some embodiments, the first type of identifier is related to a sending node of the S-SSB, or the first type of identifier is related to a receiving node of the S-SSB, or the first type of identifier is related to a beam transmitting the S-SSB.

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

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

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

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

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

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

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

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

[0154] As an embodiment, the first type of identifier carried by the first side synchronization signal block is used to identify the target receiving node of the first side synchronization signal block. For example, the first type of identifier carried by the first S-SSB can identify the first node. For another example, the first type of identifier is a destination identifier, and the first S-SSB carries the destination identifier to indicate that the receiving node includes the first node corresponding to the destination identifier.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0181] Exemplarily, the first category of resources and the second category of resources have different time domain locations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0199] In some embodiments, the multiple S-SSBs received by the first node may also include a second S-SSB. The second S-SSB may be any S-SSB among the multiple S-SSBs except the first S-SSB. The second S-SSB is different from the first S-SSB. For example, the first S-SSB is configured for the first operation, and the second S-SSB is not configured for the first operation. For another example, the first S-SSB carries a first type of identifier, and the second S-SSB does not carry the first type of identifier. For another example, the first S-SSB occupies the first type of resources, and the second S-SSB does not occupy the first type of resources.

[0200] Continue to see Figure 4 In step S420, it is determined whether the sending node of the first S-SSB is selected as the synchronization reference according to the target priority group order. That is, the first node selects the synchronization reference according to the target priority group order.

[0201] The first node selects a synchronization reference means that the first node selects a reference source for side synchronization from 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 can determine the synchronization reference source according to a certain synchronization priority rule.

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

[0203] In order to facilitate improving (or adjusting) the priority of sending nodes with specific needs, the embodiments of the present application use different priority group orders (also called priority group sorting) to respectively determine the priorities corresponding to sending nodes of different types of S-SSBs. When there are multiple priority group orders, the first node can determine the priority group order corresponding to the first S-SSB sending node based on the relevant information of the received first S-SSB, that is, the target priority group order. In other words, after receiving the first S-SSB, the first node can determine the target priority group order corresponding to the sending node of the first S-SSB, and then determine whether the sending node of the first S-SSB is selected as a priority reference based on the target priority group order.

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

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

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

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

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

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

[0210] Exemplarily, the first node selects a target priority group order from multiple priority group orders according to the first S-SSB. For the sake of brevity, the following text will take two priority group orders as an example for introduction. When the two priority group orders are the first priority group order and the second priority group order, the target priority group order is one of the first priority group order and the second priority group order.

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

[0212] In some embodiments, when the first S-SSB is configured for the first operation, the first S-SSB carries the first type of identifier, and the first S-SSB occupies at least one of the first type of resources, the target priority group order is the first priority group order; when the first S-SSB is not configured for the first operation, the first S-SSB does not carry the first type of identifier, and the first S-SSB does not occupy at least one of the first type of resources, the target priority group order is the second priority group order.

[0213] For ease of understanding, the following Figure 8 The flowchart shown is provided for exemplary purposes. Figure 8 The method shown is executed by a first node. Figure 8 Shown is a method for the first node to determine the order of target priority groups after receiving the first S-SSB.

[0214] See also Figure 8 In step S810, after receiving the first S-SSB, the first node needs to identify the purpose or related information of the first S-SSB. The first node needs to determine whether the first S-SSB is configured for the first operation, or whether it carries the first type of identification, or whether it occupies the first type of resources. If the first S-SSB is at least one of the three, execute step S820; if not, execute step S830.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0257] gNB / eNB, or GNSS;

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

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

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

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

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

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

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

[0265] gNB / eNB, or GNSS;

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

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

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

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

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

[0271] It should be noted that the S-SSB sent by UE(s) in multiple first-class priority groups carries the first-class identifier or occupies the first-class resources. Conversely, the S-SSB sent by UE(s) in multiple second-class priority groups does not carry the first-class identifier and does not occupy the first-class resources.

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

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

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

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

[0276] gNB / eNB, or GNSS;

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

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

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

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

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

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

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

[0284] gNB / eNB, or GNSS;

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

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

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

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

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

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

[0291] gNB / eNB, or GNSS;

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

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

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

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

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

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

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

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

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

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

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

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

[0304] In some embodiments, the position of the first priority group among the multiple first 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 first priority groups is after the position of the second priority group among the multiple candidate priority groups, or, a first parameter is used to determine the order of the first priority group and the second priority group.

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

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

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

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

[0309] In some embodiments, the first priority group order and the multiple first-class priority groups therein are related to at least one of the first operation, the first-class identification and the first-class resources mentioned above; conversely, the second priority group order and the multiple second-class priority groups therein are not related to at least one of the first operation, the first-class identification and the first-class resources mentioned above.

[0310] As an embodiment, the first priority group order and the second priority group order are: GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; the remaining UE(s) excluding the above UEs are arranged in sequence of seven candidate priority groups; however, the identifiers carried by the UE(s) or the occupied resources in the first priority group order and the second priority group order are different.

[0311] As an embodiment, the first priority group order and the second priority group order are: gNB / eNB; UE(s) directly synchronized to gNB / eNB; UE(s) indirectly synchronized to gNB / eNB; GNSS; UE(s) directly synchronized to GNSS; UE(s) indirectly synchronized to GNSS; the remaining UE(s) excluding the above UEs are arranged in sequence of seven candidate priority groups; however, the identifiers carried by the UE(s) or the occupied resources in the first priority group order and the second priority group order are different.

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

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

[0314] SLSSID = 0, Destination ID = xx, SLSS is not transmitted in the time slot indicated by sl-SSB-TimeAllocation3, and

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

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

[0317] gNB / eNB;

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

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

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

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

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

[0323] UE(s) transmitting on;

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

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

[0326] gNB / eNB;

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

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

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

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

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

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

[0333] GNSS;

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

[0335] SLSSID = 0, Destination ID = xx, SLSS is not transmitted in the time slot indicated by sl-SSB-TimeAllocation3, and

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

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

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

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

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

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

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

[0343] gNB / eNB;

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

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

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

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

[0348] Table 3

[0349]

[0350]

[0351] The above describes the differences between the first priority group order and the second priority group order and the plurality of priority groups thereof. The first priority group order and the second priority group order are respectively used to prioritize different sending nodes so that the first node can select a synchronization reference.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0378] In order to select the synchronization reference more efficiently, the first node may also determine whether one or more transmitting nodes are selected as the synchronization reference according to the result of measuring one or more S-SSBs. For example, the first S-SSB is measured, and the measurement result of the first S-SSB is used to determine whether the second node is selected as the synchronization reference.

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

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

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

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

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

[0384] As an embodiment, if the result of the first signal measurement is less than the target threshold, the sending node of the first S-SSB is not selected as a synchronization reference. In other words, a part of the nodes as synchronization reference sources can be excluded according to the measurement result to improve communication efficiency.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0398] Fig. 9 It is written from the perspective of the interaction between the first node and the second node. Fig. 9 In step S910, the second node receives first information. The first information may indicate how the second node sends a first S-SSB.

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

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

[0401] Fig.10 The method shown is executed by a first node. Fig.10 The method shown is a flow chart of a possible implementation manner of making a judgment according to the measurement result after the first node executes step S930.

[0402] See also Fig.10 In step S1010, it is determined whether the result of the first signal measurement is greater than the target threshold. If yes, step S1020 is executed; if not, step S1030 is executed.

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

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

[0405] Combination of the above Figures 1 to 10 , describes the method embodiment of the present application in detail, and the following is combined with Figures 11 to 14 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0433] As an embodiment, the first transmitter 1210 may be a transceiver 1330. The second node 1100 may also include a processor 1310 and a memory 1320. Fig.13 shown.

[0434] Fig.13 It is a schematic structural diagram of a communication device according to an embodiment of the present application. Fig.13 The dotted line in the figure indicates that the unit or module is optional. The device 1300 can be used to implement the method described in the above method embodiment. The device 1300 can be a chip, a user equipment or a network device.

[0435] 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 method embodiment above. 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 also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0436] The apparatus 1300 may further include one or more memories 1320. The memory 1320 stores a program, which can be executed by the processor 1310, so that the processor 1310 executes the method described in the above method embodiment. The memory 1320 may be independent of the processor 1310 or integrated in the processor 1310.

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

[0438] Fig.14 A schematic diagram of the hardware modules of a communication device provided in an embodiment of the present application. Specifically, Fig.14 A block diagram is shown of a first communication device 1450 and a second communication device 1410 communicating with each other in an access network.

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

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

[0441] In the transmission from the second communication device 1410 to the first communication device 1450, at the second communication device 1410, the upper layer data packets from the core network or the upper layer data packets from the data source 1477 are provided to the controller / processor 1475. The core network and the data source 1477 represent all the protocol layers above the L2 layer. The controller / processor 1475 implements the functionality of the L2 layer. In the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and allocation of radio resources to the first communication device 1450 based on various priority metrics. The controller / processor 1475 is also responsible for the retransmission of lost packets and signaling to the first communication device 1450. The transmit processor 1416 and the multi-antenna transmit processor 1471 implement various signal processing functions for the 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, M quadrature amplitude modulation). The multi-antenna transmit processor 1471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing 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 with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform to generate a physical channel carrying a time domain multi-carrier symbol stream. The multi-antenna transmit processor 1471 then performs a transmit analog precoding / beamforming operation on the time domain multi-carrier symbol stream. Each transmitter 1418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 1471 into a radio frequency stream, and then provides it to a different antenna 1420 .

[0442] In the transmission from the second communication device 1410 to the first communication device 1450, at the first communication device 1450, each receiver 1454 receives a signal through its corresponding antenna 1452. Each receiver 1454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 1456. The receiving processor 1456 and the multi-antenna receiving processor 1458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 1458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 1454. The receiving processor 1456 uses a fast Fourier transform to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 1456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 1458 to any spatial stream with the first communication device 1450 as the destination. The symbols on each spatial stream are demodulated and recovered in the receiving processor 1456, and soft decisions are generated. The receiving 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. In the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, 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 for L3 processing.

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

[0444] In the transmission from the first communication device 1450 to the second communication device 1410, the function at the second communication device 1410 is similar to the reception function at the first communication device 1450 described in the transmission from the second communication device 1410 to the first communication device 1450. Each receiver 1418 receives a radio frequency signal through its corresponding antenna 1420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to a multi-antenna reception processor 1472 and a reception processor 1470. The reception processor 1470 and the multi-antenna reception processor 1472 jointly implement the functions of the L1 layer. The controller / processor 1475 implements the L2 layer functions. 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. In transmission from the first communication device 1450 to the second communication device 1410, the controller / processor 1475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the first communication 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.

[0445] As an embodiment, the first communication device 1450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 1450 apparatus at least: receives one or more sideline synchronization signal blocks, the one or more sideline synchronization signal blocks including a first sideline synchronization signal block; determines whether the sending node of the first sideline synchronization signal block is selected as a synchronization reference according to a target priority group order, the target priority group order is one of a first priority group order and a second priority group order; wherein at least one of whether the first sideline synchronization signal block is configured for a first operation, whether the first sideline synchronization signal block carries a first type of identifier, and whether the first sideline synchronization signal block occupies a first type of resource is used to determine the target priority group order; the first operation includes at least one of initial beam pairing, sideline unicast link establishment, and sideline beam management.

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

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

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

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

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

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

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

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

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

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

[0456] 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 the present application.

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

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

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

[0460] 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 the present application, and are not intended to limit the present 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 of their variations are intended to cover non-exclusive inclusions.

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

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

[0463] In the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

[0464] In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a user device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0465] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication 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.

[0466] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. 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 article generally indicates that the associated objects before and after are in an "or" relationship.

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

[0468] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.

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

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

[0471] 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 may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may 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 may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0472] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

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

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

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

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

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

6. A method in a second node for wireless communication, characterized in that: include: Sending a first sideline synchronization signal block; At least one of whether the first sideline synchronization signal block is configured for the first operation, whether the first sideline synchronization signal block carries the first type of identifier, and whether the first sideline synchronization signal block occupies the first type of resources is used by the receiving node of the first sideline synchronization signal block to determine the target priority group order; The target priority group order is used to determine whether the second node is selected by the receiving node as a synchronization reference; the target priority group order is one of a first priority group order and a second priority group order.

7. A method in a first node for wireless communication, characterized in that: include: receiving one or more sideline synchronization signal blocks, wherein the one or more sideline synchronization signal blocks include a first sideline synchronization signal block; Performing a first signal measurement on the first sideline synchronization signal block; The relationship between the result of the first signal measurement and the target threshold is used to determine whether the sending node of the first side synchronization signal block is selected as the synchronization reference.

8. A method in a second node for wireless communication, characterized in that: include: Sending a first sideline synchronization signal block; The first side synchronization signal block is used to perform a first signal measurement, and the relationship between the result of the first signal measurement and the target threshold is used to determine whether the second node is selected as a synchronization reference.

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

10. A second node for wireless communication, characterized in that: include: A first transmitter, configured to send a first sideline synchronization signal block; At least one of whether the first sideline synchronization signal block is configured for the first operation, whether the first sideline synchronization signal block carries the first type of identifier, and whether the first sideline synchronization signal block occupies the first type of resources is used by the receiving node of the first sideline synchronization signal block to determine the target priority group order; The target priority group order is used to determine whether the second node is selected by the receiving node as a synchronization reference; the target priority group order is one of a first priority group order and a second priority group order.

Images