Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The method comprises: a terminal device receives first information sent by a network device, the first information comprising one or more physical random access channel (PRACH) configurations. Thus, PRACH transmission is enabled to be more flexible, thereby improving PRACH transmission performance.

Description

Wireless communication methods, terminal devices, and network devices Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal device, and network device. Background Technology

[0002] The random access procedure refers to the process from when a terminal device attempts to access the network by sending a random access preamble through the physical random access channel (PRACH) to when a basic signaling connection is established with the network. This process is a crucial step in establishing the initial communication connection between the terminal device and the network. Therefore, improving the performance of PRACH transmission is a problem that needs to be solved.

[0003] Summary of the Invention

[0004] This application provides a wireless communication method, terminal device, and network device. The various aspects covered by this application are described below.

[0005] In a first aspect, a wireless communication method is provided, comprising: a terminal device receiving first information sent by a network device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

[0006] In a second aspect, a wireless communication method is provided, comprising: a network device sending first information to a terminal device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

[0007] Thirdly, a terminal device is provided, comprising: a transceiver unit for receiving first information sent by a network device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

[0008] Fourthly, a network device is provided, comprising: a transceiver unit for sending first information to a terminal device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

[0009] Fifthly, a terminal device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store a program, and the processor is used to invoke the program in the memory and control the transceiver to receive or send signals so that the terminal device performs the method as described in the first aspect.

[0010] In a sixth aspect, a network device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store a program, and the processor is used to invoke the program in the memory and control the transceiver to receive or transmit signals so that the network device performs the method as described in the second aspect.

[0011] A seventh aspect provides an apparatus including a processor for calling a program from a memory to cause the apparatus to perform the method as described in any one of the first or second aspects.

[0012] Eighthly, a chip is provided, including a processor for calling a program from memory to cause a device having the chip mounted to perform the method as described in the first or second aspect.

[0013] Ninth aspect, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method as described in the first or second aspect.

[0014] A tenth aspect provides a computer program product, including a program that causes a computer to perform the method as described in the first or second aspect.

[0015] Eleventhly, a computer program is provided that causes a computer to perform the method as described in the first or second aspect.

[0016] In this embodiment of the application, the terminal device receives one or more PRACH configurations sent by the network device, thereby making PRACH transmission more flexible and improving PRACH transmission performance. Attached Figure Description

[0017] Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.

[0018] Figure 2 is a flowchart illustrating a wireless communication method according to an embodiment of this application.

[0019] Figure 3 is a flowchart illustrating a wireless communication method according to another embodiment of this application.

[0020] Figure 4 is a schematic diagram of the structure of the terminal device according to an embodiment of this application.

[0021] Figure 5 is a schematic diagram of the structure of a network device according to an embodiment of this application.

[0022] Figure 6 is a schematic diagram of a communication apparatus according to an embodiment of this application. Detailed Implementation

[0023] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0024] Wireless communication system

[0025] Figure 1 is an example diagram of the system architecture of a wireless communication system 100 to which embodiments of this application can be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network, such as a wireless network, through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity; this embodiment of the application does not limit this.

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

[0027] In this application embodiment, the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, in-vehicle equipment, etc. Terminal devices can also be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes. Optionally, terminal devices can act as base stations. For example, a terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) systems. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0028] In this embodiment, the network device can be a device used to communicate with a terminal device. The network device can be an access network device or a wireless access network device. For example, the network device can be a base station. The term "base station" can broadly encompass various names as follows, or can be replaced by names such as: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entity, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, or an entity that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or an entity that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0029] Furthermore, base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0030] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0031] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform such as a cloud platform.

[0032] In NR systems, the random access procedure allows terminal devices to initiate connection requests to network devices upon initial power-on or recovery from sleep mode. When a terminal device needs to switch to a new cell, the connection is re-established through the random access procedure. Through the random access procedure, terminal devices can request resources from network devices for data transmission or other communication. When traffic changes, terminal devices can dynamically request necessary resources via PRACH, enhancing network flexibility. Using a random preamble effectively reduces the probability of collisions, and collisions are handled through retransmission mechanisms. Events that trigger the random access procedure may include, for example, initial access from the radio resource control (RRC) idle (RRC_IDLE) state, RRC connection reconstruction, scheduling request (SR) failure, beam failure recovery, etc. Therefore, the random access procedure may execute when the terminal device is in the RRC idle, RRC inactive, or RRC connected states. To enable terminal devices in the network to have the opportunity for random access, network devices need to configure PRACH resources for the terminal devices to receive random access preambles from them. As an example, the terminal device can obtain the PRACH configuration through higher-layer signaling, thereby obtaining the PRACH resources in the time domain. Each PRACH configuration has a corresponding index, and each PRACH configuration corresponds to a distribution of random access occasions (ROs). The RO distribution is typically defined by the radio frame index, the intra-frame subframe number, and the start symbol within the time slot.

[0033] During random access, the terminal device first listens to system information sent by the network device, such as system information blocks (SIBs) 1 and 2, to understand the configuration and availability of PRACH resources. Then, based on the obtained PRACH configuration, the terminal device selects a PRACH preamble for random access. The terminal device sends the random access preamble within a predetermined PRACH time slot, and the network device processes the received preamble.

[0034] In NR, random access is a periodic, always-present process, and PRACH resources are typically fixed. However, the density of access requests from terminal devices varies over time. When user density is low, excessive PRACH resources can lead to resource waste. In such cells, even when there is no PRACH or low traffic, network devices may still need to frequently check PRACH, resulting in additional energy consumption and hindering network energy saving (NES). When terminal device density is high, insufficient PRACH resources can lead to access congestion. To achieve network energy saving, network devices can shorten monitoring time or extend sleep time between ROs when system load is low. However, PRACH configuration can only be updated via SIB1. Even if the number of terminal devices in a cell suddenly decreases significantly, and most configured ROs are not used by terminal devices to execute random access procedures, network devices may still need to monitor every configured RO. Clearly, this situation is detrimental to network energy saving.

[0035] In low-load scenarios, by adaptively adjusting the PRACH transmission period in the time domain, network devices can reduce unnecessary monitoring and thus enter a longer sleep state. However, network devices also need to ensure that this does not significantly impact the latency of end devices. PRACH configuration is provided through SIB1 or RRC messages depending on the specific use case of the random access procedure. Therefore, in principle, network devices can change the PRACH configuration by updating system information or reconfiguring RRC. However, frequent updates to SIB1 or frequent RRC reconfigurations can also have adverse effects on network energy saving and signaling overhead.

[0036] Therefore, embodiments of this application provide a wireless communication method in which a terminal device receives one or more PRACH configurations sent by a network device, thereby making PRACH transmission more flexible and improving PRACH transmission performance. In other words, through one or more PRACH configurations, dynamic adjustment of PRACH resources is achieved, allowing PRACH transmission to adapt to changes in factors such as traffic and load, network energy-saving requirements, terminal device distribution, and time, thereby optimizing resource utilization and balancing the initial access performance of the terminal device.

