Prach resource indication methods, apparatus, terminal and network side device

Abstract

The present application relates to the technical field of communications. Disclosed are PRACH resource indication methods, an apparatus, a terminal, and a network side device. A PRACH resource indication method in the embodiments of the present application comprises: a terminal receives first configuration information and first indication information of a network side device, the first configuration information being configuration information of candidate PRACH resources; and, according to the first configuration information and the first indication information, the terminal determines a target PRACH resource among the candidate PRACH resources, the candidate PRACH resources comprising different types of PRACH resources, the different types of PRACH resources at least comprising a second resource, and the second resource being a PRACH resource allowed to be activated or deactivated.

Description

PRACH resource indication method, device, terminal and network side equipment

[0001] Cross-references

[0002] The present disclosure claims priority to Chinese patent application number 2024101752860 filed on February 7, 2024, entitled “PRACH resource indication method, apparatus, terminal and network side equipment”, the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] Network energy saving is of great significance for environmental sustainability, reducing environmental impact (greenhouse gas emissions) and saving operating costs. th As 5G (5th Generation) communications systems become ubiquitous across industries and regions, they will need to handle more advanced services and applications with very high data rates. Networks will become denser, using more antennas, greater bandwidth, and more frequency bands. The environmental impact of 5G needs to be managed, and new solutions will need to be developed to improve network energy efficiency.

[0005] Furthermore, energy consumption has become a critical component of operators' operating expenses (OPEX). Mobile network energy costs account for approximately 23% of operators' total costs, with the majority of energy consumption coming from the radio access network, particularly active antenna units (AAUs), with data centers and fiber optic transmission contributing smaller shares. Wireless access power consumption can be divided into two components: a dynamic component consumed only during data transmission and / or reception, and a static component consumed at all times to maintain the operation of the radio access equipment, even when data transmission and / or reception is not in progress. In particular, the physical random access channel resources used for random access by terminals have a slow update rate and cannot cope with scenarios with large and rapidly fluctuating system loads. When there are few terminals, the network needs to continuously monitor the physical random access channel resources, even if most of them are unused, resulting in wasted energy. Summary of the Invention

[0006] The embodiments of the present application provide a PRACH resource indication method, apparatus, terminal, and network-side equipment, which can achieve network energy saving and flexible activation or deactivation of PRACH resources.

[0007] In a first aspect, a PRACH resource indication method is provided, the method comprising:

[0008] The terminal receives first configuration information and first indication information of the network side device, where the first configuration information is configuration information of the candidate PRACH resource;

[0009] The terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information;

[0010] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0011] In a second aspect, a PRACH resource indication method is provided, which is performed by a network-side device. The method includes:

[0012] The network side device sends first configuration information and / or first indication information to the terminal, where the first configuration information is configuration information of the candidate PRACH resources, so that the terminal determines the target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information;

[0013] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0014] In a third aspect, a PRACH resource indication device is provided, applied to a terminal, including:

[0015] A receiving module, configured to receive first configuration information and first indication information of a network-side device, where the first configuration information is configuration information of a candidate PRACH resource;

[0016] a processing module, configured to determine a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information;

[0017] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0018] In a fourth aspect, a PRACH resource indication device is provided, which is applied to a network-side device, including:

[0019] a sending module, configured to send first configuration information and / or first indication information to a terminal, where the first configuration information is configuration information of a candidate PRACH resource, so that the terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information;

[0020] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

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

[0022] In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive first configuration information and first indication information of a network-side device, where the first configuration information is configuration information of a candidate PRACH resource; the processor is configured to determine a target PRACH resource from the candidate PRACH resources based on the first configuration information and the first indication information;

[0023] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0024] 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 second aspect are implemented.

[0025] In an eighth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to send first configuration information and / or first indication information to a terminal, where the first configuration information is configuration information of a candidate PRACH resource, so that the terminal determines a target PRACH resource from the candidate PRACH resources based on the first configuration information and the first indication information;

[0026] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0027] 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 or the steps of the method described in the second aspect are implemented.

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

[0029] 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 steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0030] 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 to implement the steps of the method described in the second aspect.

[0031] In an embodiment of the present application, the terminal can determine the target PRACH resource from the candidate PRACH resources based on the first configuration information and the first indication information of the network-side device. The network-side device adjusts the PRACH resources to adjust which resources the terminal initiates the random access process on, thereby changing the number and time of detections and adjusting the sleep time to save energy on the network side. For example, the network-side device can first configure fewer PRACH resources to save power, and when there are more random access requests or a large number of terminals, activate the second resource to reduce the probability of random access collisions. This can achieve both network energy saving and flexible activation or deactivation of PRACH resources. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0033] Figures 2 and 3 are schematic diagrams of the association between RO and SSB;

[0034] FIG4 is a flowchart of a PRACH resource indication method provided in an embodiment of the present application;

[0035] FIG5 is a flowchart of another PRACH resource indication method provided in an embodiment of the present application;

[0036] FIG6 is a schematic diagram of the mapping relationship between a traditional RO and an independent RO and an SSB according to an embodiment of the present application;

[0037] FIG7 is a schematic diagram of the mapping relationship between a traditional RO and an independent RO and an SSB according to another embodiment of the present application;

[0038] 8-10 are schematic diagrams of traditional RACH resources and independent RACH resources according to an embodiment of the present application;

[0039] FIG11 is a schematic structural diagram of a PRACH resource indication device provided in an embodiment of the present application;

[0040] FIG12 is a schematic structural diagram of another PRACH resource indication device provided in an embodiment of the present application;

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

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

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

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

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

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

[0047] 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 described technology 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 example 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) communication systems.

[0048] FIG1 shows 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 can 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 user equipment (VUE), a ship-borne 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), a teller machine (ATM), or a self-service machine, etc. 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 (AP) 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.

[0049] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0050] The configuration parameters for the Physical Random Access Channel (PRACH) resources and the Synchronization Signal and PBCH block (SSB) - PRACH transmission occasion (PRACH Occasion, abbreviated as RO) are configured in the System Information Block (SIB1). In NR, a cell can configure multiple frequency division multiplex (FDM) ROs at a time domain location for PRACH transmission. The number of ROs that can be FDMed at a time can be: {1, 2, 4, 8}, which is configured and determined by the high-level parameter msg1-FDM.

[0051] 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 high-level parameter msg1-FDM. At the time of initial access, the PRACH frequency domain resource n RA The RO resource with the lowest frequency in the initial active uplink bandwidth part is numbered in ascending order. Otherwise, the PRACH frequency domain resource n RA The RO resources are numbered in ascending order, starting from the lowest frequency resource within the active uplink bandwidth part. For example, in Figure 2, the number of FDM ROs at a time is 8 (msg1-FDM=8), and the RO resources are numbered from RO#0 to RO#7 in ascending order of frequency.

[0052] In NR, there is an association between RO and the SSB actually sent. RO is associated with SSB in the order of frequency domain (from low frequency to high frequency) and then time domain. One SSB may be associated with multiple consecutive ROs, or multiple SSBs may be associated with one RO (in this case, different SSBs correspond to different Preambles). It is configured by the network-side device through the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. For example, oneEighth means that one 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 Preambles associated with each SSB on an RO. For example, the value n4 means that the number of Preambles associated with each SSB on an RO is 4, and n8 means that the number of Preambles associated with each SSB on an RO is 8.

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

[0054] Typically, a base station can use different beams to transmit different SSBs. The number of SSBs is configured using the ssb-PositionsInBurst parameter. For FR2, the maximum number of SSBs is 64. Based on the strength of the received downlink beam / SSB, the UE selects the RO / RO and preamble combination associated with a high-signal SSB to send Msg1. The network device then determines the UE's selected SSB based on the RO / RO and preamble combination of the received preamble. Msg2 is then sent on the downlink beam corresponding to the SSB to ensure downlink signal reception quality.

[0055] Taking Figure 2 as an example, at a given moment in time, the number of FDM ROs is eight, and the number of SSBs actually transmitted is four: SSB#0, SSB#1, SSB#2, and SSB#3. Each SSB is associated with two ROs. If the UE determines to send PRACH / Mg1 on the RO corresponding to SSB#0, the UE selects one RO between RO#0 and RO#1 for PRACH transmission.

[0056] 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. When multiple SSBs share a RO, the preamble sets associated with these multiple SSBs are different, that is, 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 indices 0 to 29 are associated with SSB#0, and preambles with indices 30 to 59 are associated with SSB#1. Each square in Figure 3 indicates an RO, not an SSB. The labeled SSB indicates which SSB(s) this RO is associated with.

[0057] Before sending PRACH, the UE first selects a received beam (SSB) with a reference signal received power (RSRP) higher than the threshold based on the RSRP of the received SSB. If the RSRP of multiple SSBs is higher than the threshold, the terminal can select any SSB with RSRP higher than the threshold. If there is no SSB with RSRP higher than the threshold, the UE selects an SSB based on the implementation.

[0058] Based on the NW (Network) configuration, the UE obtains the correspondence between the SSB and the 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 for sending PRACH / Preamble / Msg1.

[0059] For example: In the example shown in Figure 2, assuming that the UE selects SSB#1, the UE can select one from RO#2 and RO#3 to send PRACH / Msg1; in the example shown in Figure 3, if the UE selects SSB#1, the UE 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 UE 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, so in the available preamble set associated with the SSB in one RO, the preamble will be divided into two subsets, each subset corresponding to one SSB. The UE will select a preamble sequence in the preamble subset corresponding to the selected SSB for sending PRACH / Msg1.

[0060] When network-side devices are configured with a large number of RO resources, resource waste may occur, which is not conducive to base station energy conservation. The base station needs to monitor a large number of ROs all the time. When network-side devices are configured with a small number of RO resources, the problem of insufficient random access channel (RACH) resources may arise. It is necessary to introduce a flexible PRACH resource indication mechanism to achieve the purpose of energy conservation of network-side devices and solve the problem of insufficient RACH resources.

[0061] The following, in conjunction with the accompanying drawings, describes in detail the PRACH resource indication method, apparatus, terminal, and network-side equipment provided in the embodiments of the present application through some embodiments and their application scenarios.

[0062] Please refer to FIG. 4 , which is a flowchart of a PRACH resource indication method provided in an embodiment of the present application. The method is executed by a terminal. As shown in FIG. 4 , the method includes the following steps:

[0063] Step 101: The terminal receives first configuration information and first indication information from a network-side device, where the first configuration information is configuration information of a candidate PRACH resource;

[0064] Step 102: The terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information;

[0065] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0066] In an embodiment of the present application, the terminal can determine the target PRACH resource among the candidate PRACH resources based on the first configuration information and the first indication information of the network side device, so that the network side device can first configure fewer PRACH resources to save power. When there are more random access requests or a large number of terminals, the second resource is activated to alleviate the probability of random access collision. This can not only achieve network energy saving, but also solve the problem of insufficient resources when fewer PRACH resources are configured.

[0067] In some embodiments, the candidate PRACH resource further includes a first resource, and the first resource and / or the second resource satisfies at least one of the following:

[0068] The first resource and the second resource are numbered together and mapped to a synchronization signal block SSB;

[0069] The mapping relationship between the SSB and the random access occasion RO of the first resource and the second resource is the same or different;

[0070] The preamble sequence configurations of the first resource and the second resource are the same or different;

[0071] The first resource and the second resource have different priorities;

