Resource configuration method and device, communication equipment, chip and storage medium

Abstract

The embodiment of the invention provides a resource configuration method and device, communication equipment, a chip and a storage medium, and the method comprises the steps that a terminal obtains first configuration information, and the first configuration information is used for determining a first type of S-SSB synchronization resources and a second type of S-SSB synchronization resources; wherein the first type of S-SSB synchronization resources correspond to a first type of terminals, the second type of S-SSB synchronization resources correspond to a second type of terminals, and the capability of the first type of terminals is higher than that of the second type of terminals.

Description

Resource configuration method and device, communication equipment, chip, and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a resource configuration method, device, and terminal. Background Art

[0002] Reduced Capability (RedCap) is a new technology defined by the 3rd Generation Partnership Project (3GPP). In discussions of sidelink in unlicensed spectrum (SL-U), all terminals had the same capabilities, and reduced capability terminals were not considered. However, terminal cost and power consumption are crucial metrics for commercial deployment. The low cost and power consumption of reduced capability terminals can facilitate the commercialization of SL-U technology, so the introduction of reduced capability terminals into sidelink (SL) systems is a viable option.

[0003] Low-capability terminals have different capabilities from traditional terminals (also called full-capability terminals or strong-capability terminals). Therefore, the current sideline synchronization solution (ie, the sideline synchronization solution applicable to traditional terminals) is not applicable to low-capability terminals.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a resource configuration method and apparatus, a terminal, a chip, a computer-readable storage medium, a computer program product, and a computer program.

[0006] In a first aspect, an embodiment of the present application provides a resource configuration method, the method comprising:

[0007] The terminal obtains first configuration information, and the first configuration information is used to determine the synchronization resources of the first type of sidelink synchronization signal block (S-SSB) and the second type of S-SSB synchronization resources; wherein the first type of S-SSB synchronization resources corresponds to the first type of terminal, the second type of S-SSB synchronization resources corresponds to the second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

[0008] In a second aspect, an embodiment of the present application provides a resource configuration method, the method comprising:

[0009] The network device sends first configuration information, and the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resource corresponds to a first type of terminal, and the second type of S-SSB synchronization resource corresponds to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

[0010] In a third aspect, an embodiment of the present application provides a resource configuration device, applied to a terminal, the device comprising:

[0011] An acquisition unit is used to obtain first configuration information, where the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resource corresponds to a first type of terminal, the second type of S-SSB synchronization resource corresponds to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

[0012] In a fourth aspect, an embodiment of the present application provides a resource configuration device, applied to a network device, the device comprising:

[0013] A sending unit is used to send first configuration information, where the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resource corresponds to a first type of terminal, the second type of S-SSB synchronization resource corresponds to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

[0014] In a fifth aspect, an embodiment of the present application provides a communication device, which includes a memory and a processor; wherein the memory is used to store computer-executable instructions; the processor is connected to the memory and is used to implement the method described in any of the above aspects by executing the computer-executable instructions.

[0015] In a sixth aspect, an embodiment of the present application provides a chip, which includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method described in any of the above aspects.

[0016] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by at least one processor, it implements the method described in any of the above aspects.

[0017] In an eighth aspect, an embodiment of the present application provides a computer program product, which includes computer program instructions, and the computer program instructions enable a computer to execute the method described in any of the above aspects.

[0018] In a ninth aspect, an embodiment of the present application provides a computer program that enables a computer to execute the method described in any of the above aspects.

[0019] The technical solution of the embodiment of the present application configures a first type of S-SSB synchronization resource for a first type of terminal with higher capability through a first configuration information, and configures a second type of S-SSB synchronization resource for a second type of terminal with lower capability. In this way, by dividing the S-SSB synchronization resources into two parts for configuration, one part is used for the first type of terminal with higher capability, and the other part is used for the second type of terminal with lower capability, terminals with different capabilities can be taken into account at the same time in the sideline system, ensuring that terminals with different capabilities can achieve sideline synchronization. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] Figure 1-1 is a schematic diagram of sideline communication within the network coverage area provided by an embodiment of the present application;

[0022] Figure 1-2 is a schematic diagram of partial network coverage sideline communication provided by an embodiment of the present application;

[0023] Figures 1-3 are schematic diagrams of network coverage outside line communications provided by embodiments of the present application;

[0024] Figures 1-4 are schematic diagrams of sideline communications with a central control node provided by embodiments of the present application;

[0025] FIG2-1 is a schematic diagram of a unicast transmission method provided in an embodiment of the present application;

[0026] Figure 2-2 is a schematic diagram of a multicast transmission method provided in an embodiment of the present application;

[0027] Figure 2-3 is a schematic diagram of a broadcast transmission method provided in an embodiment of the present application;

[0028] Figure 3-1 is a schematic diagram of the NR-V2X frame structure provided in an embodiment of the present application;

[0029] Figure 3-2 is a second schematic diagram of the NR-V2X frame structure provided in an embodiment of the present application;

[0030] FIG4 is a structural diagram of an S-SSB time slot provided in an embodiment of the present application;

[0031] FIG5 is a schematic diagram of NR-V2X synchronization resources provided in an embodiment of the present application;

[0032] FIG6 is a schematic diagram of a set of synchronization resources within a synchronization period provided by an embodiment of the present application;

[0033] FIG7 is a flow chart of a resource configuration method according to an embodiment of the present application;

[0034] FIG8 is a first schematic diagram of an S-SSB time slot configured within a synchronization period provided by an embodiment of the present application;

[0035] FIG9 is a second schematic diagram of an S-SSB time slot configured within a synchronization period provided in an embodiment of the present application;

[0036] FIG10 is a third schematic diagram of an S-SSB time slot configured within a synchronization period provided in an embodiment of the present application;

[0037] FIG11 is a fourth schematic diagram of an S-SSB time slot configured within a synchronization period provided in an embodiment of the present application;

[0038] FIG12 is a schematic diagram of time-frequency domain resources of S-SSB synchronization resources provided in an embodiment of the present application;

[0039] FIG13 is a schematic diagram of the first structure of a resource configuration device provided in an embodiment of the present application;

[0040] FIG14 is a second schematic diagram of the structure of a resource configuration device provided in an embodiment of the present application;

[0041] FIG15 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0042] FIG16 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0043] Figure 17 is a schematic block diagram of a communication system provided by an embodiment of the present application. DETAILED DESCRIPTION

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

[0045] The technical solutions of the embodiments of the present application can be applied to various side communication systems (also referred to as side systems for short). To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies in the side communication system are explained below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0046] Sideline communication in different network coverage environments

[0047] In sideline communication, according to the network coverage of the communicating terminals, it can be divided into sideline communication within network coverage, sideline communication with partial network coverage, sideline communication outside network coverage, and sideline communication with a central control node, as shown in Figures 1-1, 1-2, 1-3, and 1-4 respectively.

[0048] As shown in Figure 1-1, in sideline communications within network coverage, all terminals performing sideline communications (such as terminal 1 and terminal 2 in Figure 1-1) are within the coverage range of the same base station. Therefore, the above terminals can all perform sideline communications based on the same sideline configuration by receiving configuration signaling from the base station.

[0049] As shown in Figure 1-2, in the case of partial network coverage for sidelink communication, some terminals performing sidelink communication (such as terminal 1 in Figure 1-2) are within the coverage of the base station. These terminals can receive configuration signaling from the base station and perform sidelink communication according to the configuration of the base station. However, terminals outside the network coverage (such as terminal 2 in Figure 1-2) cannot receive configuration signaling from the base station. In this case, the terminals outside the network coverage will determine the sidelink configuration based on pre-configuration information and information carried in the Physical Sidelink Broadcast Channel (PSBCH) sent by terminals within the network coverage, and perform sidelink communication.

[0050] As shown in Figure 1-3, for sideline communication outside the network coverage, all terminals performing sideline communication (such as terminal 1 and terminal 2 in Figure 1-3) are located outside the network coverage, and all terminals determine the sideline configuration according to the pre-configuration information for sideline communication.

[0051] As shown in Figure 1-4, for side communication with a central control node, multiple terminals form a communication group. The communication group has a central control node (such as terminal 1 in Figure 1-4), which can also become the cluster head terminal (Cluster Header, CH). The central control node has one of the following functions: responsible for establishing the communication group; joining and leaving the group members; coordinating resources, allocating side transmission resources to other terminals (such as terminal 2 and terminal 3 in Figure 1-4), receiving side feedback information from other terminals; coordinating resources with other communication groups, etc.

[0052] The terminal in the sideline system can be any terminal, including but not limited to a terminal that is connected to a network device and / or other terminals by wired or wireless connection. For example, the terminal can refer to an access terminal, user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network or a terminal in a future evolution network, etc.

[0053] Resource selection method in sideline communication

[0054] Device-to-device (D2D) communication is a sidelink transmission technology based on device-to-device (D2D). Unlike traditional cellular systems, where communication data is received or sent via base stations, D2D communication offers higher spectrum efficiency and lower transmission latency. Sidelink communication utilizes direct device-to-device communication, and 3GPP defines two transmission modes: Mode 1 and Mode 2.

[0055] Mode 1: The base station allocates transmission resources to the terminal, and the terminal sends data on the sidelink based on the allocated resources. The base station can allocate resources for either single transmission or semi-static transmission. As shown in Figure 1-1, when the terminal is within network coverage, the network allocates transmission resources for sidelink transmission.

[0056] Mode 2: The terminal selects a resource from the resource pool for data transmission. As shown in Figure 1-3, if the terminal is outside the cell coverage area, it autonomously selects a transmission resource from the preconfigured resource pool for sidelink transmission. Alternatively, as shown in Figure 1-1, the terminal autonomously selects a transmission resource from the network-configured resource pool for sidelink transmission.

[0057] It should be noted that in the embodiment of the present application, the first mode may also be referred to as the first resource selection mode or mode 1, and the second mode may also be referred to as the second resource selection mode or mode 2. The technical solution of the embodiment of the present application does not limit the names of the first mode and the second mode.

[0058] Transmission method in NR-V2X

[0059] In NR-V2X, autonomous driving needs to be supported, which places higher requirements on data interaction between vehicles, such as higher throughput, lower latency, higher reliability, larger coverage, and more flexible resource allocation.

[0060] LTE-V2X supports broadcast transmission, while NR-V2X introduces unicast and multicast transmission. For unicast transmission, there is only one receiving terminal. As shown in Figure 2-1, unicast transmission is carried out between Terminal 1 and Terminal 2. For multicast transmission, the receiving terminals are all terminals in a communication group or all terminals within a certain transmission distance. As shown in Figure 2-2, Terminals 1, 2, 3, and 4 form a communication group. Terminal 1 transmits data, and all other terminals in the group are receiving terminals. For broadcast transmission, the receiving terminal is any terminal in the vicinity of the transmitting terminal. As shown in Figure 2-3, Terminal 1 is the transmitting terminal, and all other terminals in the vicinity, Terminals 2 through 6, are receiving terminals.

[0061] Second-order SCI mechanism in NR-V2X

[0062] Second-order sidelink control information (SCI) is introduced in NR-V2X. The first-order SCI is carried in the physical sidelink control channel (PSCCH) and is used to indicate the transmission resources, reserved resource information, modulation and coding scheme (MCS) level, priority and other information of the physical sidelink shared channel (PSSCH). The second-order SCI is sent in the PSSCH resources and demodulated using the demodulation reference signal (DMRS) of the PSSCH. It is used to indicate the transmitter ID, receiver ID, hybrid automatic repeat reQuest (HARQ) ID, new data indicator (NDI) and other information used for data demodulation.