[0037] It is understandable that for traditional terminal devices, such as those supporting lower protocol versions (e.g., Release 18 and earlier in NR), network devices instruct them on PRACH configuration via system information or RRC messages. This is referred to as the basic PRACH configuration or baseline PRACH configuration, and the PRACH period included in the basic PRACH configuration is called the base period or baseline period. Various PRACH parameters included in the basic PRACH configuration can be adjusted, but need to be updated via system information or RRC messages. The baseline PRACH configuration may also be used by terminal devices supporting higher versions (e.g., Release 19 and later in NR). Simultaneously, these higher-version terminal devices can obtain multiple additional PRACH configurations, meaning they can obtain additional PRACH resources for uplink access. Since the number of higher-version terminal devices may increase in the future, providing them with multiple additional PRACH configurations and activating PRACH configurations adapted to the current scenario can achieve network energy saving while meeting uplink access requirements.

[0038] The embodiments of this application will be described in detail below with reference to Figure 2.

[0039] Figure 2 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method 200 shown in Figure 2 can be executed by a terminal device and a network device. The terminal device can be, for example, the terminal device 120 shown in Figure 1, and the network device can be, for example, the network device 110 shown in Figure 1.

[0040] Referring to Figure 2, in step 210, the network device sends the first information to the terminal device.

[0041] Accordingly, in step 220, the terminal device receives the first information sent by the network device.

[0042] The first information includes one or more PRACH configurations. This first information may be carried, for example, in an RRC message or system information (e.g., SIB1 or SIB2). It is understood that the one or more PRACH configurations may be additional PRACH configurations configured by the network device for terminal devices with higher versions (e.g., Release 19 and later in NR). The parameters in the one or more PRACH configurations may be at least partially different from the parameters in the basic PRACH configuration (e.g., the PRACH configuration configured by the network device for terminal devices with Release 18 and earlier versions in NR); or, the parameters in the one or more PRACH configurations may be the same as the parameters in the basic PRACH configuration, but the parameters in the one or more PRACH configurations can be adjusted by the second information, the details of which are described in subsequent sections.

[0043] PRACH configuration may include one or more of the following parameters: the index of the PRACH configuration; the period of the PRACH resource; the subframe number corresponding to the PRACH slot; the number of PRACH slots; the number of ROs in the PRACH slots; the RO interval; the RO offset; and the offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration. The subframe number corresponding to the PRACH slot indicates which subframes include PRACH slots for PRACH transmission, in which the terminal device needs to perform random access. The number of PRACH slots refers to the number of slots allocated to the terminal device for PRACH transmission in the subframes corresponding to the aforementioned subframe numbers. The number of ROs refers to the number of ROs available for random access in each PRACH resource (e.g., a PRACH slot). The period of the PRACH resource, also referred to as the period for PRACH transmission or the PRACH period, refers to the time interval at which the PRACH resource recurs. This parameter affects the timing of the terminal device sending a random access request, i.e., the RO. Each PRACH resource may include multiple RO positions, and the interval between adjacent RO positions is called the RO interval. In the PRACH configuration, the RO offset refers to the offset of the RO in each PRACH resource relative to a specific reference point (e.g., the calculation start point of the PRACH resource). The RO interval can be, for example, parameter x as shown in Table 6.3.3.2 of Protocol 38.211, and the RO offset can be, for example, parameter y as shown in Table 6.3.3.2 of Protocol 38.211.

[0044] Among the multiple PRACH configurations, some or all of the above parameters (e.g., the period of the PRACH resource, the subframe number corresponding to the PRACH slot, the number of PRACH slots, the number of ROs in the PRACH slot, the RO interval, the RO offset, etc.) may be different. Furthermore, the multiple PRACH configurations may have their own indices, such as PRACH configuration #1, PRACH configuration #2, ..., PRACH configuration #N.

[0045] As mentioned earlier, the network device can also send a basic PRACH configuration to the terminal device, and the terminal device receives the basic PRACH configuration sent by the network device. The basic PRACH configuration can be carried, for example, in an RRC message or system information (e.g., SIB1). The basic PRACH configuration includes a basic period for PRACH transmission. When configuring PRACH resources, the network device provides a basic PRACH configuration for traditional terminal devices, and configures one or more additional PRACH configurations (i.e., one or more PRACH configurations indicated in the first information) for higher version terminal devices. These additional PRACH configurations can share some parameters with the basic PRACH configuration. For example, the basic PRACH configuration and the additional PRACH configuration may have the same parameters, such as the subframe number corresponding to the PRACH slot, the number of PRACH slots, the number of ROs in the PRACH slots, and the RO offset, only differing in the PRACH period and / or RO interval. Furthermore, the additional PRACH configuration may include other periods different from the basic period in the basic PRACH configuration. In some implementations, the additional PRACH configuration includes a period shorter than the base PRACH period, and / or the additional PRACH configuration includes a RO interval shorter than the RO interval in the base PRACH configuration. For example, the one or more periods in the first message are half the base period. M The value of M associated with one or more periods can be different, and M is a positive integer.

[0046] For the same number of SSBs, the network energy saving gain typically increases with the increase in the number of PRACH configurations. Network devices notify terminal devices of the time-domain resources used for PRACH transmission, such as period, subframe, time slot, and orthogonal frequency division multiplexing (OFDM) symbols, through the PRACH configuration index indicated in the SIB1 or RRC message. Therefore, network devices can configure a always-on PRACH mode with a basic period for traditional terminal devices, while configuring one or more additional PRACH modes different from the basic PRACH configuration for higher-version terminal devices. This flexible and variable PRACH configuration allows for more dynamic adaptive decision-making by the network device. The network device can notify higher-version terminal devices of the current required PRACH configuration (which can be the basic PRACH configuration or one or more additional PRACH configurations) through new signaling (e.g., carrying second information), thus adapting to the current scenario without affecting the uplink access performance of traditional terminal devices.

[0047] As the number of high-version terminal devices increases, configuring more PRACH resources in addition to the basic PRACH configuration can meet the access needs of more terminal devices. For example, under high load, the PRACH transmission period can be reduced to increase PRACH resources and avoid access congestion caused by insufficient PRACH resources; while under low load, the PRACH transmission period can be increased to reduce PRACH resources and help the network save energy.

[0048] The basic PRACH configuration and one or more additional PRACH configurations can be sent to the terminal device simultaneously (e.g., carried in the same message), or they can be sent to the terminal device relatively independently (e.g., carried in different messages). The basic PRACH configuration is still present to avoid affecting uplink access for legacy terminal devices, as legacy terminal devices may not be able to parse the first and / or second information sent to higher version terminal devices.

[0049] In some implementations, as shown in Figure 3, method 200 may further include steps 230 and 240. In step 230, the network device sends second information to the terminal device; correspondingly, in step 240, the terminal device receives the second information sent by the network device. The second information may, for example, be carried in a media access control element (MAC CE) or downlink control information (DCI).

