Communication method, terminal, and network side device

By sending configuration information to the terminal in a 5G communication system, flexibly configuring the association relationship between SSB type and PRACH resources, the problem that different SSB types cannot meet the PRACH resource requirements in the prior art is solved, and higher flexibility and efficiency are achieved.

WO2025108454A1PCT designated stage expired Publication Date: 2025-05-30VIVO MOBILE COMM CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/133922
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-11-24
Filing Date
2024-11-22
Publication Date
2025-05-30

AI Technical Summary

Technical Problem

The prior art cannot flexibly configure the association relationship between SSB to PRACH resources in 5G, resulting in the inability to meet the needs of different SSB types for PRACH resources.

Method used

The configuration information is sent to the terminal through the network-side device, so that the terminal can flexibly configure the association relationship between different SSB types and PRACH resources.

Benefits of technology

It realizes the configuration of PRACH resources of different SSB types separately to meet the needs of PRACH resources of different SSB types, and improves the flexibility and efficiency of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024133922_30052025_PF_FP_ABST
    Figure CN2024133922_30052025_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications. Disclosed is a communication method. The communication method in the embodiments of the present application comprises: a terminal receiving first configuration information from a network side device, the first configuration information being used for configuring a physical random access channel (PRACH) resource associated with at least one synchronization signal block (SSB) type; and the terminal determining an association result from an SSB of the at least one SSB type to the PRACH resource according to the first configuration information. The embodiments of the present application can respectively configure PRACH resources associated with different SSB types, so that the association relationship between the SSBs of different SSB types and the PRACH resources can be flexibly configured, which facilitates satisfying requirements of different SSB types for the PRACH resources.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on November 24, 2023, with application number 202311588065.8 and invention name “Communication Method, Terminal and Network Side Equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a communication method, a terminal, and a network-side device. Background Art

[0004] The 5G synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH) and demodulation reference signal (DMRS). At the same time, the cell can configure multiple frequency division multiplexing (FDM) PRACH transmission opportunities (also called PRACH Occasion, abbreviated as RO) in the time domain position of a physical random access channel (PRACH).

[0005] In the related art, the number of ROs associated with all SSBs is the same, and the number of ROs associated with different SSBs cannot be flexibly configured. How to flexibly configure the association relationship between SSBs and ROs needs to be solved urgently. Summary of the Invention

[0006] The embodiments of the present application provide a communication method, a terminal, and a network-side device, which can flexibly configure the association relationship between SSBs of different SSB types and PRACH resources, thereby meeting the requirements of different SSB types for PRACH resources.

[0007] In a first aspect, a communication method is provided, which is executed by a terminal, and the method includes:

[0008] The terminal receives first configuration information from a network side device, where the first configuration information is used to configure a physical random access channel (PRACH) resource associated with at least one synchronization signal block (SSB) type;

[0009] The terminal determines the association result of the SSB of the at least one SSB type to the PRACH resource based on the first configuration information.

[0010] In a second aspect, a communication method is provided, which is performed by a network-side device, and the method includes:

[0011] The network side device determines first configuration information, where the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type;

[0012] The network side device sends the first configuration information to the terminal.

[0013] According to a third aspect, a communication device is provided, including:

[0014] A receiving module, configured to receive first configuration information from a network side device, where the first configuration information is used to configure a physical random access channel (PRACH) resource associated with at least one synchronization signal block (SSB) type;

[0015] A determination module is used to determine the association result of the SSB of at least one SSB type to the PRACH resource based on the first configuration information.

[0016] In a fourth aspect, a communication device is provided, including:

[0017] A determination module, configured to determine first configuration information, where the first configuration information is used to configure a physical random access channel (PRACH) resource associated with at least one synchronization signal block (SSB) type;

[0018] A sending module is used to send the first configuration information to the terminal.

[0019] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0020] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive first configuration information from a network side device, the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type, and the processor is used to determine the association result of the SSB of the at least one SSB type to the PRACH resource based on the first configuration information.

[0021] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0022] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the processor is used to determine first configuration information, the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type, and the communication interface is used to send the first configuration information to the terminal.

[0023] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0024] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0025] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0026] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect or the steps of the method described in the second aspect.

[0027] In an embodiment of the present application, first configuration information is sent to the terminal through a network side device, so that the terminal determines the association result of the SSB of at least one SSB type to the PRACH resource according to the first configuration information, and can configure the PRACH resources associated with different SSB types separately, thereby enabling flexible configuration of the association relationship between the SSB of different SSB types and the PRACH resources, which is conducive to meeting the needs of different SSB types for PRACH resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0029] FIG2 is a schematic diagram of the mapping from SSB to RO;

[0030] FIG3 is another schematic diagram of the mapping of SSB to RO;

[0031] FIG4 is a schematic diagram of the mapping of SSB to RO groups;

[0032] FIG5 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0033] FIG6A is a schematic diagram of an RO group provided in an embodiment of the present application;

[0034] FIG6B is a schematic diagram of another RO group provided in an embodiment of the present application;

[0035] FIG6C is a schematic diagram of another RO group provided in an embodiment of the present application;

[0036] FIG7A is a schematic diagram of an SSB to RO association result provided by an embodiment of the present application;

[0037] FIG7B is a schematic diagram of another SSB to RO association result provided by an embodiment of the present application;

[0038] FIG8A is a schematic diagram of another SSB to RO association result provided by an embodiment of the present application;

[0039] FIG8B is a schematic diagram of another SSB to RO association result provided by an embodiment of the present application;

[0040] FIG8C is a schematic diagram of another SSB to RO association result provided by an embodiment of the present application;

[0041] FIG8D is a schematic diagram of another SSB to RO association result provided in an embodiment of the present application;

[0042] FIG9 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0043] FIG10 is a schematic block diagram of another communication device provided in an embodiment of the present application;

[0044] FIG11 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0045] FIG12 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

[0046] FIG13 is a schematic structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described 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 are within the scope of protection of this application.

[0048] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0049] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0050] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0051] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0052] First, the SSB to RO mapping rules involved in this application are introduced.

[0053] The 5G synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH), and demodulation reference signal (DMRS). Through the cell search process, the wireless device (terminal) obtains the synchronization signal and broadcast signal / channel provided by the base station cell and performs time-frequency domain synchronization with the base station, and obtains the location of the time-frequency resources of the cell deployed by the base station in the frequency and time domains, as well as the physical cell ID.

[0054] The terminal further receives the System Information Block (SIB) 1 by receiving the SSB. SIB1 contains various parameters for initial access. The configuration parameters of the PRACH resources and the mapping rules of the SSB to the RO are configured in the System Information Block (SIB) 1. In the NR system, the cell can configure multiple FDM ROs at a time domain position for transmitting PRACH. At a time, the number of ROs that can perform FDM can be: {1, 2, 4, 8}, which is configured and determined by the high-level parameter msg1-FDM.

[0055] The random access preamble can only be transmitted on the time domain resources configured by the parameter PRACHConfigurationIndex and the frequency domain resources configured by the parameter msg1-FDM. RA ∈{0,1,…,M-1}, where M is equal to the higher-layer parameter msg1-FDM. During initial access, PRACH frequency-domain resources are numbered in ascending order, starting with the lowest-frequency RO resource within the initial active uplink bandwidth part. Otherwise, PRACH frequency-domain resources are numbered in ascending order, starting with the lowest-frequency RO resource within the active uplink bandwidth part. For example, in Figure 2, the number of FDM ROs at a given moment is 8 (msg1-FDM=8), and the RO resources are numbered from low to high frequency, RO#0 to RO#7.

[0056] In the NR system, there is an association between the RO and the actual transmitted SSB. ROs are associated with SSBs in the frequency domain (from low frequency to high frequency) and then in the time domain. An SSB may be associated with multiple consecutive ROs, or multiple SSBs may be associated with a single RO (in this case, different SSBs correspond to different preambles). This is configured by the network using the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0057] For example, oneEighth means that an SSB is associated with 8 consecutive ROs, eight means that 8 SSBs are associated with one RO, and {n4, n8, n12, ...} represents the number of consecutive preambles associated with an SSB on an RO. For example, the value n4 means that the number of consecutive preambles associated with an SSB on an RO is 4, and n8 means that the number of consecutive preambles associated with an SSB on an RO is 4.