[0063] NR-V2X system frame structure

[0064] For example, the time slot structure in NR-V2X is shown in Figures 3-1 and 3-2. A time slot includes 14 side symbols. Each rectangular box in Figures 3-1 and 3-2 represents a side symbol, and the side symbol can be an orthogonal frequency division multiplexing (OFDM) symbol (also referred to as a symbol for short).

[0065] Figure 3-1 shows the timeslot structure without the Physical Sidelink Feedback Channel (PSFCH); Figure 3-2 shows the timeslot structure with the PSFCH. In both Figures 3-1 and 3-2, the PSCCH begins in the time domain at the second sidelink symbol of the timeslot and occupies two or three symbols. In the frequency domain, it can occupy {10, 12, 15, 20, 25} Physical Resource Blocks (PRBs). To reduce the complexity of blind PSCCH detection by terminals, only one number of PSCCH symbols and PRBs is allowed in a resource pool. Furthermore, because subchannels are the minimum granularity for PSSCH resource allocation in NR-V2X, the number of PRBs occupied by the PSCCH must be less than or equal to the number of PRBs contained in a subchannel within the resource pool to avoid additional restrictions on PSSCH resource selection or allocation. The PSSCH also begins in the time domain at the second sidelink symbol of the timeslot. The last sidelink symbol in a time slot is a guard period (GP) symbol, and the remaining symbols are mapped to the PSSCH. The first sidelink symbol in a time slot is a repetition of the second sidelink symbol. The receiver typically uses the first sidelink symbol as an automatic gain control (AGC) symbol, and the data on this symbol is not typically used for data demodulation. The PSSCH occupies K (K ≥ 1) subchannels in the frequency domain, each of which consists of N (N ≥ 1) consecutive PRBs. In Figure 3-2, the time slot contains the PSFCH. The second-to-last and third-to-last symbols in the time slot are used for PSFCH transmission, and the symbol preceding the PSFCH is used as a GP symbol.

[0066] Side synchronization

[0067] 1) Sidelink Synchronization Signal Block (S-SSB)

[0068] In the sidelink system, the terminal can use the base station or the Global Navigation Satellite System (GNSS) as the original reference synchronization source. In addition, in order to ensure that sidelink communications can proceed normally in different coverage environments, the sidelink system supports the terminal as the reference synchronization source. When the terminal serves as the reference synchronization source, the terminal needs to send the sidelink synchronization signal (SLSS) and the physical sidelink broadcast channel (PSBCH) to provide synchronization information and necessary sidelink configuration information to other terminals. In the sidelink system, SLSS and PSBCH are sent in the same time slot, which is called the S-SSB time slot. The SLSS is further divided into the sidelink primary synchronization signal (S-PSS) and the sidelink secondary synchronization signal (S-SSS). The structure of the S-SSB time slot is shown in Figure 4. It should be noted that each rectangular box in Figure 4 represents a symbol, S-PSS occupies 2 symbols, S-SSS occupies 2 symbols, the last symbol in the time slot is used as the GP symbol, and the remaining symbols are used for PSBCH transmission.

[0069] 2) Synchronize resources

[0070] After the terminal obtains synchronization information from the synchronization source, it needs to send a sidelink synchronization signal and PSBCH (i.e., S-SSB) on the sidelink to assist other terminals in obtaining synchronization information. The resources used to transmit the sidelink synchronization signal and PSBCH are called sidelink synchronization resources (referred to as synchronization resources for short).

[0071] Due to the limitation of half-duplex, when a terminal sends a signal on a carrier, it cannot receive a signal on the carrier at the same time. In order to avoid the terminal being unable to receive the side data sent by other terminals when sending the side synchronization signal, resulting in the loss of side data, in the side link transmission, the synchronization resources and the side data transmission resources are time division multiplexed (Time-Division Multiplexing, TDM), that is, S-SSB and side data are not supported in a frequency division multiplexing (FDM) manner. Specifically, when determining the resource pool for side data transmission, the time slot where the synchronization resource is located will be excluded, that is, the time slot where the synchronization resource is located will not be included in the resource pool. The time slot where the synchronization resource is located is also the S-SSB time slot.

[0072] The period of synchronization resources in the NR-V2X system (also called the synchronization period) is 160ms, and the number of time slots included in a synchronization period is 160*2^μ, where μ=0, 1, 2, 3 correspond to subcarrier spacings of 15kHz, 30kHz, 60kHz, and 120kHz, respectively. Also due to the limitation of half-duplex, the terminal needs to send and receive side synchronization signals on different time domain resources. Therefore, at least two sets of synchronization resources are configured in each synchronization period for sending or receiving S-SSBs respectively. When a carrier has GNSS as the highest priority, in order to avoid mutual interference between the S-SSBs sent by terminals within the cell and the S-SSBs sent by terminals outside the cell, an additional set of synchronization resources may be configured on the carrier, that is, the third set of synchronization resources. When a terminal located outside the network coverage and directly synchronized to the GNSS sends an S-SSB, the third set of synchronization resources will be used.

[0073] R16NR-V2X does not support beam-based sidelink transmissions. However, to improve S-SSB detection performance, each set of synchronization resources includes multiple transmission opportunities for S-SSB transmissions. If beam-based sidelink transmissions are introduced in subsequent releases, terminals can use different beams to send S-SSBs in multiple transmission opportunities.

[0074] For example, Figure 5 shows a schematic diagram of an NR-V2X synchronization resource. The synchronization period is 160ms, and two sets of synchronization resources are configured in each synchronization period, which are recorded as the first set of synchronization resources and the second set of synchronization resources. Four synchronization time slots (i.e., four S-SSB time slots or four transmission opportunities) are configured in each set of synchronization resources, and the transmitter can send S-SSBs on each of the four synchronization time slots. When the receiver detects a sideline synchronization signal on a certain synchronization time slot, based on the direct frame number (DFN) and time slot number carried in the PSBCH transmitted simultaneously with the sideline synchronization signal, the receiver can determine whether the synchronization time slot belongs to the first set of synchronization resources or the second set of synchronization resources, and then select the four synchronization time slots of the other set of synchronization resources to send S-SSBs.

[0075] For any set of synchronization resources within a synchronization period, you can determine each synchronization time slot contained in the set of synchronization resources (i.e., the time slot where the synchronization resource is located) by configuring the following three parameters:

[0076] Parameter 1: Number of synchronization slots within a period (sl-NumSSB-WithinPeriod): This parameter is used to indicate the number of synchronization slots included in a set of synchronization resources within a synchronization period. Specifically, for different subcarrier spacings in FR1 and FR2, the number of synchronization slots supported in each set of synchronization resources can be referred to in the following Table 1:

[0077] Table 1

[0078] Parameter 2: Synchronization time slot offset (sl-TimeOffsetSSB): This parameter is used to indicate the time slot offset of the first synchronization resource in each set of synchronization resources within a synchronization period relative to the synchronization period boundary;

[0079] Parameter 3: Time interval (sl-TimeInterval): This parameter is used to indicate the time slot interval between two adjacent synchronization resources in each set of synchronization resources within a synchronization cycle.

[0080] The above three parameters may be configured by the network device, agreed upon by the protocol, or predefined.

[0081] For example, Figure 6 shows a set of synchronization resources within a synchronization period. The synchronization period is 160ms. When the subcarrier spacing is 60KHz, a synchronization period includes 640 time slots. A set of synchronization resources is configured to include 4 synchronization time slots, that is, sl-NumSSB-WithinPeriod=4, the time slot offset of the first synchronization resource in a set of synchronization resources relative to the period boundary is 15 time slots, that is, sl-TimeOffsetSSB=15, and the time slot interval between two adjacent synchronization resources in a set of synchronization resources is 10 time slots, that is, sl-TimeInterval=10. It can be determined that the time slots where the four synchronization resources are located are time slots 15, 25, 35, and 45 respectively.

[0082] In current sidelink systems, it is assumed that all terminals in the system have the same capabilities, such as supporting the same bandwidth and transmit power. Therefore, the synchronization resources (including time domain resources and frequency domain resources) for sending / receiving S-SSBs are supported by all terminals. For example, if a synchronization cycle contains four synchronization slots, all terminals need to attempt to send S-SSBs in these four synchronization slots. At the same time, when detecting / receiving S-SSBs, the terminals assume that all synchronization slots have the potential for S-SSB transmissions and therefore attempt to detect / receive them.

[0083] Low-capability terminals

[0084] Low Capability (RedCap) is a 5G technology defined by 3GPP. 5G offers significant advantages over 4G in terms of communication speed, latency, and reliability, but this also increases the complexity and cost of terminal design. The high cost of terminals makes this unacceptable in many actual commercial deployment scenarios. In these scenarios, terminals have lower communication performance requirements and do not need to support 5G's most powerful features, but they have higher cost and power consumption requirements. Therefore, to achieve a balance between performance and cost and better meet the cost and power reduction needs of the Industrial Internet and the Internet of Things, 3GPP Rel-17 defined a low-capability terminal type. Low-capability terminals can reduce terminal cost and power consumption through technologies such as reduced bandwidth, fewer antennas, and lower modulation order.

[0085] 3GPP Rel-18SL is promoting the standardization of sidewalk technology deployed in unlicensed frequency bands, known as SL-U technology. SL-U technology can be deployed in commercial scenarios such as wearable smart devices, smart homes, and the Industrial Internet. In the Rel-18SL-U discussion, all terminals had the same capabilities, and low-capability terminals were not considered. However, terminal cost and power consumption are crucial metrics for commercial deployment. The low cost and power consumption offered by low-capability terminals could facilitate the commercialization of SL-U technology. Therefore, standardization of SL-U RedCap technology could be considered in Rel-19SL.

[0086] During the side synchronization process, within a synchronization cycle, the terminal needs to try to send S-SSB on all synchronization time slots. If the low-capability terminal also tries to send S-SSB in all synchronization time slots in this way, it will consume a lot of power. In addition, if the low-capability terminal and the traditional terminal (also known as a full-capability terminal or a strong-capability terminal, etc.) are configured with the same synchronization resources (such as S-SSB frequency domain resources and S-SSB time domain resources), the complexity and energy consumption of the low-capability terminal will be further increased. To this end, the following technical solutions of the embodiments of the present application are proposed.

[0087] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the objects associated before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application 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. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in devices (for example, including terminals and network devices). This application does not limit its specific implementation method. For example, predefined can refer to those defined in the protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to a standard protocol in the field of communications.

[0088] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0089] The sidewalk synchronization process is a very important link and step in the sidewalk system and occurs before the sidewalk communication. The technical solution of the embodiment of the present application divides the S-SSB synchronization resources into two parts for configuration, one part for the first type of terminals with higher capabilities and the other part for the second type of terminals with lower capabilities. This can take into account terminals with different capabilities in the sidewalk system at the same time, ensuring that terminals with different capabilities can achieve sidewalk synchronization.

[0090] It should be noted that the terminal capabilities or terminal capabilities described in the embodiments of the present application can also be described as UE capabilities.

[0091] It should be noted that the synchronization resources described in the embodiments of the present application can also be described as side synchronization resources, which refer to resources used to transmit S-SSB.

[0092] It should be noted that the synchronization time slot described in the embodiment of the present application refers to the time slot where the synchronization resource is located, that is, the S-SSB time slot, or the S-SSB transmission opportunity.

[0093] It should be noted that the low-capability terminal described in the embodiments of the present application may also be described as a weak-capability terminal or a RedCap UE.

[0094] It should be noted that the reception described in the embodiments of the present application can also be replaced by detection or monitoring in some cases.