[0072] The time-frequency positions of the first resource and the second resource completely overlap, completely do not overlap, or partially overlap;

[0073] The business types of the business associated with the first resource and the second resource are different;

[0074] The quality of service (QoS) of services associated with the first resource and the second resource are different;

[0075] The first resource and the second resource are associated with different terminal types;

[0076] The first resource is a PRACH resource that is not allowed to be activated or deactivated.

[0077] In this embodiment, the first resource can be understood as a legacy PRACH resource, which is a PRACH resource that is not allowed to be activated or deactivated by indication information or configuration information, and is a resource configured by RACH-ConfigCommon included in the bandwidth part uplink common signaling (BWP-UplinkCommon). The second resource is an RO resource that satisfies at least one of the following:

[0078] a resource independent of the first resource;

[0079] Resources that can be activated or deactivated by network-side devices;

[0080] Resources with a different mapping mode from the first resource mapping mode, the mapping mode including mapping between SSB and RO and mapping between preamble and SSB;

[0081] Resources configured by attaching RACH-ConfigCommon.

[0082] The second resource can be called an additional PRACH resource, a separate PRACH resource, or a dynamic PRACH resource. In this embodiment, the network-side device can initially configure fewer PRACH resources to save power. When there are a large number of random access requests or a large number of terminals, the second resource is activated to reduce the probability of random access collisions. This can achieve network energy conservation and solve the problem of insufficient RACH resources.

[0083] The mapping relationship between separate RO and SSB includes the following methods:

[0084] (1) Separate RO is a time-frequency resource that does not overlap with legacy RO;

[0085] When the separate RO is activated, the legacy RO is invalid; or when the separate RO is activated, the legacy RO is still valid.

[0086] The mapping relationship between separate RO and SSB refers to ssb-perRACH-OccasionAndCB-PreamblesPerSSB of legacy RO. As shown in Figure 6, the mapping relationship between dynamic RO and SSB is the same as that between legacy RO and SSB, including the same number of SSBs mapped to each RO, the same SSBs associated with dynamic RO and legacy RO, and the same number of preambles associated with each SSB.

[0087] (2) The mapping relationship between separate RO and SSB refers to the new ssb-perRACH-OccasionAndCB-PreamblesPerSSB; the new ssb-perRACH-OccasionAndCB-PreamblesPerSSB is indicated by the network-side device or configured in advance. You can configure only the new SSB per RO (mapping relationship between SSB and RO) or only the new number of preambles per SSB (preamble configuration); as shown in Figure 7, the mapping relationship between separate RO and SSB is different from the mapping relationship between legacy RO and SSB. In legacy RO, SSB per RO = 2, and in dynamic RO, SSB per RO = 1;

[0088] In addition to the different mapping relationships between RO and SSB, the mapping relationship (configuration) between preamble and SSB can also be different: for example, in the legacy RO, each SSB is associated with 20 preambles, and each SSB can be configured with multiple preambles of different features; in the dynamic RO, each SSB can be associated with 10 preambles, and each SSB can be configured with multiple preambles of different features.

[0089] To alleviate the pressure of RACH collision, the network-side device can dynamically activate or deactivate the separate RO. In order to allow the UE to give priority to the separate RO for random access, the RO priority can be configured for the separate RO and the legacy RO, and the UE selects the RO for random access based on the priority; or for the UE, the preamble of the Network Energy Saving (NES) feature is configured only on the separate RO, and the UE supporting NES can only perform random access on the separate RO.

[0090] In some embodiments, the mapping relationship between the SSB and the RO of the first resource and the second resource being the same includes at least one of the following:

[0091] The number and / or number of SSBs mapped to the first resource is the same as the number and / or number of SSBs mapped to the second resource;

[0092] The number of SSBs associated with each opportunity on the first resource is the same as the number of SSBs associated with each opportunity on the second resource.

[0093] In some embodiments, the difference in mapping relationship between SSB and RO between the first resource and the second resource includes at least one of the following:

[0094] The number and / or number of SSBs mapped to the first resource is different from the number and / or number of SSBs mapped to the second resource;

[0095] The number of SSBs associated with each opportunity on the first resource is different from the number of SSBs associated with each opportunity on the second resource.

[0096] In this embodiment, the SSB index associated with the first resource and the second resource may be different. For example, if the network-side device finds that there are a large number of UEs in certain directions, it may increase the RACH opportunities in these SSB directions and activate the second resource through the first indication information. The SSB index associated with the second resource may also be indicated by the first indication information: assuming that there are 8 candidate SSBs in total, the ssb-PositionsInBurst (bitmap 11111111) indicated by ServingCellConfigCommon corresponds to the SSB associated with the first resource, so the first resource is associated with 8 SSBs, and the mapping relationship between SSB and RO and the mapping relationship between preamble and SSB of the first resource and the second resource are the same. The network-side device indicates the first indication information, and the first indication information includes ssb-PositionsInBurst = bitmap11110000. The ssb-PositionsInBurst indicated by the first indication information is the SSB index associated with the second resource. According to the first indication information, the second resource can confirm that it is only associated with the first four SSBs of the SSB Index.

[0097] In some embodiments, the preamble configurations of the first resource and the second resource are different. For example, a UE supporting PRACH adaptation is associated with the NES feature, and the preamble related to the NES feature is only associated with the second resource (separate RO). In this case, the UE receiving the indication from the network side device may preferentially select the preamble associated with the NES feature on the second resource to initiate random access. Alternatively, the preamble configurations of the first resource and the second resource are different. For example, a UE supporting PRACH adaptation is associated with the NES feature, and the preamble related to the NES feature can be associated with both the first resource and the second resource (separate RO). In this case, the UE receiving the indication from the network side device may preferentially select the preamble associated with the NES feature on the second resource to initiate random access.

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

[0099] The time domain resource configuration, frequency domain resource configuration, and preamble sequence configuration of the first resource may include all parameters of RACH-ConfigCommon;

[0100] Time domain resource configuration and frequency domain resource configuration of the second resource;

[0101] preamble configuration of the second resource;

[0102] The SSB index index associated with the second resource can be indicated by configuring ssb-PositionsInBurst in the second resource configuration. The length of the bitmap used for indication is based on the number of all possible candidate SSBs, or can be based on the SSB indicated by ssb-PositionsInBurst corresponding to the first resource, and further indicates which SSBs are associated with the second resource based on the SSB indicated by ssb-PositionsInBurst corresponding to the first resource;

[0103] The time domain relative relationship between the second resource and the first resource.

[0104] In some embodiments, the time domain resource configuration and frequency domain resource configuration of the second resource include at least one of the following:

[0105] All parameters of the random access channel common configuration RACH-ConfigCommon;

[0106] Some parameters of RACH-ConfigCommon, such as ssb-perRACH-OccasionAndCB-PreamblesPerSSB, prach-ConfigurationIndex, and msg1-FDM

[0107] msg1-FrequencyStart, featureCombinationPreambles, the configuration of these parameters is different from the configuration of the first resource;

[0108] RO group information that the second resource allows to be activated or deactivated;

[0109] Target SSB index;

[0110] RO mask mask.

[0111] In some embodiments, when the time domain resource configuration and frequency domain resource configuration of the second resource only include some parameters of RACH-ConfigCommon, other parameters used to determine the second resource are determined by the time domain resource configuration and / or frequency domain resource configuration of the first resource.

[0112] In some embodiments, the grouping manner of the RO group of the second resource includes at least one of the following:

[0113] The network side device configures the group identifier to which each RO in the RO of the second resource belongs;

[0114] ROs are grouped according to the RO mask configured on the network side device;

[0115] Grouping according to the rules predefined by the protocol;

[0116] The protocol predefined rules include any of the following: ROs within a preset time domain range are grouped together, ROs within a preset frequency domain range are grouped together, ROs within a preset number range are grouped together, ROs with even occasion numbers are grouped together, or ROs with odd occasion numbers are grouped together.

[0117] In some embodiments, when the first configuration information includes a target SSB index,

[0118] The RO associated with the target SSB index is allowed to be activated or deactivated; and / or

[0119] The terminal determines a timing when the second resource is allowed to be activated or deactivated according to the RO associated with the target SSB index.

[0120] In some embodiments, when the time domain resource configuration and the frequency domain resource configuration of the second resource include an RO mask,

[0121] The RO corresponding to the RO mask is allowed to be activated or deactivated; and / or

[0122] The terminal determines, according to the RO mask, a timing at which the second resource is allowed to be activated or deactivated.

[0123] In some embodiments, the preamble configuration of the second resource includes at least one of the following:

[0124] The feature associated with the preamble of the second resource and the starting preamble number and quantity of each feature;

[0125] The starting index and number of the target preamble. The terminal can determine the preambles that can be used in the RO of the second resource according to the starting index and number of the target preamble.

[0126] In some embodiments, the temporal relative relationship between the second resource and the first resource includes at least one of the following:

[0127] the period of the second resource within the period of the first resource;

[0128] the number of cluster bursts and / or opportunities of the second resource within the period of the first resource;

[0129] a ratio of a period of the second resource to a period of the first resource;

[0130] The time interval between each opportunity and / or opportunity cluster RO cluster of the second resource;

[0131] a time interval between the timing of the second resource and the timing of the first resource;

[0132] In each time unit, the time interval between the timing of the second resource and the timing of the first resource;

[0133] The timing and / or number of clusters at which the second resource is allowed to be activated or deactivated within each time unit;

[0134] an offset value between the PRACH configuration index of the second resource and the PRACH configuration index of the first resource, wherein the PRACH configuration index applicable to the second resource may be a PRACH configuration index newly defined or newly added in a table of an existing protocol, which is used to configure an additional PRACH slot or RO under certain specific configurations;

[0135] The time offset value of the second resource relative to the first PRACH time slot or the last PRACH time slot or each PRACH time slot or the first RO or the last RO or the first PRACH cluster or each PRACH cluster of the first resource is as shown in FIG8 . In some embodiments, each radio frame has one PRACH slot, and each PRACH slot has multiple PRACH occasions (blue resources, 6 occasions in FIG8 ). The network side device can configure the time offset value timeoffset of the second resource relative to the first RACH occasion of the first resource. Then, within each radio frame, the UE can find the starting position of the second resource according to the timeoffset. The number of occasions of each PRACH slot of the second resource can be the same as that of the first resource, or can be independently configured by the first configuration information.

[0136] In FIG8 , it can also be understood that each radio frame has a PRACH cluster of the first resource, and the network side device can configure the offset value of each cluster of the second resource relative to each cluster of the first resource to determine the second resource.

[0137] The number of PRACH time slots, ROs, or clusters of the second resource relative to the first resource;

[0138] The unit of the period and / or the time interval includes at least one of the following: a radio frame, a half frame, a subframe, a time slot, a millisecond, a PRACH period, a PRACH time slot, a PRACH opportunity, a PRACH association period, and a PRACH association pattern period. In this embodiment, the number of PRACH slots or ROs of the second resource can be independently configured.

[0139] In some embodiments, the first indication information indicates at least one of the following:

[0140] PRACH configuration index: When the terminal receives the PRACH configuration index included in the first indication information, it will overwrite the PRACH time domain configuration previously received in SIB1, and the terminal defaults to keeping the other parameters unchanged;

[0141] Activate or deactivate all second resources, where the second resources include time-frequency resources, preamble sequence resources, etc.;

[0142] activating or deactivating part of the second resource;