[0058] After all SSBs have completed one round of association with the RO, an SSB-RO mapping cycle is formed. An SSB-RO association period may include one or more SSB-RO mapping cycles. An SSB-RO association pattern period may include one or more SSB-RO association periods. The SSB-RO mapping is repeated based on the association pattern period, and the maximum association pattern period is 160ms.

[0059] Typically, a base station can use different beams to transmit different SSBs, with the number of SSBs configured using the ssb-PositionsInBurst parameter. For example, for FR2, the maximum number of SSBs is 64. Based on the strength of the received downlink beam SSB, the terminal selects the RO or RO and preamble combination associated with the SSB with the best signal to send Msg1. The network then determines the SSB selected by the terminal based on the RO or RO and preamble combination received in the preamble and sends Msg2 on the downlink beam corresponding to the SSB, ensuring downlink signal reception quality.

[0060] Taking Figure 2 as an example, the number of FDM ROs at a given moment is 8, and the number of SSBs actually transmitted is 4, namely SSB#0, SSB#1, SSB#2, and SSB#3. Each SSB is associated with two ROs. If the terminal determines to send PRACH / Mg1 on the RO corresponding to SSB#0, the UE selects an RO between RO#0 and RO#1 to send the PRACH.

[0061] Taking Figure 3 as an example, the number of FDM ROs at a given moment is 2, and the number of SSBs actually transmitted is 8, namely SSB#0, SSB#1, ..., SSB#7, with one RO associated with every two SSBs. Each square in Figure 3 corresponds to a RO, not an SSB. The SSB labeled in the square refers to which SSB(s) the RO is associated with. When multiple SSBs share a RO, the preamble sets associated with the multiple SSBs are different, i.e., the same preamble cannot belong to the preamble sets associated with different SSBs at the same time. Taking RO#0 in Figure 3 as an example, RO#0 has a total of 60 preambles, of which preambles with indexes 0 to 29 are associated with SSB#0, and preambles with indexes 30 to 59 are associated with SSB#1.

[0062] Before transmitting a PRACH, the terminal first selects an SSB with an RSRP above a threshold based on the received beam's RSRP. If multiple SSBs have RSRPs above the threshold, the terminal selects any SSB with an RSRP above the threshold. If no SSB has an RSRP above the threshold, the terminal selects an SSB based on the implementation.

[0063] Based on the configuration of the network, the terminal can obtain the correspondence between SSB and RO. After selecting the SSB, the RO corresponding to the selected SSB is used as the RO for sending PRACH / Preamble / Msg1. If the selected SSB is associated with multiple ROs, the terminal can select one of the ROs to send PRACH / Preamble / Msg1. For example: in the example shown in Figure 2, assuming that the terminal selects SSB#1, the terminal can select one from RO#2 and RO#3 to send PRACH / Msg1; in the example shown in Figure 3, if the terminal selects SSB#1, the terminal can select the available RO closest to the current time among the ROs (RO#0 or 4) associated with SSB#1 to send PRACH / Msg1. In the selected RO, the terminal selects a preamble from the preamble set associated with the selected SSB to send PRACH. As shown in Figure 3, one RO is associated with two SSBs. In the available preamble set associated with the SSB in one RO, the preamble will be divided into two subsets, each corresponding to one SSB. The terminal will select a preamble sequence in the preamble subset corresponding to the selected SSB for PRACH / Mg1 transmission.

[0064] Secondly, the RO set determination process when PRACH is repeatedly transmitted is described. PRACH repeated transmission is introduced in Rel-18 to enhance uplink coverage. For PRACH repeated transmission, the terminal needs to repeatedly send the Preamble on multiple ROs at different positions in the time domain associated with the same SSB, and the number of repetitions can be {2, 4, 8}. After the terminal determines the number of PRACH repetitions, it needs to determine the RO set. The number of valid ROs in the RO set is equal to the number of PRACH repetitions. Assuming that the number of PRACH repetitions is N1, the RO group (group) determination rule is: first determine the starting RO of the RO group, and then determine the remaining N1-1 ROs of the RO group. The remaining N1-1 ROs of each RO group are ROs that are associated with the same SSB, the same frequency position, and the same associated Preamble set as the starting RO. For example, in Figure 4, assuming that the number of PRACH repetitions is 2, for SSB#0, the RO group can be determined as follows: the first RO group (1 st RO group), the second RO group (2 st RO group), the third RO group (3 st RO group) and the 4th RO group (4 st RO group).

[0065] In future communication systems (such as 6G communication systems), SSBs may be designed in different formats to effectively support a variety of terminal types, use case service types, and so on. Exemplary terminal types may include, but are not limited to, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), reduced capability (RedCap), machine-type communication (MTC), and Internet of Things (IoT) UEs, among others. Exemplary terminal types may include devices with different capabilities, such as different maximum radio bandwidths, baseband bandwidths, system bandwidths, channel bandwidths, frequency band support, and downlink processing capabilities. Exemplary use case service types include, but are not limited to, use cases providing services such as eMBB, URLLC, virtual reality / augmented reality (VR / AR), IoT, and non-terrestrial networks (NTN). Different SSB types may have different resource requirements. For example, different SSB types are associated with different beams, and each beam has different coverage areas. For example, different SSB types within an NTN cell may cover different areas. For example, SSB#1 may cover the entire province, while SSB#1 / 2 / 3 / 4 may cover four prefecture-level cities within the province. The resource allocation corresponding to SSBs and the mapping of SSBs to resources in related technologies are not flexible enough to meet the resource requirements of different SSB types.

[0066] In view of this, an embodiment of the present application provides a communication method, a terminal and a network-side device, which can separately configure the PRACH resources associated with at least one synchronization signal block SSB type, thereby flexibly configuring the association relationship between SSBs of different SSB types and PRACH resources, which is conducive to meeting the needs of different SSB types for PRACH resources.

[0067] The communication method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0068] FIG5 shows an interactive diagram of a communication method provided by an embodiment of the present application. As shown in FIG5 , the communication method includes at least the following steps 510 and 520:

[0069] 510. The network device sends first configuration information to the terminal, where the first configuration information is used to configure a physical random access channel (PRACH) resource associated with at least one synchronization signal block (SSB) type. Correspondingly, the terminal receives the first configuration information from the network device.

[0070] In the embodiments of the present application, the SSB type may be referred to as the structure or format of a synchronization signal or broadcast channel, or may be referred to as an SSB structure or SSB format, all of which have the same or similar meanings. Optionally, at least two SSBs may be divided into different groups based on the SSB type, with one SSB group being one of the SSB types. For ease of description, the embodiments of the present application collectively refer to the SSB type, SSB structure, or SSB type as the SSB type.

[0071] Exemplarily, different SSB types may be SSB types corresponding to different terminal types, including but not limited to enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), reduced capability (RedCap), machine-type communication (MTC), Internet of Things (IoT) UE and other different terminal types, without limitation. Exemplarily, different SSB types may be SSB types corresponding to terminals with different capabilities, including but not limited to terminals with different maximum radio frequency bandwidth, baseband bandwidth, system bandwidth, channel bandwidth, support for different frequency bands, downlink processing capabilities, etc. Exemplarily, different SSB types may be SSB types corresponding to different use case service types, including but not limited to use cases that provide eMBB, URLLC, AR / VR, IOT, NTN and other service types. Optionally, different SSB types also include SSBs in different frequency bands / different carrier frequencies, SSBs of different service types, and whether the SSBs are configured on demand (on demand) / flexibly (flexible), etc. The embodiments of the present application do not limit this.

[0072] In an embodiment of the present application, the synchronization channel block SSB, that is, the synchronization signal / physical broadcast channel block (SS / PBCH block, SSB), can be any module that includes at least one of the synchronization signal, broadcast signal, broadcast channel (PBCH) and other system message downlink broadcast channels.

[0073] In some embodiments of the present application, a PRACH resource includes a PRACH transmission opportunity (PRACH transmission occasion), also known as a PRACH opportunity (RO). The RO includes at least one preamble. In other embodiments, the PRACH resource includes a preamble.

[0074] Among them, the PRACH resource associated with the SSB type, that is, the PRACH resource associated with at least one SSB in the SSB type. In an embodiment of the present application, the first configuration information is used to configure at least one PRACH resource associated with an SSB type, that is, the first configuration information is used to configure a PRACH resource associated with an SSB type, or to configure PRACH resources associated with multiple SSB types. When the first configuration information is used to configure a PRACH resource associated with an SSB type, multiple first configuration information can be used to configure multiple PRACH resources associated with SSB types. When the first configuration information is used to configure PRACH resources associated with multiple SSB types, one first configuration information can be used to configure multiple PRACH resources associated with SSB types. Among them, multiple includes at least two, that is, two and more than two.