[0095] FIG7 is a flow chart of a resource configuration method provided in an embodiment of the present application. As shown in FIG7 , the method includes some or all of the following contents:

[0096] Step 701: The terminal obtains first configuration information, which is used to determine the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources; wherein, the first type of S-SSB synchronization resources correspond to the first type of terminals, and the second type of S-SSB synchronization resources correspond to the second type of terminals, and the capability of the first type of terminals is higher than that of the second type of terminals.

[0097] In the embodiment of the present application, the terminal is a terminal in a sidewalk system. In some embodiments, the sidewalk system may be an SL-U system.

[0098] In some implementations, the terminal may be a first type terminal, which refers to a traditional terminal (also referred to as a full-capability terminal or a high-capability terminal). In other implementations, the terminal may be a second type terminal, which refers to a low-capability terminal.

[0099] In this embodiment of the present application, the capabilities of the first category of terminals are higher than those of the second category of terminals. For example, terminal capabilities include transmit / receive bandwidth, transmit power, and codec capabilities. For the second category of terminals, the lower capabilities of such terminals may be reflected in one or more of the following aspects: a relatively small transmit / receive bandwidth supported by such terminals, a relatively small transmit power supported by such terminals, or a relatively low codec capability supported by such terminals.

[0100] In the embodiments of the present application, the first type of S-SSB synchronization resource refers to a synchronization resource used by a first type of terminal to transmit / receive S-SSBs. The second type of S-SSB synchronization resource refers to a synchronization resource used by a second type of terminal to transmit / receive S-SSBs. Here, the synchronization resource includes time domain resources and / or frequency domain resources.

[0101] In an embodiment of the present application, the first type of S-SSB synchronization resource and the second type of S-SSB synchronization resource are configured through the first configuration information. In some embodiments, the first configuration information is configured by the network. In other embodiments, the first configuration information is pre-configured.

[0102] As a case where the first configuration information is a network configuration, the network device sends the first configuration information, and accordingly, the terminal receives the first configuration information sent by the network device.

[0103] In some implementations, the first configuration information is carried in RRC signaling. In other implementations, the first configuration information is carried in a system broadcast message.

[0104] Exemplarily, the first configuration information may be called sideline synchronization configuration (ie, SL-SyncConfig). Of course, the first configuration information may also have other names, which is not limited in this application.

[0105] In an embodiment of the present application, the configuration of the first type of S-SSB synchronization resource and the second type of S-SSB synchronization resource may include time domain resource configuration, and optionally, may also include frequency domain resource configuration. The following describes the configuration of these two aspects.

[0106] Time domain resource configuration

[0107] In some embodiments, the time domain resources of the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources can be configured independently or uniformly.

[0108] Solution 1: Independently configure time domain resources

[0109] In some embodiments, the first configuration information includes first time domain configuration information and second time domain configuration information, the first time domain configuration information is used to determine a first type of synchronization time slot, and the second time domain configuration information is used to determine a second type of synchronization time slot, the first type of synchronization time slot corresponds to a first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to a second type of S-SSB synchronization resource.

[0110] Here, the first type of synchronization time slot refers to the time slot where the first type of S-SSB synchronization resource is located. The first type of synchronization time slot may also be referred to as the first type of S-SSB time slot.

[0111] Here, the second type of synchronization time slot refers to the time slot where the second type of S-SSB synchronization resource is located. The second type of synchronization time slot may also be referred to as the second type of S-SSB time slot.

[0112] The first type of synchronization time slot and the second type of S-SSB time slot are independently configured through the first time domain configuration information and the second time domain configuration information.

[0113] In some implementations, the first time domain configuration information includes at least one of the following:

[0114] A first parameter, the first parameter is used to indicate a first synchronization period;

[0115] A second parameter, the second parameter is used to indicate the number of first-type synchronization time slots included in the first synchronization period;

[0116] A third parameter, the third parameter is used to indicate the time slot offset of the first first-type synchronization time slot in the first synchronization period relative to the first synchronization period boundary;

[0117] The fourth parameter is used to indicate the time slot interval between two adjacent first-type synchronization time slots in the first synchronization period.

[0118] Exemplarily, the second parameter may be the number of synchronization time slots within a period (sl-NumSSB-WithinPeriod) #1; the third parameter may be the synchronization time slot offset (sl-TimeOffsetSSB) #1; and the fourth parameter may be the time interval (sl-TimeInterval) #1.

[0119] The above-mentioned first time domain configuration information can be used to determine the time domain position of each first-type synchronization time slot in the first synchronization period, that is, the time slot position where the first-type S-SSB synchronization resource is located.

[0120] Exemplarily, for different subcarrier spacings in FR1 and FR2, the number of first-type synchronization time slots included in the first synchronization period may refer to Table 1 above.

[0121] In some implementations, the second time domain configuration information includes at least one of the following:

[0122] A fifth parameter, the fifth parameter is used to indicate a second synchronization period;

[0123] A sixth parameter, which is used to indicate the number of second-type synchronization time slots included in the second synchronization period;

[0124] A seventh parameter, the seventh parameter is used to indicate a time slot offset of the first second-type synchronization time slot in the second synchronization period relative to a boundary of the second synchronization period;

[0125] An eighth parameter is used to indicate a time slot interval between two adjacent second-type synchronization time slots in a second synchronization period.

[0126] Exemplarily, the sixth parameter may be the number of synchronization time slots within a period (sl-NumSSB-WithinPeriod) #2; the seventh parameter may be the synchronization time slot offset (sl-TimeOffsetSSB) #2; and the eighth parameter may be the time interval (sl-TimeInterval) #2.

[0127] Exemplarily, for different subcarrier spacings in FR1 and FR2, the number of second-type synchronization time slots included in the second synchronization period may be as shown in Table 2 below.

[0128] Table 2

[0129] The above-mentioned second time domain configuration information can be used to determine the time domain position of each second-type synchronization time slot in the second synchronization period, that is, the time slot position where the second-type S-SSB synchronization resource is located.

[0130] It should be noted that the various parameters configured in the first time domain configuration information and the various parameters configured in the second time domain configuration information may have the same value or different values.

[0131] In some embodiments, the first synchronization period configured by the first time domain configuration information is the same as the second synchronization period configured by the second time domain configuration information. In other embodiments, the first synchronization period configured by the first time domain configuration information is different from the second synchronization period configured by the second time domain configuration information.

[0132] Here, the first synchronization period and the second synchronization period are the same, which can be reflected in that the lengths of the first synchronization period and the second synchronization period are the same, and the starting boundaries of the first synchronization period and the second synchronization period are aligned.

[0133] Here, the first synchronization period and the second synchronization period are different, which may be reflected in that the lengths of the first synchronization period and the second synchronization period are different, and / or the starting boundaries of the first synchronization period and the second synchronization period are not aligned.

[0134] In some embodiments, the length of the first synchronization period is L times the length of the second synchronization period, where L is an integer greater than 1. The start boundary of the first synchronization period is aligned with the start boundaries of the L second synchronization periods.

[0135] Solution 2: Centrally configure time domain resources

[0136] In some embodiments, the first configuration information includes third time domain configuration information and the first information; the third time domain configuration information and the first information are used to determine a first type of synchronization time slot and a second type of synchronization time slot, the first type of synchronization time slot corresponds to a first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to a second type of S-SSB synchronization resource.

[0137] Here, the first type of synchronization time slot refers to the time slot where the first type of S-SSB synchronization resource is located. The first type of synchronization time slot may also be referred to as the first type of S-SSB time slot.

[0138] Here, the second type of synchronization time slot refers to the time slot where the second type of S-SSB synchronization resource is located. The second type of synchronization time slot may also be referred to as the second type of S-SSB time slot.

[0139] The first type of synchronization time slot and the second type of S-SSB time slot are uniformly configured through the third time domain configuration information and the first information.

[0140] In some implementations, the third time domain configuration information includes at least one of the following:

[0141] A ninth parameter, which is used to indicate a third synchronization period;

[0142] A tenth parameter, the tenth parameter is used to indicate the number of synchronization time slots included in the third synchronization period;

[0143] The eleventh parameter is used to indicate the time slot offset of the first synchronization time slot in the third synchronization period relative to the boundary of the third synchronization period;

[0144] The twelfth parameter is used to indicate the time slot interval between two adjacent synchronization time slots in the third synchronization period.

[0145] Exemplarily, the tenth parameter may be the number of synchronization time slots within a period (sl-NumSSB-WithinPeriod) #3; the eleventh parameter may be the synchronization time slot offset (sl-TimeOffsetSSB) #3; and the twelfth parameter may be the time interval (sl-TimeInterval) #3.

[0146] Exemplarily, for different subcarrier spacings in FR1 and FR2, the number of synchronization time slots included in the third synchronization period may be as shown in Table 3 below.

[0147] Table 3

[0148] The time domain position of each synchronization time slot in the third synchronization period, ie, the time slot position where the synchronization resource is located, can be determined through the third time domain configuration information.

[0149] The first type of synchronization time slot and the second type of synchronization time slot overlap

[0150] In some implementations, all synchronization time slots configured by the third time domain configuration information are first-type synchronization time slots; a first portion of synchronization time slots configured by the third time domain configuration information are second-type synchronization time slots, and the first portion of synchronization time slots are indicated by the first information.

[0151] Here, the first type of synchronization time slot is configured through the third time domain configuration information, and some of the synchronization time slots in the first type of synchronization time slot are second type of synchronization time slots, that is, some synchronization time slots belong to both the first type of synchronization time slot and the second type of synchronization time slot, and these part of the synchronization time slots are indicated by the first information.

[0152] There are several schemes for indicating the first part of synchronization time slots through the first information:

[0153] Solution 1-1: In some implementations, the first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots.

[0154] Here, by default or by agreement, the first part of synchronization time slots includes the last N synchronization time slots of all synchronization time slots; or, by default or by agreement, the first part of synchronization time slots includes the first N synchronization time slots of all synchronization time slots.

[0155] Illustratively, P synchronization time slots within a third synchronization period are configured as first-category synchronization time slots through third time domain configuration information, and N synchronization time slots among the P synchronization time slots are indicated through first information as second-category synchronization time slots. By default or by protocol, the last / first N synchronization time slots among the P synchronization time slots are designated as second-category synchronization time slots.

[0156] Scheme 1-2: In some embodiments, the first information includes a first bit map, the P bits in the first bit map correspond to P synchronization time slots, the P synchronization time slots are all synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots.

[0157] Exemplarily, the third time domain configuration information configures P synchronization time slots within the third synchronization period to belong to the first type of synchronization time slots, and the P bits in the first bitmap indicate which of the P synchronization time slots belong to the second type of synchronization time slots. The P bits correspond to the P synchronization time slots, where a bit value of 1 represents that the corresponding synchronization time slot belongs to the second type of synchronization time slot, and a bit value of 0 represents that the corresponding synchronization time slot does not belong to the second type of synchronization time slot; alternatively, a bit value of 0 represents that the corresponding synchronization time slot belongs to the second type of synchronization time slot, and a bit value of 1 represents that the corresponding synchronization time slot does not belong to the second type of synchronization time slot.

[0158] Solution 1-3: In some implementations, the first information includes a first pattern index, where the first pattern index is used to indicate a first pattern among a plurality of patterns, and each pattern among the plurality of patterns corresponds to a synchronization time slot pattern corresponding to the first part of synchronization time slots.

