WO2025208539A1 - Rach configuration adjustment method and apparatus - Google Patents

Abstract

Embodiments of the present application provide an RACH configuration adjustment method and apparatus. The method comprises: a terminal device receives a first RACH configuration and/or a second RACH configuration from a network device; and the terminal device receives first indication information and/or second indication information, wherein the first indication information is used for indicating activating/deactivating or enabling/disabling of the first RACH configuration, and the second indication information is used for indicating activating/deactivating or enabling/disabling of the second RACH configuration.

Description

RACH configuration adjustment method and device Technical Field

The embodiments of the present application relate to the field of communication technologies.

Background Art

As a crucial component of new global infrastructure, 5G communication networks have experienced rapid development in recent years. As networks expand, operators' energy consumption continues to rise. For example, data released by China's Ministry of Industry and Information Technology indicates that energy consumption will increase by approximately 80% between 2015 and 2022.

With the construction of 5G and the large-scale commercial use of 5G active antenna units (AAUs), energy consumption is expected to increase exponentially compared to the remote radio units (RRUs) used primarily in 3G and 4G due to their higher power consumption. 5G defines three major service types: enhanced mobile broadband (eMBB), massive machine type of communication (mMTC), and ultra-reliable low-latency communication (URLLC). This is driving an increase in bursty small packet traffic and the 24/7 operation of base stations. The average daily energy consumption of 5G sites is expected to be more than double that of 4G.

In the 5G era, 3GPP has introduced key technologies such as Massive MIMO and increased RF bandwidth. 5G supports higher data rates and greater data traffic, requiring more transmission bandwidth. High-frequency bands will be the primary frequency band for future 5G expansion. However, the transmission characteristics of high-frequency bands limit site coverage, resulting in denser 5G site deployments. Furthermore, the increased energy consumption will place significant pressure on operators' operating costs. Therefore, network energy conservation is crucial for reducing operating costs, and energy conservation in 5G networks is a pressing issue.

To achieve energy conservation, network devices can perform energy conservation processing in the time domain, frequency domain, spatial domain, and/or energy domain based on network load. For example, in the spatial and energy domains, network devices can turn off some antennas to achieve energy conservation when the load is low. In the time domain, network devices can adjust the period or time domain position of the cell common reference signal (such as SSB/SIB) when there are few users and light load to achieve energy conservation.

It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

Summary of the Invention

The inventors discovered that, in terms of time-domain energy conservation, to increase the chances of network devices entering sleep mode, the number of frequent transmissions between synchronization signal blocks (SSBs) can be reduced. For example, minimizing the number of periodic receptions, such as those involving the Physical Uplink Control Channel (PUCCH) or the Physical Random Access Channel (PRACH), can save significant energy.

However, currently, information such as PRACH time-frequency resources and PRACH and SSB mapping is obtained through system information (SIB1) or radio resource control (RRC) configuration messages. If network equipment needs to adjust PRACH-related configuration information, it can only be achieved through SI update or RRC reconfiguration, which takes a long time to change and cannot quickly and flexibly adjust PRACH. Therefore, providing a PRACH adjustment mechanism that is lighter than SI has become a pressing issue for network energy-saving technology.

To address at least one of the above problems, embodiments of the present application provide a method and apparatus for adjusting RACH configuration.

According to one aspect of an embodiment of the present application, a method for adjusting RACH configuration is provided, including:

The terminal device receives the first RACH configuration and/or the second RACH configuration from the network device;

The terminal device receives first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enable/disable of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enable/disable of the second RACH configuration.

According to another aspect of an embodiment of the present application, a device for adjusting a RACH configuration is provided, including:

a receiving unit configured to receive a first RACH configuration and/or a second RACH configuration from a network device;

The receiving unit further receives first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disability of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disability of the second RACH configuration.

According to another aspect of an embodiment of the present application, a method for adjusting RACH configuration is provided, including:

The network device sends the first RACH configuration and/or the second RACH configuration;

The network device further sends first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disability of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disability of the second RACH configuration.

According to another aspect of an embodiment of the present application, a device for adjusting a RACH configuration is provided, including:

a sending unit, configured to send a first RACH configuration and/or a second RACH configuration;

The sending unit further sends first indication information and/or second indication information; wherein the first indication information is used Indicates activation/deactivation or enabling/disabling of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enabling/disabling of the second RACH configuration.

According to another aspect of an embodiment of the present application, a communication system is provided, including:

A network device, which sends a first RACH configuration and/or a second RACH configuration to a terminal device; sends first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enabling/disabling of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enabling/disabling of the second RACH configuration;

A terminal device receives the first RACH configuration and/or the second RACH configuration; and receives the first indication information and/or the second indication information.

One of the beneficial effects of the embodiments of the present application is that in some scenarios of wireless communication applications (such as energy-saving mode), network equipment and terminal equipment can quickly and flexibly indicate/activate/trigger RACH configuration, which can not only improve network gain (such as energy-saving gain) but also ensure normal transmission of terminal equipment.

With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

Features described and/or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

It should be emphasized that the term "include/comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components.

BRIEF DESCRIPTION OF THE DRAWINGS

The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

FIG2 is a schematic diagram of a method for adjusting RACH configuration according to an embodiment of the present application;

FIG3 is an example diagram of SSB-RO mapping according to an embodiment of the present application;

FIG4 is another example diagram of SSB-RO mapping according to an embodiment of the present application;

FIG5 is another example diagram of SSB-RO mapping according to an embodiment of the present application;

FIG6 is another example diagram of SSB-RO mapping according to an embodiment of the present application;

FIG7 is a schematic diagram of a method for adjusting RACH configuration according to an embodiment of the present application;

FIG8 is a schematic diagram of a device for adjusting RACH configuration according to an embodiment of the present application;

FIG9 is a schematic diagram of a device for adjusting RACH configuration according to an embodiment of the present application;

FIG10 is a schematic diagram of a terminal device according to an embodiment of the present application;

FIG11 is a schematic diagram of a network device according to an embodiment of the present application.

DETAILED DESCRIPTION

The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and/or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.

Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, such as but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and/or other communication protocols currently known or to be developed in the future.

In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. The network device may include but is not limited to the following devices: a base station (BS, Base Station), Access Point (AP), Transmission Reception Point (TRP), Broadcast Transmitter, Mobile Management Entity (MME), Gateway, Server, Radio Network Controller (RNC), Base Station Controller (BSC), etc.

Among them, base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB) and 5G base station (gNB), IAB host, etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femeto, pico, etc.). The term "base station" can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area. The term "cell" can refer to a base station and/or its coverage area, depending on the context in which the term is used.

In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.

Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and the like.

In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation in which a terminal device and a network device are used as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 only illustrates two terminal devices and one network device as an example, but the embodiment of the present application is not limited thereto. Here.

In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

It is worth noting that FIG1 shows that both terminal devices 102 and 103 are within the coverage range of network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 may not be within the coverage range of network device 101, or one terminal device 102 may be within the coverage range of network device 101 while the other terminal device 103 is outside the coverage range of network device 101.

Random access is a key function of the access network. For example, it is the fundamental process for establishing a connection between a UE and a gNB, and plays a crucial role from 2G to 5G. The random access process involves protocols such as the physical layer, MAC layer, and RRC layer. The physical layer defines the preamble sequence code, PRACH resources, and timing required for the random access process; the MAC layer defines the overall random access process; and the RRC layer, in addition to configuring random access parameters, is directly involved in some specific random access procedures.

In an RRC establishment scenario, the UE transitions from the idle state (RRC_IDLE) to the connected state (RRC_CONNECTED). This means that the initial UE must establish a connection with the cell to enable signaling and data transmission within the cell. From an RRC perspective, the UE must complete the RRC establishment process, which is interspersed with the random access process. Because the UE in the idle state can only receive cell system messages and no dedicated signaling, contention-based random access (CBRA) is employed. This means that the gNB cannot identify the UE until random access contention is resolved. The UE's contention-based random access parameters are broadcast via cell system information.

For example, the information exchange process for contention random access is divided into four steps: the first step is to send Msg1, i.e., send the preamble code; the second step is to receive Msg2, i.e., the random access response (RAR); the third step is to send Msg3, i.e., the RRC request; and the fourth step is to receive Msg4, which is the contention resolution. The embodiments of this application mainly involve the first step, Msg1, so Msg1 is introduced below.