[0050] The second information can be used to instruct the adjustment of parameters in the first PRACH configuration. For example, the first information may include an additional PRACH configuration, and the second information can be used to instruct the terminal device to adjust parameters in that PRACH configuration, such as adjusting parameters like the period, number of ROs, and RO interval of the PRACH resources. As an example, the second information may be an instruction to increase the period of PRACH resources, an instruction to decrease the period of PRACH resources, an instruction to increase the RO interval, an instruction to decrease the RO interval, or an instruction to adjust other parameters in the PRACH configuration.

[0051] Alternatively, the second information can be used to activate a first PRACH configuration in one or more PRACH configurations. The network device configures multiple additional PRACH configurations for the terminal device via, for example, system information or RRC configuration, and indicates, via, for example, RRC messages, system information, MAC CE, or DCI, which PRACH configuration needs to be activated, i.e., the first PRACH configuration. The network device can activate one or more PRACH configurations simultaneously using the second information. For example, when activating a single PRACH configuration, the index of that PRACH configuration can be carried in the second information; when activating multiple PRACH configurations, a set of indices for multiple PRACH configurations can be carried in the second information.

[0052] Optionally, the network device can configure one or more PRACH configurations for the terminal device using the first information, while simultaneously activating the first PRACH configuration or adjusting the parameters in the PRACH configuration using the second information. Alternatively, it can configure one or more PRACH configurations for the terminal device using the first information, and then activate the first PRACH configuration or adjust the parameters in the PRACH configuration using the second information. When the first and second information are transmitted simultaneously, when the terminal device first accesses the cell, it can obtain additional PRACH configuration information at the same time as acquiring the first information. This way, when a newer version of the terminal device first accesses the cell, it will not compete with traditional terminal devices for uplink PRACH resources applicable to traditional terminal devices, reducing the probability of PRACH resource conflicts.

[0053] Compared to the basic RACH configuration, this embodiment does not require updating system information. It can use second information to indicate which of the multiple RACH configurations previously configured for the terminal device via higher-layer signaling should be used. In other words, without updating system information, additional RACH resources are provided for the terminal device's uplink access using dynamic signaling, based on the needs of the current scenario. By reducing RACH reception activity, longer sleep periods for network devices can be achieved. Furthermore, by increasing RACH resources, congestion caused by a large number of terminal devices having access needs can be avoided.

[0054] Since one or more of the aforementioned PRACH configurations have their own indices, the second information can carry the index of the first PRACH configuration to be activated. For example, if the network device configures three additional PRACH configurations for the terminal device, with corresponding indices of PRACH configuration #1, PRACH configuration #2, and PRACH configuration #3, and the index of the first PRACH configuration to be activated is PRACH configuration #1, then the second information carries PRACH configuration #1; if the index of the first PRACH configuration to be activated is PRACH configuration #2, then the second information carries PRACH configuration #2; and if the index of the first PRACH configuration to be activated is PRACH configuration #3, then the second information carries PRACH configuration #3. Of course, the second information can also carry the index of the basic PRACH configuration. Assuming the index of the basic PRACH configuration is PRACH configuration #0, when the second information carries PRACH configuration #0, the terminal device can perform uplink access based on the basic PRACH configuration. The second information can also carry indexes of multiple PRACH configurations at the same time. In this case, the terminal device can perform uplink access based on multiple PRACH configurations, such as using ROs determined based on different periods in one or more PRACH configurations for uplink access.

[0055] In some implementations, the index of the first PRACH configuration is adjacent to the index of the second PRACH configuration, where the second PRACH configuration is the previously activated PRACH configuration. That is, the network device can activate PRACH configurations based on the order of the indices. For example, if the network device configures three PRACH configurations for the terminal device, with corresponding indices of PRACH configuration #1, PRACH configuration #2, and PRACH configuration #3, where the period of PRACH configuration #1 < the period of PRACH configuration #3 < the period of PRACH configuration #3, and if the previously activated configuration was PRACH configuration #2, then if it is necessary to increase the PRACH transmission period, the network device instructs the terminal device, through the second information, to activate PRACH configuration #2, and the index after activation is PRACH configuration #3. If it is necessary to decrease the PRACH transmission period, the network device instructs the terminal device, through the second information, to activate PRACH configuration #2, and the index before activation is PRACH configuration #1.

[0056] In addition to activating a specific PRACH configuration (the first PRACH configuration) from one or more PRACH configurations to make all parameters in the first PRACH configuration effective, a network device can also activate only a specific period from different periods included in one or more PRACH configurations, while keeping other parameters in the PRACH configuration unchanged. In this case, the second information can also include information about the period of the first PRACH configuration. Optionally, if the network device configures multiple periods for the terminal device, and these multiple periods also have corresponding indices, the second information can include the index of the first period that needs to be activated among the multiple periods. As an example, if the network device configures three PRACH resource periods for the terminal device, with corresponding indices of period #1, period #2, and period #3, if the index of the first period to be activated is period #1, then the second information carries period #1; if the index of the first period to be activated is period #2, then the second information carries period #2; and if the index of the first period to be activated is period #3, then the second information carries period #3. Of course, the second information can also carry the index of the base period (e.g., the period in the base PRACH configuration). Assuming the index of the base period is period #0, when the second information carries period #0, the terminal device can perform uplink access based on the base period. The second information can also carry the indexes of multiple periods simultaneously. In this case, the terminal device can perform uplink access based on multiple periods, for example, using RO determined based on multiple periods for uplink access.

[0057] In some implementations, the index of the first cycle is adjacent to the index of the second cycle, where the second cycle is the previously activated cycle. That is, the network device can activate cycles based on the order of the indices. As an example, the network device configures three cycles for the terminal device, with corresponding indices of cycle #1, cycle #2, and cycle #3. The cycle of cycle #1 < the second cycle of cycle #2 < the third cycle of cycle #3. If the previously activated cycle was #2, then if it is necessary to increase the cycle for PRACH resources, the network device instructs the terminal device, through the second information, to activate the index after cycle #2 as the cycle of cycle #3. If it is necessary to decrease the cycle for PRACH transmission, the network device instructs the terminal device, through the second information, to activate the index before cycle #2 as the cycle of cycle #1.

[0058] In other implementations, the second information may also include indications for increasing or decreasing the period of the PRACH resource. That is, the network device can instruct the terminal device to increase or decrease the period of the currently used PRACH resource based on predetermined rules. For example, the first period may be 1 / N1 of the previously activated second period, where N1 is a positive integer (e.g., N1 = 2); or, the first period may be N2 times the second period, where N2 is a positive integer (e.g., N2 = 2); or, the first period may be the result of increasing the second period by a first proportion (i.e., increasing the second period by a first proportion to obtain the first period); or, the first period may be the result of decreasing the second period by a second proportion (i.e., decreasing the second period by a second proportion to obtain the first period). The first and second proportions are, for example, greater than 0 and less than 1. The possible values ​​of the increased or decreased first period are pre-agreed or configured by the network device. As an example, the period of a PRACH resource may include 20ms, 40ms, 80ms, 120ms, and 160ms. The currently used period is 80ms. If the network device activates a new period via a second message, and the new period is twice the current period, the terminal device will switch the PRACH transmission period from 80ms to 160ms and perform PRACH transmission based on the new 160ms period. If the network device activates a new period via a second message, and the new period is half the current period, the terminal device will switch the PRACH transmission period from 80ms to... The terminal device switches its PRACH transmission period from 80ms to 120ms and performs PRACH transmission based on the new 40ms period. If the network device activates a new period via the second information indication, and the new period is 50% larger than the current period, the terminal device switches its PRACH transmission period from 80ms to 20ms and performs PRACH transmission based on the new 120ms period. If the network device activates a new period via the second information indication, and the new period is 75% smaller than the current period, the terminal device switches its PRACH transmission period from 80ms to 20ms and performs PRACH transmission based on the new 20ms period. It should be noted that the aforementioned multiple periods can be multiple periods included in multiple PRACH configurations, or multiple periods configured independently of the aforementioned multiple PRACH configurations.