[0159] Exemplarily, the third time domain configuration information is used to configure the P synchronization time slots within the third synchronization period to belong to the first type of synchronization time slots. Multiple patterns are preconfigured, each of which corresponds to a synchronization time slot pattern. The synchronization time slot pattern can also be understood as the pattern of the P synchronization time slots belonging to the second type of synchronization time slots. The pattern of the second type of synchronization time slot can be described by the time slot index of the second type of synchronization time slot or in a manner similar to the first bitmap described above. Each pattern corresponds to a pattern index, and the pattern indicated by a pattern index (i.e., the first pattern index described above) can be used to determine which of the P synchronization time slots belong to the second type of synchronization time slots.

[0160] When the first type of synchronization time slot and the second type of synchronization time slot do not overlap

[0161] In some embodiments, the second part of the synchronization time slots configured by the third time domain configuration information are first-type synchronization time slots, and the first part of the synchronization time slots configured by the third time domain configuration information are second-type synchronization time slots; the first part of the synchronization time slots and / or the second part of the synchronization time slots are indicated by the first information.

[0162] Here, two parts of synchronization time slots are configured through the third time domain configuration information, the first part of the synchronization time slots belongs to the second type of synchronization time slots, and the second part of the synchronization time slots belongs to the first type of synchronization time slots. As to which part of the synchronization time slots belongs to the first type of synchronization time slots and / or which part of the synchronization time slots belongs to the second type of synchronization time slots, it can be indicated by the first information.

[0163] There are several schemes for indicating the first part of synchronization time slots and / or the second part of synchronization time slots through the first information:

[0164] Solution 2-1: In some implementations, the first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots and / or the number M of synchronization time slots included in the second part of synchronization time slots.

[0165] Here, it is agreed by default or protocol that: the first part of the synchronization time slots includes the last N synchronization time slots of all synchronization time slots, and the second part of the synchronization time slots includes the first M synchronization time slots of all synchronization time slots; or, the first part of the synchronization time slots includes the first N synchronization time slots of all synchronization time slots, and the second part of the synchronization time slots includes the last M synchronization time slots of all synchronization time slots.

[0166] Illustratively, P synchronization time slots within a third synchronization period are configured using third time domain configuration information, and the first information indicates that N of the P synchronization time slots belong to the second type of synchronization time slots and / or M of the P synchronization time slots belong to the first type of synchronization time slots. By default or protocol agreement, the last / first N of the P synchronization time slots belong to the second type of synchronization time slots, and the first / last M of the P synchronization time slots belong to the second type of synchronization time slots.

[0167] Scheme 2-2: In some embodiments, the first information includes a second bit map, and the P bits in the second bit map correspond to P synchronization time slots, the P synchronization time slots are the first part of the synchronization time slots and the second part of the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots or the second part of the synchronization time slots.

[0168] Exemplarily, P synchronization time slots within a third synchronization period are configured using third time domain configuration information, and P bits in a second bitmap are used to indicate which of the P synchronization time slots belong to the first type of synchronization time slots and which belong to the second type of synchronization time slots. The P bits correspond to the P synchronization time slots, where a bit value of 1 represents that the corresponding synchronization time slot belongs to the second type of synchronization time slot, and a bit value of 0 represents that the corresponding synchronization time slot belongs to the first type of synchronization time slot; alternatively, a bit value of 0 represents that the corresponding synchronization time slot belongs to the second type of synchronization time slot, and a bit value of 1 represents that the corresponding synchronization time slot belongs to the first type of synchronization time slot.

[0169] Solution 2-3: In some implementations, the first information includes a second pattern index, which is used to indicate a second pattern among multiple patterns, each of which corresponds to a synchronization time slot pattern corresponding to the first part of the synchronization time slot and the second part of the synchronization time slot.

[0170] Exemplarily, the P synchronization time slots within the third synchronization period are configured using third time domain configuration information. Multiple patterns are preconfigured, and each of the multiple patterns corresponds to a synchronization time slot style. The synchronization time slot style can also be understood as the style of the P synchronization time slots belonging to the first type of synchronization time slots and the second type of synchronization time slots. The styles of the first type of synchronization time slots and the second type of synchronization time slots can be described using time slot indexes of the first type of synchronization time slots and the second type of synchronization time slots, or in a manner similar to the second bitmap described above. Each pattern corresponds to a pattern index, and the pattern indicated by a pattern index (i.e., the first pattern index described above) can be used to determine which of the P synchronization time slots belong to the first type of synchronization time slots and which belong to the second type of synchronization time slots.

[0171] The above-mentioned solution 1 can achieve the following configuration: configure two synchronization periods in the sideline system, namely the first synchronization period T1 and the second synchronization period T2; wherein, P1 (P1 ≥ 1) first-type synchronization time slots (also called first-type S-SSB time domain resources) are configured in the first synchronization period T1, and P2 (P2 ≥ 0) second-type synchronization time slots (also called second-type S-SSB time domain resources) are configured in the second synchronization period T2. The length of the second synchronization period T2 can be equal to the length of the first synchronization period T1, and the starting boundary of the second synchronization period T2 is aligned with the starting boundary of the first synchronization period T1. Alternatively, the length of the second synchronization period T2 can also be different from the length of the first synchronization period T1. In one implementation, T2 = L × T1, that is, the length of the second synchronization period T2 is L times the length of the first synchronization period T1, and the starting boundary of the second synchronization period T2 is aligned with the starting boundaries of L first synchronization periods T1.

[0172] The following configuration can be achieved through the above-mentioned scheme 2: configure 1 synchronization period in the sideline system, which is the third synchronization period T3; wherein, configure D (D≥1) first-class synchronization time slots (also called first-class S-SSB time domain resources) in the third synchronization period T3, and configure P4 (P4≥1) synchronization time slots among the D first-class synchronization time slots as second-class synchronization time slots (also called second-class S-SSB time domain resources); or, configure P3 (P3≥1) first-class synchronization time slots (also called first-class S-SSB time domain resources) and P4 (P4≥1) second-class synchronization time slots (also called second-class S-SSB time domain resources) in the third synchronization period T3.

[0173] Of course, the above-mentioned solution 1 can also achieve the configuration effect achieved by the above-mentioned solution 2. It only needs to configure the two synchronization periods as the same synchronization period, and the position of the synchronization time slot configured in each synchronization period is consistent with the position of the synchronization time slot configured in the above-mentioned solution 2.

[0174] Frequency domain resource allocation

[0175] In some embodiments, the frequency domain resources of the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources can be configured independently or uniformly.

[0176] Solution A: Independently configure frequency domain resources

[0177] In some embodiments, the first configuration information also includes first frequency domain configuration information and second frequency domain configuration information, the first frequency domain configuration information is used to determine the first type of S-SSB frequency domain resources, and the second frequency domain configuration information is used to determine the second type of S-SSB frequency domain resources. The first type of S-SSB frequency domain resources corresponds to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponds to the second type of S-SSB synchronization resources.

[0178] Here, the first type of S-SSB frequency domain resources refer to the frequency domain resources where the first type of S-SSB synchronization resources are located or the frequency domain resources corresponding to the first type of synchronization time slot.

[0179] Here, the second type of S-SSB frequency domain resources refer to the frequency domain resources where the second type of S-SSB synchronization resources are located or the frequency domain resources corresponding to the second type of synchronization time slot.

[0180] The first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources are independently configured through the first frequency domain configuration information and the second frequency domain configuration information.

[0181] In some embodiments, the first frequency domain configuration information is used to configure a first type of S-SSB frequency domain resources for one or more frequency bands; the second frequency domain configuration information is used to configure a second type of frequency domain resources for one or more frequency bands.

[0182] Exemplarily, the following configuration can be achieved through the first frequency domain configuration information: in the first frequency band, K1 (K1 ≥ 1) first-class S-SSB frequency domain resources are configured; in the second frequency band, K2 (K2 ≥ 1) first-class S-SSB frequency domain resources are configured. The following configuration can be achieved through the second frequency domain configuration information: in the first frequency band, K3 (K3 ≥ 1) second-class S-SSB frequency domain resources are configured; in the second frequency band, K4 (K4 ≥ 1) second-class S-SSB frequency domain resources are configured. The values ​​of K1, K2, K3, and K4 are independently configured and can be the same or different.

[0183] It should be noted that the frequency band where the first type of S-SSB frequency domain resources are located and the frequency band where the second type of S-SSB frequency domain resources are located can be exactly the same, completely different, or partially the same.

[0184] In the above scheme, since the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources are independently configured, the resources occupied by the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources in the frequency domain may be different or the same. Here, the resources occupied in the frequency domain may be reflected in one or more of the following aspects: the number of S-SSB frequency domain resources, the number of RBs occupied by each S-SSB frequency domain resource, and the RB position.

[0185] Solution B: Unified configuration of frequency domain resources

[0186] In some embodiments, the first configuration information also includes third frequency domain configuration information, and the third frequency configuration information is used to determine the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources. The first type of S-SSB frequency domain resources corresponds to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponds to the second type of S-SSB synchronization resources.

[0187] Here, the first type of S-SSB frequency domain resources refer to the frequency domain resources where the first type of S-SSB synchronization resources are located or the frequency domain resources corresponding to the first type of synchronization time slot.

[0188] Here, the second type of S-SSB frequency domain resources refer to the frequency domain resources where the second type of S-SSB synchronization resources are located or the frequency domain resources corresponding to the second type of synchronization time slot.

[0189] The first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources are uniformly configured through the third frequency domain configuration information.

[0190] In some embodiments, the third frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources for one or more frequency bands.

[0191] Exemplarily, the definition of the above-mentioned frequency band may include but is not limited to: carrier, bandwidth part (Bandwidth Part, BWP), sidelink BWP (SL BWP), channel, resource pool, RB set (RB set), frequency range, etc.

[0192] In the above scheme, since the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources are uniformly configured, the resources occupied by the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources in the frequency domain are the same. Here, the resources occupied in the frequency domain can be reflected in one or more of the following aspects: the number of S-SSB frequency domain resources, the number of RBs occupied by each S-SSB frequency domain resource, and the RB position.

[0193] In an embodiment of the present application, the first type of S-SSB frequency domain resources have a mapping relationship with the first type of synchronization time slot, and the second type of S-SSB frequency domain resources have a mapping relationship with the second type of synchronization time slot. That is, the first type of S-SSB frequency domain resources are mapped to the first type of synchronization time slot, and the second type of S-SSB frequency domain resources are mapped to the second type of synchronization time slot. It can be understood that if the first type of S-SSB synchronization resources are mapped in the time domain, they are mapped to the first type of synchronization time slot, and if they are mapped in the frequency domain, they are mapped to the first type of S-SSB frequency domain resources. Similarly, if the second type of S-SSB synchronization resources are mapped in the time domain, they are mapped to the second type of synchronization time slot, and if they are mapped in the frequency domain, they are mapped to the second type of S-SSB frequency domain resources.

[0194] In some embodiments, when the terminal is a first type terminal, the first type terminal sends or receives S-SSB on a first type S-SSB synchronization resource, or the first type terminal sends or receives S-SSB on a first type S-SSB synchronization resource and a second type S-SSB synchronization resource.

[0195] Here, the first type of S-SSB synchronization resources may refer to the first type of synchronization time slots and / or the first type of S-SSB frequency domain resources.

[0196] Here, on which type of S-SSB synchronization resource the first type terminal receives the S-SSB is related to the object with which it needs to communicate; if the first type terminal needs to communicate with another first type terminal, then the first type terminal can receive the S-SSB on the first type S-SSB synchronization resource; if the first type terminal needs to communicate with one or more other terminals (including the second type terminal), then the first type terminal can receive the S-SSB on the first type S-SSB synchronization resource and the second type S-SSB synchronization resource.