[0075] 520. The terminal determines, based on the first configuration information, an association result of at least one SSB type to a PRACH resource. The association result of the SSB type to the PRACH resource refers to a PRACH resource associated with at least one SSB corresponding to the SSB type.

[0076] Therefore, in the embodiment of the present application, the first configuration information is sent to the terminal through the network side device, so that the terminal determines the association result of the SSB of at least one SSB type to the PRACH resource according to the first configuration information, and can configure the PRACH resources associated with different SSB types separately, thereby being able to flexibly configure the association relationship between the SSB of different SSB types and the PRACH resources, which is conducive to meeting the needs of different SSB types for PRACH resources.

[0077] In some embodiments, the first configuration information includes at least one of an SSB parameter, a PRACH resource set, and an association relationship between SSB and PRACH resources.

[0078] Exemplarily, the SSB parameters may include at least one of the following: the maximum number of SSBs corresponding to the SSB type, the number of SSBs used by the current cell, and at least one SSB used by the current cell.

[0079] Specifically, the maximum number of SSBs corresponding to an SSB type is the maximum number of SSBs under the same SSB type, for example, the maximum number of SSBs under each SSB type involved. As a specific example, the maximum number of SSBs corresponding to SSB type #1 may be 8.

[0080] Optionally, the first configuration information may further include bitmap information, where the bitmap information is used to indicate the number of SSBs used in the current cell and at least one SSB used in the current cell. Exemplarily, the bitmap information is [11110000], which is used to indicate that the SSB type currently uses the first 4 SSBs of 8 SSBs.

[0081] Exemplarily, a PRACH resource set refers to a currently available PRACH resource set, which may include at least one currently available RO resource or preamble resource. Exemplarily, a preamble resource may be an available preamble resource on at least one RO, which is not limited in this application.

[0082] Exemplarily, the association relationship between SSB and PRACH resources is a mapping relationship between SSB and PRACH resources. Optionally, the association relationship between SSB and PRACH resources includes at least one of the following:

[0083] An association relationship between at least one SSB and at least one RO;

[0084] An association relationship between at least one SSB and at least one RO group;

[0085] An association relationship between at least one SSB group and at least one RO group;

[0086] The RO group includes at least one RO; the SSB group includes at least one SSB.

[0087] The association relationship between at least one SSB and at least one RO may include the number of ROs associated with each SSB, or the number of SSBs associated with each RO. The association relationship between at least one SSB and at least one RO group may include the number of RO groups associated with each SSB, or the number of SSBs associated with each RO group. The association relationship between at least one SSB group and at least one RO group may include the number of RO groups associated with each SSB group, or the number of SSB groups associated with each RO group.

[0088] Optionally, the association relationship between the SSB and the PRACH resource also includes the number of preambles associated with at least one SSB on an RO, or the number of preambles associated with at least one SSB group on an RO.

[0089] As an example, the number of ROs or RO groups associated with an SSB or an SSB group is N1, and the number of preambles associated with an SSB or an SSB group on an RO is R. As another example, the number of SSBs associated with an RO or RO group is N2. When N2 ≥ 1, one SSB or multiple SSBs are associated with one RO or RO group. When N2 < 1, one SSB or one SSB group is associated with (1 / N2) ROs or RO groups. N1 or N2 can be configured by the network or specified by the protocol, and this application does not limit this.

[0090] In some embodiments, the first configuration information satisfies at least one of the following:

[0091] Different SSB types correspond to the same SSB parameters, or different SSB types correspond to different SSB parameters;

[0092] Different SSB types correspond to the same PRACH resource set, or different SSB types correspond to different PRACH resource sets;

[0093] Different SSB types correspond to the same association relationship between SSB and PRACH resources, or different SSB types correspond to different association relationships between SSB and PRACH resources.

[0094] That is to say, the first configuration information can configure the same SSB parameters (common SSB parameters) for different SSB types, or configure different SSB parameters for different SSB types; the first configuration information can configure the same PRACH resource set (common PRACH resource set) for different SSB types, or configure different PRACH resource sets for different SSB types; the first configuration information can configure the same SSB to PRACH resource association relationship (common SSB to PRACH resource association relationship) for different SSB types, or configure different SSB to PRACH resource association relationships for different SSB types.

[0095] In some embodiments, different SSBs or different SSB groups are associated with different numbers of ROs, or are associated with different numbers of RO groups, or the associated RO groups include different numbers of ROs.

[0096] In some embodiments, the RO group includes at least one of the following:

[0097] At least two ROs with the same frequency domain position and continuous time domain;

[0098] At least two consecutive ROs determined in the order of frequency domain first and time domain second;

[0099] At least two ROs determined according to predefined rules.

[0100] For example, Figure 6A shows a schematic diagram of RO groups. As shown in Figure 6A, RO group #1 includes two ROs with the same frequency domain position and continuous time domain, and RO group #2 includes four ROs with the same frequency domain position and continuous time domain.

[0101] For example, for at least two consecutive ROs determined in the order of frequency domain first and time domain second, at least two consecutive ROs can be obtained from multiple ROs at the same time domain location based on the frequency domain to form the RO group. Alternatively, when the number of ROs obtained based on the frequency domain is insufficient, at least one RO can be obtained from a subsequent time domain location based on the frequency domain to form the RO group. For example, Figure 6B shows another schematic diagram of an RO group. As shown in Figure 6B, RO group #3 includes four ROs in the continuous frequency domain at time domain location #1 and two ROs in the lower frequency domain at time domain location #2.

[0102] Exemplarily, the above-mentioned predefined rules may include predefined frequency hopping rules. Exemplarily, FIG6C shows another schematic diagram of an RO group. As shown in FIG6C , RO group #4 includes at least two ROs whose time domain positions and frequency domain positions are discontinuous, such as RO #1, RO #2, RO #3, and RO #4.

[0103] Optionally, the number of ROs in the RO group (ie, the size of the RO group) may be configured by the network or predefined by a protocol, which is not limited in this application.

[0104] In some embodiments, in the above step 510, the terminal may receive a system information block SIB1 from a network-side device, where the SIB1 includes the first configuration information.

[0105] Specifically, in this embodiment, different SSB types correspond to the same SIB1, and the same SIB1 includes the configuration of the PRACH resource associated with the SSB type corresponding to at least one (for example, each) SSB type. That is to say, after the terminal selects the SSB type, no matter which SSB type the terminal selects, it can receive the same SIB1 from the network side device. The SIB1 may include first configuration information for configuring a common set of SSB parameters for different SSB types, or configuring different SSB parameters respectively; configuring a set of common PRACH resources for different SSB types, or configuring different PRACH resources respectively; configuring a set of common SSB to PRACH resource associations for different SSB types, or configuring different SSB to PRACH resource associations respectively. By having different SSB types correspond to the same SIB1, it is beneficial to reduce signaling overhead.

[0106] In some embodiments, in the above step 510, the terminal may receive at least one SIB1 from a network-side device, wherein different SIB1s include the first configuration information corresponding to different SSB types.

[0107] Specifically, in this embodiment, different SSB types correspond to different SIB1s, and each SIB1 includes the configuration of the PRACH resources associated with the SSB type corresponding to the corresponding SSB type. That is, after the terminal selects the SSB type, it can receive the corresponding SIB1 corresponding to the selected SSB type, and the SIB1 includes the first configuration information for the SSB type, such as the SSB parameters corresponding to the SSB type, PRACH resources, and the association relationship between the SSB and the PRACH resources. By having different SSB types correspond to SIB1, it is beneficial to flexibly configure the PRACH resources associated with the SSB type.

[0108] In some embodiments, if at least two SSB types correspond to the same PRACH resource set, step 520 may include:

[0109] The terminal maps the SSBs corresponding to at least two SSB types and the association relationships corresponding to at least two SSB types in the same PRACH resource set to obtain the association results of the SSBs of at least two SSB types to the PRACH resources.

[0110] Exemplarily, when at least two SSB types correspond to the same PRACH resource set, the association relationship between the SSBs and the PRACH resources corresponding to the at least two SSB types may be the same or different, and this embodiment of the present application does not limit this. That is, all SSBs of different SSB types may apply the same association relationship between SSBs and PRACH resources, or apply their respective association relationships between SSBs and PRACH resources, and perform mapping in the same PRACH resource set to determine the association relationship between the SSBs and PRACH resources of at least two SSB types.