[0143] a validity period for activating or deactivating all or part of the second resource;

[0144] an SSB index associated with the second resource;

[0145] The second indication information for turning on or off the discontinuous transmission (DTX) and / or discontinuous reception (DRX) of the cell may be stipulated in the protocol that the second resource is in an activated state during the cell DTX / DRX duration, and in a deactivated state during the cell DRX / DTX off period.

[0146] In some embodiments, when the first indication information indicates activation or deactivation of part of the second resources, the first indication information further indicates at least one of the following:

[0147] an identifier of a resource group activated or deactivated in the second resource;

[0148] a subframe number or a time slot number, such that in the second resource, the occasion of the target subframe number or the target time slot number in each subframe is activated or deactivated;

[0149] The frequency domain starting position of the starting opportunity in the second resource and the number of multiple opportunities that are consecutive in the order of first frequency domain and then time domain;

[0150] an identifier of a starting opportunity in the second resource and a number of consecutive opportunities in the order of first frequency domain and then time domain;

[0151] an identifier of a starting preamble and the number of activated or deactivated preambles in the second resource;

[0152] The period of the second resource activated within the period of the first resource;

[0153] the number of the second resources activated during the first resource cycle;

[0154] a period of the second resource being activated within a single time unit;

[0155] The number of activated second resources in a single time unit.

[0156] In a specific example, the first indication information may indicate at least one of the following:

[0157] (1) Deactivate or activate part of the preamble, and indicate the starting preamble index and the number of consecutive preambles in the first indication information.

[0158] (2) Deactivate or activate all separate ROs.

[0159] (3) Deactivate or activate some separate ROs. The partial separate ROs are determined by the following methods:

[0160] Number of the RO group to be activated or deactivated;

[0161] The number of activated or deactivated RO groups. The grouping methods include the following: ROs with the same frequency domain as one group; ROs with the same time domain as one group; ROs with even occasion numbers as one group, and ROs with odd occasion numbers as one group.

[0162] Activate or deactivate the RO corresponding to the target RO mask, where the first indication information includes the target RO mask for determining a separate RO;

[0163] Activate or deactivate the RO on the target subframe number. The RO on the target subframe number is a separate RO.

[0164] Indicates the frequency domain starting position and continuous occasions, and determines separate ROs based on the frequency domain starting position and continuous occasions;

[0165] Indicate PRACH configuration index;

[0166] Indicates the offset value of the PRACH configuration index of the second resource relative to the PRACH configuration index of the first resource;

[0167] Indicates the target subframe number and time slot number, and determines the separate RO according to the target subframe number and time slot number.

[0168] (4) Deactivate or activate part of the preamble of a separate RO.

[0169] Part of the separate RO can be determined by the method mentioned in (3) above, and part of the preamble can be determined by the starting preamble index indicated in the first indication information and the number of consecutive preambles.

[0170] In some embodiments, the first indication information is carried by at least one of the following:

[0171] paging messages;

[0172] Radio Resource Control RRC connection establishment message;

[0173] RRC connection release message;

[0174] Downlink control information DCI;

[0175] Media Access Control Element MAC CE;

[0176] System Information Block SIB.

[0177] In some embodiments, the first configuration information is carried by at least one of the following:

[0178] paging messages;

[0179] RRC connection establishment message;

[0180] RRC connection release message;

[0181] SIB.

[0182] When the network device wants to adjust the period of the PRACH resource, it can update the RACH configuration (including parameters such as the PRACH configuration index) through SIB1. However, the update speed of SIB1 is too slow and the transmission overhead is large. One way is to reduce the configuration parameters in the SIB and reconfigure only the override parameters in the updated SIB (for example, only reconfigure the PRACH period parameter) to reduce the SIB overhead. Another way is to update the RACH configuration through other messages instead of SIB messages. For example, for idle UEs, the network device can update the RACH configuration by sending a paging message. For connected UEs, the network device can update the RACH configuration through DCI / MAC CE, which only carries the updated PRACH period (PRACH configuration index). Alternatively, the network device can activate one of the multiple RACH configurations to indicate the target RACH configuration identifier. Alternatively, the first resource and the second resource can be configured through the first configuration information. When the second resource needs to be activated, the first indication information can indicate the activation of the second resource.

[0183] In some embodiments, when both the first resource and the second resource are configured or indicated as valid by a network-side device, the terminal determines the RO for random access in the target PRACH resource according to at least one of the following:

[0184] Instructions or configuration of network-side equipment;

[0185] The number of random access failures, for example, if there are too many failures on the first resource, the second resource is selected for RACH;

[0186] The time and / or distance at which the PRACH is sent is the shortest;

[0187] The priority of the RO resource, where the priority of the RO resource is indicated by the network side device or configured in advance, or predefined by the protocol. For example, once the configuration of the dynamic RO is valid, or once the activation of the dynamic RO is received, the dynamic RO is preferentially selected;

[0188] Service type or service QoS. The network side device can configure the mapping relationship between the service and the RO. For example, the voice service is mapped to a specific RO. When the terminal has a voice service, this specific RO can be selected.

[0189] The type or capabilities of the terminal.

[0190] In this embodiment, the terminal can determine the target PRACH resource based on the first configuration information and the first indication information. For example, the first configuration information configures the specific time-frequency positions of the first resource and the second resource, but the second resource is initially invalid by default. When the first indication information further indicates the activation of the second resource, the terminal defaults to giving priority to the second resource, that is, the first resource is not considered; or, the terminal can determine the target PRACH resource based on the first configuration information, the first indication information and the terminal's selection. For example, when the first configuration information configures the first resource and the second resource, and the first indication information indicates the activation of the second resource, it means that both the first resource and the second resource are valid at this time, and the terminal can autonomously select the first resource or the second resource as the target PRACH resource according to some rules.

[0191] In this embodiment, the network device may configure or indicate different types of RO priorities, such as prioritizing a legacy RO over a separate RO, or vice versa. When the network device is configured with both legacy PRACH resources and PRACH resources that allow dynamic activation or deactivation, if the UE receives an activation indication from the network device, the UE prioritizes dynamic PRACH resources for random access in accordance with the indication of the network device.

[0192] In some embodiments, when the terminal determines the target PRACH resource according to an instruction or configuration of a network-side device, the terminal determines the target PRACH resource including:

[0193] In a case where the network side device configures the second resource, the terminal preferentially selects the second resource as the target PRACH resource; or

[0194] In a case where the network side device configures the second resource and the second resource is initially an invalid resource by default, the terminal preferentially selects the second resource as the target PRACH resource after receiving the first indication information.

[0195] In some embodiments, the method further comprises:

[0196] When the first indication information is not received, the terminal determines the target PRACH resource according to the parameters indicated in the RACH-ConfigCommon or the message MsgA-ConfigCommon.

[0197] The embodiment of the present application further provides a PRACH resource indication method, as shown in FIG5 , including:

[0198] Step 201: A network-side device sends first configuration information and / or first indication information to a terminal, where the first configuration information is configuration information of candidate PRACH resources, so that the terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information.

[0199] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0200] In this embodiment, the network side device can first configure fewer PRACH resources to save power. When there are more random access requests or a large number of terminals, the second resource is activated to alleviate the probability of random access collision. This can not only achieve network energy saving, but also activate or deactivate PRACH resources.

[0201] In some embodiments, the network-side device determines whether to send the first indication information based on at least one of the following:

[0202] Random access collision level of the terminal;

[0203] The number of terminals that support sending the uplink wake-up signal WUS;

[0204] The number of idle terminals;

[0205] Information reported by idle terminals.

[0206] In this embodiment, when the random access collision degree of the terminal is high, for example, greater than a set first threshold, a first indication message may be sent to instruct activation of the second resource to reduce the random access collision degree of the terminal; when the random access collision degree of the terminal is low, for example, less than a set second threshold, a first indication message may be sent to instruct deactivation of the second resource to achieve network energy saving. When the number of terminals supporting the sending of the uplink wake-up signal WUS is large, for example, greater than a set third threshold, a first indication message may be sent to instruct activation of the second resource to avoid insufficient RACH resources; when the number of terminals supporting the sending of the uplink wake-up signal WUS is small, for example, less than a set fourth threshold, a first indication message may be sent to instruct deactivation of the second resource to achieve network energy saving. When the number of idle terminals is large, for example, greater than a set fifth threshold, a first indication message may be sent to instruct activation of the second resource to avoid insufficient RACH resources; when the number of idle terminals is small, for example, less than a set sixth threshold, a first indication message may be sent to instruct deactivation of the second resource to achieve network energy saving.

[0207] In some embodiments, the random access collision degree of the terminal is determined based on at least one of the following:

[0208] The percentage of random access preamble used;

[0209] The number or percentage of messages MSG3 with different terminal identifiers, for example, whether there is always more than one UE sending MSG3.

[0210] In some embodiments, the information reported by the idle terminal includes at least one of the following:

[0211] Msg1 is sent repeatedly.

[0212] Msg1 power increase times;

[0213] Msg1 power boost value;

[0214] Feedback information after successful access carried in MSG3.

[0215] Specifically, when Msg1 is repeatedly sent a large number of times or the Msg1 power is increased a large number of times or the Msg1 power increase value is large, and it is judged that access is difficult, a first indication message can be sent to instruct the activation of the second resource to avoid insufficient RACH resources; when Msg1 is repeatedly sent a small number of times or the Msg1 power is increased a small number of times or the Msg1 power increase value is small, a first indication message can be sent to instruct the deactivation of the second resource to achieve network energy saving.

[0216] In some embodiments, the candidate PRACH resource further includes a first resource, and the first resource and / or the second resource satisfies at least one of the following:

[0217] The first resource and the second resource are numbered together and mapped to a synchronization signal block SSB;

[0218] The mapping relationship between the SSB and the random access occasion RO of the first resource and the second resource is the same or different;

[0219] The preamble sequence configurations of the first resource and the second resource are the same or different;

[0220] The first resource and the second resource have different priorities;

[0221] The time-frequency positions of the first resource and the second resource completely overlap, completely do not overlap, or partially overlap;

[0222] The business types of the business associated with the first resource and the second resource are different;

[0223] The quality of service (QoS) of services associated with the first resource and the second resource are different;

[0224] The first resource and the second resource are associated with different terminal types;

[0225] The first resource is a PRACH resource that is not allowed to be activated or deactivated.

[0226] In this embodiment, the first resource can be understood as a legacy PRACH resource, which is a PRACH resource that is not allowed to be activated or deactivated by indication information or configuration information, and is a resource configured by RACH-ConfigCommon included in the bandwidth part uplink common signaling (BWP-UplinkCommon). The second resource is an RO resource that satisfies at least one of the following:

[0227] a resource independent of the first resource;

[0228] Resources that can be activated or deactivated by network-side devices;

[0229] Resources with a different mapping mode from the first resource mapping mode, the mapping mode including mapping between SSB and RO and mapping between preamble and SSB;

[0230] Resources configured by attaching RACH-ConfigCommon.

[0231] The second resource can be called an additional PRACH resource, a separate PRACH resource, or a dynamic PRACH resource. In this embodiment, the network-side device can initially configure fewer PRACH resources to save power. When there are a large number of random access requests or a large number of terminals, the second resource is activated to reduce the probability of random access collisions. This can achieve network energy conservation and solve the problem of insufficient RACH resources.

[0232] The mapping relationship between separate RO and SSB includes the following methods:

[0233] (1) Separate RO is a time-frequency resource that does not overlap with legacy RO;

[0234] When the separate RO is activated, the legacy RO is invalid; or when the separate RO is activated, the legacy RO is still valid.

[0235] The mapping relationship between separate RO and SSB refers to ssb-perRACH-OccasionAndCB-PreamblesPerSSB of legacy RO. As shown in Figure 6, the mapping relationship between dynamic RO and SSB is the same as that between legacy RO and SSB, including the same number of SSBs mapped to each RO, the same SSBs associated with dynamic RO and legacy RO, and the same number of preambles associated with each SSB.

[0236] (2) The mapping relationship between separate RO and SSB refers to the new ssb-perRACH-OccasionAndCB-PreamblesPerSSB; the new ssb-perRACH-OccasionAndCB-PreamblesPerSSB is indicated by the network-side device or configured in advance. You can configure only the new SSB per RO (mapping relationship between SSB and RO) or only the new number of preambles per SSB (preamble configuration); as shown in Figure 7, the mapping relationship between separate RO and SSB is different from the mapping relationship between legacy RO and SSB. In legacy RO, SSB per RO = 2, and in dynamic RO, SSB per RO = 1;

[0237] In addition to the different mapping relationships between RO and SSB, the mapping relationship (configuration) between preamble and SSB can also be different: for example, in the legacy RO, each SSB is associated with 20 preambles, and each SSB can be configured with multiple preambles of different features; in the dynamic RO, each SSB can be associated with 10 preambles, and each SSB can be configured with multiple preambles of different features.

[0238] To alleviate RACH collision pressure, network-side equipment can dynamically activate or deactivate separate ROs. To allow UEs to prioritize separate ROs for random access, RO priorities can be configured for separate ROs and legacy ROs, and UEs select ROs for random access based on the priorities. Alternatively, for UEs, the NES feature preamble can be configured only on separate ROs, and UEs that support NES can only perform random access on separate ROs.

[0239] In some embodiments, the mapping relationship between the SSB and the RO of the first resource and the second resource being the same includes at least one of the following:

[0240] The number and / or number of SSBs mapped to the first resource is the same as the number and / or number of SSBs mapped to the second resource;

[0241] The number of SSBs associated with each opportunity on the first resource is the same as the number of SSBs associated with each opportunity on the second resource.

[0242] In some embodiments, the difference in mapping relationship between SSB and RO between the first resource and the second resource includes at least one of the following:

[0243] The number and / or number of SSBs mapped to the first resource is different from the number and / or number of SSBs mapped to the second resource;

[0244] The number of SSBs associated with each opportunity on the first resource is different from the number of SSBs associated with each opportunity on the second resource.

[0245] In this embodiment, the SSB index associated with the first resource and the second resource may be different. For example, if the network-side device finds that there are a large number of UEs in certain directions, it may increase the RACH opportunities in these SSB directions and activate the second resource through the first indication information. The SSB index associated with the second resource may also be indicated by the first indication information: assuming that there are 8 candidate SSBs in total, the ssb-PositionsInBurst (bitmap 11111111) indicated by ServingCellConfigCommon corresponds to the SSB associated with the first resource, so the first resource is associated with 8 SSBs, and the mapping relationship between SSB and RO and the mapping relationship between preamble and SSB of the first resource and the second resource are the same. The network-side device indicates the first indication information, and the first indication information includes ssb-PositionsInBurst = bitmap11110000. The ssb-PositionsInBurst indicated by the first indication information is the SSB index associated with the second resource. According to the first indication information, the second resource can confirm that it is only associated with the first four SSBs of the SSB Index.

[0246] In some embodiments, the preamble configurations of the first resource and the second resource are different. For example, a UE supporting PRACH adaptation is associated with the NES feature, and the preamble related to the NES feature is only associated with the second resource (separate RO). In this case, the UE receiving the indication from the network side device may preferentially select the preamble associated with the NES feature on the second resource to initiate random access. Alternatively, the preamble configurations of the first resource and the second resource are different. For example, a UE supporting PRACH adaptation is associated with the NES feature, and the preamble related to the NES feature can be associated with both the first resource and the second resource (separate RO). In this case, the UE receiving the indication from the network side device may preferentially select the preamble associated with the NES feature on the second resource to initiate random access.

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

[0248] time domain resource configuration, frequency domain resource configuration, and preamble sequence configuration of the first resource;

[0249] Time domain resource configuration and frequency domain resource configuration of the second resource;

[0250] preamble configuration of the second resource;

[0251] The SSB index index associated with the second resource can be indicated by configuring ssb-PositionsInBurst in the second resource configuration. The length of the bitmap used for indication is based on the number of all possible candidate SSBs, or can be based on the SSB indicated by ssb-PositionsInBurst corresponding to the first resource, and further indicates which SSBs are associated with the second resource based on the SSB indicated by ssb-PositionsInBurst corresponding to the first resource;

[0252] The time domain relative relationship between the second resource and the first resource.

[0253] In some embodiments, the time domain resource configuration and frequency domain resource configuration of the second resource include at least one of the following:

[0254] All parameters of the random access channel common configuration RACH-ConfigCommon;

[0255] Some parameters of RACH-ConfigCommon;

[0256] RO group information that the second resource allows to be activated or deactivated;

[0257] Target SSB index;

[0258] RO mask mask.

[0259] In some embodiments, when the time domain resource configuration and frequency domain resource configuration of the second resource only include some parameters of RACH-ConfigCommon, other parameters used to determine the second resource are determined by the time domain resource configuration and / or frequency domain resource configuration of the first resource.

[0260] In some embodiments, the grouping manner of the RO group of the second resource includes at least one of the following:

[0261] The network side device configures the group identifier to which each RO in the RO of the second resource belongs;

[0262] ROs are grouped according to the RO mask configured on the network side device;

[0263] Grouping according to the rules predefined by the protocol;

[0264] The protocol predefined rules include any of the following: ROs within a preset time domain range are grouped together, ROs within a preset frequency domain range are grouped together, ROs within a preset number range are grouped together, ROs with even occasion numbers are grouped together, or ROs with odd occasion numbers are grouped together.

[0265] In some embodiments, when the first configuration information includes a target SSB index,

[0266] The RO associated with the target SSB index is allowed to be activated or deactivated; and / or

[0267] The terminal determines a timing when the second resource is allowed to be activated or deactivated according to the RO associated with the target SSB index.

[0268] In some embodiments, when the time domain resource configuration and the frequency domain resource configuration of the second resource include an RO mask,

[0269] The RO corresponding to the RO mask is allowed to be activated or deactivated; and / or

[0270] The terminal determines, according to the RO mask, a timing at which the second resource is allowed to be activated or deactivated.

[0271] In some embodiments, the preamble configuration of the second resource includes at least one of the following:

[0272] The feature associated with the preamble of the second resource and the starting preamble number and quantity of each feature;

[0273] The starting index and number of target preambles.

[0274] In some embodiments, the temporal relative relationship between the second resource and the first resource includes at least one of the following:

[0275] the period of the second resource within the period of the first resource;

[0276] the number of cluster bursts and / or opportunities of the second resource within the period of the first resource;

[0277] a ratio of a period of the second resource to a period of the first resource;

[0278] The time interval between each opportunity and / or opportunity cluster RO cluster of the second resource;

[0279] a time interval between the timing of the second resource and the timing of the first resource;

[0280] In each time unit, the time interval between the timing of the second resource and the timing of the first resource;

[0281] The timing and / or number of clusters at which the second resource is allowed to be activated or deactivated within each time unit;

[0282] an offset value between the PRACH configuration index of the second resource and the PRACH configuration index of the first resource, wherein the PRACH configuration index applicable to the second resource may be a PRACH configuration index newly defined or newly added in a table of an existing protocol, which is used to configure an additional PRACH slot or RO under certain specific configurations;

[0283] The time offset value of the second resource relative to the first PRACH time slot or the last PRACH time slot or each PRACH time slot or the first RO or the last RO or the first PRACH cluster or each PRACH cluster of the first resource is as shown in FIG8 . In some embodiments, each radio frame has one PRACH slot, and each PRACH slot has multiple PRACH occasions (blue resources, 6 occasions in FIG8 ). The network side device can configure the time offset value timeoffset of the second resource relative to the first RACH occasion of the first resource. Then, within each radio frame, the UE can find the starting position of the second resource according to the timeoffset. The number of occasions of each PRACH slot of the second resource can be the same as that of the first resource, or can be independently configured by the first configuration information.

[0284] In FIG8 , it can also be understood that each radio frame has a PRACH cluster of the first resource, and the network side device can configure the offset value of each cluster of the second resource relative to each cluster of the first resource to determine the second resource.

[0285] The number of PRACH time slots, ROs, or clusters of the second resource relative to the first resource;

[0286] The period and / or the time interval includes at least one of the following: a radio frame, a half frame, a subframe, a time slot, a millisecond, a PRACH period, a PRACH time slot, a PRACH opportunity, a PRACH association period, and a PRACH association pattern period.

[0287] In some embodiments, the first indication information indicates at least one of the following:

[0288] PRACH configuration index;

[0289] Activate or deactivate all second resources;

[0290] activating or deactivating part of the second resource;

[0291] a validity period for activating or deactivating all or part of the second resource;

[0292] an SSB index associated with the second resource;

[0293] The second indication information for turning on or off discontinuous transmission and / or discontinuous reception of the cell may be such that the protocol stipulates that during the cell DTX / DRX onduration period, the second resource is in an activated state, and during the cell DRX / DTX offduration period, the second resource is in a deactivated state.

[0294] In some embodiments, when the first indication information indicates activation or deactivation of part of the second resources, the first indication information further indicates at least one of the following:

[0295] an identifier of a resource group activated or deactivated in the second resource;

[0296] a subframe number or a time slot number, such that in the second resource, the occasion of the target subframe number or the target time slot number in each subframe is activated or deactivated;

[0297] The frequency domain starting position of the starting opportunity in the second resource and the number of multiple opportunities that are consecutive in the order of first frequency domain and then time domain;

[0298] an identifier of a starting opportunity in the second resource and a number of consecutive opportunities in the order of first frequency domain and then time domain;

[0299] an identifier of a starting preamble and the number of activated or deactivated preambles in the second resource;

[0300] The period of the second resource activated within the period of the first resource;

[0301] the number of the second resources activated during the first resource cycle;

[0302] a period of the second resource being activated within a single time unit;

[0303] The number of activated second resources in a single time unit.

[0304] In a specific example, the first indication information may indicate at least one of the following:

[0305] (1) Deactivate or activate part of the preamble, and indicate the starting preamble index and the number of consecutive preambles in the first indication information.

[0306] (2) Deactivate or activate all separate ROs.

[0307] (3) Deactivate or activate some separate ROs. The partial separate ROs are determined by the following methods:

[0308] Number of the RO group to be activated or deactivated;

[0309] The number of activated or deactivated RO groups. The grouping methods include the following: ROs with the same frequency domain as one group; ROs with the same time domain as one group; ROs with even occasion numbers as one group, and ROs with odd occasion numbers as one group.

[0310] Activate or deactivate the RO corresponding to the target RO mask, where the first indication information includes the target RO mask for determining a separate RO;

[0311] Activate or deactivate the RO on the target subframe number. The RO on the target subframe number is a separate RO.