[0197] In some embodiments, the first-category terminal transmits or receives S-SSBs on some resources in the first-category S-SSB synchronization resources. In other embodiments, the first-category terminal transmits or receives S-SSBs on all resources in the first-category S-SSB synchronization resources.

[0198] Here, some of the resources in the first category of S-SSB synchronization resources can be understood as default / mandatory synchronization resources. The first category of terminals sends or receives S-SSBs on these resources instead of sending or receiving S-SSBs on all resources, thereby saving energy consumption of the terminal. Optionally, the first category of terminals can also send or receive S-SSBs on other remaining resources.

[0199] In some embodiments, part of the resources in the above-mentioned first-class S-SSB synchronization resources include: part of the first-class synchronization time slots corresponding to the first-class S-SSB synchronization resources, and / or part of the first-class S-SSB frequency domain resources corresponding to the first-class S-SSB synchronization resources.

[0200] Here, part of the first-class synchronization time slots corresponding to the above-mentioned first-class S-SSB synchronization resources can be understood as default / mandatory synchronization time slots. Part of the first-class S-SSB frequency domain resources corresponding to the above-mentioned first-class S-SSB synchronization resources can be understood as default / mandatory S-SSB frequency domain resources. The first-class terminal sends or receives S-SSB on part of the first-class synchronization time slots and / or part of the first-class S-SSB frequency domain resources, rather than on all first-class synchronization time slots and / or all first-class S-SSB frequency domain resources, thereby saving energy consumption of the terminal. Optionally, the first-class terminal can also send or receive S-SSB on the remaining other resources.

[0201] In some embodiments, when the terminal is a second-type terminal, the second-type terminal sends or receives S-SSB on the second-type S-SSB synchronization resource, or the first-type terminal sends or receives S-SSB on the second-type S-SSB synchronization resource and the first-type S-SSB synchronization resource.

[0202] Here, on which type of S-SSB synchronization resource the second type terminal receives the S-SSB is related to the object with which it needs to communicate; if the second type terminal needs to communicate with another second type terminal, then the second type terminal can receive the S-SSB on the second type S-SSB synchronization resource; if the second type terminal needs to communicate with one or more other terminals (including the first type terminal), then the second type terminal can receive the S-SSB on the first type S-SSB synchronization resource and the second type S-SSB synchronization resource.

[0203] Here, the second type of S-SSB synchronization resources may refer to the second type of synchronization time slots and / or the second type of S-SSB frequency domain resources.

[0204] In some embodiments, the second type of terminal sends or receives S-SSB on part of the second type of S-SSB synchronization resources; or, the second type of terminal sends or receives S-SSB on all of the second type of S-SSB synchronization resources.

[0205] Here, some of the resources in the second category of S-SSB synchronization resources can be understood as default / mandatory synchronization resources. The second category terminal sends or receives S-SSBs on these resources instead of sending or receiving S-SSBs on all resources, thereby saving energy consumption of the terminal. Optionally, the second category terminal can also send or receive S-SSBs on other remaining resources.

[0206] In some embodiments, part of the second-class S-SSB synchronization resources include: part of the second-class synchronization time slots corresponding to the second-class S-SSB synchronization resources, and / or part of the second-class S-SSB frequency domain resources corresponding to the second-class S-SSB synchronization resources.

[0207] Here, part of the second-class synchronization time slots corresponding to the above-mentioned second-class S-SSB synchronization resources can be understood as default / mandatory synchronization time slots. Part of the second-class S-SSB frequency domain resources corresponding to the above-mentioned second-class S-SSB synchronization resources can be understood as default / mandatory S-SSB frequency domain resources. The second-class terminal sends or receives S-SSB on part of the second-class synchronization time slots and / or part of the second-class S-SSB frequency domain resources, rather than on all second-class synchronization time slots and / or all second-class S-SSB frequency domain resources, thereby saving energy consumption of the terminal. Optionally, the second-class terminal can also send or receive S-SSB on the remaining other resources.

[0208] In the above scheme, if the synchronization resource is an unlicensed frequency band resource, the above terminal needs to perform Listen Before Talk (LBT) before sending S-SSB. Only when it is determined based on the LBT result that the S-SSB synchronization resource is not occupied can the S-SSB be sent on the S-SSB synchronization resource.

[0209] It should be noted that the first type of S-SSB synchronization resources may include two sets of synchronization resources, one set of synchronization resources is used for the first type of terminal to send S-SSB, and the other set of synchronization resources is used for the first type of terminal to receive S-SSB. Accordingly, the configuration of the first type of S-SSB synchronization resources may include two sets of configurations corresponding to the two sets of synchronization resources, each set of configurations may refer to the above configuration scheme.

[0210] It should be noted that the second type of S-SSB synchronization resources may include two sets of synchronization resources, one set of synchronization resources is used for the second type of terminal to send S-SSB, and the other set of synchronization resources is used for the second type of terminal to receive S-SSB. Accordingly, the configuration of the second type of S-SSB synchronization resources may include two sets of configurations corresponding to the two sets of synchronization resources, each set of configurations may refer to the above configuration scheme.

[0211] The technical solution of the embodiment of the present application proposes a side synchronization resource configuration method, which configures additional exclusive S-SSB synchronization resources (i.e., second-class S-SSB synchronization resources) for terminals with lower capabilities (i.e., second-class terminals). The additional exclusive S-SSB synchronization resources may be different from the S-SSB synchronization resources (i.e., first-class S-SSB synchronization resources) corresponding to terminals with stronger capabilities (i.e., first-class terminals). In addition, terminals with lower capabilities (i.e., second-class terminals) do not need to try to send or receive S-SSBs in all S-SSB synchronization resources, but can send or receive S-SSBs on the default / mandatory S-SSB synchronization resources, which can effectively save energy consumption. The technical solution of the embodiment of the present application greatly reduces the energy consumed and processing complexity of sending or receiving S-SSBs by low-capability terminals, can save power for low-capability terminals and does not require complex hardware design. At the same time, it can also ensure that low-capability terminals and strong-capability terminals coexist on the same resources and achieve interconnection and interoperability, providing a better solution for the interconnection and interoperability of multiple devices (terminals with different capabilities) in the future smart Internet of Things.

[0212] The technical solutions of the embodiments of the present application are illustrated below with reference to specific application examples.

[0213] Application Example 1

[0214] In this application example, the time domain resources corresponding to the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources (i.e., S-SSB time domain resources) can be configured independently or uniformly. In the case of independent configuration, the configuration method can refer to Scheme 1 (independent configuration of time domain resources) in the related scheme of Figure 7 above. In the case of unified configuration, the configuration method can refer to Scheme 2 (uniform configuration of time domain resources) in the related scheme of Figure 7 above. Among them, the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources have the same synchronization period.

[0215] Exemplarily, as shown in FIG8 , four first-class S-SSB time slots (i.e., four first-class synchronization time slots) are configured in one synchronization cycle, and two second-class S-SSB time slots (i.e., four second-class synchronization time slots) are configured, and there is no overlap between the four first-class S-SSB time slots and the two second-class S-SSB time slots.

[0216] For example, as shown in FIG9 , four S-SSB time slots (i.e., synchronization time slots) are configured in one synchronization cycle. These four S-SSB time slots belong to the first type of S-SSB time slots (i.e., the first type of synchronization time slots), and the last two of these four S-SSB time slots also belong to the second type of S-SSB time slots (i.e., the second type of synchronization time slots). In other words, there is an overlap between the four first type of S-SSB time slots and the two second type of S-SSB time slots.

[0217] For example, as shown in Figure 10, 6 S-SSB time slots (i.e., synchronization time slots) are configured in a synchronization cycle, of which 4 S-SSB time slots belong to the first type of S-SSB time slots (i.e., the first type of synchronization time slots), and the other 2 S-SSB time slots belong to the second type of S-SSB time slots (i.e., the second type of synchronization time slots).

[0218] For the second type of terminals (i.e., low-capability terminals), when the second type of terminals send S-SSBs in the second type of S-SSB time slots, they can choose to send S-SSBs in part of the S-SSB time slots in the second type of S-SSB time slots, thereby saving energy consumption; this part of the S-SSB time slots can be the default / mandatory S-SSB time slots configured by the network or pre-configured or agreed upon by the protocol.

[0219] For the second type of terminals (i.e., low-capability terminals), the second type of terminals receive S-SSBs on the second type of S-SSB time slots. Optionally, the second type of terminals can also receive S-SSBs on the first type of S-SSB time slots. Here, the type of S-SSB synchronization time slot on which the second type of terminal receives the S-SSB is related to the object with which it needs to communicate. If the second type of terminal needs to communicate with another second type of terminal, then the second type of terminal can receive the S-SSB on the second type of S-SSB synchronization time slot. If the second type of terminal needs to communicate with one or more other terminals (including the first type of terminal), then the second type of terminal can receive the S-SSB on both the first type of S-SSB synchronization time slot and the second type of S-SSB synchronization time slot.

[0220] Application Example 2

[0221] In this application example, the time domain resources corresponding to the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources (i.e., S-SSB time domain resources) can be independently configured. The independent configuration method can refer to Scheme 1 (independent configuration of time domain resources) in the related scheme of Figure 7 above. Among them, the synchronization period of the first type of S-SSB synchronization resources is the first synchronization period T1, and the synchronization period of the second type of S-SSB synchronization resources is the second synchronization period T2.

[0222] For example, as shown in FIG11 , the first synchronization period T1 and the second synchronization period T2 have a multiple relationship. Here, T2 = 2 × T1 is used as an example for illustration, where the starting boundary of the second synchronization period T2 is aligned with the starting boundaries of two first synchronization periods T1. Two first-type S-SSB time slots (i.e., two first-type synchronization time slots) are configured in the first synchronization period T1, and one second-type S-SSB time slot (i.e., one second-type synchronization time slot) is configured in the second synchronization period T2.

[0223] For the second type of terminals (i.e., low-capability terminals), the second type of terminals receive S-SSBs on the second type of S-SSB time slots. Optionally, the second type of terminals can also receive S-SSBs on the first type of S-SSB time slots. Here, the type of S-SSB synchronization time slot on which the second type of terminal receives the S-SSB is related to the object with which it needs to communicate. If the second type of terminal needs to communicate with another second type of terminal, then the second type of terminal can receive the S-SSB on the second type of S-SSB synchronization time slot. If the second type of terminal needs to communicate with one or more other terminals (including the first type of terminal), then the second type of terminal can receive the S-SSB on both the first type of S-SSB synchronization time slot and the second type of S-SSB synchronization time slot.

[0224] Application Example 3

[0225] In this application example, the time domain resources (i.e., S-SSB time domain resources) corresponding to the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources can be configured independently or uniformly. In the case of independent configuration, the configuration method can refer to Scheme 1 (independent configuration of time domain resources) in the aforementioned Figure 7 related scheme; in the case of unified configuration, the configuration method can refer to Scheme 2 (uniform configuration of time domain resources) in the aforementioned Figure 7 related scheme. The frequency domain resources (i.e., S-SSB frequency domain resources) corresponding to the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources can be configured independently or uniformly. In the case of independent configuration, the configuration method can refer to Scheme A (independent configuration of frequency domain resources) in the aforementioned Figure 7 related scheme; in the case of unified configuration, the configuration method can refer to Scheme B (uniform configuration of frequency domain resources) in the aforementioned Figure 7 related scheme.