[0059] In other implementations, the second information may also include one or more of the following: information on the RO interval in the first PRACH configuration; information on the RO offset in the first PRACH configuration; indication information for increasing the RO interval; and indication information for decreasing the RO interval. The process for adjusting the RO interval can be referred to the above-described process for adjusting the PRACH resource cycle using the second information, and will not be repeated here.

[0060] Furthermore, in some implementations, the second information may also include the offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration. Optionally, the index of the first PRACH configuration may be one of the indices of multiple PRACH configurations associated with the first preamble format, where the first preamble format is the preamble format associated with the base PRACH configuration. Here, the indices of the multiple PRACH configurations associated with the first preamble format are reordered indices; that is, the indices of the multiple PRACH configurations associated with the first preamble format can be renumbered to obtain the corresponding multiple PRACH configuration indices. For example, if preamble format 0 is associated with PRACH configuration indices #0 to #27, preamble format 1 is associated with PRACH configuration indices #28 to #56, and the index of the base PRACH configuration is index #28, then the first preamble format is preamble format 1. Therefore, the index of the first PRACH configuration should be one of the indices #28 to #56 of the PRACH configurations associated with preamble format 1. Alternatively, the PRACH configuration associated with preamble format 1 can be rearranged according to the index order. The rearranged PRACH configuration has indices from index #0 to index #28. Therefore, the index of the first PRACH configuration should be one of index #0 to index #28. By indicating the index offset through the second information, the overhead of physical layer signaling can be saved.

[0061] As mentioned earlier, network devices can dynamically activate (or disable) or activate (or enable) one of the additional PRACH configurations. Inactive PRACH configurations indicated by the network device will be disabled, and the network device will not need to monitor the RO locations determined based on these PRACH configurations, thus achieving energy savings. If a higher version terminal device has one of the additional PRACH configurations activated, it will preferably select the RO location determined by that PRACH configuration for uplink access, thereby avoiding increasing random access congestion at the RO locations determined by the basic PRACH configuration. When a large number of terminal devices have access needs, activating additional PRACH configurations provides more RO resources, thereby mitigating collisions during random access.

[0062] In NR, the random access procedure uses beams, where the SSB (Service Subsystem for Backplanes) has multiple transmission opportunities within a time period and is assigned a number corresponding to a different beam. For the terminal device, it can only transmit a preamble when the SSB's beam scanning signal covers it. When the network device receives the preamble from the terminal device, it knows the optimal downlink beam, i.e., which beam points to the terminal device. Therefore, there needs to be an association between the SSB and the preamble. Since preambles are transmitted on the RO (Redirecting Optical Line), there is usually a predetermined mapping relationship between the SSB and the RO. In other words, with a fixed PRACH configuration, the RO location is fixed, and there is a mapping relationship between the SSB and the RO location. For example, taking the basic PRACH configuration as an example, assuming that an SSB burst includes 4 SSBs, with corresponding SSB indices of SSB#0, SSB#1, SSB#2, and SSB#3, the mapping relationship may include, for example, SSB#0 mapped to RO position 0, SSB#1 mapped to RO position 1, SSB#2 mapped to RO position 2, and SSB#3 mapped to RO position 3. RO positions 0, 1, 2, and 3 can be determined based on relevant parameters in the basic PRACH configuration. For example, the interval between two adjacent RO positions can be equal to the basic period. At this point, if the terminal device uses the beam corresponding to SSB#0, it can perform PRACH transmission at RO position 0; if it uses the beam corresponding to SSB#1, it can perform PRACH transmission at RO position 1; if it uses the beam corresponding to SSB#2, it can perform PRACH transmission at RO position 2; and if it uses the beam corresponding to SSB#3, it can perform PRACH transmission at RO position 3. Here, one SSB can be mapped to one or more ROs, and one RO can also be mapped to one or more SSBs. In different mapping relationships, the ROs associated with the same SSB may be different, and the SSBs associated with the same RO may also be different. This application does not limit this aspect.

[0063] When introducing one or more additional PRACH configurations, it's necessary to consider how the RO (Redirect Origin) location determined by the new PRACH configuration is mapped to the SSB (Security Service Bus). If the RO location determined by the additional PRACH configuration is mapped to the SSB along with the RO location determined by the basic PRACH configuration, the mapping relationship between the RO location and SSB determined by the basic PRACH configuration may be disrupted after adding the additional PRACH configuration. In other words, additional RO locations configured for higher version terminal devices may lead to inconsistencies in the SSB-RO location mapping between traditional and higher version terminal devices. This inconsistency may prevent network devices from determining which SSB corresponds to a received PRACH transmission, and the network device may be unable to obtain the receiving direction from the SSB corresponding to the PRACH, only able to receive signals through beam scanning instead of efficient reception through beamforming.

[0064] Therefore, in some implementations, a first mapping relationship exists between ROs and SSBs determined by each of the one or more additional PRACH configurations, and a second mapping relationship exists between ROs and SSBs determined by the basic PRACH configuration. In this case, two mapping relationships are set: one is the second mapping relationship between ROs and SSBs determined by the basic PRACH configuration, which can also be considered a traditional mapping relationship; the other is the first mapping relationship between ROs and SSBs determined by the additional PRACH configurations. That is, the ROs determined by each of the one or more PRACH configurations and the ROs determined by the basic PRACH configuration are mapped separately. The first mapping relationship can be used, for example, by traditional terminal devices, and the second mapping relationship can be used, for example, by higher version terminal devices.