[0312] Indicates the frequency domain starting position and continuous occasions, and determines separate ROs based on the frequency domain starting position and continuous occasions;

[0313] Indicate PRACH configuration index;

[0314] Indicates the offset value of the PRACH configuration index of the second resource relative to the PRACH configuration index of the first resource;

[0315] Indicates the target subframe number and time slot number, and determines the separate RO according to the target subframe number and time slot number.

[0316] (4) Deactivate or activate part of the preamble of a separate RO.

[0317] Part of the separate RO can be determined by the method mentioned in (3) above, and part of the preamble can be determined by the starting preamble index indicated in the first indication information and the number of consecutive preambles.

[0318] In some embodiments, the first indication information is carried by at least one of the following:

[0319] paging messages;

[0320] Radio Resource Control RRC connection establishment message;

[0321] RRC connection release message;

[0322] Downlink control information DCI;

[0323] Media Access Control Element MAC CE;

[0324] System Information Block SIB.

[0325] In some embodiments, the first configuration information is carried by at least one of the following:

[0326] paging messages;

[0327] RRC connection establishment message;

[0328] RRC connection release message;

[0329] SIB.

[0330] In one specific embodiment, PRACH resource adaptation is performed, and the dynamically adjusted resources (secondary resources and / or separate RO and / or dynamic RO) are not allowed to overlap with the legacy RO, and the frequency domain starting position and frequency domain length of the dynamically adjusted resources are the same as those of the legacy RO. As shown in Figure 9, blue represents legacy RACH resources, and red represents RACH resources that can be dynamically activated or deactivated (applicable to UEs), which can be named separate PRACH resources or dynamic PRACH resources.

[0331] The configuration method of the PRACH resource that is allowed to be dynamically activated includes at least one of the following:

[0332] Configuration method (1): The RA partition configuration method is not used.

[0333] Configure rach-ConfigCommonForNES in the bandwidth part uplink common configuration (BWP-UplinkCommon) in the following ways:

[0334] Method 1: rach-ConfigCommonForNES can be a complete set of RACH time and frequency resource configurations, including all parameters included in rach-ConfigCommon in existing protocols;

[0335] Method 2: rach-ConfigCommonForNES can indicate only some parameters, such as at least one of the following:

[0336] The period (y) of PRACH resources (red) allowed to be dynamically activated within a single legacy PRACH resource period (x);

[0337] The number of PRACH resource clusters (e.g., 3 clusters in Figure 9 ) or the number of occasions (e.g., 6 occasions per cluster in the figure) that can be dynamically activated within a single legacy PRACH resource period (x) is defined as follows:

[0338] The period of the PRACH resource allowed to be dynamically activated is 1 / Q of the period (i.e., the period ratio) of a single legacy PRACH resource period (x). For example, in Figure 9, x = 4, 1 / Q = 1 / 4;

[0339] The time interval (y) between multiple PRACH resources (red) allowed to be dynamically activated;

[0340] The time interval (z) between the first PRACH resource allowed to be dynamically activated and the first legacy PRACH resource in each cycle, and the number of PRACH resources and / or PRACH opportunities allowed to be dynamically activated.

[0341] The above-mentioned method 2 can reduce the configuration parameters and save the configuration overhead of SIB1. The units of the above-mentioned period include: system frame, subframe, ms, slot, symbol, etc.

[0342] The resources configured by rach-ConfigCommonForNES are not activated by default and are subsequently activated by the network-side device; or they are activated by default and can be deactivated by instructions from the network-side device later.

[0343] Configuration method (2): Use the same configuration method as for RA partition and configure rach-ConfigCommonForNES in additionalRACH-ConfigCommonList.

[0344] Method 1: rach-ConfigCommonForNES can be a complete set of rach-ConfigCommon parameters, including the time-frequency resource configuration parameters already in the current protocol, such as PRACH configuration index.

[0345] Method 2: rach-ConfigCommonForNES can also specify only some parameters, such as at least one of the following:

[0346] The period (y) of PRACH resources (red) allowed to be dynamically activated within a single legacy PRACH resource period (x);

[0347] The number of PRACH resources allowed to be dynamically activated within a single legacy PRACH resource period (x) (e.g., 3 in Figure 9);

[0348] Once activated, the dynamically activated PRACH resource (second resource) is valid for P system frames or subframes or ms or slots;

[0349] The period of candidate PRACH resources allowed to be dynamically activated is 1 / Q (i.e., the period ratio relationship) of a single legacy PRACH resource period (x). For example, in Figure 9, x = 4, 1 / Q = 1 / 4;

[0350] The time interval (y) between multiple PRACH resources (red) allowed to be dynamically activated;

[0351] The time interval (z) between the first PRACH resource allowed to be dynamically activated and the first legacy PRACH resource in each cycle, and the number of PRACH resources allowed to be dynamically activated;

[0352] The above method 2 can reduce the configuration parameters and save the configuration overhead of SIB1.

[0353] The resources configured by rach-ConfigCommonForNES are not activated by default and are subsequently activated by the network-side device; or they are activated by default and are subsequently deactivated by instructions from the network-side device.

[0354] The network side device can configure resources through RRC or SIB. The network side device can activate or deactivate dynamic PRACH resource configuration through messages such as paging messages, SIB, RRC release / RRC setup, DCI / MAC CE, etc.

[0355] The content indicated by the network side device may include at least one of the following:

[0356] Activate dynamic PRACH resources;

[0357] Deactivate dynamic PRACH resources;

[0358] PRACH configuration Index (i.e., directly indicating the new PRACH cycle);

[0359] The period (y) of dynamically activated PRACH resources (red) within a single legacy PRACH resource period (x);

[0360] The number of candidate PRACH resources dynamically activated within a single legacy PRACH resource period (x) (e.g., 3 in Figure 9 );

[0361] The period (y) of dynamically activated PRACH resources (red) within a single radio frame;

[0362] The number of candidate PRACH resources that are dynamically activated within a single radio frame;

[0363] The time interval (y) between multiple dynamically activated PRACH resources (red).

[0364] When the UE receives an activation indication from the network-side device, the UE may apply the parameters of rach-ConfigCommonForNES to determine the RACH resources. For parameters not configured, the UE applies the corresponding parameters indicated in RACH-ConfigCommon or MsgA-ConfigCommon.

[0365] In another specific embodiment, PRACH resource adaptation, the dynamically adjusted resources are not allowed to overlap with the legacy RO, and the frequency domain starting position and length of the dynamically adjusted resources are different from the frequency domain starting position and length of the legacy RO, as shown in Figure 10, where blue represents the legacy RACH resources, and red represents the RACH resources that can be dynamically activated or deactivated, which can be named separate PRACH resources or dynamic PRACH resources.

[0366] The configuration method of PRACH resources that can be dynamically activated includes at least one of the following:

[0367] Configuration method (1): Do not use the configuration method of RApartition.

[0368] Configure rach-ConfigCommonForNES in BWP-UplinkCommon, including the following methods:

[0369] Method 1: rach-ConfigCommonForNES can be a complete set of RACH time and frequency resource configurations, including all parameters included in rach-ConfigCommon in existing protocols;

[0370] Method 2: rach-ConfigCommonForNES can indicate only some parameters, such as at least one of the following:

[0371] Frequency domain starting position msg1-FrequencyStart;

[0372] Number of frequency domain PRACH occasions msg1-FDM;

[0373] Allows the PRACH configuration index corresponding to the dynamically activated PRACH resource to be offset from the PRACH configuration index corresponding to the legacy PRACH resource. This method can save bits.

[0374] The ratio or relative value between the period of the PRACH resources allowed to be dynamically activated and the period of the legacy PRACH resources. For example, by configuring the period of the dynamically activated PRACH resources to be 1 / 4 of the blue resources, the frequency domain starting position, and the frequency domain length, the position of the PRACH resources allowed to be dynamically activated can be determined. Other parameters, such as the number of RACH time slots in each subframe or the number of RACH opportunities in a RACH time slot, refer to the configuration of legacy RACH resources.

[0375] The resources configured by rach-ConfigCommonForNES are not activated by default and are subsequently activated by the network-side device; or they are activated by default and are subsequently deactivated by the network-side device.

[0376] Configuration method (2): Use the same configuration method as for RA partition and configure rach-ConfigCommonForNES in additionalRACH-ConfigCommonList.

[0377] Method 1: rach-ConfigCommonForNES can be a complete set of rach-ConfigCommon parameters, including the time-frequency resource configuration parameters already in the current protocol, such as PRACH configuration index.

[0378] Method 2: rach-ConfigCommonForNES can also specify only some parameters, such as at least one of the following:

[0379] Frequency domain starting position msg1-FrequencyStart;

[0380] The ratio or relative value between the period of PRACH resources allowed to be dynamically activated and the period of legacy PRACH resources;

[0381] Whether the time domain position of the PRACH resources allowed to be dynamically activated is the same as the time domain position of the legacy PRACH resources.

[0382] The resources configured by rach-ConfigCommonForNES are not activated by default and are subsequently activated by the network-side device; or they are activated by default and are subsequently deactivated by the network-side device.

[0383] In a specific embodiment, as shown in Figure 10, the network side device configures the first resource and the second resource in the first configuration information, wherein the first resource has a PRACH cluster in each radio frame, and each PRACH cluster has 6 PRACH occasions. When configuring the time-frequency resources of the second resource, it is only necessary to configure the frequency domain starting position of the second resource, the number of clusters of the second resource relative to the clusters of the first resource in each radio frame, and the interval between each cluster of the second resource.

[0384] The PRACH resource indication method provided in the embodiment of the present application may be performed by a PRACH resource indication device. In the embodiment of the present application, the PRACH resource indication device performing the PRACH resource indication method is taken as an example to illustrate the PRACH resource indication device provided in the embodiment of the present application.

[0385] Please refer to FIG11, which is a schematic structural diagram of a PRACH resource indication device provided in an embodiment of the present application. The device is applied to a terminal 3. As shown in FIG11, the PRACH resource indication device includes:

[0386] A receiving module 31 is configured to receive first configuration information and first indication information of a network-side device, where the first configuration information is configuration information of a candidate PRACH resource;

[0387] A processing module 32, configured to determine a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information;

[0388] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0389] In some embodiments, the candidate PRACH resource further includes a first resource, and the first resource and / or the second resource satisfies at least one of the following:

[0390] The first resource and the second resource are numbered together and mapped to a synchronization signal block SSB;

[0391] The mapping relationship between the SSB and the random access occasion RO of the first resource and the second resource is the same or different;

[0392] The preamble sequence configurations of the first resource and the second resource are the same or different;

[0393] The first resource and the second resource have different priorities;

[0394] The time-frequency positions of the first resource and the second resource completely overlap, completely do not overlap, or partially overlap;

[0395] The business types of the business associated with the first resource and the second resource are different;

[0396] The quality of service (QoS) of services associated with the first resource and the second resource are different;

[0397] The first resource and the second resource are associated with different terminal types;

[0398] The first resource is a PRACH resource that is not allowed to be activated or deactivated.

[0399] In some embodiments, the mapping relationship between the SSB and the RO of the first resource and the second resource being the same includes at least one of the following:

[0400] The number and / or number of SSBs mapped to the first resource is the same as the number and / or number of SSBs mapped to the second resource;

[0401] The number of SSBs associated with each opportunity on the first resource is the same as the number of SSBs associated with each opportunity on the second resource.