[0226] For example, as shown in Figure 12, two first-type S-SSB time slots and one second-type S-SSB time slot are configured within a synchronization period. The frequency domain resources corresponding to the first-type S-SSB time slot are: three S-SSB frequency domain resources in frequency band 1 and two S-SSB frequency domain resources in frequency band 0. The frequency domain corresponding to the second-type S-SSB time slot is: one S-SSB frequency domain resource in frequency band 1.

[0227] For the first type of terminal, the first type of terminal can send S-SSB on the first type of S-SSB synchronization resource. The first type of S-SSB synchronization resource occupies one or two first type S-SSB time slots in the time domain, and can occupy at least one S-SSB frequency domain resource in frequency band 1 in the frequency domain. Optionally, it can also occupy at least one S-SSB frequency domain resource in frequency band 0. Here, frequency band 1 can be understood as a default / mandatory frequency band, and frequency band 0 can be understood as an optional / auxiliary frequency band.

[0228] For the second type of terminal, the second type of terminal can send S-SSB on the second type of S-SSB synchronization resource. The second type of S-SSB synchronization resource occupies a second type of S-SSB time slot in the time domain and occupies 1 S-SSB frequency domain resource in frequency band 1 in the frequency domain.

[0229] In addition, in one embodiment, the first type of terminal may use the second type of S-SSB synchronization resource to send S-SSB, and / or the second type of terminal may also use the first type of S-SSB synchronization resource to send S-SSB. This implementation method may have a prerequisite, namely: the first type of terminal needs to send S-SSB on at least the first type of S-SSB frequency domain resources of the first frequency band, and the second type of terminal needs to send S-SSB on at least the second type of S-SSB frequency domain resources of the first frequency band. Taking Figure 12 as an example, the prerequisite is: the first type of terminal needs to send S-SSB on at least the first type of S-SSB frequency domain resources of frequency band 1, and the second type of terminal needs to send S-SSB on at least the second type of S-SSB frequency domain resources of frequency band 1.

[0230] For the first type of terminal, the first type of terminal can receive S-SSB on the first type of S-SSB synchronization resource. Optionally, the first type of terminal can also receive S-SSB on the second type of S-SSB synchronization resource. Taking Figure 12 as an example, the first type of terminal receives S-SSB on each first type of S-SSB frequency domain resource on frequency band 1. The first type of terminal can also receive S-SSB on each second type of S-SSB frequency domain resource on frequency band 1.

[0231] For the second type of terminal, the second type of terminal can receive S-SSB on the second type of S-SSB synchronization resource. Optionally, the second type of terminal can also receive S-SSB on the first type of S-SSB synchronization resource. Taking Figure 12 as an example, the second type of terminal receives S-SSB on each second type of S-SSB frequency domain resource on frequency band 1. The second type of terminal can also receive S-SSB on each first type of S-SSB frequency domain resource on frequency band 1.

[0232] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0233] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in 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. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0234] FIG13 is a schematic diagram of the first structure of a resource configuration device provided in an embodiment of the present application, which is applied to a terminal. As shown in FIG13 , the device includes:

[0235] Acquisition unit 1301 is used to obtain first configuration information, and the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resource corresponds to a first type of terminal, and the second type of S-SSB synchronization resource corresponds to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

[0236] In some embodiments, the first configuration information includes first time domain configuration information and second time domain configuration information, the first time domain configuration information is used to determine a first type of synchronization time slot, and the second time domain configuration information is used to determine a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

[0237] In some implementations, the first time domain configuration information includes at least one of the following:

[0238] A first parameter, wherein the first parameter is used to indicate a first synchronization period;

[0239] a second parameter, where the second parameter is used to indicate the number of first-type synchronization time slots included in the first synchronization period;

[0240] a third parameter, the third parameter being used to indicate a time slot offset of a first first-type synchronization time slot within a first synchronization period relative to a boundary of the first synchronization period;

[0241] A fourth parameter is used to indicate a time slot interval between two adjacent first-type synchronization time slots in the first synchronization period.

[0242] In some implementations, the second time domain configuration information includes at least one of the following:

[0243] a fifth parameter, where the fifth parameter is used to indicate a second synchronization period;

[0244] a sixth parameter, the sixth parameter being used to indicate the number of second-type synchronization time slots included in the second synchronization period;

[0245] a seventh parameter, the seventh parameter being used to indicate a time slot offset of a first second-type synchronization time slot in a second synchronization period relative to a boundary of the second synchronization period;

[0246] An eighth parameter is used to indicate a time slot interval between two adjacent second-type synchronization time slots in a second synchronization period.

[0247] In some implementations, a first synchronization period configured by the first time domain configuration information is the same as a second synchronization period configured by the second time domain configuration information.

[0248] In some implementations, a first synchronization period configured by the first time domain configuration information is different from a second synchronization period configured by the second time domain configuration information.

[0249] In some embodiments, the length of the first synchronization period is L times the length of the second synchronization period, where L is an integer greater than 1.

[0250] In some embodiments, the first configuration information includes third time domain configuration information and first information; the third time domain configuration information and the first information are used to determine a first type of synchronization time slot and a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

[0251] In some embodiments, all synchronization time slots configured by the third time domain configuration information are the first type of synchronization time slots; the first part of the synchronization time slots configured by the third time domain configuration information are the second type of synchronization time slots, and the first part of the synchronization time slots are indicated by the first information.

[0252] In some embodiments, the first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots.

[0253] In some embodiments, the first portion of synchronization time slots includes the last N synchronization time slots of the entire synchronization time slots; or, the first portion of synchronization time slots includes the first N synchronization time slots of the entire synchronization time slots.

[0254] In some embodiments, the first information includes a first bit map, wherein P bits in the first bit map correspond to P synchronization time slots, the P synchronization time slots are all the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots.

[0255] In some embodiments, the first information includes a first pattern index, where the first pattern index is used to indicate a first pattern among a plurality of patterns, each pattern among the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first part of synchronization time slots.

[0256] In some embodiments, the second part of the synchronization time slot configured by the third time domain configuration information is the first type of synchronization time slot, and the first part of the synchronization time slot configured by the third time domain configuration information is the second type of synchronization time slot; the first part of the synchronization time slot and / or the second part of the synchronization time slot is indicated by the first information.

[0257] In some embodiments, the first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots and / or the number M of synchronization time slots included in the second part of synchronization time slots.

[0258] In some embodiments, the first part of the synchronization time slots includes the last N synchronization time slots of all the synchronization time slots, and the second part of the synchronization time slots includes the first M synchronization time slots of all the synchronization time slots; or, the first part of the synchronization time slots includes the first N synchronization time slots of all the synchronization time slots, and the second part of the synchronization time slots includes the last M synchronization time slots of all the synchronization time slots.

[0259] In some embodiments, the first information includes a second bit map, and the P bits in the second bit map have a corresponding relationship with P synchronization time slots, the P synchronization time slots are the first part of the synchronization time slots and the second part of the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots or the second part of the synchronization time slots.

[0260] In some embodiments, the first information includes a second pattern index, where the second pattern index is used to indicate a second pattern among a plurality of patterns, each pattern among the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first portion of synchronization time slots and the second portion of synchronization time slots.

[0261] In some implementations, the third time domain configuration information includes at least one of the following:

[0262] a ninth parameter, where the ninth parameter is used to indicate a third synchronization period;

[0263] a tenth parameter, the tenth parameter being used to indicate the number of synchronization time slots included in the third synchronization period;

[0264] an eleventh parameter, the eleventh parameter being used to indicate a time slot offset of a first synchronization time slot in a third synchronization period relative to a boundary of the third synchronization period;

[0265] A twelfth parameter is used to indicate a time slot interval between two adjacent synchronization time slots in a third synchronization period.

[0266] In some embodiments, the first configuration information also includes first frequency domain configuration information and second frequency domain configuration information, the first frequency domain configuration information is used to determine a first type of S-SSB frequency domain resources, and the second frequency domain configuration information is used to determine a second type of S-SSB frequency domain resources, the first type of S-SSB frequency domain resources corresponds to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponds to the second type of S-SSB synchronization resources.

[0267] In some embodiments, the first frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources for one or more frequency bands; the second frequency domain configuration information is used to configure the second type of frequency domain resources for one or more frequency bands.

[0268] In some embodiments, the first configuration information also includes third frequency domain configuration information, and the third frequency configuration information is used to determine a first type of S-SSB frequency domain resources and a second type of S-SSB frequency domain resources, the first type of S-SSB frequency domain resources corresponding to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponding to the second type of S-SSB synchronization resources.

[0269] In some embodiments, the third frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources for one or more frequency bands.

[0270] In some embodiments, the first type of S-SSB frequency domain resources have a mapping relationship with the first type of synchronization time slots, and the second type of S-SSB frequency domain resources have a mapping relationship with the second type of synchronization time slots.

[0271] In some embodiments, the device further includes: a sending / receiving unit 1302, which is used to send or receive S-SSB on the first type of S-SSB synchronization resource when the terminal is the first type of terminal, or to send or receive S-SSB on the first type of S-SSB synchronization resource and the second type of S-SSB synchronization resource.

[0272] In some embodiments, the sending / receiving unit 1302 is used to send or receive S-SSB on part of the resources in the first type of S-SSB synchronization resources; or, to send or receive S-SSB on all resources in the first type of S-SSB synchronization resources.

[0273] In some embodiments, part of the resources in the first type of S-SSB synchronization resources include: part of the first type of synchronization time slots corresponding to the first type of S-SSB synchronization resources, and / or part of the first type of S-SSB frequency domain resources corresponding to the first type of S-SSB synchronization resources.

[0274] In some embodiments, the sending / receiving unit 1302 is used to send or receive S-SSB on the second type of S-SSB synchronization resources when the terminal is the second type of terminal, or to send or receive S-SSB on the second type of S-SSB synchronization resources and the first type of S-SSB synchronization resources.

[0275] In some embodiments, the sending / receiving unit 1302 is used to send or receive S-SSB on part of the second-type S-SSB synchronization resources; or, to send or receive S-SSB on all of the second-type S-SSB synchronization resources.

[0276] In some embodiments, the partial resources of the second type of S-SSB synchronization resources include: partial second type synchronization time slots corresponding to the second type of S-SSB synchronization resources, and / or partial second type S-SSB frequency domain resources corresponding to the second type of S-SSB synchronization resources.

[0277] In some implementations, the first configuration information is network configured or pre-configured.

[0278] Those skilled in the art should understand that the relevant description of the above-mentioned resource configuration device in the embodiment of the present application can be understood with reference to the relevant description of the resource configuration method in the embodiment of the present application.

[0279] FIG14 is a second schematic diagram of the structure of a resource configuration device provided in an embodiment of the present application, which is applied to a network device. As shown in FIG14 , the device includes:

[0280] Sending unit 1401 is used to send first configuration information, where the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resource corresponds to a first type of terminal, and the second type of S-SSB synchronization resource corresponds to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

[0281] In some embodiments, the first configuration information includes first time domain configuration information and second time domain configuration information, the first time domain configuration information is used to determine a first type of synchronization time slot, and the second time domain configuration information is used to determine a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

[0282] In some implementations, the first time domain configuration information includes at least one of the following:

[0283] A first parameter, wherein the first parameter is used to indicate a first synchronization period;

[0284] a second parameter, where the second parameter is used to indicate the number of first-type synchronization time slots included in the first synchronization period;

[0285] a third parameter, the third parameter being used to indicate a time slot offset of a first first-type synchronization time slot within a first synchronization period relative to a boundary of the first synchronization period;

[0286] A fourth parameter is used to indicate a time slot interval between two adjacent first-type synchronization time slots in the first synchronization period.