[0111] In some embodiments, the association relationships corresponding to the at least two SSB types include at least one of the following:

[0112] The number of SSBs corresponding to the nth SSB type (type n) n is a positive integer

[0113] Number of SSBs of the nth SSB type associated with an RO or RO group

[0114] The number of ROs or RO groups associated with an SSB of the nth SSB type

[0115] The number of preambles associated with an SSB of the nth SSB type on an RO

[0116] Among them, in the configuration When and The product of the reciprocals of is an integer, that is is an integer, thus ensuring that the number of ROs required to complete one round of SSB mapping corresponding to the nth SSB type is an integer.

[0117] Optional, and It is not necessary to configure them at the same time. The total number of preambles available on an RO or RO group.

[0118] For example, SSB format #0 and SSB format #1 correspond to the same PRACH resource set. SSB format #0 has a total of 4 SSBs, each SSB is associated with 1 RO, and SSB format #1 has a total of 2 SSBs, each SSB is associated with 2 ROs. Then, the SSB to RO association result can be determined for a total of 6 SSBs corresponding to SSB format #0 and SSB format #1. Figure 7A shows a schematic diagram of the SSB to RO association result determined for a total of 6 SSBs corresponding to SSB format #0 and SSB format #1. Each square represents an RO instead of an SSB, and the SSB marked in the RO refers to the SSB associated with the RO. As shown in Figure 7A, the RO on the first time domain is sequentially associated with the four SSBs in SSB format#0 from low frequency to high frequency, namely format#0 SSB#1, format#0 SSB#2, format#0 SSB#3, and format#0 SSB#4. The RO on the second time domain is sequentially associated with the two SSBs in SSB format#1 from low frequency to high frequency, namely format#1 SSB#1 and format#1 SSB#2 (one SSB is associated with two ROs), and so on.

[0119] For another example, SSB format #0 and SSB format #1 correspond to the same PRACH resource set. SSB format #0 has a total of 4 SSBs, and every 4 SSBs are associated with the same RO. SSB format #1 has a total of 4 SSBs, and every 2 SSBs are associated with the same RO. Then, the SSB to RO association result can be determined for a total of 8 SSBs corresponding to SSB format #0 and SSB format #1. Figure 7B shows another schematic diagram of the SSB to RO association result determined for a total of 8 SSBs corresponding to SSB format #0 and SSB format #1. Each square represents an RO instead of an SSB, and the SSB marked in the RO refers to the SSB associated with the RO. As shown in Figure 7B, an RO at the first time domain position is associated with 4 SSBs in SSB format#0, that is, format#0 SSB#1 / 2 / 3 / 4, an RO at the second time domain position is associated with 2 SSBs in SSB format#1, that is, format#1 SSB#1 / 2, an RO at the third time domain position is associated with 2 SSBs in SSB format#1, that is, format#1 SSB#3 / 4, and so on.

[0120] Optionally, in Figure 7B , there are 64 preambles on each RO. For SSB format #0, each SSB is associated with 16 preambles on one RO, and for SSB format #1, each SSB is associated with 32 preambles on one RO. All SSBs in SSB format #0 and SSB format #1 are mapped to ROs or preambles in sequence.

[0121] In some embodiments, a first index can be determined in sequence for all SSBs corresponding to at least two SSB types, and a first order can be determined for each RO in the PRACH resource set; then, according to the first index and the first order, the SSBs corresponding to at least two SSB types are mapped to the RO in the PRACH resource set to obtain the association results of the SSBs to the PRACH resources for all SSBs corresponding to at least two SSB types.

[0122] For example, only the number of ROs associated with each SSB type is configured, such as When an SSB All preambles on the RO are associated. At this time, the mapping rule from SSB to RO can be as described above, that is, all SSBs of different types jointly determine the index, all ROs determine the order, and then each SSB is mapped to a continuous ROs, of which The number of ROs associated with type n.

[0123] For example, SSB format#0 and SSB format#1 correspond to the same PRACH resource set. SSB format#0 has a total of 4 SSBs, each SSB is associated with 1 RO, and SSB format#1 has a total of 2 SSBs, each SSB is associated with 2 ROs. The PRACH resource set may include 16 ROs. Then, the indexes of the 6 SSBs may be determined in sequence, such as SSB index#0 / 1 / 2 / 3 / 4 / 5, and the order of the PRACH resource set may be determined in sequence, such as RO#0 / 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9 / 10 / 11 / 12 / 13 / 14 / 15. The association result of SSB to RO may be determined jointly for the 6 SSBs on the PRACH resource set. Figure 8A shows a schematic diagram of jointly determining the association result of SSB to RO for SSB index#0 / 1 / 2 / 3 / 4 / 5. Each square represents an RO instead of an SSB, and the SSB marked in the RO refers to the SSB associated with the RO. As shown in FIG8A , RO#0 to RO#3 are associated with SSB indexes 0 / 1 / 2 / 3, and RO#4 to RO#7 are associated with SSB indexes #4 / 5, with one SSB associated with two ROs. RO#8 to RO#15 are associated with the same SSBs as RO#0 to RO#7.

[0124] For another example, SSB format#0 and SSB format#1 correspond to the same PRACH resource set, and each SSB is associated in units of RO groups. An RO group is a group of ROs with the same frequency domain position and continuous time domain. The sizes of RO groups associated with different SSBs can be different. Among them, each SSB is associated with all preambles on the RO. SSB format#0 has a total of 4 SSBs, namely SSB#1, SSB#2, SSB#3, and SSB#4. Each SSB is associated with 1 RO group, and the size of the RO group is 2 (i.e., one RO group contains 2 ROs); SSB format#1 has a total of 4 SSBs, namely SSB#5, SSB#6, SSB#7, and SSB#8. Each SSB is associated with 1 RO group, and the size of the RO group is 4 (i.e., one RO group contains 4 ROs). Then, the association results of SSBs to RO groups can be determined for a total of 8 SSBs corresponding to SSB format#0 and SSB format#1. Figure 8B shows a schematic diagram of the SSB-to-RO association results determined by a total of eight SSBs corresponding to SSB format #0 and SSB format #1. As shown in Figure 8B, the RO group in the first time domain is associated with the four SSBs in SSB format #0, namely, SSB #1, SSB #2, SSB #3, and SSB #4, from low frequency to high frequency. The RO group in the second time domain is associated with the four SSBs in SSB format #1, namely, SSB #5, SSB #6, SSB #7, and SSB #8, from low frequency to high frequency, and so on.

[0125] For another example, SSB format#0 and SSB format#1 correspond to the same PRACH resource set, and each SSB group (i.e., multiple SSBs) are associated in units of RO groups. An RO group is a group of ROs with the same frequency domain position and continuous time domain. The sizes of RO groups associated with different SSB groups can be different. SSB format#0 has a total of 4 SSBs, namely SSB#1, SSB#2, SSB#3, and SSB#4. Each SSB is associated with 1 RO group, and the size of the RO group is 2 (i.e., one RO group contains 2 ROs); SSB format#1 has a total of 4 SSBs, namely SSB#5, SSB#6, SSB#7, and SSB#8. Each SSB is associated with 1 RO group, and the size of the RO group is 4 (i.e., one RO group contains 4 ROs). Then, the association result of the SSB to RO group can be determined for a total of 8 SSBs corresponding to SSB format#0 and SSB format#1. Figure 8C shows a schematic diagram of the SSB to RO association result determined for a total of 8 SSBs corresponding to SSB format#0 and SSB format#1. As shown in Figure 8C , RO group #1 is associated with the four SSBs in SSB format #0, namely, SSB #1, SSB #2, SSB #3, and SSB #4. RO group #2 is associated with the first two SSBs in SSB format #1, namely, SSB #5 and SSB #6. RO group #2 is associated with the last two SSBs in SSB format #1, namely, SSB #7 and SSB #8, and so on. The same SSB is associated with the same preamble on each RO within an RO group, while different SSBs are associated with different preambles on the same RO.

[0126] In some embodiments, a second index can be determined in sequence for all SSBs corresponding to at least two SSB types, a second order can be determined for each RO in the PRACH resource set, and a third order can be determined for the preamble code on each RO; then, according to the second index, the second order and the third order, all SSBs corresponding to at least two SSB types are mapped to the preamble code of each RO in the PRACH resource set to obtain the association result of SSB to PRACH resources for all SSBs corresponding to at least two SSB types.