Msg1 is an uplink message sent by the UE and received by the gNB. For example, based on the random access channel (RACH) configuration information broadcast by the cell, the UE determines the preamble code, PRACH time-frequency resources, and the mapping between the SSB and RACH opportunity (RO). The UE then sends the preamble code to the gNB to initiate the random access procedure.

The above schematically illustrates random access, and the following further illustrates PRACH time-frequency resource configuration.

PRACH resources are periodic resources. In the time domain, different PRACH Preamble formats have different durations. The time domain position of PRACH resources is defined by the PRACH configuration period, radio frame index, subframe/time slot index, starting PRACH OFDM symbol index in the time slot, and the number of time domain ROs in the time slot. Among them, the candidate values of the PRACH configuration period are {10, 20, 40, 80, 160} ms. In each PRACH configuration period, PRACH resources are only distributed in a valid radio frame (10ms). The valid radio frame contains one or more subframes/time slots. There is only one starting PRACH OFDM symbol index in each subframe/time slot, and there is one or more time domain ROs in a time slot.

In the frequency domain, different PRACH preamble formats and subcarrier spacing jointly determine the frequency domain bandwidth occupied by PRACH. For the long preamble format with a length of 839, when the PRACH subcarrier spacing is 1.25kHz, the frequency domain bandwidth is 1.08MHz (corresponding to 6 PRBs with a PUSCH subcarrier spacing of 15kHz), and when the PRACH subcarrier spacing is 5kHz, the frequency domain bandwidth is 4.32MHz. For the short preamble format with a length of 139, when the PRACH subcarrier spacing is 15kHz, 30kHz, 60kHz and 120kHz, the corresponding frequency domain bandwidths are 2.16MHz, 4.32MHz, 8.64MHz and 17.28MHz respectively.

The configuration of PRACH time domain resources in NR is the same as that in LTE, that is, the PRACH configuration is determined by looking up the configuration table pre-defined in the protocol. For each configuration index, the table defines the period, system frame number, subframe/time slot number, starting symbol index in a time slot, and the number of time domain ROs. There are a total of 256 configurable indexes, which are notified by 8-bit signaling in SIB1. The number of different PRACH frequency domain resources for frequency division multiplexing (FDM) occupying the same time domain resources is 1, 2, 4, and 8, and the specific value is notified by 2-bit signaling in SIB1.

NR defines three PRACH configuration tables. These tables are designed to support different TDD semi-static uplink and downlink cycle configurations, different PRACH capacities, typical configuration cycles for common PRACH preamble formats of interest to different operators, and the uplink starting position within a time slot in the TDD system.

For example, the first table applies to the uplink carrier or supplementary uplink carrier (SUL) of the FDD spectrum in FR1, including four long preamble formats 0/1/2/3 and 10 short preamble formats: A1, A2, A3, B1, B4, A1/B1, A2/B2, A3/B3, C0, and C2. Among them, the period of formats A1/B1, A2/B2, and A3/B3 is {10, 20} ms, the period of format C0 is {10, 20, 40, 80} ms, and the period of the remaining 10 formats is {10, 20, 40, 80, 160} ms. The starting symbol index within a time slot is all 0.