[0287] In some implementations, the second time domain configuration information includes at least one of the following:

[0288] a fifth parameter, where the fifth parameter is used to indicate a second synchronization period;

[0289] a sixth parameter, the sixth parameter being used to indicate the number of second-type synchronization time slots included in the second synchronization period;

[0290] a seventh parameter, the seventh parameter being used to indicate a time slot offset of a first second-type synchronization time slot in a second synchronization period relative to a boundary of the second synchronization period;

[0291] An eighth parameter is used to indicate a time slot interval between two adjacent second-type synchronization time slots in a second synchronization period.

[0292] In some implementations, a first synchronization period configured by the first time domain configuration information is the same as a second synchronization period configured by the second time domain configuration information.

[0293] In some implementations, a first synchronization period configured by the first time domain configuration information is different from a second synchronization period configured by the second time domain configuration information.

[0294] In some embodiments, the length of the first synchronization period is L times the length of the second synchronization period, where L is an integer greater than 1.

[0295] In some embodiments, the first configuration information includes third time domain configuration information and first information; the third time domain configuration information and the first information are used to determine a first type of synchronization time slot and a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

[0296] In some embodiments, all synchronization time slots configured by the third time domain configuration information are the first type of synchronization time slots; the first part of the synchronization time slots configured by the third time domain configuration information are the second type of synchronization time slots, and the first part of the synchronization time slots are indicated by the first information.

[0297] In some embodiments, the first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots.

[0298] In some embodiments, the first portion of synchronization time slots includes the last N synchronization time slots of the entire synchronization time slots; or, the first portion of synchronization time slots includes the first N synchronization time slots of the entire synchronization time slots.

[0299] In some embodiments, the first information includes a first bit map, wherein P bits in the first bit map correspond to P synchronization time slots, the P synchronization time slots are all the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots.

[0300] In some embodiments, the first information includes a first pattern index, where the first pattern index is used to indicate a first pattern among a plurality of patterns, each pattern among the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first part of synchronization time slots.

[0301] In some embodiments, the second part of the synchronization time slot configured by the third time domain configuration information is the first type of synchronization time slot, and the first part of the synchronization time slot configured by the third time domain configuration information is the second type of synchronization time slot; the first part of the synchronization time slot and / or the second part of the synchronization time slot is indicated by the first information.

[0302] In some embodiments, the first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots and / or the number M of synchronization time slots included in the second part of synchronization time slots.

[0303] In some embodiments, the first part of the synchronization time slots includes the last N synchronization time slots of all the synchronization time slots, and the second part of the synchronization time slots includes the first M synchronization time slots of all the synchronization time slots; or, the first part of the synchronization time slots includes the first N synchronization time slots of all the synchronization time slots, and the second part of the synchronization time slots includes the last M synchronization time slots of all the synchronization time slots.

[0304] In some embodiments, the first information includes a second bit map, and the P bits in the second bit map have a corresponding relationship with P synchronization time slots, the P synchronization time slots are the first part of the synchronization time slots and the second part of the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots or the second part of the synchronization time slots.

[0305] In some embodiments, the first information includes a second pattern index, where the second pattern index is used to indicate a second pattern among a plurality of patterns, each pattern among the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first portion of synchronization time slots and the second portion of synchronization time slots.

[0306] In some implementations, the third time domain configuration information includes at least one of the following:

[0307] a ninth parameter, where the ninth parameter is used to indicate a third synchronization period;

[0308] a tenth parameter, the tenth parameter being used to indicate the number of synchronization time slots included in the third synchronization period;

[0309] an eleventh parameter, the eleventh parameter being used to indicate a time slot offset of a first synchronization time slot in a third synchronization period relative to a boundary of the third synchronization period;

[0310] A twelfth parameter is used to indicate a time slot interval between two adjacent synchronization time slots in a third synchronization period.

[0311] In some embodiments, the first configuration information also includes first frequency domain configuration information and second frequency domain configuration information, the first frequency domain configuration information is used to determine a first type of S-SSB frequency domain resources, and the second frequency domain configuration information is used to determine a second type of S-SSB frequency domain resources, the first type of S-SSB frequency domain resources corresponds to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponds to the second type of S-SSB synchronization resources.

[0312] In some embodiments, the first frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources for one or more frequency bands; the second frequency domain configuration information is used to configure the second type of frequency domain resources for one or more frequency bands.

[0313] In some embodiments, the first configuration information also includes third frequency domain configuration information, and the third frequency configuration information is used to determine a first type of S-SSB frequency domain resources and a second type of S-SSB frequency domain resources, the first type of S-SSB frequency domain resources corresponding to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponding to the second type of S-SSB synchronization resources.

[0314] In some embodiments, the third frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources for one or more frequency bands.

[0315] In some embodiments, the first type of S-SSB frequency domain resources have a mapping relationship with the first type of synchronization time slots, and the second type of S-SSB frequency domain resources have a mapping relationship with the second type of synchronization time slots.

[0316] Those skilled in the art should understand that the relevant description of the above-mentioned resource configuration device in the embodiment of the present application can be understood with reference to the relevant description of the resource configuration method in the embodiment of the present application.

[0317] Figure 15 is a schematic diagram of a communication device 1500 provided in an embodiment of the present application. The communication device can be a terminal or a network device. The communication device 1500 shown in Figure 15 includes a processor 1510, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0318] Optionally, as shown in FIG15 , the communication device 1500 may further include a memory 1520. The processor 1510 may call and execute a computer program from the memory 1520 to implement the method in the embodiment of the present application.

[0319] The memory 1520 may be a separate device independent of the processor 1510 , or may be integrated into the processor 1510 .

[0320] Optionally, as shown in FIG15 , the communication device 1500 may further include a transceiver 1530 , and the processor 1510 may control the transceiver 1530 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0321] The transceiver 1530 may include a transmitter and a receiver. The transceiver 1530 may further include an antenna, and the number of antennas may be one or more.

[0322] Optionally, the communication device 1500 may specifically be a network device in an embodiment of the present application, and the communication device 1500 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0323] Optionally, the communication device 1500 may specifically be a mobile terminal / terminal of an embodiment of the present application, and the communication device 1500 may implement the corresponding processes implemented by the mobile terminal / terminal in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0324] Figure 16 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1600 shown in Figure 16 includes a processor 1610, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0325] Optionally, as shown in FIG16 , the chip 1600 may further include a memory 1620. The processor 1610 may call and execute a computer program from the memory 1620 to implement the method in the embodiment of the present application.

[0326] The memory 1620 may be a separate device independent of the processor 1610 , or may be integrated into the processor 1610 .

[0327] Optionally, the chip 1600 may further include an input interface 1630. The processor 1610 may control the input interface 1630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0328] Optionally, the chip 1600 may further include an output interface 1640. The processor 1610 may control the output interface 1640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0329] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0330] Optionally, the chip can be applied to the mobile terminal / terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0331] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0332] FIG17 is a schematic block diagram of a communication system 1700 provided in an embodiment of the present application. As shown in FIG17 , the communication system 1700 includes a terminal 1710 and a network device 1720 .

[0333] Among them, the terminal 1710 can be used to implement the corresponding functions implemented by the terminal in the above method, and the network device 1720 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0334] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0335] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0336] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0337] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0338] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0339] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0340] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0341] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0342] Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0343] The embodiment of the present application also provides a computer program.

[0344] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0345] Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0346] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0347] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

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

[0351] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

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

Claims

1. A resource configuration method, the method comprising: The terminal obtains first configuration information, and the first configuration information is used to determine the synchronization resources of the first type of side synchronization signal block S-SSB and the second type of S-SSB synchronization resources; wherein the first type of S-SSB synchronization resources correspond to the first type of terminals, the second type of S-SSB synchronization resources correspond to the second type of terminals, and the capability of the first type of terminals is higher than that of the second type of terminals.

2. The method according to claim 1, wherein: The first configuration information includes first time domain configuration information and second time domain configuration information, the first time domain configuration information is used to determine a first type of synchronization time slot, and the second time domain configuration information is used to determine a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

3. The method according to claim 2, wherein: The first time domain configuration information includes at least one of the following: A first parameter, wherein the first parameter is used to indicate a first synchronization period; A second parameter, wherein the second parameter is used to indicate the number of first-type synchronization time slots included in the first synchronization cycle; A third parameter, the third parameter being used to indicate a time slot offset of a first type-one synchronization time slot within a first synchronization period relative to a boundary of the first synchronization period; A fourth parameter, wherein the fourth parameter is used to indicate a time slot interval between two adjacent first-type synchronization time slots in a first synchronization cycle.

4. The method according to claim 2 or 3, wherein: The second time domain configuration information includes at least one of the following: a fifth parameter, wherein the fifth parameter is used to indicate a second synchronization period; a sixth parameter, the sixth parameter being used to indicate the number of second-type synchronization time slots included in the second synchronization period; a seventh parameter, the seventh parameter being used to indicate a time slot offset of a first second-type synchronization time slot in a second synchronization period relative to a boundary of the second synchronization period; An eighth parameter, wherein the eighth parameter is used to indicate a time slot interval between two adjacent second-type synchronization time slots in a second synchronization period.

5. The method according to any one of claims 2 to 4, wherein: The first synchronization period configured by the first time domain configuration information is the same as the second synchronization period configured by the second time domain configuration information.

6. The method according to any one of claims 2 to 4, wherein: A first synchronization period configured by the first time domain configuration information is different from a second synchronization period configured by the second time domain configuration information.

7. The method according to claim 6, wherein: The length of the first synchronization period is L times the length of the second synchronization period, where L is an integer greater than 1.

8. The method according to claim 1, wherein: The first configuration information includes third time domain configuration information and first information; the third time domain configuration information and the first information are used to determine a first type of synchronization time slot and a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

9. The method according to claim 8, wherein: All synchronization time slots configured by the third time domain configuration information are the first type of synchronization time slots; the first part of synchronization time slots configured by the third time domain configuration information are the second type of synchronization time slots, and the first part of synchronization time slots are indicated by the first information.

10. The method according to claim 9, wherein: The first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots.

11. The method according to claim 10, wherein: The first part of synchronization time slots includes the last N synchronization time slots of all synchronization time slots; or, The first part of synchronization time slots includes the first N synchronization time slots of the entire synchronization time slots.

12. The method according to claim 9, wherein: The first information includes a first bit map, wherein P bits in the first bit map correspond to P synchronization time slots, the P synchronization time slots are all the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots.

13. The method according to claim 9, wherein: The first information includes a first pattern index, where the first pattern index is used to indicate a first pattern among a plurality of patterns, each of the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first part of synchronization time slots.

14. The method according to claim 8, wherein: The second part of synchronization time slots configured by the third time domain configuration information are the first type of synchronization time slots, and the first part of synchronization time slots configured by the third time domain configuration information are the second type of synchronization time slots; the first part of synchronization time slots and / or the second part of synchronization time slots are indicated by the first information.

15. The method according to claim 14, wherein: The first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots and / or the number M of synchronization time slots included in the second part of synchronization time slots.

16. The method according to claim 15, wherein: The first part of synchronization time slots includes the last N synchronization time slots of all synchronization time slots, and the second part of synchronization time slots includes the first M synchronization time slots of all synchronization time slots; or, The first part of synchronization time slots includes the first N synchronization time slots of the entire synchronization time slots, and the second part of synchronization time slots includes the last M synchronization time slots of the entire synchronization time slots.

17. The method according to claim 14, wherein: The first information includes a second bit map, and the P bits in the second bit map correspond to P synchronization time slots, the P synchronization time slots are the first part of the synchronization time slots and the second part of the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots or the second part of the synchronization time slots.