[0127] For example, only the number of preambles associated with each SSB type is configured, such as When the SSB is mapped to the RO, the mapping rule can be as described above, that is, all SSBs of different types jointly determine the index, all ROs determine the order, and the preamble on each RO determines the order, and then each SSB is mapped to consecutive ROs in the order of preamble first and then RO. preamble, where The number of preambles associated with type n.

[0128] For example, SSB format#0 and SSB format#1 correspond to the same PRACH resource set. SSB format#0 has a total of 4 SSBs, and each SSB is associated with 64 preambles on an RO. SSB format#1 has a total of 2 SSBs, and each SSB is associated with 32 preambles on one RO. The PRACH resource set may include 16 ROs, and each RO may include 64 preambles. Then, the indexes of the 6 SSBs may be determined in sequence, such as SSB index#0 / 1 / 2 / 3 / 4 / 5, and the order of the PRACH resource set may be determined in sequence, such as RO#0 / 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9 / 10 / 11 / 12 / 13 / 14 / 15, and the order of the preambles on all ROs may be determined. The association result of SSB to RO may be determined jointly for the 6 SSBs on the PRACH resource set. Figure 8D shows a schematic diagram of jointly determining the association result of SSB to RO for SSB index#0 / 1 / 2 / 3 / 4 / 5. Each square represents a RO, not an SSB. The SSB marked in the RO refers to the SSB associated with that RO. As shown in Figure 8D, the 64 preambles on each RO from RO#0 to RO#3 are associated with SSB indexes 0 / 1 / 2 / 3, respectively. The 64 preambles on RO#4 are associated with SSB indexes 4 / 5, respectively. RO#5 to RO#9 are associated with the same SSBs as RO#0 to RO#4, and so on.

[0129] In some embodiments, the association result of the SSB to the RO satisfies at least one of the following:

[0130] SSB associates all preambles on a RO;

[0131] The preamble code associated with the same SSB on each RO in an RO group is the same; the RO group includes at least one RO;

[0132] Different SSBs are associated with different preambles on the same RO.

[0133] For example, when one SSB is associated with at least one RO or RO group, the SSB is associated with all preambles on one RO. As a specific example, in Figures 7A, 8A, and 8B, one SSB is associated with all preambles on one RO.

[0134] For example, when an SSB group is associated with an RO group, or when an SSB group is associated with a single RO, the preamble associated with each RO within an RO group for the same SSB is the same, or different SSBs on the same RO have different preambles associated with them. As specific examples, in Figures 8C and 8D , the preamble associated with each RO within an RO group for the same SSB is the same, or different SSBs on the same RO have different preambles associated with them. This helps avoid resource conflicts between different SSBs on a single RO, improves the detection performance of the receiving end during repeated PRACH transmissions, and enhances signal transmission reliability.

[0135] In some embodiments, at least one of the mapping cycle, association period and association pattern period of SSB to PRACH resources can also be determined, where the mapping period is a period for associating all SSBs of at least two SSB types to PRACH resources in one round, the association period includes at least one mapping period, and the association pattern period includes at least one association period.

[0136] Here, the mapping period, association period or association mode period is a common value of the time period for all SSBs of different SSB types to be associated with ROs. For example, the mapping period from SSB to RO (or RO group) is: or or

[0137] For example, in Figures 7A, 7B, 8A, 8B, 8C, and 8D above, the mapping period is the period for associating all SSBs in SSB format #0 and SSB format #1 with an RO or RO group for one round. The association period may include one or more mapping periods, and the association mode period may include one or more association periods. Optionally, the association mode period is the period for forming a repeatable pattern between the SSB and the RO. Optionally, the association mode period does not exceed the maximum time specified in the protocol.

[0138] Optionally, the first time window may be determined based on at least one of a mapping period, an association period, and an association mode period; wherein the first time window is an integer multiple of the mapping period, the association period, or the association mode period. The terminal may send a signal to the network-side device within the first time window based on the association result of at least two SSB types of SSBs to PRACH resources. Exemplarily, the signal is PRACH. When the first time window is exceeded, the terminal does not send a signal. Here, by setting the terminal to send a signal in the first time window, it can be helpful to ensure that there are sufficient PRACH resources within the window for the terminal to select to send a signal.

[0139] In some embodiments, if at least two SSB types correspond to different PRACH resource sets, step 520 may include:

[0140] The terminal maps the SSBs corresponding to at least two SSB types and the association relationship corresponding to at least two SSB types in the PRACH resource sets corresponding to at least two SSB types, and obtains the association results of the SSBs of at least two SSB types to the PRACH resources.

[0141] That is to say, at least two SSB types can correspond to different PRACH resource sets, respectively, and correspond to the association relationship between SSB and PRACH resources, so at least two SSB types independently determine the association results between SSB and PRACH resources, that is, according to their respective association relationships, they are mapped in their respective corresponding PRACH resource sets to obtain the association results of SSB to PRACH resources of at least two SSB types.

[0142] For example, the mapping period of each SSB type to RO (or RO group) is or or

[0143] In some embodiments, the terminal may further send a signal to the network-side device within at least two second time windows corresponding to the at least two SSB types, based on the association results of the SSBs of the at least two SSB types to the PRACH resources. That is, each SSB type corresponds to its own second time window, and the terminal selects a corresponding associated RO within the time window corresponding to each SSB type to send a signal to the network-side device.

[0144] In some embodiments, at least one of a mapping period, an association period, and an association mode period for SSBs of at least two SSB types to PRACH resources may be determined separately, wherein the mapping period for each SSB type is a period for associating all SSBs of each SSB type to PRACH resources for one round, the association period includes at least one mapping period, and the association mode period includes at least one association period. Then, a second time window for each SSB type may be determined based on at least one of the mapping period, association period, and association mode period for each SSB type.

[0145] In some embodiments, the second time window of each SSB type is an integer multiple of the mapping period or association period or association mode period corresponding to each SSB type.

[0146] In some embodiments, the at least two second time windows are respectively determined based on the maximum mapping period, association period, or association mode period of the at least two SSB types. In this case, the second time windows corresponding to the at least two SSB types are equal.

[0147] Therefore, by setting the terminal to send signals in the second time window, it can be helpful to ensure that each SSB type has sufficient PRACH resources in the window for the terminal to choose to send signals.

[0148] In some embodiments, the terminal may further receive second configuration information from a network-side device, where the second configuration information is used to update at least one of the SSB parameters, PRACH resource sets, and association relationships corresponding to at least one SSB type. Specifically, the second configuration information is similar to the first configuration information described above, and reference may be made to the relevant descriptions above, which will not be repeated here. Correspondingly, the terminal uses the updated SSB parameters, PRACH resource sets, and association relationships to determine the association result of the SSB corresponding to the SSB type to the PRACH resource.

[0149] Therefore, by sending the second configuration information to the terminal, dynamic configuration of PRACH resources associated with at least one SSB type can be achieved.

[0150] In some embodiments, the second configuration information can perform activation / deactivation configuration of the PRACH resource set and the association relationship between SSB and PRACH resources for at least some SSB types, thereby updating the association relationship between the PRACH resource set and SSB and PRACH resources.

[0151] In some embodiments, the terminal may receive signaling from the network-side device, the signaling being used to indicate the second configuration information. Exemplarily, the signaling includes at least one of RRC, physical downlink control channel PDCCH, and medium access control (MAC) control element (CE).

[0152] In some embodiments, when the SSB type of the terminal changes, such as when the terminal switches from one SSB type to another SSB type, or a portion of the current SSB is deactivated, or a new portion of the SSB is activated, the terminal applies the SSB parameters, PRACH resources, and the corresponding association relationship between the SSB and the PRACH resources corresponding to the switched SSB type to determine the association result of the SSB to the PRACH resources of the switched SSB type. Here, the SSB parameters, PRACH resources, and the corresponding association relationship between the SSB and the PRACH resources corresponding to the switched SSB type are the updated (e.g., latest) configurations.

[0153] As an example, when different SSB types correspond to different service types, such as SSB format #1 corresponds to eMBB service and SSB format #2 corresponds to NTN service. When the terminal switches from eMBB service to NTN service, the terminal chooses to switch the SSB type from SSB format #1 to SSB format #2, and uses the corresponding SSB to RO association relationship in the PRACH resource set corresponding to SSB format #2, selects the PRACH resource to send a message (such as Msg1) to request the service corresponding to NTN.