[0402] In some embodiments, the difference in mapping relationship between SSB and RO between the first resource and the second resource includes at least one of the following:

[0403] The number and / or number of SSBs mapped to the first resource is different from the number and / or number of SSBs mapped to the second resource;

[0404] The number of SSBs associated with each opportunity on the first resource is different from the number of SSBs associated with each opportunity on the second resource.

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

[0406] time domain resource configuration, frequency domain resource configuration, and preamble sequence configuration of the first resource;

[0407] Time domain resource configuration and frequency domain resource configuration of the second resource;

[0408] preamble configuration of the second resource;

[0409] The SSB index associated with the second resource;

[0410] The time domain relative relationship between the second resource and the first resource.

[0411] In some embodiments, the time domain resource configuration and frequency domain resource configuration of the second resource include at least one of the following:

[0412] All parameters of the random access channel common configuration RACH-ConfigCommon;

[0413] Some parameters of RACH-ConfigCommon;

[0414] RO group information that the second resource allows to be activated or deactivated;

[0415] Target SSB index;

[0416] RO mask mask.

[0417] In some embodiments, when the time domain resource configuration and frequency domain resource configuration of the second resource only include some parameters of RACH-ConfigCommon, other parameters used to determine the second resource are determined by the time domain resource configuration and / or frequency domain resource configuration of the first resource.

[0418] In some embodiments, the grouping manner of the RO group of the second resource includes at least one of the following:

[0419] The network side device configures the group identifier to which each RO in the RO of the second resource belongs;

[0420] ROs are grouped according to the RO mask configured on the network side device;

[0421] Grouping according to the rules predefined by the protocol;

[0422] The protocol predefined rules include any of the following: ROs within a preset time domain range are grouped together, ROs within a preset frequency domain range are grouped together, ROs within a preset number range are grouped together, ROs with even occasion numbers are grouped together, or ROs with odd occasion numbers are grouped together.

[0423] In some embodiments, when the first configuration information includes a target SSB index,

[0424] The RO associated with the target SSB index is allowed to be activated or deactivated; and / or

[0425] The processing module 32 determines a timing when the second resource is allowed to be activated or deactivated according to the RO associated with the target SSB index.

[0426] In some embodiments, when the time domain resource configuration and the frequency domain resource configuration of the second resource include an RO mask,

[0427] The RO corresponding to the RO mask is allowed to be activated or deactivated; and / or

[0428] The processing module 32 determines a timing at which the second resource is allowed to be activated or deactivated according to the RO mask.

[0429] In some embodiments, the preamble configuration of the second resource includes at least one of the following:

[0430] The feature associated with the preamble of the second resource and the starting preamble number and quantity of each feature;

[0431] The starting index and number of target preambles.

[0432] In some embodiments, the temporal relative relationship between the second resource and the first resource includes at least one of the following:

[0433] the period of the second resource within the period of the first resource;

[0434] the number of cluster bursts and / or opportunities of the second resource within the period of the first resource;

[0435] a ratio of a period of the second resource to a period of the first resource;

[0436] The time interval between each opportunity and / or opportunity cluster RO cluster of the second resource;

[0437] a time interval between the timing of the second resource and the timing of the first resource;

[0438] In each time unit, the time interval between the timing of the second resource and the timing of the first resource;

[0439] The timing and / or number of clusters at which the second resource is allowed to be activated or deactivated within each time unit;

[0440] an offset value between the PRACH configuration index of the second resource and the PRACH configuration index of the first resource;

[0441] A time offset value of the second resource relative to the first PRACH time slot or the last PRACH time slot or each PRACH time slot or the first RO or the last RO or the first PRACH cluster or each PRACH cluster of the first resource;

[0442] The number of PRACH time slots, ROs, or clusters of the second resource relative to the first resource;

[0443] The period and / or the time interval includes at least one of the following: a radio frame, a half frame, a subframe, a time slot, a millisecond, a PRACH period, a PRACH time slot, a PRACH opportunity, a PRACH association period, and a PRACH association pattern period.

[0444] In some embodiments, the first indication information indicates at least one of the following:

[0445] PRACH configuration index;

[0446] Activate or deactivate all second resources;

[0447] activating or deactivating part of the second resource;

[0448] a validity period for activating or deactivating all or part of the second resource;

[0449] an SSB index associated with the second resource;

[0450] Second indication information for turning on or off discontinuous transmission and / or discontinuous reception of a cell.

[0451] In some embodiments, when the first indication information indicates activation or deactivation of part of the second resources, the first indication information further indicates at least one of the following:

[0452] an identifier of a resource group activated or deactivated in the second resource;

[0453] Subframe number or time slot number;

[0454] The frequency domain starting position of the starting opportunity in the second resource and the number of multiple opportunities consecutively in the order of first frequency domain and then time domain;

[0455] an identifier of a starting opportunity in the second resource and a number of consecutive opportunities in the order of first frequency domain and then time domain;

[0456] an identifier of a starting preamble and the number of activated or deactivated preambles in the second resource;

[0457] The period of the second resource activated within the period of the first resource;

[0458] the number of the second resources activated during the first resource cycle;

[0459] a period of the second resource being activated within a single time unit;

[0460] The number of activated second resources in a single time unit.

[0461] In some embodiments, the first indication information is carried by at least one of the following:

[0462] paging messages;

[0463] Radio Resource Control RRC connection establishment message;

[0464] RRC connection release message;

[0465] Downlink control information DCI;

[0466] Media Access Control Element MAC CE;

[0467] System Information Block SIB.

[0468] In some embodiments, the first configuration information is carried by at least one of the following:

[0469] paging messages;

[0470] RRC connection establishment message;

[0471] RRC connection release message;

[0472] SIB.

[0473] In some embodiments, when both the first resource and the second resource are configured or indicated as valid by the network-side device, the processing module 32 determines the RO for random access in the target PRACH resource according to at least one of the following:

[0474] Instructions or configuration of network-side equipment;

[0475] Number of random access failures;

[0476] The time and / or distance at which the PRACH is sent is the shortest;

[0477] Priority of RO resources;

[0478] Service type or service QoS;

[0479] The type or capabilities of the terminal.

[0480] In some embodiments, when the terminal determines the target PRACH resource according to the instruction or configuration of the network side device, if the network side device configures the second resource, the processing module 32 preferentially selects the second resource as the target PRACH resource; or

[0481] In a case where the network side device configures the second resource and the second resource is initially an invalid resource by default, the processing module 32 preferentially selects the second resource as the target PRACH resource after receiving the first indication information.

[0482] In some embodiments, the second resource is an RO resource that satisfies at least one of the following:

[0483] a resource independent of the first resource;

[0484] Resources that can be activated or deactivated by network-side devices;

[0485] Resources with a different mapping mode from the first resource mapping mode, the mapping mode including mapping between SSB and RO and mapping between preamble and SSB;

[0486] Resources configured by attaching RACH-ConfigCommon.

[0487] In some embodiments, when the first indication information is not received, the processing module 32 determines the target PRACH resource according to the parameters indicated in the RACH-ConfigCommon or the message MsgA-ConfigCommon.

[0488] The embodiment of the present application further provides a PRACH resource indication device, as shown in FIG12 , which is applied to a network-side device 4 and includes:

[0489] A sending module 41 is configured to send first configuration information and / or first indication information to a terminal, where the first configuration information is configuration information of a candidate PRACH resource, so that the terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information;

[0490] The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

[0491] In some embodiments, the sending module 41 is specifically configured to determine whether to send the first indication information according to at least one of the following:

[0492] Random access collision level of the terminal;

[0493] The number of terminals that support sending the uplink wake-up signal WUS;

[0494] The number of idle terminals;

[0495] Information reported by idle terminals.

[0496] In some embodiments, the random access collision degree of the terminal is determined based on at least one of the following:

[0497] The percentage of random access preamble used;

[0498] The number or percentage of messages MSG3 with different terminal identifiers.

[0499] In some embodiments, the information reported by the idle terminal includes at least one of the following:

[0500] Msg1 is sent repeatedly.

[0501] Msg1 power increase times;

[0502] Msg1 power boost value;

[0503] Feedback information after successful access carried in MSG3.

[0504] In some embodiments, the candidate PRACH resource further includes a first resource, and the first resource and / or the second resource satisfies at least one of the following:

[0505] The first resource and the second resource are numbered together and mapped to a synchronization signal block SSB;

[0506] The mapping relationship between the SSB and the random access occasion RO of the first resource and the second resource is the same or different;

[0507] The preamble sequence configurations of the first resource and the second resource are the same or different;

[0508] The first resource and the second resource have different priorities;

[0509] The time-frequency positions of the first resource and the second resource completely overlap, completely do not overlap, or partially overlap;

[0510] The business types of the business associated with the first resource and the second resource are different;

[0511] The quality of service (QoS) of services associated with the first resource and the second resource are different;

[0512] The first resource and the second resource are associated with different terminal types;

[0513] The first resource is a PRACH resource that is not allowed to be activated or deactivated.

[0514] In some embodiments, the mapping relationship between the SSB and the RO of the first resource and the second resource being the same includes at least one of the following:

[0515] The number and / or number of SSBs mapped to the first resource is the same as the number and / or number of SSBs mapped to the second resource;

[0516] The number of SSBs associated with each opportunity on the first resource is the same as the number of SSBs associated with each opportunity on the second resource.

[0517] In some embodiments, the difference in mapping relationship between SSB and RO between the first resource and the second resource includes at least one of the following:

[0518] The number and / or number of SSBs mapped to the first resource is different from the number and / or number of SSBs mapped to the second resource;

[0519] The number of SSBs associated with each opportunity on the first resource is different from the number of SSBs associated with each opportunity on the second resource.

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

[0521] time domain resource configuration, frequency domain resource configuration, and preamble sequence configuration of the first resource;

[0522] Time domain resource configuration and frequency domain resource configuration of the second resource;

[0523] preamble configuration of the second resource;

[0524] The SSB index associated with the second resource;

[0525] The time domain relative relationship between the second resource and the first resource.

[0526] In some embodiments, the time domain resource configuration and frequency domain resource configuration of the second resource include at least one of the following:

[0527] All parameters of the random access channel common configuration RACH-ConfigCommon;

[0528] Some parameters of RACH-ConfigCommon;

[0529] RO group information that the second resource allows to be activated or deactivated;

[0530] Target SSB index;

[0531] RO mask mask.

[0532] In some embodiments, when the time domain resource configuration and frequency domain resource configuration of the second resource only include some parameters of RACH-ConfigCommon, other parameters used to determine the second resource are determined by the time domain resource configuration and / or frequency domain resource configuration of the first resource.

[0533] In some embodiments, the grouping manner of the RO group of the second resource includes at least one of the following:

[0534] The network side device configures the group identifier to which each RO in the RO of the second resource belongs;

[0535] ROs are grouped according to the RO mask configured on the network side device;

[0536] Grouping according to the rules predefined by the protocol;

[0537] The protocol predefined rules include any of the following: ROs within a preset time domain range are grouped together, ROs within a preset frequency domain range are grouped together, ROs within a preset number range are grouped together, ROs with even occasion numbers are grouped together, or ROs with odd occasion numbers are grouped together.

[0538] In some embodiments, when the first configuration information includes a target SSB index,

[0539] The RO associated with the target SSB index is allowed to be activated or deactivated; and / or

[0540] The terminal determines a timing when the second resource is allowed to be activated or deactivated according to the RO associated with the target SSB index.