18. The method according to claim 14, wherein: The first information includes a second pattern index, where the second pattern index is used to indicate a second pattern among a plurality of patterns, each pattern among the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first part of synchronization time slots and the second part of synchronization time slots.

19. The method according to any one of claims 8 to 18, wherein: The third time domain configuration information includes at least one of the following: a ninth parameter, wherein the ninth parameter is used to indicate a third synchronization period; a tenth parameter, the tenth parameter being used to indicate the number of synchronization time slots included in the third synchronization period; An eleventh parameter, the eleventh parameter is used to indicate a time slot offset of a first synchronization time slot in a third synchronization period relative to a boundary of the third synchronization period; A twelfth parameter is used to indicate a time slot interval between two adjacent synchronization time slots in a third synchronization period.

20. The method according to any one of claims 2 to 19, wherein: The first configuration information also includes first frequency domain configuration information and second frequency domain configuration information. The first frequency domain configuration information is used to determine a first type of S-SSB frequency domain resources, and the second frequency domain configuration information is used to determine a second type of S-SSB frequency domain resources. The first type of S-SSB frequency domain resources corresponds to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponds to the second type of S-SSB synchronization resources.

21. The method according to claim 20, wherein: The first frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources for one or more frequency bands; the second frequency domain configuration information is used to configure the second type of frequency domain resources for one or more frequency bands.

22. The method according to any one of claims 2 to 19, wherein: The first configuration information also includes third frequency domain configuration information, and the third frequency configuration information is used to determine a first type of S-SSB frequency domain resources and a second type of S-SSB frequency domain resources, the first type of S-SSB frequency domain resources correspond to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources correspond to the second type of S-SSB synchronization resources.

23. The method according to claim 22, wherein: The third frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources for one or more frequency bands.

24. The method according to any one of claims 20 to 23, wherein: The first type of S-SSB frequency domain resources have a mapping relationship with the first type of synchronization time slots, and the second type of S-SSB frequency domain resources have a mapping relationship with the second type of synchronization time slots.

25. The method according to any one of claims 1 to 24, wherein: The method further comprises: When the terminal is the first type of terminal, the first type of terminal sends or receives S-SSB on the first type of S-SSB synchronization resources, or the first type of terminal sends or receives S-SSB on the first type of S-SSB synchronization resources and the second type of S-SSB synchronization resources.

26. The method according to claim 25, wherein: The first-type terminal sending or receiving the S-SSB on the first-type S-SSB synchronization resource includes: The first-category terminal sends or receives S-SSB on part of the first-category S-SSB synchronization resources; or, The first type of terminal sends or receives S-SSB on all resources in the first type of S-SSB synchronization resources.

27. The method according to claim 26, wherein: Part of the resources in the first type of S-SSB synchronization resources include: part of the first type of synchronization time slots corresponding to the first type of S-SSB synchronization resources, and / or part of the first type of S-SSB frequency domain resources corresponding to the first type of S-SSB synchronization resources.

28. The method according to any one of claims 1 to 24, wherein: The method further comprises: When the terminal is the second-category terminal, the second-category terminal sends or receives S-SSB on the second-category S-SSB synchronization resources, or the first-category terminal sends or receives S-SSB on the second-category S-SSB synchronization resources and the first-category S-SSB synchronization resources.

29. The method according to claim 28, wherein: The second-type terminal sending or receiving the S-SSB on the second-type S-SSB synchronization resource includes: The second-type terminal sends or receives S-SSB on part of the second-type S-SSB synchronization resources; or, The second type of terminal sends or receives S-SSB on all resources of the second type of S-SSB synchronization resources.

30. The method of claim 29, wherein: The partial resources of the second type of S-SSB synchronization resources include: part of the second type of synchronization time slots corresponding to the second type of S-SSB synchronization resources, and / or part of the second type of S-SSB frequency domain resources corresponding to the second type of S-SSB synchronization resources.

31. The method according to any one of claims 1 to 30, wherein: The first configuration information is network configured or pre-configured.

32. A resource configuration method, the method comprising: The network device sends first configuration information, and the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resources correspond to a first type of terminal, and the second type of S-SSB synchronization resources correspond to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

33. The method of claim 32, wherein: The first configuration information includes first time domain configuration information and second time domain configuration information, the first time domain configuration information is used to determine a first type of synchronization time slot, and the second time domain configuration information is used to determine a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

34. The method of claim 33, wherein: The first time domain configuration information includes at least one of the following: A first parameter, wherein the first parameter is used to indicate a first synchronization period; A second parameter, wherein the second parameter is used to indicate the number of first-type synchronization time slots included in the first synchronization cycle; A third parameter, the third parameter being used to indicate a time slot offset of a first type-one synchronization time slot within a first synchronization period relative to a boundary of the first synchronization period; A fourth parameter, wherein the fourth parameter is used to indicate a time slot interval between two adjacent first-type synchronization time slots in a first synchronization cycle.

35. The method according to claim 33 or 34, wherein: The second time domain configuration information includes at least one of the following: a fifth parameter, wherein the fifth parameter is used to indicate a second synchronization period; a sixth parameter, the sixth parameter being used to indicate the number of second-type synchronization time slots included in the second synchronization period; a seventh parameter, the seventh parameter being used to indicate a time slot offset of a first second-type synchronization time slot in a second synchronization period relative to a boundary of the second synchronization period; An eighth parameter, wherein the eighth parameter is used to indicate a time slot interval between two adjacent second-type synchronization time slots in a second synchronization period.

36. A method according to any one of claims 33 to 35, wherein: The first synchronization period configured by the first time domain configuration information is the same as the second synchronization period configured by the second time domain configuration information.

37. A method according to any one of claims 33 to 35, wherein: A first synchronization period configured by the first time domain configuration information is different from a second synchronization period configured by the second time domain configuration information.

38. The method of claim 37, wherein: The length of the first synchronization period is L times the length of the second synchronization period, where L is an integer greater than 1.

39. The method of claim 32, wherein: The first configuration information includes third time domain configuration information and first information; the third time domain configuration information and the first information are used to determine a first type of synchronization time slot and a second type of synchronization time slot, the first type of synchronization time slot corresponds to the first type of S-SSB synchronization resource, and the second type of synchronization time slot corresponds to the second type of S-SSB synchronization resource.

40. The method of claim 39, wherein: All synchronization time slots configured by the third time domain configuration information are the first type of synchronization time slots; the first part of synchronization time slots configured by the third time domain configuration information are the second type of synchronization time slots, and the first part of synchronization time slots are indicated by the first information.

41. The method of claim 40, wherein: The first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots.

42. The method according to claim 41, wherein: The first part of synchronization time slots includes the last N synchronization time slots of all synchronization time slots; or, The first part of synchronization time slots includes the first N synchronization time slots of the entire synchronization time slots.

43. The method of claim 40, wherein: The first information includes a first bit map, wherein P bits in the first bit map correspond to P synchronization time slots, the P synchronization time slots are all the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots.

44. The method of claim 40, wherein: The first information includes a first pattern index, where the first pattern index is used to indicate a first pattern among a plurality of patterns, each of the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first part of synchronization time slots.

45. The method of claim 39, wherein: The second part of synchronization time slots configured by the third time domain configuration information are the first type of synchronization time slots, and the first part of synchronization time slots configured by the third time domain configuration information are the second type of synchronization time slots; the first part of synchronization time slots and / or the second part of synchronization time slots are indicated by the first information.

46. ​​The method of claim 45, wherein: The first information is used to indicate the number N of synchronization time slots included in the first part of synchronization time slots and / or the number M of synchronization time slots included in the second part of synchronization time slots.

47. The method of claim 46, wherein: The first part of synchronization time slots includes the last N synchronization time slots of all synchronization time slots, and the second part of synchronization time slots includes the first M synchronization time slots of all synchronization time slots; or, The first part of synchronization time slots includes the first N synchronization time slots of the entire synchronization time slots, and the second part of synchronization time slots includes the last M synchronization time slots of the entire synchronization time slots.

48. The method of claim 45, wherein: The first information includes a second bit map, and the P bits in the second bit map correspond to P synchronization time slots, the P synchronization time slots are the first part of the synchronization time slots and the second part of the synchronization time slots, and the value of the bit is used to indicate whether the synchronization time slot corresponding to the bit belongs to the first part of the synchronization time slots or the second part of the synchronization time slots.

49. The method of claim 45, wherein: The first information includes a second pattern index, where the second pattern index is used to indicate a second pattern among a plurality of patterns, each pattern among the plurality of patterns corresponding to a synchronization time slot pattern corresponding to the first part of synchronization time slots and the second part of synchronization time slots.

50. The method according to any one of claims 39 to 49, wherein: The third time domain configuration information includes at least one of the following: a ninth parameter, wherein the ninth parameter is used to indicate a third synchronization period; a tenth parameter, the tenth parameter being used to indicate the number of synchronization time slots included in the third synchronization period; An eleventh parameter, the eleventh parameter is used to indicate a time slot offset of a first synchronization time slot in a third synchronization period relative to a boundary of the third synchronization period; A twelfth parameter is used to indicate a time slot interval between two adjacent synchronization time slots in a third synchronization period.

51. A method according to any one of claims 33 to 50, wherein: The first configuration information also includes first frequency domain configuration information and second frequency domain configuration information. The first frequency domain configuration information is used to determine a first type of S-SSB frequency domain resources, and the second frequency domain configuration information is used to determine a second type of S-SSB frequency domain resources. The first type of S-SSB frequency domain resources corresponds to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources corresponds to the second type of S-SSB synchronization resources.

52. The method of claim 51, wherein: The first frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources for one or more frequency bands; the second frequency domain configuration information is used to configure the second type of frequency domain resources for one or more frequency bands.

53. The method according to any one of claims 33 to 50, wherein: The first configuration information also includes third frequency domain configuration information, and the third frequency configuration information is used to determine a first type of S-SSB frequency domain resources and a second type of S-SSB frequency domain resources, the first type of S-SSB frequency domain resources correspond to the first type of S-SSB synchronization resources, and the second type of S-SSB frequency domain resources correspond to the second type of S-SSB synchronization resources.

54. The method of claim 53, wherein: The third frequency domain configuration information is used to configure the first type of S-SSB frequency domain resources and the second type of S-SSB frequency domain resources for one or more frequency bands.

55. The method according to any one of claims 51 to 54, wherein: The first type of S-SSB frequency domain resources have a mapping relationship with the first type of synchronization time slots, and the second type of S-SSB frequency domain resources have a mapping relationship with the second type of synchronization time slots.

56. A resource configuration device, applied to a terminal, the device comprising: An acquisition unit is used to acquire first configuration information, wherein the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resource corresponds to a first type of terminal, the second type of S-SSB synchronization resource corresponds to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

57. A resource configuration device, applied to a network device, comprising: A sending unit is used to send first configuration information, wherein the first configuration information is used to determine a first type of S-SSB synchronization resource and a second type of S-SSB synchronization resource; wherein the first type of S-SSB synchronization resource corresponds to a first type of terminal, the second type of S-SSB synchronization resource corresponds to a second type of terminal, and the capability of the first type of terminal is higher than that of the second type of terminal.

58. A communication device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 31, or the method according to any one of claims 32 to 55.

59. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of claims 1 to 31, or a method as described in any one of claims 32 to 55.

60. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 31, or the method according to any one of claims 32 to 55.

61. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 31, or any one of claims 32 to 55.

62. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 31, or any one of claims 32 to 55.

Images