[0154] As another example, there are a total of 8 SSBs. The SSB currently used by the terminal can be indicated by a bitmap, where 1 indicates that the corresponding SSB is in use, and 0 indicates that the corresponding SSB is not in use. At time t1, the bitmap can be indicated as [11110000], that is, the first 4 SSBs are used. Then, when the terminal determines the association relationship between SSB and RO, it only needs to consider the first 4 SSBs. At the next time t2, the bitmap is indicated as [11111111], that is, the last 4 SSBs are activated, so that the terminal uses all 8 SSBs. Then, the terminal must apply the SSB to RO association relationship corresponding to the 8 SSBs and re-determine the SSB to RO association result.

[0155] Therefore, the embodiment of the present application can determine the association result of the SSB of the updated SSB type to the PRACH resource when the SSB type is updated.

[0156] The communication method provided in the embodiment of the present application can be executed by a communication device. In the embodiment of the present application, the communication device provided in the embodiment of the present application is described by taking the communication method executed by the communication device as an example.

[0157] FIG9 shows a schematic block diagram of a communication device 900 provided in an embodiment of the present application. For example, the communication device 900 may be a terminal. As shown in FIG9 , the communication device 900 includes a receiving module 910 and a determining module 920 .

[0158] A receiving module 910 is configured to receive first configuration information from a network-side device, where the first configuration information is used to configure a physical random access channel (PRACH) resource associated with at least one synchronization signal block (SSB) type;

[0159] The determination module 920 is used to determine the association result of the SSB of the at least one SSB type to the PRACH resource based on the first configuration information.

[0160] In some embodiments, the first configuration information includes at least one of an SSB parameter, a PRACH resource set, and an association relationship between SSB and PRACH resources.

[0161] In some embodiments, the first configuration information satisfies at least one of the following:

[0162] Different SSB types correspond to the same SSB parameters, or different SSB types correspond to different SSB parameters;

[0163] Different SSB types correspond to the same PRACH resource set, or different SSB types correspond to different PRACH resource sets;

[0164] Different SSB types correspond to the same association relationship, or different SSB types correspond to different association relationships.

[0165] In some embodiments, the SSB parameter includes at least one of the following:

[0166] The maximum number of SSBs corresponding to the SSB type, the number of SSBs used by the current cell, and at least one SSB used by the current cell.

[0167] In some embodiments, the association relationship between the SSB and the PRACH resource includes at least one of the following:

[0168] An association relationship between at least one SSB and at least one PRACH transmission opportunity RO;

[0169] An association relationship between at least one SSB and at least one RO group;

[0170] An association relationship between at least one SSB group and at least one RO group;

[0171] The RO group includes at least one RO; the SSB group includes at least one SSB.

[0172] In some embodiments, different SSBs or different SSB groups are associated with different numbers of ROs, or are associated with different numbers of RO groups, or the associated RO groups include different numbers of ROs.

[0173] In some embodiments, the RO group includes at least one of the following:

[0174] At least two ROs with the same frequency domain position and continuous time domain;

[0175] At least two consecutive ROs determined in the order of frequency domain first and time domain second;

[0176] At least two ROs determined according to predefined rules.

[0177] In some embodiments, if at least two of the SSB types correspond to the same PRACH resource set, the determination module 920 is specifically configured to:

[0178] According to the SSBs corresponding to at least two of the SSB types and the association relationships corresponding to at least two of the SSB types, mapping is performed in the same PRACH resource set to obtain the association results of the SSBs of at least two of the SSB types to the PRACH resources.

[0179] In some embodiments, the association relationships corresponding to at least two of the SSB types include at least one of the following:

[0180] The number of SSBs corresponding to the nth SSB type n is a positive integer

[0181] The number of SSBs of the nth SSB type associated with an RO or RO group

[0182] The number of ROs or RO groups associated with an SSB of the nth SSB type

[0183] The number of preambles associated with an SSB of the nth SSB type on an RO

[0184] In some embodiments, the and The product of the reciprocals of is an integer.

[0185] In some embodiments, the determining module 920 is specifically configured to:

[0186] determining a first index for all SSBs corresponding to at least two of the SSB types in sequence, and determining a first order for each RO in the PRACH resource set;

[0187] According to the first index and the first order, all SSBs corresponding to the at least two SSB types are mapped to the RO in the PRACH resource set to obtain the SSB to PRACH resource association results of all SSBs corresponding to the at least two SSB types.

[0188] In some embodiments, the determining module 920 is specifically configured to:

[0189] determining a second index for all SSBs corresponding to at least two of the SSB types in sequence;

[0190] Determining a second order for each RO in the PRACH resource set, and determining a third order for the preamble on each RO;

[0191] According to the second index, the second order and the third order, all SSBs corresponding to the at least two SSB types are mapped to the preamble code of each RO in the PRACH resource set to obtain the association result of the SSB to PRACH resources of all SSBs corresponding to the at least two SSB types.

[0192] In some embodiments, the determination module 920 is further configured to:

[0193] Determining at least one of a mapping period, an association period, and an association mode period from an SSB to a PRACH resource, wherein the mapping period is a period for associating all SSBs of at least two of the SSB types to the PRACH resource for one round, the association period includes at least one of the mapping periods, and the association mode period includes at least one of the association periods;

[0194] A first time window is determined according to at least one of the mapping period, the association period, and the association mode period; wherein the first time window is an integer multiple of the mapping period, the association period, or the association mode period.

[0195] The communication device 900 further includes a sending unit configured to:

[0196] According to the association results of at least two SSB types to PRACH resources, a signal is sent to the network side device within the first time window.

[0197] In some embodiments, if at least two of the SSB types correspond to different PRACH resource sets, the determination module 920 is specifically configured to:

[0198] According to the SSBs corresponding to at least two of the SSB types and the association relationships corresponding to at least two of the SSB types, mapping is performed in the PRACH resource sets corresponding to at least two of the SSB types to obtain association results from the SSBs of at least two of the SSB types to the PRACH resources.

[0199] In some embodiments, the sending module is further configured to:

[0200] According to the association results of the SSBs of at least two of the SSB types to the PRACH resources, a signal is sent to the network side device within at least two second time windows corresponding to the at least two SSB types respectively.

[0201] In some embodiments, the determination module 920 is further configured to:

[0202] respectively determining at least one of a mapping period, an association period, and an association mode period of at least two SSB types to PRACH resources, wherein the mapping period of each SSB type is a period for associating all SSBs of each SSB type to PRACH resources for one round, the association period includes at least one mapping period, and the association mode period includes at least one association period;

[0203] The second time window of each of the SSB types is determined according to at least one of the mapping period, the association period and the association mode period of each of the SSB types.

[0204] In some embodiments, the second time window of each of the SSB types is an integer multiple of the mapping period or the association period or the association mode period corresponding to each of the SSB types.

[0205] In some embodiments, the at least two second time windows are respectively determined according to the maximum mapping period, association period or association mode period of the at least two SSB types.

[0206] In some embodiments, the PRACH resource includes an RO or a preamble.

[0207] In some embodiments, the one RO includes at least one of the preamble codes, and the association result satisfies at least one of the following:

[0208] SSB associates all preambles on a RO;

[0209] The preamble code associated with the same SSB on each RO in an RO group is the same; the RO group includes at least one RO;

[0210] Different SSBs are associated with different preambles on the same RO.

[0211] In some embodiments, the receiving module 910 is specifically configured to:

[0212] A system information block SIB1 is received from the network side device, where the SIB1 includes the first configuration information.

[0213] In some embodiments, the receiving module 910 is specifically configured to:

[0214] Receive at least one SIB1 from the network side device, wherein different SIB1s include the first configuration information corresponding to different SSB types.

[0215] In some embodiments, the receiving module 910 is further configured to:

[0216] Receive second configuration information from the network side device, where the second configuration information is used to update at least one of the SSB parameters, PRACH resource sets and association relationships corresponding to the at least one SSB type.

[0217] In some embodiments, the receiving module 910 is specifically configured to:

[0218] Receive signaling from the network side device, where the signaling is used to indicate the second configuration information; the signaling includes at least one of RRC, physical downlink control channel PDCCH, and media access control MAC control element CE.