[0541] In some embodiments, when the time domain resource configuration and the frequency domain resource configuration of the second resource include an RO mask,

[0542] The RO corresponding to the RO mask is allowed to be activated or deactivated; and / or

[0543] The terminal determines, according to the RO mask, a timing at which the second resource is allowed to be activated or deactivated.

[0544] In some embodiments, the preamble configuration of the second resource includes at least one of the following:

[0545] The feature associated with the preamble of the second resource and the starting preamble number and quantity of each feature;

[0546] The starting index and number of target preambles.

[0547] In some embodiments, the temporal relative relationship between the second resource and the first resource includes at least one of the following:

[0548] the period of the second resource within the period of the first resource;

[0549] the number of cluster bursts and / or opportunities of the second resource within the period of the first resource;

[0550] a ratio of a period of the second resource to a period of the first resource;

[0551] The time interval between each opportunity and / or opportunity cluster RO cluster of the second resource;

[0552] a time interval between the timing of the second resource and the timing of the first resource;

[0553] In each time unit, the time interval between the timing of the second resource and the timing of the first resource;

[0554] The timing and / or number of clusters at which the second resource is allowed to be activated or deactivated within each time unit;

[0555] an offset value between the PRACH configuration index of the second resource and the PRACH configuration index of the first resource;

[0556] A time offset value of the second resource relative to the first PRACH time slot or the last PRACH time slot or each PRACH time slot or the first RO or the last RO or the first PRACH cluster or each PRACH cluster of the first resource;

[0557] The number of PRACH time slots, ROs, or clusters of the second resource relative to the first resource;

[0558] The period and / or the time interval includes at least one of the following: a radio frame, a half frame, a subframe, a time slot, a millisecond, a PRACH period, a PRACH time slot, a PRACH opportunity, a PRACH association period, and a PRACH association pattern period.

[0559] In some embodiments, the first indication information indicates at least one of the following:

[0560] PRACH configuration index;

[0561] Activate or deactivate all second resources;

[0562] activating or deactivating part of the second resource;

[0563] a validity period for activating or deactivating all or part of the second resource;

[0564] an SSB index associated with the second resource;

[0565] Second indication information for turning on or off discontinuous transmission and / or discontinuous reception of a cell.

[0566] In some embodiments, when the first indication information indicates activation or deactivation of part of the second resources, the first indication information further indicates at least one of the following:

[0567] an identifier of a resource group activated or deactivated in the second resource;

[0568] Subframe number or time slot number;

[0569] The frequency domain starting position of the starting opportunity in the second resource and the number of multiple opportunities that are consecutive in the order of first frequency domain and then time domain;

[0570] an identifier of a starting opportunity in the second resource and a number of consecutive opportunities in the order of first frequency domain and then time domain;

[0571] an identifier of a starting preamble and the number of activated or deactivated preambles in the second resource;

[0572] The period of the second resource activated within the period of the first resource;

[0573] the number of the second resources activated during the first resource cycle;

[0574] a period of the second resource being activated within a single time unit;

[0575] The number of activated second resources in a single time unit.

[0576] In some embodiments, the first indication information is carried by at least one of the following:

[0577] paging messages;

[0578] Radio Resource Control RRC connection establishment message;

[0579] RRC connection release message;

[0580] Downlink control information DCI;

[0581] Media Access Control Element MAC CE;

[0582] System Information Block SIB.

[0583] In some embodiments, the first configuration information is carried by at least one of the following:

[0584] paging messages;

[0585] RRC connection establishment message;

[0586] RRC connection release message;

[0587] SIB.

[0588] The PRACH resource indication device 30 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 the electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device 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 include servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0589] The PRACH resource indication device provided in the embodiment of the present application can implement the various processes implemented in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0590] As shown in Figure 13, an embodiment of the present application further provides a communication device 60, including a processor 61 and a memory 62. The memory 62 stores a program or instruction that can be run on the processor 61. For example, when the communication device 60 is a terminal, the program or instruction is executed by the processor 61 to implement the various steps of the above-mentioned PRACH resource indication method embodiment and can achieve the same technical effect. When the communication device 60 is a network-side device, the program or instruction is executed by the processor 61 to implement the various steps of the above-mentioned PRACH resource indication method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0591] The present application also provides a terminal 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 in the method embodiment shown in FIG4 . This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this terminal embodiment and can achieve the same technical effects.

[0592] Specifically, FIG14 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0593] The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709 and at least some of the components of the processor 710.

[0594] Those skilled in the art will appreciate that the terminal 700 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 710 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 14 does not constitute a limitation of the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be described in detail here.

[0595] It should be understood that in an embodiment of the present application, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processing unit 7041 processes the 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 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 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.

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

[0597] The memory 709 can be used to store software programs or instructions and various data. The memory 709 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 709 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 a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0598] Processor 710 may include one or more processing units. Optionally, processor 710 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 710.

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

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

[0601] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 15, the network-side device 80 includes an antenna 81, a radio frequency device 82, a baseband device 83, a processor 84, and a memory 85. Antenna 81 is connected to radio frequency device 82. In the uplink direction, radio frequency device 82 receives information via antenna 81 and sends the received information to baseband device 83 for processing. In the downlink direction, baseband device 83 processes the information to be transmitted and sends it to radio frequency device 82. Radio frequency device 82 processes the received information and then sends it through antenna 81.

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

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

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

[0605] Specifically, the network side device 80 of the embodiment of the present application also includes: instructions or programs stored in the memory 85 and can be run on the processor 84. The processor 84 calls the instructions or programs in the memory 85 to execute the methods executed by each module shown in Figure 12 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0606] 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 the processor, the various processes of the above-mentioned PRACH resource indication method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0608] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run a program or instruction to implement the various processes of the above-mentioned PRACH resource indication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0610] 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 of the above-mentioned PRACH resource indication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0611] An embodiment of the present application further provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the PRACH resource indication method described above, and the network-side device can be used to execute the steps of the PRACH resource indication method described above.

[0612] 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, but 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.

[0613] 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 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 causing a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0614] 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 PRACH resource indication method, comprising: The terminal receives first configuration information and first indication information of the network side device, where the first configuration information is configuration information of a candidate physical random access channel PRACH resource; The terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information; The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

2. The PRACH resource indication method according to claim 1, wherein: The candidate PRACH resources further include a first resource, where the first resource and / or the second resource meets at least one of the following conditions: The first resource and the second resource are numbered together and mapped to a synchronization signal block SSB; The mapping relationship between the SSB and the random access occasion RO of the first resource and the second resource is the same or different; The preamble sequence configurations of the first resource and the second resource are the same or different; The first resource and the second resource have different priorities; The time-frequency positions of the first resource and the second resource completely overlap, completely do not overlap, or partially overlap; The business types of the business associated with the first resource and the second resource are different; The quality of service (QoS) of services associated with the first resource and the second resource are different; The first resource and the second resource are associated with different terminal types; The first resource is a PRACH resource that is not allowed to be activated or deactivated.

3. The PRACH resource indication method according to claim 2, wherein: The mapping relationship between the SSB and the RO of the first resource and the second resource is the same, including at least one of the following: The number and / or number of SSBs mapped to the first resource is the same as the number and / or number of SSBs mapped to the second resource; The number of SSBs associated with each opportunity on the first resource is the same as the number of SSBs associated with each opportunity on the second resource.

4. The PRACH resource indication method according to claim 2, wherein: The difference in mapping relationship between the SSB and the RO between the first resource and the second resource includes at least one of the following: The number and / or number of SSBs mapped to the first resource is different from the number and / or number of SSBs mapped to the second resource; The number of SSBs associated with each opportunity on the first resource is different from the number of SSBs associated with each opportunity on the second resource.

5. The PRACH resource indication method according to claim 2, wherein: The first configuration information includes at least one of the following: time domain resource configuration, frequency domain resource configuration, and preamble sequence configuration of the first resource; Time domain resource configuration and frequency domain resource configuration of the second resource; A random access preamble configuration of the second resource; The SSB index associated with the second resource; The time domain relative relationship between the second resource and the first resource.

6. The PRACH resource indication method according to claim 5, wherein: The time domain resource configuration and frequency domain resource configuration of the second resource include at least one of the following: All parameters of the random access channel common configuration RACH-ConfigCommon; Some parameters of RACH-ConfigCommon; RO group information that the second resource allows to be activated or deactivated; Target SSB index; RO mask mask.

7. The PRACH resource indication method according to claim 6, wherein: In a case where the time domain resource configuration and the frequency domain resource configuration of the second resource only include some parameters of RACH-ConfigCommon, other parameters used to determine the second resource are determined by the time domain resource configuration and / or the frequency domain resource configuration of the first resource.

8. The PRACH resource indication method according to claim 6, wherein: The grouping manner of the RO group of the second resource includes at least one of the following: The network side device configures the group identifier to which each RO in the RO of the second resource belongs; ROs are grouped according to the RO mask configured on the network side device; Grouping according to the rules predefined by the protocol; The protocol predefined rules include any of the following: ROs within a preset time domain range are grouped together, ROs within a preset frequency domain range are grouped together, ROs within a preset number range are grouped together, ROs with even occasion numbers are grouped together, or ROs with odd occasion numbers are grouped together.

9. The PRACH resource indication method according to claim 6, wherein: When the first configuration information includes the target SSB index, The RO associated with the target SSB index is allowed to be activated or deactivated; and / or The terminal determines a timing when the second resource is allowed to be activated or deactivated according to the RO associated with the target SSB index.

10. The PRACH resource indication method according to claim 6, wherein: When the time domain resource configuration and frequency domain resource configuration of the second resource include an RO mask, The RO corresponding to the RO mask is allowed to be activated or deactivated; and / or The terminal determines, according to the RO mask, a timing at which the second resource is allowed to be activated or deactivated.

11. The PRACH resource indication method according to claim 5, wherein: The preamble configuration of the second resource includes at least one of the following: The feature associated with the preamble of the second resource and the starting preamble number and quantity of each feature; The starting index and number of target preambles.

12. The PRACH resource indication method according to claim 5, wherein: The temporal relationship between the second resource and the first resource includes at least one of the following: the period of the second resource within the period of the first resource; the number of cluster bursts and / or opportunities of the second resource within the period of the first resource; a ratio of a period of the second resource to a period of the first resource; The time interval between each opportunity and / or opportunity cluster RO cluster of the second resource; a time interval between the timing of the second resource and the timing of the first resource; In each time unit, the time interval between the timing of the second resource and the timing of the first resource; The timing and / or number of clusters at which the second resource is allowed to be activated or deactivated within each time unit; an offset value between the PRACH configuration index of the second resource and the PRACH configuration index of the first resource; A time offset value of the second resource relative to the first PRACH time slot or the last PRACH time slot or each PRACH time slot or the first RO or the last RO or the first PRACH cluster or each PRACH cluster of the first resource; The number of PRACH time slots, ROs, or clusters of the second resource relative to the first resource; The period and / or the time interval includes at least one of the following: a radio frame, a half frame, a subframe, a time slot, a millisecond, a PRACH period, a PRACH time slot, a PRACH opportunity, a PRACH association period, and a PRACH association pattern period.

13. The PRACH resource indication method according to claim 2, wherein: The first indication information indicates at least one of the following: PRACH configuration index; Activate or deactivate all second resources; activating or deactivating part of the second resource; a validity period for activating or deactivating all or part of the second resource; an SSB index associated with the second resource; Second indication information for turning on or off discontinuous transmission and / or discontinuous reception of a cell.