For example, the second table is applicable to the TDD spectrum of FR1, including 4 long preamble formats 0/1/2/3 and 10 short preamble formats: A1, A2, A3, B1, B4, A1/B1, A2/B2, A3/B3, C0 and C2. Among them, the period of formats A1/B1, A2/B2 and A3/B3 is {10, 20} ms, and the period of format B1 is {10, 20, The periods of the other 10 formats are {10, 20, 40, 80, 160} ms, and the value set of the starting symbol index in a time slot is {0, 2, 6, 7, 8, 9}. Each format uses two index values.

For example, the third table is applicable to the TDD spectrum of FR2, including 10 short preamble formats: A1, A2, A3, B1, B4, A1/B1, A2/B2, A3/B3, C0 and C2. The period of all formats is {10, 20, 40, 80, 160} ms, and the value set of the start symbol index in a time slot is {0, 2, 5, 6, 7, 8}. Except for the index value of format A3/B3 being 2 and the index values of formats A3 and C2 being 0, 2, and 7, the remaining 7 formats use two index values.

For each PRACH configuration table, the PRACH configuration index (8 bits indicating 0 to 255) indicates the PRACH Preamble format, configuration period, system frame number, subframe/time slot number, starting symbol index within a time slot, and the number of time domain ROs within the time slot. The contents are as follows:

-PRACH Preamble format;

-PRACH configuration period: {10, 20, 40, 80, 160} ms;

- System frame number index within the PRACH configuration period;

-For frequency bands below 6 GHz, the number of PRACH slots contained in 1 ms is:

--When the subcarrier spacing of the PRACH Preamble is 15 kHz, the number of PRACH slots in a subframe is 1;

--When the subcarrier spacing of the PRACH preamble is 30 kHz, the number of PRACH slots in a subframe can be 1 or 2; when there is only one PRACH slot, the second PRACH slot is used;

-For frequency bands above 6 GHz, the number of PRACH slots contained in 0.25 ms is:

--When the subcarrier spacing of the PRACH Preamble is 60kHz, the number of PRACH slots in 0.25ms is 1;

--When the subcarrier spacing of the PRACH Preamble is 120 kHz, the number of PRACH slots within 0.25 ms can be 1 or 2; when there is only one PRACH slot, the second PRACH slot is used;

-PRACH Preamble starting OFDM symbol index within a time slot. For the long preamble format, the PRACH OFDM symbol is calculated according to the subcarrier spacing of the long PRACH Preamble format; for the short PRACH Preamble format, the PRACH OFDM symbol is calculated according to the 15Hz subcarrier spacing;

-The number of time-domain ROs in a time slot; if there are multiple ROs in a time slot, the multiple time-domain ROs are numbered in the order of the time domains.

The above schematically illustrates the PRACH time-frequency resource configuration, and the following describes the SSB and RO resource mapping.

The association relationship between SSB and RO supports one-to-one, many-to-one and one-to-many. The mapping is applied to the scenario where the SSB period is moderate and the total number of SSBs and ROs in the association period is close; the many-to-one mapping is applied to the scenario where the SSB period is short and the number of SSBs in the association period is greater than the number of ROs; the one-to-many mapping is applied to the scenario where the SSB period is long and the number of SSBs in the association period is less than the number of ROs.

For example, the specific mapping rules are as follows: The UE reads the higher-layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB and obtains two parameters, N and R, where N represents the number of SSBs associated with a RO and R represents the number of consecutive contention-based random access preambles corresponding to each SSB. If N < 1 (one-to-many association), one SSB is mapped to 1/N consecutive ROs. If N ≥ 1 (many-to-one association or one-to-one association), R consecutive indexed contention-based random access (CBRA) preambles are associated with SSB#n, and the CBRA preamble index value corresponding to SSB#n associated with each RO starts from n·N _preamble /N, where the parameter n represents the sequence number of the actual SSB associated with an RO, and its value range is 0≤n≤N-1. N _preamble is defined by the higher-layer parameter totalNumberOfRA-Preambles and is an integer multiple of N. The preamble of non-contention random access (CFRA) is directly allocated to the UE by the base station.

For the contention-based random access process, the order in which the SSB index is mapped to the RO is as follows: first, within an RO, arrange in ascending order of the Preamble index; second, multiple frequency-division multiplexed ROs are arranged in ascending order of the frequency resource index; third, time-division multiplexed ROs within a PRACH time slot are arranged in ascending order of the time resource index; fourth, arrange in ascending order of the PRACH time slot index. After a round of SSB to RO mapping is completed, all SSBs actually sent within an SSB cycle are mapped to the RO once. For the random access process triggered by the PDCCH, the order in which the SSB index is mapped to the RO index only includes steps 2 to 4 above.

The association period for SSB mapping to RO is defined as the period during which at least one round of SSB to RO mapping is completed, so that each actually transmitted SSB is mapped to at least one RO. The association period for SSB mapping to RO must be an integer multiple of the PRACH configuration period, and the multiple is the minimum value listed in Table 1 below.

Table 1: Mapping between PRACH configuration period and SSB to RO association period

(Mapping between PRACH configuration period and SS/PBCH block to PRACH occasion association period)

For example, the association period is calculated from radio frame 0. Within an association period, after completing a round of SSB to RO mapping, the next round of mapping continues until the remaining ROs are insufficient to complete a round of SSB to RO mapping. If the remaining ROs are insufficient to complete a round of SSB to RO mapping, these remaining ROs are an invalid RO set. All ROs in the invalid RO set cannot be associated with SSB and cannot be used for PRACH transmission. Because under some configuration conditions, the number of valid ROs contained in the association period of SSB mapping to RO is variable, the NR protocol further defines the time domain repetition period of the association period of SSB mapping to RO through the association mode period. The maximum value of the association mode period of SSB mapping to RO is 160ms.

The above schematically illustrates the contents of the PRACH-related configurations of the embodiments of the present application, and reference may also be made to related technologies.

In the embodiments of the present application, signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, MIB, system information, or a dedicated RRC message; or an RRC IE (RRC information element). Signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC CE (MAC control element). However, the present application is not limited thereto.

In the following description, the terms "PRACH" and "physical random access channel" or "random access information" or "RACH" can be used interchangeably without causing confusion. In addition, transmitting or receiving PRACH can be understood as transmitting or receiving random access information carried by PRACH. In the embodiments of the present application, the terms "indication", "activation" and "trigger" can be used interchangeably, or two or more of them can be used in combination. RACH configuration can be replaced by PRACH resource configuration, PRACH opportunity (RO), PRACH transmission opportunity (PRACH transmission occasion), PRACH resource. RACH configuration can also include parameters or information related to PRACH, such as PRACH preamble format, subcarrier spacing (SCS), etc.

Embodiments of the first aspect

The present invention provides a method for adjusting RACH configuration, which is described from the perspective of a terminal device. FIG2 is a schematic diagram of the method for adjusting RACH configuration according to the present invention. As shown in FIG2 , the method includes:

201. A terminal device receives a first RACH configuration and/or a second RACH configuration from a network device.

202. The terminal device receives first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disablement of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disablement of the second RACH configuration.

It is worth noting that FIG2 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG2 above.

In an embodiment of the present application, a UE in RRC_IDLE state, RRC_INACTIVE state, or RRC_CONNECTED state can be provided with N PRACH-related configurations, where N ≥ 1. For example, for a terminal device in RRC_IDLE state, the terminal device receives the N PRACH-related configurations via a broadcast message (SIB1); for a terminal device in RRC_CONNECTED state, the terminal receives the N PRACH-related configurations via an RRC message. The N PRACH-related configurations include a first RACH configuration and/or a second RACH configuration.

In some embodiments, the N PRACH-related configurations may be PRACH enhanced configurations based on network energy saving, that is, in addition to receiving/being provided with the legacy (conventional or default) RACH configuration, the terminal device also receives/is provided with the N PRACH-related configurations of the embodiment of the present application, that is, N PRACH enhanced configurations. Among them, the legacy (conventional or default) RACH configuration is a PRACH-related configuration parameter/IE in an existing or future protocol. The present application is not limited to this, and may not distinguish between the legacy (conventional or default) RACH configuration and the enhanced RACH configuration.

For example, the first RACH configuration and/or the second RACH configuration are related to network energy saving. The terminal device is a device that supports NES, such as a Rel-19 NES UE, or a UE that has or supports Rel-19 network energy saving (Rel-19 NES capable UE), but the present application is not limited thereto.

For the sake of convenience, the RACH configuration of the embodiment of the present application includes a first RACH configuration and/or a second RACH configuration, but the present application is not limited thereto. For example, a RACH configuration may be provided for a terminal device, and a portion of the RACH configuration is used for energy saving; for another example, N network energy-saving RACH configurations (including the first RACH configuration and/or the second RACH configuration) and M default RACH configurations may be provided for the terminal device; the present application is not limited to the specific RACH configuration. The configuration form of the body.

In some embodiments, if the terminal device is provided with N PRACH-related configurations, such as a first PRACH configuration and/or a second RACH configuration, the terminal device may also receive first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disenablement of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disenablement of the second RACH configuration.

For example, the first indication information and/or the second indication information is: RRC signaling and/or MAC CE and/or DCI, and the RRC signaling and/or MAC CE and/or DCI are used to indicate/activate/trigger at least one PRACH-related configuration among N PRACH-related configurations, that is, the RRC signaling and/or MAC CE and/or DCI are used for dynamic adjustment of PRACH in the time domain.

In some embodiments, the first RACH configuration corresponds to a first type of random access (type 1 RA), such as a 4-step random access. The second RACH configuration corresponds to a second type of random access (type 2 RA), such as a 2-step random access.

In some embodiments, the terminal device performs a random access procedure according to the first RACH configuration and/or the second RACH configuration. The random access procedure is contention-based random access (CBRA) and/or non-contention-based random access (CFRA).

For example, the terminal device may perform a first type of random access and/or contention-based random access (CBRA) according to an activated/enabled/triggered/indicated first RACH configuration and/or a legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration may be RACH configuration information in an existing protocol for legacy UEs or non-NES-capable UEs, or RACH configuration information in a future protocol. The terminal device may be an RRC_idle UE or an RRC_connected UE; and the random access may be a random access in an RRC_idle/inactive mode or a random access in an RRC_connected mode.

Alternatively, the terminal device supports or expects to perform a first type of random access and/or contention-based random access (CBRA) according to the first RACH configuration, or the terminal device does not support or expect to perform a second type of random access and/or non-contention-based random access (CFRA) according to the first RACH configuration.

For another example, the terminal device may perform a first type of random access and/or a non-contention random access (CFRA) according to the activated/enabled/triggered/indicated first RACH configuration and/or the legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration may be RACH configuration information in an existing protocol, used for legacy UEs or non-NES-capable UEs, or RACH configuration information in a future protocol. The terminal device may be an RRC_idle UE or an RRC_connected UE; the random access may be a random access in RRC_idle/inactive mode or a random access in RRC_connected mode.

Alternatively, the terminal device supports or expects to perform a first type of random access and/or non-contention random access (CFRA) according to the first RACH configuration, or the terminal device does not support or expect to perform a second type of random access and/or contention random access (CBRA) according to the first RACH configuration.

For another example, the terminal device may perform a first type of random access and/or contention-based random access (CBRA) and/or non-contention-based random access (CFRA) according to an activated/enabled/triggered/indicated first RACH configuration and/or a legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration may be RACH configuration information in an existing protocol for legacy UEs or non-NES-capable UEs, or RACH configuration information in a future protocol. The terminal device may be an RRC_idle UE or an RRC_connected UE; and the random access may be random access in RRC_idle/inactive mode or random access in RRC_connected mode.

Alternatively, the terminal device supports or expects to perform a first type of random access and/or contention-based random access (CBRA) and/or non-contention random access (CFRA) according to the first RACH configuration, or the terminal device does not support or expect to perform a second type of random access according to the first RACH configuration.

For another example, the terminal device may perform a second type of random access and/or contention-based random access (CBRA) according to an activated/enabled/triggered/indicated second RACH configuration and/or a legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration may be RACH configuration information in an existing protocol, used for legacy UEs or non-NES-capable UEs, or RACH configuration information in a future protocol.

Alternatively, the terminal device supports or expects to perform a second type of random access and/or contention-based random access (CBRA) according to the second RACH configuration, or the terminal device does not support or expect to perform a first type of random access and/or non-contention-based random access (CFRA) according to the second RACH configuration.

For another example, the terminal device can perform a second type of random access and/or a non-contention random access (CFRA) according to the activated/enabled/triggered/indicated second RACH configuration and/or the legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration can be the RACH configuration information in the existing protocol, used for legacy UE or non-NES capable UE, or it can be the RACH configuration information in the future protocol.

Alternatively, the terminal device supports or expects to perform a second type of random access and/or non-contention random access (CFRA) according to the second RACH configuration, or the terminal device does not support or expect to perform a first type of random access and/or contention random access (CBRA) according to the second RACH configuration.

For another example, the terminal device may configure and/or legacy the second RACH according to the activation/enabling/triggering/indication. (conventional or default) RACH configuration for second type random access and/or contention-based random access (CBRA) and/or non-contention random access (CFRA), wherein the legacy (conventional or default) RACH configuration may be RACH configuration information in an existing protocol for legacy UE or non-NES capable UE, or RACH configuration information in a future protocol.

Alternatively, the terminal device supports or expects to perform a second type of random access and/or contention-based random access (CBRA) and/or non-contention random access (CFRA) according to the second RACH configuration, or the terminal device does not support or expect to perform a first type of random access according to the second RACH configuration.

The above schematically illustrates the combination of various random access procedures, and the present application is not limited thereto. The first RACH configuration and the second RACH configuration are further described below.

In some embodiments, the first RACH configuration includes at least one of the following information:

A first time domain parameter, used to indicate time domain information of the first RACH configuration;

A first FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance;

A first frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the first RACH configuration in the frequency domain;

A first time domain offset parameter is used to indicate time domain offset information of the first RACH configuration relative to the four-step random access resource;

A first frequency domain offset parameter is used to indicate frequency domain offset information of the first RACH configuration relative to the four-step random access resource;

The first mapping parameter is used to indicate the number of SSBs of each first RO and/or a preamble of each SSB based on each first RO.

For example, the first RACH configuration includes at least one of the following parameters:

--First time domain parameter: This parameter is used to indicate the parameters of the time domain information such as the PRACH period and frame/subframe position corresponding to the first RACH configuration; if this parameter is absent, the terminal device uses the existing high-level parameter prach-configurationInde;

First frequency-domain FDM parameter: This parameter indicates the number of times the first PRACH occasion is FDMed in a time instance. If this parameter is absent, the terminal device uses the existing higher-layer parameter msg1-FD. The first PRACH occasion is the PRACH occasion corresponding to the first RACH configuration.

--First frequency domain parameter: This parameter is used to indicate the offset of the lowest transmission occasion of the first PRACH in the frequency domain relative to PRB0; if this parameter does not exist, the terminal device uses msg1-FrequencyStart;

--First time domain offset parameter: This parameter is used to indicate the time domain offset information of the first PRACH occasion relative to the PRACH occasion of 4-step RA;

First frequency offset parameter: This parameter indicates the time domain offset of the first PRACH occasion relative to the PRACH occasion of the 4-step RA.

--First SSB-RO mapping parameter: This parameter is used to indicate the number of SSBs for each first PRACH occasion and/or the preamble of each SSB based on each RO; if this parameter does not exist, the terminal device uses the existing higher-layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

In some embodiments, the second RACH configuration includes at least one of the following information:

A second time domain parameter, used to indicate time domain information of the second RACH configuration;

The second FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance;

A second frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the second RACH configuration in the frequency domain;

A second time domain offset parameter is used to indicate time domain offset information of the second RACH configuration relative to the 2-step random access resource;

A second frequency domain offset parameter, used to indicate frequency domain offset information of the second RACH configuration relative to the 2-step random access resource;

The second mapping parameter is used to indicate the number of SSBs of each second RO and/or a preamble of each SSB based on each second RO.

For example, the second RACH configuration includes at least one of the following parameters:

--Second time domain parameter: This parameter is used to indicate the parameters of the time domain information such as the PRACH period and frame/subframe position corresponding to the second RACH configuration. If this parameter does not exist (absent), the terminal device uses the existing high-level parameter prach-configurationInde or msgA-prach-configurationInde;

Second frequency-domain FDM parameter: This parameter indicates the number of times the second PRACH occasion is FDMed in a time instance. If this parameter is absent, the terminal device uses the existing higher-layer parameters msg1-FDM or msgA-RO-FDM. The second PRACH occasion is the PRACH occasion corresponding to the second RACH configuration.

--Second frequency domain parameter: This parameter indicates the offset of the second PRACH's lowest transmission opportunity in the frequency domain relative to PRB0. If this parameter does not exist, the terminal device uses msg1-FrequencyStart or msgA-RO-FrequencyStart.

--Second time domain offset parameter: The parameter is used to indicate the time domain offset information of the second PRACH occasion relative to the PRACH occasion of 2-step RA. The 2-step RA and 4-step RA have separate RRACH occasion configuration;

Second frequency offset parameter: This parameter indicates the frequency offset of the second PRACH occasion relative to the PRACH occasion of 2-step RA, where 2-step RA and 4-step RA have separate RRACH occasion configurations.

--Second SSB-RO mapping parameter: This parameter is used to indicate the number of SSBs for each second PRACH occasion and/or the preamble for each SSB on a per RO basis; if this parameter does not exist, the terminal device uses the existing higher-layer parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB or msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB-r16.

The above schematically illustrates the PRACH-related configuration of an embodiment of the present application. The present application is not limited thereto. For example, it may include one or more of the above IEs, other IEs may also be used, and other names or information formats may also be used. In addition, the PRACH-related configuration of the embodiment of the present application may also be referred to as PRACH (time-frequency) resources, RACH/PRACH occasion, PRACH resource configuration, PRACH, RO, PRACH transmission occasion, or PRACH resources, PRACH occasion configuration. Etc., the present application is not limited thereto.

In some embodiments, the terminal device receives a third RACH configuration from the network device; the terminal device performs a random access procedure according to the third RACH configuration. The first indication information is further used to indicate activation/deactivation or enable/disable of the third RACH configuration.

For example, the third RACH configuration corresponds to a first type of random access and a second type of random access. The random access procedure is contention-based random access (CBRA) and/or non-contention-based random access (CFRA). For example, the third RACH configuration may be a RACH configuration for type-1 RA and type-2 RA.

In some embodiments, the terminal device performs the first type of random access or the second type of random access according to the activated/enabled/triggered/indicated third RACH configuration, and/or performs contention-based random access (CBRA) or non-contention-based random access (CFRA).

For example, the terminal device can perform first type random access and/or second type random access and/or contention-based random access (CBRA) according to the activated/enabled/triggered/indicated second RACH configuration and/or the legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration can be the RACH configuration information in the existing protocol, used for legacy UE or non-NES capable UE, or it can be the RACH configuration information in the future protocol.

Alternatively, the terminal device supports or expects to perform the first type of random access and/or the second type of random access and/or contention-based random access (CBRA) according to the third RACH configuration, or the terminal device does not support or expect to perform non-contention random access (CFRA) according to the third RACH configuration.

For another example, the terminal device may perform a first type of random access and/or a second type of random access and/or a non-contention based random access (CFRA) according to an activated/enabled/triggered/indicated second RACH configuration and/or a legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration may be RACH configuration information in an existing protocol, used for legacy UEs or non-NES capable UEs, or RACH configuration information in a future protocol.

Alternatively, the terminal device supports or expects to perform the first type of random access and/or the second type of random access and/or non-contention based random access (CFRA) according to the third RACH configuration, or the terminal device does not support or expect to perform contention based random access (CBRA) according to the third RACH configuration.

For another example, the terminal device may perform first type random access and/or second type random access and/or non-contention based random access (CFRA) and/or contention based random access (CBRA) according to the activated/enabled/triggered/indicated second RACH configuration and/or the legacy (conventional or default) RACH configuration, wherein the legacy (conventional or default) RACH configuration may be the RACH configuration information in the existing protocol, used for legacy UE or non-NES capable UE, or may be the RACH configuration information in the future protocol.

Alternatively, the terminal device supports or expects to perform the first type of random access and/or the second type of random access and/or non-contention based random access (CFRA) and/or contention based random access (CBRA) according to the third RACH configuration. In some embodiments, the third RACH configuration includes at least one of the following information:

A third time domain parameter, used to indicate time domain information of the third RACH configuration;

The third FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance;

A third frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the third RACH configuration in the frequency domain;

A third time domain offset parameter is used to indicate the time domain offset information of the third RACH configuration relative to the 4-step random access resource;

A third frequency domain offset parameter is used to indicate frequency domain offset information of the third RACH configuration relative to the 4-step random access resource;

a third mapping parameter, configured to indicate the number of SSBs of each third RO and/or a preamble of each SSB based on each third RO;

A third preamble parameter is used to indicate the number of preambles for 2-step random access associated with each SSB of a third RO shared with 4-step random access, or to indicate that 2-step random access is not supported;

The third RO parameter is used to indicate the RO subset of the 4-step random access shared with the 2-step random access.

For example, the third RACH configuration includes at least one of the following parameters:

--Third time domain parameter: This parameter is used to indicate the PRACH period, frame/subframe corresponding to the third RACH configuration. Parameters of time domain information such as frame position. If the parameters do not exist (absent), the terminal device uses the existing high-level parameter prach-configurationInde;

-- Third frequency-domain FDM parameter: This parameter indicates the number of times the third PRACH occasion is FDMed in a time instance. If this parameter is absent, the terminal device uses the existing higher-layer parameter msg1-FD. The third PRACH occasion is the PRACH occasion corresponding to the third RACH configuration.

--Third frequency domain parameter: This parameter indicates the offset of the lowest transmission opportunity of the third PRACH in the frequency domain relative to PRB0. If this parameter does not exist, the terminal device uses msg1-FrequencyStart.

--Third time domain offset parameter: This parameter is used to indicate the time domain offset information of the third PRACH occasion relative to the PRACH occasion of 4-step RA;

--Third frequency domain offset parameter: This parameter is used to indicate the time domain offset information of the third PRACH occasion relative to the PRACH occasion of 4-step RA;

--Third SSB-RO mapping parameter: This parameter is used to indicate the number of SSBs per third PRACH occasion and/or the preamble per SSB per RO. If this parameter does not exist, the terminal device uses the existing higher-layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

--Third preamble parameter: Type-1 RA and type-2 RA share the third RO. This parameter is used to indicate the number of preambles associated with the CBRA for type-2 RA per SSB of the third RO shared with the type-1 RA. If this parameter does not exist, the terminal device uses msgA-CB-PreamblesPerSSB-PerSharedRO; or it indicates that the Rel-19 NES does not support 2-step RA.

--Third RO mask index parameter: This parameter is used to indicate the subset of ROs of type-1 RA shared with type-2 RA, which is used for 2-step RA. This field is configured when there are multiple ROs per SSB. If there are multiple ROs per SSB and this parameter is not present, the terminal device can use msgA-SSB-SharedRO-MaskIndex.

The above schematically illustrates PRACH configurations, and the present application is not limited thereto. Rel-19 network energy conservation can make corresponding adjustments to PRACH time domain resources, frequency domain resources, and the SSB and RACH mapping relationship. The following further describes SSB-RO mapping.

In some embodiments, the mapping rules of SSB to the valid first PRACH occasion and/or the valid second PRACH occasion and/or the valid third PRACH occasion may be in accordance with the SSB-RO mapping rules in the existing protocol. For example, it may be as described in the following Table 2:

Table 2

In some embodiments, for example, a terminal device receives a first RACH configuration for type-1 random access. The first RACH configuration includes at least a first SSB-RO mapping parameter. The terminal device determines a mapping relationship between an SSB and a first PRACH occasion based on the first SSB-RO mapping parameter, and determines a preamble for each SSB mapped to each valid first PRACH occasion; the first PRACH occasion is a PRACH occasion used only for type-1 random access.

Alternatively, the first RACH configuration does not include the first SSB-RO mapping parameter, and the terminal device determines the mapping relationship between the SSB and the first PRACH occasion based on the existing parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB, and determines the preamble of each SSB mapped to each valid first PRACH occasion.

In some embodiments, for example, a terminal device receives a third RACH configuration for type-1 random access and/or type-2 random access. The third RACH configuration includes a third SSB-RO mapping parameter and/or a third RO mask index parameter and/or a third preamble parameter. The terminal device determines, based on the third SSB-RO mapping parameter, a mapping relationship between the SSB and the third PRACH occasion of type-1 random access (4-step), and determines each valid third PRACH occasion mapping. The terminal device also determines, based on the third SSB-RO mapping parameter and/or the third RO mask index parameter and/or the third preamble parameter, a mapping relationship between the SSB and the third PRACH occasion of type-2 random access (2-step random access), and determines the preamble of each SSB mapped to the third PRACH occasion of each valid type-2 random access (2-step random access), where the third PRACH occasion is a shared PRACH occasion for type-1 random access (4-step random access) and type-2 random access (2-step random access).

Alternatively, the third RACH configuration does not include the third SSB-RO mapping parameter and/or the third RO mask index parameter and/or the third preamble parameter, and the terminal device is based on the existing parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB determines the mapping relationship between SSB and the third PRACH occasion of type-1 random access (4-step), and determines the preamble of each SSB mapped to the third PRACH occasion of each valid type-1 random access (4-step). The terminal device also determines the mapping relationship between SSB and the third PRACH occasion of type-2 random access (2-step) based on the existing parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB and/or msgA-CB-PreamblesPerSSB-PerSharedRO and/or msgA-SSB-SharedRO-MaskIndex, and determines the preamble of each SSB mapped to the third PRACH occasion of each valid type-2 random access (2-step), where the third PRACH occasion is a shared PRACH occasion for type-1 random access (4-step random access) and type-2 random access (2-step random access).

For example, for PRACH occasion configuration, a UE is configured with a separate/additional PRACH occasion configuration or PRACH resource related to network energy saving through the first parameter of the higher layer.

For type-1 random access procedure, if the first PRACH configuration and/or the third RACH configuration is activated/indicated/triggered, a NES-capable UE is provided with N SS/PBCH block indices associated with a PRACH occasion and R contention-based ordinals for each SS/PBCH block index for each valid PRACH occasion via the SSB-RO mapping parameter (if configured); otherwise, via existing parameters (e.g., ssb-perrach-OccasionAndCB-preamblePerSSB). For example, it may be as described in Table 3:

Table 3

Figure 3 is an example diagram of SSB-RO mapping according to an embodiment of the present application. As shown in Figure 3, for example, existing 4-step random access and 2-step random access have separate RACH configurations, as shown in Figure 3 for the RO for 4-step RA and the RO for 2-step RA; for example, in the random access of the embodiment of the present application for NES, as shown in Figure 3 for the first RO.

FIG4 is another example diagram of SSB-RO mapping in an embodiment of the present application. As shown in FIG4, for example, the existing 4-step random access and 2-step random access have a shared common RACH configuration, as shown in FIG4 for the RO for 4-step RA and 2-step RA; the embodiment of the present application, for example, for the random access of NES, as shown in FIG4 for the first RO Show.

For type-2 random access procedure, if the third RACH configuration is activated and the type-2 random access procedure and the type-1 random access procedure share the PRACH occasion configuration, a NES capable UE is provided with N SS/PBCH block indices associated with one PRACH occasion based on the third SSB-RO mapping parameter (if configured) or the existing parameters (e.g. ssb-perrach-OccasionAndCB-preamblePerSSB), and is provided with Q contention-based ordinals for type-2 random access for each SS/PBCH block index for each valid PRACH occasion via the third preamble parameter (if configured) or the existing parameter msgA-CB-PreamblesPerSSB-PerSharedRO. For a terminal device that provides a PRACH mask index by the third RO mask index parameter (if configured) or msgA-SSB-SharedRO-MaskIndex, PRACH transmissions may be performed on a subset of PRACH occasions associated with the same SSB index within the SSB-RO mapping period. For example, this may be as described in Table 4:

Table 4

Accordingly, examples of SSB-RO mapping can be found in Figures 3 and 4.

In some embodiments, for example, a terminal device receives a first RACH configuration and a second RACH configuration, where the first RACH configuration is for type-1 random access and the second RACH configuration is for type-2 random access. The second RACH configuration includes a second SSB-RO mapping parameter, and the terminal device determines a mapping relationship between an SSB and a second PRACH occasion based on the second SSB-RO mapping parameter, and determines a preamble for each SSB mapped to each valid second PRACH occasion.

Alternatively, the second RACH configuration does not include the second SSB-RO mapping parameter, and the terminal device is based on the second The SSB-RO mapping parameter or the existing mapping parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB or msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB determines the mapping relationship between SSB and the second PRACH occasion, and also determines the preamble of each SSB mapped to each valid second PRACH occasion.

For type-2 random access procedures, if the first PRACH configuration and/or the second RACH configuration are activated, the type-2 random access procedure and the type-1 random access procedure use an independent/separate second RACH configuration, and a UE with NES capability is provided with N SS/PBCH block indices associated with a PRACH occasion based on the second SSB-RO mapping parameter (if configured), and R contention-based ordinal numbers for each SS/PBCH block index for each valid PRACH occasion. If the second SSB-RO mapping parameter is configured, it is determined by that parameter, otherwise it is determined by the first SSB-RO mapping parameter or ssb-perrach-OccasionAndCB-preamblePerSSB or msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB. For example, it can be as described in Table 5:

Table 5

Figure 5 is another example diagram of SSB-RO mapping according to an embodiment of the present application. As shown in Figure 5 , for example, existing 4-step random access and 2-step random access have separate RACH configurations, as shown in Figure 5 for the RO for 4-step RA and the RO for 2-step RA; for example, in the random access of an embodiment of the present application for NES, as shown in Figure 5 for the first RO and the second RO.

Figure 6 is another example diagram of SSB-RO mapping according to an embodiment of the present application. As shown in Figure 6, for example, existing 4-step random access and 2-step random access share a common RACH configuration, as shown in Figure 6 for the ROs of 4-step RA and 2-step RA; for example, in the random access of an NES according to an embodiment of the present application, as shown in Figure 6 for the first and second ROs.

The above is a schematic illustration of the SSB-RO mapping of the present application, and the present application is not limited thereto. The preamble format associated with the first RACH configuration/second RACH configuration may use the existing preamble format without defining a new preamble format; alternatively, the preamble format associated with the first RACH configuration/second RACH configuration may define a new preamble format; the present application is not limited thereto.

The following embodiments illustrate that when the first RACH configuration and/or the second RACH configuration and/or the third RACH configuration is enabled/activated triggered/indicated, a terminal device with Rel-19 network energy saving capability performs random access in RRC_idle/inactive mode and/or random access in RRC_connected mode.

In some embodiments, when the first RACH configuration and/or the second RACH configuration and/or the third RACH configuration is enabled/activated triggered/indicated, the terminal device with Rel-19 network energy saving capability performs random access in RRC_connected mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, that is, PRACH resources related to network energy saving, including random access triggered by handover, beam failure recovery, SI request, PDCCH order, uplink data arrival, etc.; and performs random access in RRC_idle/inactive mode, that is, initial random access.

Therefore, terminal devices with Rel-19 network energy-saving capabilities perform random access on PRACH resources related to network energy-saving in RRC_connected mode and RRC_idle/inactive mode. There is no restriction on which type of random access the terminal device performs on PRACH resources related to network energy-saving, which can increase the flexibility of terminal implementation and improve network energy-saving gains.

For example, a terminal device with Rel-19 network energy saving capability may perform CBRA and CFRA in RRC_connected mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, i.e., PRACH resources related to network energy saving, and may perform CBRA and CFRA in RRC_idle/inactive mode;

For another example, a terminal device with Rel-19 network energy-saving capability can perform CBRA and CFRA in RRC_connected mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, that is, the PRACH resources related to network energy saving. At the same time, it can perform CBRA but not CFRA in RRC_idle/inactive mode.

In some embodiments, when the first RACH configuration and/or the second RACH configuration and/or the third RACH configuration is enabled/activated triggered/indicated, the terminal device with Rel-19 network energy saving capability performs random access in RRC_connected mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, that is, the PRACH resource related to network energy saving, including random access triggered by handover, beam failure recovery, SI request, PDCCH order, uplink data arrival, etc.; or, the terminal device with Rel-19 network energy saving capability performs random access in RRC_connected mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, that is, the PRACH resource related to network energy saving, including random access triggered by handover, beam failure recovery, SI request, PDCCH order, uplink data arrival, etc.; The terminal device with the capability does not perform random access, i.e., initial random access, in RRC_idle/inactive mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, i.e., PRACH resources related to network energy saving. RRC_idle/inactive UE does not support random access, i.e., initial random access, on the PRACH related to network energy saving.

Therefore, terminal devices with Rel-19 network energy-saving capabilities only need to perform random access in RRC_connected mode on PRACH resources related to network energy-saving, which can reduce the complexity of base station implementation and configuration. For the activation/deactivation indication of PRACH resources related to network energy-saving, it is only necessary to notify the RRC_connected state UE, which is simple and convenient.

In some embodiments, when the first RACH configuration and/or the second RACH configuration and/or the third RACH configuration is enabled/activated triggered/indicated, a terminal device with Rel-19 network energy saving capability performs random access, i.e., initial random access, in RRC_idle/inactive mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, i.e., PRACH resources related to network energy saving. Alternatively, a terminal device with Rel-19 network energy saving capability does not perform random access in RRC_connected mode based on the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, i.e., PRACH resources related to network energy saving, including random access triggered by handover, beam failure recovery, SI request, PDCCH order, uplink data arrival, etc. RRC_connected UE does not support random access on PRACH resources related to network energy saving. The following embodiments illustrate how a terminal device with Rel-19 network energy saving capability selects PRACH resources when the first RACH configuration and/or the second RACH configuration and/or the third RACH configuration is enabled/activated triggered/indicated.

The terminal device determines, based on the first indication information and/or the second indication information, that the first RACH configuration and/or the second RACH configuration and/or the third RACH configuration is activated/enabled/indicated/triggered, and the terminal device with Rel-19 network energy-saving capability may select the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource and/or the legacy PRACH resource (PRACH resource of a legacy UE or a non-network energy-saving UE) for random access. The first/second/third PRACH resource is a PRACH resource associated with the first/second/third RACH configuration.

In some embodiments, a terminal device with Rel-19 network energy-saving capability may select the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource, or legacy PRACH resources (PRACH resources of legacy UE or non-network energy-saving UE) based on the terminal implementation in all PRACH attempts after the first PRACH attempt and the failure of the PRACH attempt. Whether to select the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource related to network energy saving or the legacy PRACH resource depends on the UE terminal implementation.

In some embodiments, a terminal device with Rel-19 network energy saving capability may receive a PRACH signal on the first PRACH attempt. When the PRACH attempt fails, the first PRACH resource and/or the second PRACH resource and/or the third PRACH resource related to network energy saving are selected. After the PRACH attempt fails, the legacy PRACH resource is selected. This method can avoid or reduce the impact on the PRACH attempt of the legacy UE.

In some embodiments, a terminal device with Rel-19 network energy-saving capability selects legacy PRACH resources during a first PRACH attempt, and then selects a first PRACH resource and/or a second PRACH resource and/or a third PRACH resource related to network energy saving after the PRACH attempt fails.

The following embodiments illustrate power control parameters for the first/second/third RACH configurations.

In some embodiments, the power control parameters of the first RACH configuration and/or the second RACH configuration and/or the third RACH configuration are the same as the power control parameters of the legacy RACH configuration (PRACH or RACH configuration of legacy UE or non-network energy-saving UE) or the values of the parameter configurations are the same.

The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

It can be seen from the above embodiments that in some scenarios of wireless communication applications (such as energy-saving mode), network equipment and terminal equipment can quickly and flexibly indicate/activate/trigger RACH configuration, which can not only improve network gain (such as energy-saving gain) but also ensure normal transmission of terminal equipment.

Embodiments of the second aspect

The embodiment of the present application provides a method for adjusting RACH configuration, which is described from the perspective of a network device. The embodiment of the second aspect can be combined with the embodiment of the first aspect, and the same contents as the embodiment of the first aspect will not be repeated.

FIG7 is a schematic diagram of a method for adjusting RACH configuration according to an embodiment of the present application. As shown in FIG7 , the method includes:

701. A network device sends a first RACH configuration and/or a second RACH configuration.

702. The network device sends first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enabling/disabling of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enabling/disabling of the second RACH configuration.

In some embodiments, the PRACH resource related to network energy saving supports type-1 random access but does not support type-2 random access. The terminal device is configured with a first RACH configuration, and the terminal device further receives first indication information, where the first indication information is used to indicate activation/deactivation, or enable/disable of the first RACH configuration.

In some embodiments, network energy saving related PRACH resources support type-1 random access and type-2 random access. Access, the type-1 random access and the type-2 random access share the same RO configuration, that is, the third RACH configuration. The terminal device is configured with the third RACH configuration, and the terminal device further receives first indication information, where the first indication information is used to indicate activation/deactivation, or enabling/disabling, of the third RACH configuration.

In some embodiments, network energy-saving-related PRACH resources support type-1 random access and type-2 random access, and the type-1 random access and type-2 random access have independent RO configurations, that is, the first RACH configuration corresponds to type-1 random access, and the second RACH configuration corresponds to type-2 random access. The terminal device is configured with the first RACH configuration and the second RACH configuration, and the terminal further receives first indication information and second indication information, the first indication information is used to indicate activation/deactivation, or enablement/disablement, of the first RACH configuration, and the second indication information is used to indicate activation/deactivation, or enablement/disablement of the second RACH configuration.

It is worth noting that FIG7 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG7 above.

As shown in FIG7 , the method may further include:

703. The network device receives random access information from the terminal device.

The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

It can be seen from the above embodiments that in some scenarios of wireless communication applications (such as energy-saving mode), network equipment and terminal equipment can quickly and flexibly indicate/activate/trigger RACH configuration, which can not only improve network gain (such as energy-saving gain) but also ensure normal transmission of terminal equipment.

Embodiments of the third aspect

The embodiment of the present application provides a RACH configuration adjustment device. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. The same contents as those in the embodiment of the first aspect will not be repeated here.

FIG8 is a schematic diagram of an apparatus for adjusting RACH configuration according to an embodiment of the present application. As shown in FIG8 , the apparatus 800 for adjusting RACH configuration includes:

A receiving unit 801, configured to receive a first RACH configuration and/or a second RACH configuration from a network device;

The receiving unit 801 further receives first indication information and/or second indication information; wherein the first indication information The second indication information is used to indicate activation/deactivation or enabling/disabling of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enabling/disabling of the second RACH configuration.

In some embodiments, as shown in FIG8 , the RACH configuration adjustment apparatus 800 may further include:

The sending unit 802 performs a random access procedure according to the first RACH configuration and/or the second RACH configuration.

In some embodiments, the random access procedure is contention-based random access (CBRA) and/or non-contention random access (CFRA).

In some embodiments, the first RACH configuration corresponds to a first type of random access.

In some embodiments, the sending unit 802 performs a first type of random access and/or performs contention-based random access (CBRA) or non-contention random access (CFRA) according to the activated/enabled/triggered/indicated first RACH configuration.

In some embodiments, the terminal device supports or desires to perform a first type of random access and/or contention-based random access (CBRA) or non-contention random access (CFRA) according to a first RACH configuration.

In some embodiments, the terminal device does not support or desire to perform the second type of random access according to the first RACH configuration and/or perform contention-based random access (CBRA) or non-contention random access (CFRA).

In some embodiments, the first RACH configuration includes at least one of the following information:

A first time domain parameter, used to indicate time domain information of the first RACH configuration;

A first FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance;

A first frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the first RACH configuration in the frequency domain;

A first time domain offset parameter is used to indicate time domain offset information of the first RACH configuration relative to the four-step random access resource;

A first frequency domain offset parameter is used to indicate frequency domain offset information of the first RACH configuration relative to the four-step random access resource;

The first mapping parameter is used to indicate the number of SSBs of each first RO and/or a preamble of each SSB based on each first RO.

In some embodiments, the second RACH configuration corresponds to a second type of random access.

In some embodiments, the sending unit 802 performs a second type of random access and/or performs a non-contention random access (CFRA) or a contention-based random access (CBRA) according to the activated/enabled/indicated/triggered second RACH configuration.

In some embodiments, the terminal device supports or expects a second type of random Access and/or perform non-contention random access (CFRA) or contention-based random access (CBRA).

In some embodiments, the terminal device does not support or desire to perform the first type of random access and/or perform contention-based random access (CBRA) or non-contention random access (CFRA) according to the second RACH configuration.

In some embodiments, the second RACH configuration includes at least one of the following information:

A second time domain parameter, used to indicate time domain information of the second RACH configuration;

The second FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance;

A second frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the second RACH configuration in the frequency domain;

A second time domain offset parameter is used to indicate time domain offset information of the second RACH configuration relative to the 2-step random access resource;

A second frequency domain offset parameter, used to indicate frequency domain offset information of the second RACH configuration relative to the 2-step random access resource;

The second mapping parameter is used to indicate the number of SSBs of each second RO and/or a preamble of each SSB based on each second RO.

In some embodiments, the first indication information and/or the second indication information is carried by at least one of the following: RRC message, MAC CE, downlink control information (DCI).

In some embodiments, the receiving unit 801 further receives a third RACH configuration from the network device; the sending unit 802 further performs a random access procedure according to the third RACH configuration. The first indication information is further used to indicate activation/deactivation or enable/disable of the third RACH configuration.

In some embodiments, the random access procedure is contention-based random access (CBRA) and/or non-contention-based random access (CFRA).

In some embodiments, the third RACH configuration corresponds to a first type of random access and a second type of random access.

In some embodiments, the terminal device performs the first type of random access or the first type of random access according to the activated/enabled/triggered/indicated third RACH configuration, and/or performs contention-based random access (CBRA) or non-contention random access (CFRA).

In some embodiments, the third RACH configuration includes at least one of the following information:

A third time domain parameter, used to indicate time domain information of the third RACH configuration;

The third FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance;

A third frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the third RACH configuration in the frequency domain;

The third time domain offset parameter is used to indicate the time domain of the third RACH configuration relative to the 4-step random access resource. offset information;

A third frequency domain offset parameter is used to indicate frequency domain offset information of the third RACH configuration relative to the 4-step random access resource;

a third mapping parameter, configured to indicate the number of SSBs of each third RO and/or a preamble of each SSB based on each third RO;

A third preamble parameter is used to indicate the number of preambles for 2-step random access associated with each SSB of a third RO shared with 4-step random access, or to indicate that 2-step random access is not supported;

The third RO parameter is used to indicate the RO subset of the 4-step random access shared with the 2-step random access.

In some embodiments, the terminal device is a device supporting NES; the first RACH configuration and/or the second RACH configuration are related to network energy saving.

It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The RACH configuration adjustment device 800 may also include other components or modules. For details of these components or modules, reference may be made to related technologies.

In addition, for the sake of simplicity, FIG8 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

Through the embodiments of the present application, in some scenarios of wireless communication applications (such as energy-saving mode), network devices and terminal devices can quickly and flexibly indicate/activate/trigger RACH configuration, which can not only improve network gain (such as energy-saving gain) but also ensure normal transmission of terminal devices.

Embodiments of the fourth aspect

The embodiment of the present application provides a RACH configuration adjustment device, which can be, for example, a network device, or one or more components or assemblies configured in the network device, and the same contents as those in the first and second aspects of the embodiment will not be repeated.

FIG9 is a schematic diagram of an apparatus for adjusting RACH configuration according to an embodiment of the present application. As shown in FIG9 , the apparatus 900 for adjusting RACH configuration includes:

A sending unit 901, configured to send a first RACH configuration and/or a second RACH configuration;

The sending unit 901 further sends first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enable/disable of the first RACH configuration, and the second indication information is used to indicate Indicates activation/deactivation or enable/disable of the second RACH configuration.

In some embodiments, as shown in FIG9 , the RACH configuration adjustment apparatus 900 may further include:

The receiving unit 902 receives random access information from a terminal device.

It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The RACH configuration adjustment device 900 may also include other components or modules. For details of these components or modules, reference may be made to related technologies.

In addition, for the sake of simplicity, FIG9 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

Through the embodiments of the present application, in some scenarios of wireless communication applications (such as energy-saving mode), network devices and terminal devices can quickly and flexibly indicate/activate/trigger RACH configuration, which can not only improve network gain (such as energy-saving gain) but also ensure normal transmission of terminal devices.

Embodiments of the fifth aspect

An embodiment of the present application also provides a communication system, and reference may be made to FIG1 . The contents that are the same as those in the first to fourth aspects of the embodiments will not be repeated.

In some embodiments, the communication system 100 may include at least:

A network device, which sends a first RACH configuration and/or a second RACH configuration to a terminal device; sends first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enabling/disabling of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enabling/disabling of the second RACH configuration;

A terminal device receives the first RACH configuration and/or the second RACH configuration; and receives the first indication information and/or the second indication information.

The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

Figure 10 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 10 , terminal device 1000 may include a processor 1010 and a memory 1020. Memory 1020 stores data and programs and is coupled to processor 1010. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

For example, the processor 1010 may be configured to execute a program to implement the RACH as described in the embodiment of the first aspect. Configuration adjustment method. For example, the processor 1010 may be configured to perform the following control: receiving a first RACH configuration and/or a second RACH configuration from a network device; receiving first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disability of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disability of the second RACH configuration.

As shown in Figure 10 , the terminal device 1000 may further include: a communication module 1030, an input unit 1040, a display 1050, and a power supply 1060. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1000 does not necessarily include all of the components shown in Figure 10 , and these components are not essential. Furthermore, the terminal device 1000 may also include components not shown in Figure 10 , for which reference may be made to the prior art.

An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

Figure 11 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 11 , network device 1100 may include a processor 1110 (e.g., a central processing unit (CPU)) and a memory 1120 ; the memory 1120 is coupled to the processor 1110 . The memory 1120 may store various data and may also store an information processing program 1130 , which is executed under the control of the processor 1110 .

For example, the processor 1110 may be configured to execute a program to implement the RACH configuration adjustment method as described in the embodiment of the second aspect. For example, the processor 1110 may be configured to perform the following control: sending a first RACH configuration and/or a second RACH configuration; sending first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disability of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disability of the second RACH configuration.

In addition, as shown in FIG11 , the network device 1100 may further include: a transceiver 1140 and an antenna 1150; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that the network device 1100 does not necessarily include all the components shown in FIG10 ; in addition, the network device 1100 may also include components not shown in FIG10 , and reference may be made to the prior art for details.

An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the RACH configuration adjustment method described in the embodiment of the first aspect.

An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the RACH configuration adjustment method described in the embodiment of the first aspect.

An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the RACH configuration adjustment method described in the embodiment of the second aspect.

An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the RACH configuration adjustment method described in the embodiment of the second aspect.

The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

The method/device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and/or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

One or more of the functional blocks and/or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and/or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

1. A method for adjusting RACH configuration, comprising:

The terminal device receives the first RACH configuration and/or the second RACH configuration from the network device;

The terminal device also receives first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enable/disable of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enable/disable of the second RACH configuration.

2. A method for adjusting RACH configuration, comprising:

The network device sends the first RACH configuration and/or the second RACH configuration;

The network device further sends first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disability of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disability of the second RACH configuration.

3. A terminal device comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the RACH configuration adjustment method as described in Note 1.

4. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the RACH configuration adjustment method as described in Note 2.

5. A computer program product, comprising at least a computer program, wherein when the computer program is executed by a processor, the terminal device executes the RACH configuration adjustment method as described in Note 1.

6. A computer program product, comprising at least a computer program, wherein when the computer program is executed by a processor, the network device executes the RACH configuration adjustment method as described in Note 2.

Claims (20)

A RACH configuration adjustment device, comprising: a receiving unit configured to receive a first RACH configuration and/or a second RACH configuration from a network device; The receiving unit further receives first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disability of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disability of the second RACH configuration. The apparatus according to claim 1, further comprising: A sending unit, configured to perform a random access procedure according to the first RACH configuration and/or the second RACH configuration. The apparatus according to claim 2, wherein the random access procedure is contention-based random access and/or non-contention-based random access. The apparatus of claim 2, wherein the first RACH configuration corresponds to a first type of random access. The apparatus according to claim 4, wherein the transmitting unit performs a first type of random access and/or performs contention-based random access or non-contention random access according to the activated/enabled/triggered/indicated first RACH configuration. The apparatus according to claim 4, wherein the terminal device supports or desires to perform a first type of random access and/or contention-based random access or non-contention random access according to the first RACH configuration, and/or The terminal device does not support or expects to perform the second type of random access and/or contention-based random access or non-contention random access according to the first RACH configuration. The apparatus according to claim 1, wherein the first RACH configuration includes at least one of the following information: A first time domain parameter, used to indicate time domain information of the first RACH configuration; A first FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance; A first frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the first RACH configuration in the frequency domain; A first time domain offset parameter is used to indicate time domain offset information of the first RACH configuration relative to the four-step random access resource; A first frequency domain offset parameter is used to indicate frequency domain offset information of the first RACH configuration relative to the four-step random access resource; The first mapping parameter is used to indicate the number of SSBs of each first RO and/or a preamble of each SSB based on each first RO. The apparatus of claim 3, wherein the second RACH configuration corresponds to a second type of random access. The apparatus according to claim 8, wherein the transmitting unit performs the second type of random access and/or performs non-contention random access or contention-based random access according to the activated/enabled/indicated/triggered second RACH configuration. The apparatus according to claim 8, wherein the terminal device supports or desires to perform the second type of random access and/or perform non-contention random access or contention-based random access according to the second RACH configuration, and/or The terminal device does not support or expects to perform the first type of random access and/or contention-based random access or non-contention random access according to the second RACH configuration. The apparatus according to claim 1, wherein the second RACH configuration includes at least one of the following information: A second time domain parameter, used to indicate time domain information of the second RACH configuration; The second FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance; A second frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the second RACH configuration in the frequency domain; A second time domain offset parameter is used to indicate time domain offset information of the second RACH configuration relative to the 2-step random access resource; A second frequency domain offset parameter, used to indicate frequency domain offset information of the second RACH configuration relative to the 2-step random access resource; The second mapping parameter is used to indicate the number of SSBs of each second RO and/or a preamble of each SSB based on each second RO. The device according to claim 1, wherein the first indication information and/or the second indication information is carried by at least one of the following: RRC message, MAC CE, downlink control information. The apparatus according to claim 2, wherein the receiving unit further receives a third RACH configuration from the network device, and the first indication information is further used to indicate activation/deactivation or enablement/disablement of the third RACH configuration; and the sending unit further performs a random access procedure according to the third RACH configuration. The apparatus according to claim 13, wherein the random access procedure is contention-based random access and/or non-contention-based random access. The apparatus of claim 13, wherein the third RACH configuration corresponds to a first type of random access and a second type of random access. The apparatus according to claim 15, wherein the terminal device performs the first type of random access or the first type of random access according to the activated/enabled/triggered/indicated third RACH configuration, and/or performs contention-based random access or non-contention-based random access. The apparatus according to claim 13, wherein the third RACH configuration comprises at least one of the following information: A third time domain parameter, used to indicate time domain information of the third RACH configuration; The third FDM parameter is used to indicate the number of frequency division multiplexing times in a time instance; A third frequency domain parameter, used to indicate a relative offset of a minimum transmission opportunity of the third RACH configuration in the frequency domain; A third time domain offset parameter is used to indicate the time domain offset information of the third RACH configuration relative to the 4-step random access resource; A third frequency domain offset parameter is used to indicate frequency domain offset information of the third RACH configuration relative to the 4-step random access resource; a third mapping parameter, configured to indicate the number of SSBs of each third RO and/or a preamble of each SSB based on each third RO; A third preamble parameter is used to indicate the number of preambles for 2-step random access associated with each SSB of a third RO shared with 4-step random access, or to indicate that 2-step random access is not supported; The third RO parameter is used to indicate the RO subset of the 4-step random access shared with the 2-step random access. The apparatus according to claim 1, wherein the terminal device is a device supporting NES; and the first RACH configuration and/or the second RACH configuration are related to network energy saving. A RACH configuration adjustment device, comprising: a sending unit, configured to send a first RACH configuration and/or a second RACH configuration; The sending unit further sends first indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enablement/disability of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enablement/disability of the second RACH configuration. A communication system comprising: The network device sends a first RACH configuration and/or a second RACH configuration to the terminal device; sends a first instruction indication information and/or second indication information; wherein the first indication information is used to indicate activation/deactivation or enable/disable of the first RACH configuration, and the second indication information is used to indicate activation/deactivation or enable/disable of the second RACH configuration; A terminal device receives the first RACH configuration and/or the second RACH configuration; and receives the first indication information and/or the second indication information.