[0065] To avoid resource interference between ROs involved in the two mapping relationships, in some implementations, the ROs in the first mapping relationship do not overlap with those in the second mapping relationship. That is, the first mapping relationship only maps SSBs to RO locations that are different from the RO locations in the second mapping relationship. In other implementations, the ROs in the first mapping relationship overlap at least partially with those in the second mapping relationship. For example, the first mapping relationship might map SSBs to all ROs that a higher version of the terminal device might use (e.g., including ROs determined based on the basic PRACH configuration and ROs determined based on additional PRACH configurations). In other words, the ROs in the first mapping relationship include ROs determined based on the basic PRACH configuration and ROs determined based on additional PRACH configurations, while the ROs in the second mapping relationship include ROs determined based on the basic PRACH configuration. In this case, there may be partial overlap between the ROs in the first and second mapping relationships. For traditional terminal devices, the number of ROs mapped to an SSB or the number of ROs mapped to an SSB is configured by the network device (e.g., via RRC messages), and the mapping order is also predetermined. If ROs determined based on the basic PRACH configuration are mapped to SSBs together with ROs determined based on additional PRACH configurations, the second mapping relationship between ROs determined based on the basic PRACH configuration and SSBs may be disrupted. Clearly, ensuring the mapping relationship remains unchanged after an RO determined based on an additional PRACH configuration appears is not easy, as the mapping between SSBs and ROs is usually performed sequentially. In this case, when an RO determined based on an additional PRACH configuration is activated, the behavior of traditional terminal devices in RO selection changes, leading to unnecessary implementation complexity for traditional terminal devices. Therefore, mapping ROs determined based on additional PRACH configurations and ROs determined based on the basic PRACH configuration to SSBs separately helps maintain the mapping relationship between SSBs and ROs used by traditional terminal devices.

[0066] Optionally, for higher version terminal devices, if the ROs associated with the same SSB are different in the first and second mapping relationships, the RO associated with the same SSB in the first mapping relationship is used for PRACH transmission of the terminal device. For higher version terminal devices, if an additional PRACH configuration is activated, and there are two ROs associated with the same SSB—one a RO location determined based on the basic PRACH configuration and the other a RO determined based on the additional PRACH configuration—when the higher version terminal device preferentially selects the RO determined based on the basic PRACH configuration, the congestion level on that RO will significantly increase because it may also be used for random access by traditional terminal devices. Therefore, in this case, the RO determined based on the additional PRACH configuration can be preferentially selected. Furthermore, the preamble configuration related to network power saving functions is transmitted within the RO determined based on the additional PRACH configuration. Therefore, when the network power saving function or the corresponding PRACH configuration is activated, the higher version terminal device selects the RO determined based on the additional PRACH configuration.

[0067] The above describes the mapping of ROs determined by each PRACH configuration in one or more PRACH configurations, as well as the mapping of ROs determined by the basic PRACH configuration. In other implementations, the ROs determined by each PRACH configuration in the one or more PRACH configurations, as well as the ROs determined by the basic PRACH configuration, can also be mapped together. That is, the ROs determined by each PRACH configuration in the one or more PRACH configurations, as well as the ROs determined by the basic PRACH configuration, are treated as a whole and mapped to the SSB. For example, the ROs determined by parameters in the additional PRACH configuration and the ROs determined by parameters in the basic PRACH configuration have a third mapping relationship with the SSB. In this case, both high-version terminal devices and traditional terminal devices need to follow this third mapping relationship. Assuming that 4 RO positions are determined based on the basic PRACH configuration and 8 RO positions are determined based on the additional PRACH configuration, these 12 RO positions can be mapped as a whole to the SSB, thus obtaining the third mapping relationship.

[0068] The method embodiments of this application have been described in detail above with reference to Figures 1 to 3. The apparatus embodiments of this application will be described in detail below with reference to Figures 4 to 6. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0069] Figure 4 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 400 shown in Figure 4 may include a transceiver unit 410. The transceiver unit 410 is used to receive first information sent by a network device, wherein the first information includes one or more PRACH configurations.

[0070] In some implementations, the PRACH configuration includes one or more of the following parameters: the index of the PRACH configuration; the period of the PRACH resource; the subframe number corresponding to the PRACH slot; the number of PRACH slots; the number of random access channel opportunities (ROs) in the PRACH slots; the RO interval; the RO offset; and the offset of the index of the first PRACH configuration relative to the index of the basic PRACH configuration.

[0071] In some implementations, the transceiver unit 410 is further configured to: receive second information sent by the network device, the second information being used to activate a first PRACH configuration in one or more PRACH configurations, or to instruct adjustments to parameters in the first PRACH configuration.

[0072] In some implementations, the second information includes one or more of the following: the index of the first PRACH configuration; period information in the first PRACH configuration; RO interval information in the first PRACH configuration; RO offset information in the first PRACH configuration; indication information for increasing the period of PRACH resources; indication information for decreasing the period of PRACH resources; indication information for increasing the RO interval; indication information for decreasing the RO interval; and the offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

[0073] In some implementations, the index of the first PRACH configuration is one of the multiple PRACH configuration indices associated with the first preamble format, the first preamble format is the preamble format associated with the index of the base PRACH configuration, and the multiple PRACH configuration indices associated with the first preamble format are indices obtained after reordering.

[0074] In some implementations, the index of the first PRACH configuration is adjacent to the index of the second PRACH configuration, and the second PRACH configuration is the previously activated PRACH configuration; the index of the first period is adjacent to the index of the second period, the first period is the period in the first PRACH configuration, and the second period is the period in the previously activated PRACH configuration; the first period is 1 / N1 of the second period, where N1 is a positive integer; the first period is N2 times the second period, where N2 is a positive integer; the first period is the result of increasing the second period by a first proportion; the first period is the result of decreasing the second period by a second proportion.

[0075] In some implementations, the first information is carried in an RRC message or system information; and / or, the second information is carried in an RRC message, system information, MAC CE, or DCI.

[0076] In some implementations, the transceiver unit 410 is further configured to: receive a basic PRACH configuration sent by the network device, the basic PRACH configuration including a basic period for PRACH transmission, and the one or more PRACH configurations including a period different from the basic PRACH period.

[0077] In some implementations, the period in the one or more PRACH configurations is shorter than the base PRACH period.

[0078] In some implementations, the period in the one or more PRACH configurations is 1 / 2 of the base period. M In this context, the value of M associated with the period in one or more PRACH configurations is different, and M is a positive integer.

[0079] In some implementations, the basic PRACH configuration is carried in RRC messages or system information.

[0080] In some implementations, there is a first mapping relationship between the RO determined based on each PRACH configuration in the one or more PRACH configurations and the synchronization signal broadcast channel block (SSB), and a second mapping relationship between the RO determined based on the basic PRACH configuration and the SSB.

[0081] In some implementations, the ROs in the first mapping relationship do not overlap with the ROs in the second mapping relationship; or, the ROs in the first mapping relationship and the ROs in the second mapping relationship at least partially overlap.

[0082] In some implementations, if the ROs associated with the same SSB in the first mapping relationship and the second mapping relationship are different, the ROs associated with the same SSB in the first mapping relationship are used for PRACH transmission of the terminal device.

[0083] In some implementations, there is a third mapping relationship between the RO determined based on each PRACH configuration in the one or more PRACH configurations and the RO determined based on the basic PRACH configuration and the SSB.

[0084] It is understood that the transceiver unit 410 may be, for example, a transceiver 630. Additionally, the terminal device 400 may optionally include a processor 610 and a memory 620, as detailed in Figure 6.