14. The PRACH resource indication method according to claim 13, wherein: When the first indication information indicates activation or deactivation of part of the second resources, the first indication information further indicates at least one of the following: an identifier of a resource group activated or deactivated in the second resource; Subframe number or time slot number; The frequency domain starting position of the starting opportunity in the second resource and the number of multiple opportunities that are consecutive in the order of first frequency domain and then time domain; an identifier of a starting opportunity in the second resource and a number of consecutive opportunities in the order of first frequency domain and then time domain; an identifier of a starting preamble and the number of activated or deactivated preambles in the second resource; The period of the second resource activated within the period of the first resource; the number of the second resources activated during the period of the first resource; a period of the second resource being activated within a single time unit; The number of activated second resources in a single time unit.

15. The PRACH resource indication method according to claim 2, wherein: When both the first resource and the second resource are configured or indicated as valid by the network side device, the terminal determines the RO for random access in the target PRACH resource according to at least one of the following: Instructions or configuration of network-side equipment; Number of random access failures; The time and / or distance at which the PRACH is sent is the shortest; Priority of RO resources; Service type or service QoS; The type or capabilities of the terminal.

16. The PRACH resource indication method according to claim 15, wherein: When the terminal determines the target PRACH resource according to the instruction or configuration of the network side device, the terminal determines the target PRACH resource including: In a case where the network side device configures the second resource, the terminal preferentially selects the second resource as the target PRACH resource; or In a case where the network side device configures the second resource and the second resource is initially an invalid resource by default, the terminal preferentially selects the second resource as the target PRACH resource after receiving the first indication information.

17. The PRACH resource indication method according to claim 2, wherein: The second resource is an RO resource that satisfies at least one of the following conditions: a resource independent of the first resource; Resources that can be activated or deactivated by network-side devices; Resources with a different mapping mode from the first resource mapping mode, the mapping mode including mapping between SSB and RO and mapping between preamble and SSB; Resources configured by attaching RACH-ConfigCommon.

18. The PRACH resource indication method according to claim 1, wherein: The method further comprises: When the first indication information is not received, the terminal determines the target PRACH resource according to the parameters indicated in the RACH-ConfigCommon or the message MsgA-ConfigCommon.

19. A PRACH resource indication method, comprising: The network side device sends first configuration information and / or first indication information to the terminal, where the first configuration information is configuration information of candidate physical random access channel (PRACH) resources, so that the terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information; The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

20. The PRACH resource indication method according to claim 19, wherein: The network-side device determines whether to send the first indication information according to at least one of the following: Random access collision level of the terminal; The number of terminals that support sending the uplink wake-up signal WUS; The number of idle terminals; Information reported by idle terminals.

21. The PRACH resource indication method according to claim 20, wherein: The random access collision degree of the terminal is determined according to at least one of the following: The percentage of random access preamble used; The number or percentage of messages MSG3 with different terminal identifiers.

22. The PRACH resource indication method according to claim 20, wherein: The information reported by the idle terminal includes at least one of the following: Msg1 is sent repeatedly. Msg1 power increase times; Msg1 power boost value; The feedback information after successful access carried in MSG3.

23. The PRACH resource indication method according to claim 19, wherein: The candidate PRACH resources further include a first resource, where the first resource and / or the second resource meets at least one of the following conditions: The first resource and the second resource are numbered together and mapped to a synchronization signal block SSB; The mapping relationship between the SSB and the random access occasion RO of the first resource and the second resource is the same or different; The preamble sequence configurations of the first resource and the second resource are the same or different; The first resource and the second resource have different priorities; The time-frequency positions of the first resource and the second resource completely overlap, completely do not overlap, or partially overlap; The business types of the business associated with the first resource and the second resource are different; The quality of service (QoS) of services associated with the first resource and the second resource are different; The first resource and the second resource are associated with different terminal types; The first resource is a PRACH resource that is not allowed to be activated or deactivated.

24. The PRACH resource indication method according to claim 23, wherein: The mapping relationship between the SSB and the RO of the first resource and the second resource is the same, including at least one of the following: The number and / or number of SSBs mapped to the first resource is the same as the number and / or number of SSBs mapped to the second resource; The number of SSBs associated with each opportunity on the first resource is the same as the number of SSBs associated with each opportunity on the second resource.

25. The PRACH resource indication method according to claim 23, wherein: The difference in mapping relationship between the SSB and the RO between the first resource and the second resource includes at least one of the following: The number and / or number of SSBs mapped to the first resource is different from the number and / or number of SSBs mapped to the second resource; The number of SSBs associated with each opportunity on the first resource is different from the number of SSBs associated with each opportunity on the second resource.

26. The PRACH resource indication method according to claim 23, wherein: The first configuration information includes at least one of the following: time domain resource configuration, frequency domain resource configuration, and preamble sequence configuration of the first resource; Time domain resource configuration and frequency domain resource configuration of the second resource; preamble configuration of the second resource; The SSB index associated with the second resource; The time domain relative relationship between the second resource and the first resource.

27. The PRACH resource indication method according to claim 26, wherein: The time domain resource configuration and frequency domain resource configuration of the second resource include at least one of the following: All parameters of the random access channel common configuration RACH-ConfigCommon; Some parameters of RACH-ConfigCommon; RO group information that the second resource allows to be activated or deactivated; Target SSB index; RO mask mask.

28. The PRACH resource indication method according to claim 27, wherein: In a case where the time domain resource configuration and the frequency domain resource configuration of the second resource only include some parameters of RACH-ConfigCommon, other parameters used to determine the second resource are determined by the time domain resource configuration and / or the frequency domain resource configuration of the first resource.

29. The PRACH resource indication method according to claim 27, wherein: The grouping manner of the RO group of the second resource includes at least one of the following: The network side device configures the group identifier to which each RO in the RO of the second resource belongs; ROs are grouped according to the RO mask configured on the network side device; Grouping according to the rules predefined by the protocol; The protocol predefined rules include any of the following: ROs within a preset time domain range are grouped together, ROs within a preset frequency domain range are grouped together, ROs within a preset number range are grouped together, ROs with even occasion numbers are grouped together, or ROs with odd occasion numbers are grouped together.

30. The PRACH resource indication method according to claim 27, wherein: When the first configuration information includes the target SSB index, The RO associated with the target SSB index is allowed to be activated or deactivated; and / or The terminal determines a timing when the second resource is allowed to be activated or deactivated according to the RO associated with the target SSB index.

31. The PRACH resource indication method according to claim 27, wherein: When the time domain resource configuration and frequency domain resource configuration of the second resource include an RO mask, The RO corresponding to the RO mask is allowed to be activated or deactivated; and / or The terminal determines, according to the RO mask, a timing at which the second resource is allowed to be activated or deactivated.

32. The PRACH resource indication method according to claim 26, wherein: The preamble configuration of the second resource includes at least one of the following: The feature associated with the preamble of the second resource and the starting preamble number and quantity of each feature; The starting index and number of target preambles.

33. The PRACH resource indication method according to claim 26, wherein: The temporal relationship between the second resource and the first resource includes at least one of the following: the period of the second resource within the period of the first resource; the number of cluster bursts and / or opportunities of the second resource within the period of the first resource; a ratio of a period of the second resource to a period of the first resource; The time interval between each opportunity and / or opportunity cluster RO cluster of the second resource; a time interval between the timing of the second resource and the timing of the first resource; In each time unit, the time interval between the timing of the second resource and the timing of the first resource; The timing and / or number of clusters at which the second resource is allowed to be activated or deactivated within each time unit; an offset value between the PRACH configuration index of the second resource and the PRACH configuration index of the first resource; A time offset value of the second resource relative to the first PRACH time slot or the last PRACH time slot or each PRACH time slot or the first RO or the last RO or the first PRACH cluster or each PRACH cluster of the first resource; The number of PRACH time slots, ROs, or clusters of the second resource relative to the first resource; The period and / or the time interval includes at least one of the following: a radio frame, a half frame, a subframe, a time slot, a millisecond, a PRACH period, a PRACH time slot, a PRACH opportunity, a PRACH association period, and a PRACH association pattern period.

34. The PRACH resource indication method according to claim 23, wherein: The first indication information indicates at least one of the following: PRACH configuration index; Activate or deactivate all second resources; activating or deactivating part of the second resource; a validity period for activating or deactivating all or part of the second resource; an SSB index associated with the second resource; Second indication information for turning on or off discontinuous transmission and / or discontinuous reception of a cell.

35. The PRACH resource indication method according to claim 34, wherein: When the first indication information indicates activation or deactivation of part of the second resources, the first indication information further indicates at least one of the following: an identifier of a resource group activated or deactivated in the second resource; Subframe number or time slot number; The frequency domain starting position of the starting opportunity in the second resource and the number of multiple opportunities that are consecutive in the order of first frequency domain and then time domain; an identifier of a starting opportunity in the second resource and a number of consecutive opportunities in the order of first frequency domain and then time domain; an identifier of a starting preamble and the number of activated or deactivated preambles in the second resource; The period of the second resource activated within the period of the first resource; the number of the second resources activated during the period of the first resource; a period of the second resource being activated within a single time unit; The number of activated second resources in a single time unit.

36. A PRACH resource indication device, comprising: A receiving module, configured to receive first configuration information and first indication information of a network-side device, where the first configuration information is configuration information of a candidate physical random access channel (PRACH) resource; a processing module, configured to determine a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information; The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

37. The PRACH resource indication device according to claim 36, wherein: The candidate PRACH resources further include a first resource, where the first resource and / or the second resource meets at least one of the following conditions: The first resource and the second resource are numbered together and mapped to a synchronization signal block SSB; The mapping relationship between the SSB and the random access occasion RO of the first resource and the second resource is the same or different; The preamble sequence configurations of the first resource and the second resource are the same or different; The first resource and the second resource have different priorities; The time-frequency positions of the first resource and the second resource completely overlap, completely do not overlap, or partially overlap; The business types of the business associated with the first resource and the second resource are different; The quality of service (QoS) of services associated with the first resource and the second resource are different; The first resource and the second resource are associated with different terminal types; The first resource is a PRACH resource that is not allowed to be activated or deactivated.

38. A PRACH resource indication device, comprising: a sending module, configured to send first configuration information and / or first indication information to a terminal, where the first configuration information is configuration information of a candidate physical random access channel (PRACH) resource, so that the terminal determines a target PRACH resource from the candidate PRACH resources according to the first configuration information and the first indication information; The candidate PRACH resources include different types of PRACH resources, and the different types of PRACH resources include at least a second resource, and the second resource is a PRACH resource that is allowed to be activated or deactivated.

39. The PRACH resource indication device according to claim 38, wherein: The sending module is specifically configured to determine whether to send the first indication information according to at least one of the following: Random access collision level of the terminal; The number of terminals that support sending the uplink wake-up signal WUS; The number of idle terminals; Information reported by idle terminals.

40. A terminal 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 PRACH resource indication method according to any one of claims 1 to 18 are implemented.

41. A network-side device 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 PRACH resource indication method according to any one of claims 19 to 35 are implemented.

42. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the PRACH resource indication method according to any one of claims 1 to 18, or implements the steps of the PRACH resource indication method according to any one of claims 19 to 35.

Images