[0219] The communication device 900 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0220] The communication device 900 provided in the embodiment of the present application can implement each process implemented by the terminal in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0221] FIG10 shows a schematic block diagram of a communication device 1000 provided in an embodiment of the present application. For example, the communication device 1000 may be a network-side device. As shown in FIG10 , the communication device 1000 includes a determination module 1010 and a sending module 1020.

[0222] A determination module 1010 is configured to determine first configuration information, where the first configuration information is used to configure a physical random access channel (PRACH) resource associated with at least one synchronization signal block (SSB) type;

[0223] The sending module 1020 is configured to send the first configuration information to the terminal.

[0224] In some embodiments, the first configuration information includes at least one of an SSB parameter, a PRACH resource set, and an association relationship between SSB and PRACH resources.

[0225] In some embodiments, the first configuration information satisfies at least one of the following:

[0226] Different SSB types correspond to the same SSB parameters, or different SSB types correspond to different SSB parameters;

[0227] Different SSB types correspond to the same PRACH resource set, or different SSB types correspond to different PRACH resource sets;

[0228] Different SSB types correspond to the same association relationship, or different SSB types correspond to different association relationships.

[0229] In some embodiments, the SSB parameter includes at least one of the following:

[0230] The maximum number of SSBs corresponding to the SSB type, the number of SSBs used by the current cell, and at least one SSB used by the current cell.

[0231] In some embodiments, the association relationship between the SSB and the PRACH resource includes at least one of the following:

[0232] An association relationship between at least one SSB and at least one PRACH transmission opportunity RO;

[0233] An association relationship between at least one SSB and at least one RO group;

[0234] An association relationship between at least one SSB group and at least one RO group;

[0235] The RO group includes at least one RO; the SSB group includes at least one SSB.

[0236] In some embodiments, different SSBs or different SSB groups are associated with different numbers of ROs, or are associated with different numbers of RO groups, or the associated RO groups include different numbers of ROs.

[0237] In some embodiments, the RO group includes at least one of the following:

[0238] At least two ROs with the same frequency domain position and continuous time domain;

[0239] At least two consecutive ROs determined in the order of frequency domain first and time domain second;

[0240] At least two ROs determined according to predefined rules.

[0241] In some embodiments, the PRACH resource includes an RO or a preamble.

[0242] In some embodiments, the sending module 1020 is specifically configured to:

[0243] A system information block SIB1 is sent to the terminal, where the SIB1 includes the first configuration information.

[0244] In some embodiments, the sending module 1020 is specifically configured to:

[0245] The network side device sends at least one SIB1 to the terminal, wherein different SIB1s include the first configuration information corresponding to different SSB types.

[0246] In some embodiments, the sending module 1020 is further configured to:

[0247] Send second configuration information to the terminal, where the second configuration information is used to update at least one of the SSB parameters, PRACH resource sets and association relationships corresponding to the at least one SSB type.

[0248] In some embodiments, the sending module 1020 is specifically configured to:

[0249] Send signaling to the terminal, where the signaling is used to indicate the second configuration information; the signaling includes at least one of RRC, physical downlink control channel PDCCH, and media access control MAC control element CE.

[0250] The communication device 1000 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a network-side device, or it can be a device other than a network-side device. For example, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above. Other devices can be servers, network attached storage (NAS), etc., and are not specifically limited in the embodiment of the present application.

[0251] The communication device 1000 provided in the embodiment of the present application can implement each process implemented by the network side device in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0252] As shown in Figure 11, an embodiment of the present application further provides a communication device 1100, including a processor 1101 and a memory 1102. The memory 1102 stores a program or instruction that can be run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instruction, when executed by the processor 1101, implements the various steps performed by the terminal in the above-mentioned communication method embodiment, and can achieve the same technical effect. When the communication device 1100 is a network-side device, the program or instruction, when executed by the processor 1101, implements the various steps performed by the network-side device in the above-mentioned communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0253] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps performed by the terminal in the method embodiment shown in FIG5 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG12 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0254] The terminal 1200 includes but is not limited to: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209 and at least some of the components of the processor 1210.

[0255] Those skilled in the art will appreciate that the terminal 1200 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1210 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG12 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0256] It should be understood that in an embodiment of the present application, the input unit 1204 may include a graphics processing unit (GPU) 12041 and a microphone 12042, and the graphics processor 12041 processes image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1206 may include a display panel 12061, and the display panel 12061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1207 includes a touch panel 12071 and at least one of other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include two parts: a touch detection device and a touch controller. Other input devices 12072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0257] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1201 may transmit the data to the processor 1210 for processing. Furthermore, the RF unit 1201 may send uplink data to the network-side device. Typically, the RF unit 1201 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0258] The memory 1209 can be used to store software programs or instructions and various data. The memory 1209 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1209 may include a volatile memory or a non-volatile memory. 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 random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1209 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0259] Processor 1210 may include one or more processing units. Optionally, processor 1210 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1210.

[0260] Among them, the radio frequency unit 1201 is used to receive first configuration information from a network side device, and the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type.

[0261] Processor 1210 is used to determine the association result of the SSB of at least one SSB type to the PRACH resource based on the first configuration information.

[0262] In an embodiment of the present application, first configuration information is sent to the terminal through a network side device, so that the terminal determines the association result of the SSB of at least one SSB type to the PRACH resource according to the first configuration information, and can configure the PRACH resources associated with different SSB types separately, thereby being able to flexibly configure the association relationship between the SSB of different SSB types and the PRACH resources, which is conducive to meeting the needs of different SSB types for PRACH resources.

[0263] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described here.

[0264] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps performed by the network-side device in the method embodiment shown in FIG5 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0265] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 13, network-side device 1300 includes an antenna 131, a radio frequency device 132, a baseband device 133, a processor 134, and a memory 135. Antenna 131 is connected to radio frequency device 132. In the uplink direction, radio frequency device 132 receives information via antenna 131 and sends the received information to baseband device 133 for processing. In the downlink direction, baseband device 133 processes the information to be transmitted and sends it to radio frequency device 132. Radio frequency device 132 processes the received information and then sends it through antenna 131.

[0266] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 133 , which includes a baseband processor.

[0267] The baseband device 133 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 13, one of the chips is, for example, a baseband processor, which is connected to the memory 135 through a bus interface to call the program in the memory 135 to execute the network device operations shown in the above method embodiment.

[0268] The network side device may further include a network interface 136 , which is, for example, a Common Public Radio Interface (CPRI).

[0269] Specifically, the network side device 1300 of the embodiment of the present application also includes: instructions or programs stored in the memory 135 and can be run on the processor 134. The processor 134 calls the instructions or programs in the memory 135 to execute the steps performed by the network side device in the method executed by each module shown in Figure 5, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0270] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes corresponding to the terminal of the above-mentioned communication method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0271] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0272] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes corresponding to the network side device of the above-mentioned communication method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0273] The processor is the processor in the network-side device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0274] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes corresponding to the terminal of the above-mentioned communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0275] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes corresponding to the network side device of the above-mentioned communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0277] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes corresponding to the terminal of the above-mentioned communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0278] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes corresponding to the network-side device of the above-mentioned communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0279] An embodiment of the present application also provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps executed by the terminal in the communication method described above, and the network side device can be used to execute the steps executed by the network side device in the communication method described above.

[0280] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0281] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0282] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A communication method, wherein: include: The terminal receives first configuration information from a network side device, where the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type; The terminal determines the association result of the SSB of the at least one SSB type to the PRACH resource based on the first configuration information.

2. The method according to claim 1, wherein: The first configuration information includes at least one of an SSB parameter, a PRACH resource set, and an association relationship from SSB to PRACH resources.

3. The method according to claim 2, wherein: The first configuration information satisfies at least one of the following: Different SSB types correspond to the same SSB parameters, or different SSB types correspond to different SSB parameters; Different SSB types correspond to the same PRACH resource set, or different SSB types correspond to different PRACH resource sets; Different SSB types correspond to the same association relationship, or different SSB types correspond to different association relationships.

4. The method according to claim 2 or 3, wherein: The SSB parameter includes at least one of the following: The maximum number of SSBs corresponding to the SSB type, the number of SSBs used by the current cell, and at least one SSB used by the current cell.

5. The method according to any one of claims 2 to 4, wherein: The association relationship between the SSB and the PRACH resource includes at least one of the following: An association relationship between at least one SSB and at least one PRACH transmission opportunity RO; An association relationship between at least one SSB and at least one RO group; An association relationship between at least one SSB group and at least one RO group; The RO group includes at least one RO; the SSB group includes at least one SSB.