[0085] Figure 5 is a schematic diagram of the structure of a network device provided in an embodiment of this application. The network device 500 shown in Figure 5 may include a transceiver unit 510. The transceiver unit 510 is used to send first information to a terminal device, wherein the first information includes one or more PRACH configurations.

[0086] In some implementations, the PRACH configuration includes one or more of the following parameters: the index of the PRACH configuration; the period of the PRACH resource; the subframe number corresponding to the PRACH slot; the number of PRACH slots; the number of random access channel opportunities (ROs) in the PRACH slots; the RO interval; the RO offset; and the offset of the index of the first PRACH configuration relative to the index of the basic PRACH configuration.

[0087] In some implementations, the transceiver unit 510 is further configured to: send second information to the terminal device, the second information being used to activate a first PRACH configuration in one or more PRACH configurations, or to instruct adjustments to parameters in the first PRACH configuration.

[0088] In some implementations, the second information includes one or more of the following: the index of the first PRACH configuration; period information in the first PRACH configuration; RO interval information in the first PRACH configuration; RO offset information in the first PRACH configuration; indication information for increasing the period of PRACH resources; indication information for decreasing the period of PRACH resources; indication information for increasing the RO interval; indication information for decreasing the RO interval; and the offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

[0089] In some implementations, the index of the first PRACH configuration is one of the multiple PRACH configuration indices associated with the first preamble format, the first preamble format is the preamble format associated with the index of the base PRACH configuration, and the multiple PRACH configuration indices associated with the first preamble format are indices obtained after reordering.

[0090] In some implementations, the index of the first PRACH configuration is adjacent to the index of the second PRACH configuration, and the second PRACH configuration is the previously activated PRACH configuration; the index of the first period is adjacent to the index of the second period, the first period is the period in the first PRACH configuration, and the second period is the period in the previously activated PRACH configuration; the first period is 1 / N1 of the second period, where N1 is a positive integer; the first period is N2 times the second period, where N2 is a positive integer; the first period is the result of increasing the second period by a first proportion; the first period is the result of decreasing the second period by a second proportion.

[0091] In some implementations, the first information is carried in an RRC message or system information; and / or, the second information is carried in an RRC message, system information, MAC CE, or DCI.

[0092] In some implementations, the transceiver unit 510 is further configured to: send a basic PRACH configuration to the terminal device, the basic PRACH configuration including a basic period for PRACH transmission, wherein the one or more PRACH configurations include a period different from the basic PRACH period.

[0093] In some implementations, the period in the one or more PRACH configurations is shorter than the base PRACH period.

[0094] In some implementations, the period in the one or more PRACH configurations is 1 / 2 of the base period. M In this context, the value of M associated with the period in one or more PRACH configurations is different, and M is a positive integer.

[0095] In some implementations, the basic PRACH configuration is carried in RRC messages or system information.

[0096] In some implementations, there is a first mapping relationship between the RO determined based on each PRACH configuration in the one or more PRACH configurations and the synchronization signal broadcast channel block (SSB), and a second mapping relationship between the RO determined based on the basic PRACH configuration and the SSB.

[0097] In some implementations, the ROs in the first mapping relationship do not overlap with the ROs in the second mapping relationship; or, the ROs in the first mapping relationship and the ROs in the second mapping relationship at least partially overlap.

[0098] In some implementations, if the ROs associated with the same SSB in the first mapping relationship and the second mapping relationship are different, the ROs associated with the same SSB in the first mapping relationship are used for PRACH transmission of the terminal device.

[0099] In some implementations, there is a third mapping relationship between the RO determined based on each PRACH configuration in the one or more PRACH configurations and the RO determined based on the basic PRACH configuration and the SSB.

[0100] It is understood that the transceiver unit 510 may be, for example, a transceiver 630. Additionally, the network device 500 may optionally include a processor 610 and a memory 620, as detailed in Figure 6.

[0101] Figure 6 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 6 indicate that the unit or module is optional. The apparatus 600 can be used to implement the methods described in the above method embodiments. The apparatus 600 may be, for example, a chip, a terminal device, or a network device.

[0102] Apparatus 600 may include one or more processors 610. Processor 610 may support apparatus 600 in implementing the methods described in the foregoing method embodiments. Processor 610 may be a general-purpose processor or a special-purpose processor. For example, processor 610 may be a central processing unit (CPU). Alternatively, processor 610 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors may be microprocessors or any conventional processor.

[0103] The apparatus 600 may further include one or more memories 620. The memories 620 store programs that can be executed by the processor 610, causing the processor 610 to perform the methods described in the above method embodiments. The memories 620 may be independent of the processor 610, or they may be integrated into the processor 610.

[0104] The device 600 may also include a transceiver 630. The processor 610 can communicate with other devices or chips via the transceiver 630. For example, the processor 610 can send and receive data with other devices or chips via the transceiver 630.

[0105] This application also provides a communication system. The communication system includes the terminal device and network device described above. In some implementations, the system further includes other devices that interact with the terminal device and network device.

[0106] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0107] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0108] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0109] It should be understood that the terms "system" and "network" in the embodiments of this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of this application and is not intended to limit this application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0110] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0111] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0112] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0113] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0114] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0115] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0116] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0117] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0119] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0120] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0121] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for wireless communication, characterized in that, include: The terminal device receives first information sent by the network device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

2. The method according to claim 1, characterized in that, The PRACH configuration includes one or more of the following parameters: The index configured by PRACH; The lifecycle of PRACH resources; The subframe number corresponding to the PRACH slot; The number of PRACH slots; The number of random access channel opportunities (ROs) in the PRACH time slot; RO interval; RO offset; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The terminal device receives second information sent by the network device, the second information being used to activate a first PRACH configuration in one or more PRACH configurations, or to instruct adjustments to parameters in the first PRACH configuration.

4. The method according to claim 3, characterized in that, The second information includes one or more of the following: The index configured in the first PRACH; Information about the cycle in the first PRACH configuration; Information about the RO interval in the first PRACH configuration; Information about the RO offset in the first PRACH configuration; Add periodic indication information for PRACH resources; Indication information to reduce the cycle time of PRACH resources; Increase the indication information for RO intervals; Indication to reduce RO interval; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

5. The method according to claim 3 or 4, characterized in that, The index of the first PRACH configuration is one of the multiple PRACH configuration indices associated with the first preamble format. The first preamble format is the preamble format associated with the index of the base PRACH configuration. The multiple PRACH configuration indices associated with the first preamble format are the indices obtained after reordering.

6. The method according to any one of claims 3 to 5, characterized in that, The index of the first PRACH configuration is adjacent to the index of the second PRACH configuration, and the second PRACH configuration is the previously activated PRACH configuration; The index of the first period is adjacent to the index of the second period. The first period is the period in the first PRACH configuration, and the second period is the period in the previously activated PRACH configuration. The first period is 1 / N1 of the second period, where N1 is a positive integer; The first period is N2 times the second period, where N2 is a positive integer; The first cycle is the result of increasing the second cycle by a first proportion; The first cycle is the result of reducing the second ratio in the second cycle.

7. The method according to any one of claims 3 to 6, characterized in that, The first information is carried in a Radio Resource Control (RRC) message or system information; and / or, The second information is carried in RRC messages, system information, Media Access Control (MAC) control element (CE), or Downlink Control Information (DCI).

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: The terminal device receives a basic PRACH configuration sent by the network device. The basic PRACH configuration includes a basic period for PRACH transmission, and one or more PRACH configurations include a period different from the basic PRACH period.

9. The method according to claim 8, characterized in that, The period in one or more PRACH configurations is less than the base PRACH period.

10. The method according to claim 9, characterized in that, The period in the one or more PRACH configurations is 1 / 2 of the base period. M In this context, the value of M associated with the period in one or more PRACH configurations is different, and M is a positive integer.

11. The method according to any one of claims 8 to 10, characterized in that, The basic PRACH configuration is carried in RRC messages or system information.

12. The method according to any one of claims 1 to 11, characterized in that, There is a first mapping relationship between the RO and the synchronization signal broadcast channel block (SSB) determined by each PRACH configuration in the one or more PRACH configurations, and a second mapping relationship between the RO and the SSB determined by the basic PRACH configuration.

13. The method according to claim 12, characterized in that, The ROs in the first mapping relationship do not overlap with the ROs in the second mapping relationship; or, The ROs in the first mapping relationship and the ROs in the second mapping relationship overlap at least partially.

14. The method according to claim 12 or 13, characterized in that, If the ROs associated with the same SSB are different in the first mapping relationship and the second mapping relationship, the ROs associated with the same SSB in the first mapping relationship are used for PRACH transmission of the terminal device.

15. The method according to any one of claims 8 to 11, characterized in that, There is a third mapping relationship between the RO determined by each PRACH configuration in the one or more PRACH configurations and the RO determined by the basic PRACH configuration and the SSB.

16. A method for wireless communication, characterized in that, include: The network device sends first information to the terminal device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

17. The method according to claim 16, characterized in that, The PRACH configuration includes one or more of the following parameters: The index configured by PRACH; The lifecycle of PRACH resources; The subframe number corresponding to the PRACH slot; The number of PRACH slots; The number of random access channel opportunities (ROs) in the PRACH time slot; RO interval; RO offset; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

18. The method according to claim 16 or 17, characterized in that, The method further includes: The network device sends a second message to the terminal device, the second message being used to activate a first PRACH configuration in one or more PRACH configurations, or to instruct adjustments to parameters in the first PRACH configuration.

19. The method according to claim 18, characterized in that, The second information includes one or more of the following: The index configured in the first PRACH; Information about the cycle in the first PRACH configuration; Information about the RO interval in the first PRACH configuration; Information about the RO offset in the first PRACH configuration; Add periodic indication information for PRACH resources; Indication information to reduce the cycle time of PRACH resources; Increase the indication information for RO intervals; Indication to reduce RO interval; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

20. The method according to claim 18 or 19, characterized in that, The index of the first PRACH configuration is one of the multiple PRACH configuration indices associated with the first preamble format. The first preamble format is the preamble format associated with the index of the base PRACH configuration. The multiple PRACH configuration indices associated with the first preamble format are the indices obtained after reordering.

21. The method according to any one of claims 18 to 20, characterized in that, The index of the first PRACH configuration is adjacent to the index of the second PRACH configuration, and the second PRACH configuration is the previously activated PRACH configuration; The index of the first period is adjacent to the index of the second period. The first period is the period in the first PRACH configuration, and the second period is the period in the previously activated PRACH configuration. The first period is 1 / N1 of the second period, where N1 is a positive integer; The first period is N2 times the second period, where N2 is a positive integer; The first cycle is the result of increasing the second cycle by a first proportion; The first cycle is the result of reducing the second ratio in the second cycle.

22. The method according to any one of claims 18 to 21, characterized in that, The first information is carried in a Radio Resource Control (RRC) message or system information; and / or, The second information is carried in RRC messages, system information, Media Access Control (MAC) control element (CE), or Downlink Control Information (DCI).

23. The method according to any one of claims 16 to 22, characterized in that, The method further includes: The network device sends a basic PRACH configuration to the terminal device. The basic PRACH configuration includes a basic period for PRACH transmission. The one or more PRACH configurations include a period different from the basic PRACH period.

24. The method according to claim 23, characterized in that, The period in one or more PRACH configurations is less than the base PRACH period.

25. The method according to claim 24, characterized in that, The period in the one or more PRACH configurations is 1 / 2 of the base period. M In this context, the value of M associated with the period in one or more PRACH configurations is different, and M is a positive integer.

26. The method according to any one of claims 23 to 25, characterized in that, The basic PRACH configuration is carried in RRC messages or system information.

27. The method according to any one of claims 16 to 26, characterized in that, There is a first mapping relationship between the RO and the synchronization signal broadcast channel block (SSB) determined by each PRACH configuration in the one or more PRACH configurations, and a second mapping relationship between the RO and the SSB determined by the basic PRACH configuration.

28. The method according to claim 27, characterized in that, The ROs in the first mapping relationship do not overlap with the ROs in the second mapping relationship; or, The ROs in the first mapping relationship and the ROs in the second mapping relationship overlap at least partially.

29. The method according to claim 27 or 28, characterized in that, If the ROs associated with the same SSB are different in the first mapping relationship and the second mapping relationship, the ROs associated with the same SSB in the first mapping relationship are used for PRACH transmission of the terminal device.

30. The method according to any one of claims 23 to 26, characterized in that, There is a third mapping relationship between the RO determined by each PRACH configuration in the one or more PRACH configurations and the RO determined by the basic PRACH configuration and the SSB.

31. A terminal device, characterized in that, include: A transceiver unit is used to receive first information sent by a network device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

32. The terminal device according to claim 31, characterized in that, The PRACH configuration includes one or more of the following parameters: The index configured by PRACH; The lifecycle of PRACH resources; The subframe number corresponding to the PRACH slot; The number of PRACH slots; The number of random access channel opportunities (ROs) in the PRACH time slot; RO interval; RO offset; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

33. The terminal device according to claim 31 or 32, characterized in that, The transceiver unit is also used for: The network device receives second information, which is used to activate a first PRACH configuration in one or more PRACH configurations, or to indicate the adjustment of parameters in the first PRACH configuration.

34. The terminal device according to claim 33, characterized in that, The second information includes one or more of the following: The index configured in the first PRACH; Information about the cycle in the first PRACH configuration; Information about the RO interval in the first PRACH configuration; Information about the RO offset in the first PRACH configuration; Add periodic indication information for PRACH resources; Indication information to reduce the cycle time of PRACH resources; Increase the indication information for RO intervals; Indication to reduce RO interval; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

35. The terminal device according to claim 33 or 34, characterized in that, The index of the first PRACH configuration is one of the multiple PRACH configuration indices associated with the first preamble format. The first preamble format is the preamble format associated with the index of the base PRACH configuration. The multiple PRACH configuration indices associated with the first preamble format are the indices obtained after reordering.