6. The method according to claim 5, wherein: Different SSBs or different SSB groups are associated with different numbers of ROs, or are associated with different numbers of RO groups, or the associated RO groups include different numbers of ROs.

7. The method according to any one of claims 2 to 6, wherein: If at least two of the SSB types correspond to the same PRACH resource set, the terminal determines, according to the first configuration information, an association result of the SSB of the at least one SSB type to the PRACH resource, including: The terminal maps the SSBs corresponding to at least two of the SSB types and the association relationships corresponding to at least two of the SSB types in the same PRACH resource set to obtain association results from the SSBs of at least two of the SSB types to the PRACH resources.

8. The method according to claim 7, wherein: The association relationships corresponding to at least two of the SSB types include at least one of the following: The number of SSBs corresponding to the nth SSB type n is a positive integer The number of SSBs of the nth SSB type associated with an RO or RO group The number of ROs or RO groups associated with an SSB of the nth SSB type The number of preambles associated with an SSB of the nth SSB type on an RO 9. The method according to claim 8, wherein: Said and The product of the reciprocals of is an integer.

10. The method according to any one of claims 7 to 9, wherein: The terminal performs mapping in the same PRACH resource set according to the SSBs corresponding to at least two of the SSB types and the association relationships respectively corresponding to at least two of the SSB types, and obtains association results of at least two of the SSB types to the PRACH resources, including: Determine a first index for all SSBs corresponding to at least two of the SSB types in sequence, and determine a first order for each RO in the PRACH resource set; According to the first index and the first order, all SSBs corresponding to the at least two SSB types are mapped to the RO in the PRACH resource set to obtain the association result of the SSB to PRACH resources of all SSBs corresponding to the at least two SSB types.

11. The method according to any one of claims 7 to 9, wherein: The terminal performs mapping in the same PRACH resource set according to the SSBs corresponding to at least two of the SSB types and the association relationships respectively corresponding to at least two of the SSB types, and obtains association results of at least two of the SSB types to the PRACH resources, including: Determine a second index for all SSBs corresponding to at least two of the SSB types in sequence; Determine a second order for each RO in the PRACH resource set, and determine a third order for the preamble on each RO; According to the second index, the second order and the third order, all SSBs corresponding to the at least two SSB types are mapped to the preamble code of each RO in the PRACH resource set to obtain the association result of the SSB to PRACH resources of all SSBs corresponding to the at least two SSB types.

12. The method according to any one of claims 7 to 11, wherein: Also includes: Determine at least one of a mapping period, an association period, and an association mode period from an SSB to a PRACH resource, wherein the mapping period is a period for associating all SSBs of at least two of the SSB types to a PRACH resource for one round, the association period includes at least one of the mapping periods, and the association mode period includes at least one of the association periods; Determine a first time window according to at least one of the mapping period, the association period and the association mode period; wherein the first time window is an integer multiple of the mapping period or the association period or the association mode period; The terminal sends a signal to the network side device within the first time window based on the association result of at least two SSBs of the SSB type to the PRACH resources.

13. The method according to any one of claims 2 to 6, wherein: If at least two of the SSB types correspond to different PRACH resource sets, the terminal determines, according to the first configuration information, an association result of the SSB of the at least one SSB type to the PRACH resource, including: The terminal maps the PRACH resource sets corresponding to at least two SSB types according to the SSBs corresponding to at least two of the SSB types and the association relationships corresponding to at least two of the SSB types, and obtains the association results of the SSBs of at least two of the SSB types to the PRACH resources.

14. The method according to claim 13, wherein: Also includes: The terminal sends a signal to the network side device within at least two second time windows corresponding to at least two SSB types respectively according to the association result of the SSB of at least two SSB types to the PRACH resource.

15. The method according to claim 14, wherein: Also includes: Respectively determine at least one of a mapping period, an association period, and an association mode period of at least two SSB types of the SSB to a PRACH resource, wherein the mapping period of each of the SSB types is a period for associating all SSBs of each of the SSB types to a round of PRACH resources, the association period includes at least one of the mapping periods, and the association mode period includes at least one of the association periods; The second time window of each of the SSB types is determined according to at least one of the mapping period, the association period and the association mode period of each of the SSB types.

16. The method according to claim 15, wherein: The second time window of each of the SSB types is an integer multiple of the mapping period or the association period or the association mode period corresponding to each of the SSB types.

17. The method according to claim 15, wherein: The at least two second time windows are respectively determined according to the maximum mapping period, association period or association mode period of the at least two SSB types.

18. The method according to any one of claims 1 to 17, wherein: The terminal receives first configuration information from a network side device, including: The terminal receives a system information block SIB1 from the network side device, where the SIB1 includes the first configuration information.

19. The method according to any one of claims 1 to 17, wherein: The terminal receives first configuration information from a network side device, including: The terminal receives at least one SIB1 from the network side device, wherein different SIB1s include the first configuration information corresponding to different SSB types.

20. The method according to any one of claims 1 to 19, wherein: Also includes: The terminal receives second configuration information from a network side device, where the second configuration information is used to update at least one of an SSB parameter, a PRACH resource set, and an association relationship corresponding to the at least one SSB type.

21. A communication method, wherein: include: The network side device determines first configuration information, where the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type; The network side device sends the first configuration information to the terminal.

22. The method according to claim 21, wherein: The first configuration information includes at least one of an SSB parameter, a PRACH resource set, and an association relationship from SSB to PRACH resources.

23. The method according to claim 22, wherein: The first configuration information satisfies at least one of the following: Different SSB types correspond to the same SSB parameters, or different SSB types correspond to different SSB parameters; Different SSB types correspond to the same PRACH resource set, or different SSB types correspond to different PRACH resource sets; Different SSB types correspond to the same association relationship, or different SSB types correspond to different association relationships.

24. The method according to claim 22 or 23, wherein: The SSB parameter includes at least one of the following: The maximum number of SSBs corresponding to the SSB type, the number of SSBs used by the current cell, and at least one SSB used by the current cell.

25. The method according to any one of claims 22 to 24, wherein: The association relationship between the SSB and the PRACH resource includes at least one of the following: An association relationship between at least one SSB and at least one PRACH transmission opportunity RO; An association relationship between at least one SSB and at least one RO group; An association relationship between at least one SSB group and at least one RO group; The RO group includes at least one RO; the SSB group includes at least one SSB.

26. The method according to claim 25, wherein: Different SSBs or different SSB groups are associated with different numbers of ROs, or are associated with different numbers of RO groups, or the associated RO groups include different numbers of ROs.

27. The method according to any one of claims 21 to 26, wherein: The network side device sends the first configuration information to the terminal, including: The network side device sends a system information block SIB1 to the terminal, where the SIB1 includes the first configuration information.

28. The method according to any one of claims 21 to 26, wherein: The network side device sends the first configuration information to the terminal, including: The network side device sends at least one SIB1 to the terminal, wherein different SIB1s include the first configuration information corresponding to different SSB types.

29. The method according to any one of claims 21 to 28, wherein: Also includes: The network side device sends second configuration information to the terminal, and the second configuration information is used to update at least one of the SSB parameters, PRACH resource sets and association relationships corresponding to the at least one SSB type.

30. A communication device, wherein: include: A receiving module, configured to receive first configuration information from a network side device, wherein the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type; A determination module is used to determine the association result of the SSB of at least one SSB type to the PRACH resource according to the first configuration information.

31. A communication device, wherein: include: A determination module, configured to determine first configuration information, where the first configuration information is used to configure a physical random access channel PRACH resource associated with at least one synchronization signal block SSB type; A sending module is used to send the first configuration information to the terminal.

32. A terminal, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the communication method according to any one of claims 1 to 20 are implemented.

33. A network side device, wherein: It comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the communication method according to any one of claims 21 to 29 are implemented.

34. A readable storage medium, wherein: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the communication method according to any one of claims 1 to 20, or implements the steps of the communication method according to any one of claims 21 to 29.

Citation Information

Patent Citations

  • Physical random access channel transmission method, terminal, and network side equipment

    CN111867129A

  • Method for configuring contention free random access resource, user equipment and network device

    US20210014889A1

  • Association of synchronization signal blocks to random access occasions

    US20220330348A1

  • Method for repeated transmission of prach, and terminal and network-side device

    WO2023083227A1

  • Terminal, wireless communication method, and base station

    WO2023119649A1