36. The terminal device according to any one of claims 33 to 35, characterized in that, The index configured for the first PRACH is adjacent to the index configured for the second PRACH, and the second PRACH is configured as the previous activation. Live PRACH configuration; The index of the first period is adjacent to the index of the second period. The first period is the period in the first PRACH configuration, and the second period is the period in the previously activated PRACH configuration. The first period is 1 / N1 of the second period, where N1 is a positive integer; The first period is N2 times the second period, where N2 is a positive integer; The first cycle is the result of increasing the second cycle by a first proportion; The first cycle is the result of reducing the second ratio in the second cycle.

37. The terminal device according to any one of claims 33 to 36, characterized in that, The first information is carried in a Radio Resource Control (RRC) message or system information; and / or, The second information is carried in RRC messages, system information, Media Access Control (MAC) control element (CE), or Downlink Control Information (DCI).

38. The terminal device according to any one of claims 31 to 37, characterized in that, The transceiver unit is also used for: The network device receives a basic PRACH configuration, which includes a basic period for PRACH transmission, and the one or more PRACH configurations include a period different from the basic PRACH period.

39. The terminal device according to claim 38, characterized in that, The period in one or more PRACH configurations is less than the base PRACH period.

40. The terminal device according to claim 39, characterized in that, The period in the one or more PRACH configurations is 1 / 2 of the base period. M In this context, the value of M associated with the period in one or more PRACH configurations is different, and M is a positive integer.

41. The terminal device according to any one of claims 38 to 40, characterized in that, The basic PRACH configuration is carried in RRC messages or system information.

42. The terminal device according to any one of claims 31 to 41, characterized in that, There is a first mapping relationship between the RO and the synchronization signal broadcast channel block (SSB) determined by each PRACH configuration in the one or more PRACH configurations, and a second mapping relationship between the RO and the SSB determined by the basic PRACH configuration.

43. The terminal device according to claim 42, characterized in that, The ROs in the first mapping relationship do not overlap with the ROs in the second mapping relationship; or, The ROs in the first mapping relationship and the ROs in the second mapping relationship overlap at least partially.

44. The terminal device according to claim 42 or 43, characterized in that, If the ROs associated with the same SSB are different in the first mapping relationship and the second mapping relationship, the ROs associated with the same SSB in the first mapping relationship are used for PRACH transmission of the terminal device.

45. The terminal device according to any one of claims 38 to 41, characterized in that, There is a third mapping relationship between the RO determined by each PRACH configuration in the one or more PRACH configurations and the RO determined by the basic PRACH configuration and the SSB.

46. ​​A network device, characterized in that, include: The transceiver unit is used to send first information to the terminal device, wherein the first information includes one or more Physical Random Access Channel (PRACH) configurations.

47. The network device according to claim 46, characterized in that, The PRACH configuration includes one or more of the following parameters: The index configured by PRACH; The lifecycle of PRACH resources; The subframe number corresponding to the PRACH slot; The number of PRACH slots; The number of random access channel opportunities (ROs) in the PRACH time slot; RO interval; RO offset; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

48. The network device according to claim 46 or 47, characterized in that, The transceiver unit is also used for: Send a second message to the terminal device, the second message being used to activate a first PRACH configuration in one or more PRACH configurations, or to instruct adjustments to parameters in the first PRACH configuration.

49. The network device according to claim 48, characterized in that, The second information includes one or more of the following: The index configured in the first PRACH; Information about the cycle in the first PRACH configuration; Information about the RO interval in the first PRACH configuration; Information about the RO offset in the first PRACH configuration; Add periodic indication information for PRACH resources; Indication information to reduce the cycle time of PRACH resources; Increase the indication information for RO intervals; Indication to reduce RO interval; The offset of the index of the first PRACH configuration relative to the index of the base PRACH configuration.

50. The network device according to claim 48 or 49, characterized in that, The index of the first PRACH configuration is one of the multiple PRACH configuration indices associated with the first preamble format. The first preamble format is the preamble format associated with the index of the base PRACH configuration. The multiple PRACH configuration indices associated with the first preamble format are the indices obtained after reordering.

51. The network device according to any one of claims 48 to 50, characterized in that, The index of the first PRACH configuration is adjacent to the index of the second PRACH configuration, and the second PRACH configuration is the previously activated PRACH configuration; The index of the first period is adjacent to the index of the second period. The first period is the period in the first PRACH configuration, and the second period is the period in the previously activated PRACH configuration. The first period is 1 / N1 of the second period, where N1 is a positive integer; The first period is N2 times the second period, where N2 is a positive integer; The first cycle is the result of increasing the second cycle by a first proportion; The first cycle is the result of reducing the second ratio in the second cycle.

52. The network device according to any one of claims 48 to 51, characterized in that, The first information is carried in a Radio Resource Control (RRC) message or system information; and / or, The second information is carried in RRC messages, system information, Media Access Control (MAC) control element (CE), or Downlink Control Information (DCI).

53. The network device according to any one of claims 46 to 52, characterized in that, The transceiver unit is also used for: Send a basic PRACH configuration to the terminal device. The basic PRACH configuration includes a basic period for PRACH transmission. The one or more PRACH configurations include a period different from the basic PRACH period.

54. The network device according to claim 53, characterized in that, The period in one or more PRACH configurations is less than the base PRACH period.

55. The network device according to claim 54, characterized in that, The period in the one or more PRACH configurations is 1 / 2 of the base period. M In this context, the value of M associated with the period in one or more PRACH configurations is different, and M is a positive integer.

56. The network device according to any one of claims 53 to 55, characterized in that, The basic PRACH configuration is carried in RRC messages or system information.

57. The network device according to any one of claims 46 to 56, characterized in that, There is a first mapping relationship between the RO and the synchronization signal broadcast channel block (SSB) determined by each PRACH configuration in the one or more PRACH configurations, and a second mapping relationship between the RO and the SSB determined by the basic PRACH configuration.

58. The network device according to claim 57, characterized in that, The ROs in the first mapping relationship do not overlap with the ROs in the second mapping relationship; or, The ROs in the first mapping relationship and the ROs in the second mapping relationship overlap at least partially.

59. The network device according to claim 57 or 58, characterized in that, If the ROs associated with the same SSB are different in the first mapping relationship and the second mapping relationship, the ROs associated with the same SSB in the first mapping relationship are used for PRACH transmission of the terminal device.

60. The network device according to any one of claims 53 to 56, characterized in that, There is a third mapping relationship between the RO determined by each PRACH configuration in the one or more PRACH configurations and the RO determined by the basic PRACH configuration and the SSB.

61. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method according to any one of claims 1 to 15.

62. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method according to any one of claims 16 to 30.

63. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method according to any one of claims 1 to 30.

64. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method according to any one of claims 1 to 30.

65. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method according to any one of claims 1 to 30.

66. A computer program product, characterized in that, Includes a program that causes a computer to perform the method according to any one of claims 1 to 30.

67. A computer program, characterized in that, The computer program causes the computer to perform the method according to any one of claims 1 to 30.

Images