CN116530194A

CN116530194A - Random access method, device, terminal and storage medium

Info

Publication number: CN116530194A
Application number: CN202180076923.3A
Authority: CN
Inventors: 付喆; 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-03-18
Filing date: 2021-03-18
Publication date: 2023-08-01
Also published as: WO2022193258A1

Abstract

The application discloses a random access method, a device, a terminal and a storage medium, and relates to the field of mobile communication, wherein the method comprises the following steps: the terminal receives first RACH information in a system information block; and receiving second RACH information in the dedicated signaling; a random access procedure is performed using the first RACH information or the second RACH information. In the case that the SIB and the dedicated signaling are simultaneously configured with RACH information, the present application provides a scheme in which a terminal selects RACH information suitable for itself to perform a random access procedure in the case that there are multiple sets of RACH configurations.

Description

Random access method, device, terminal and storage medium

Technical Field

The present invention relates to the field of mobile communications, and in particular, to a random access method, a device, a terminal, and a storage medium.

Background

The radio access network (Radio Access Network, RAN) needs to be enhanced on how vertical traffic is supported at the access network. For example, for network slicing (sliming) based services, lower latency, more targeted, more flexible and more scalable services are provided for multiple services of different needs.

Disclosure of Invention

The embodiment of the application provides a random access method, a device, a terminal and a storage medium, wherein User Equipment (UE) can select to use random access channel (Random Access Channel, RACH) resources configured in a system information block or RACH resources configured in proprietary signaling. The technical scheme is as follows.

According to an aspect of the present application, there is provided a random access method, the method including:

receiving first RACH information in a system information block (System Information Block, SIB);

receiving second RACH information in the dedicated signaling;

a random access procedure is performed using the first RACH information and/or the second RACH information.

acquiring at least two groups of Random Access Channel (RACH) resources, wherein the at least two groups of RACH configuration parameters are configured by a system information block and/or a dedicated signaling;

and executing a random access procedure by using one set of RACH configuration parameters in the at least two sets of RACH configuration parameters when the trigger condition is met.

According to an aspect of the present application, there is provided a random access apparatus, the apparatus comprising:

A receiving module, configured to receive first RACH information in a system information block; and receiving second RACH information in the dedicated signaling;

and the random access module is used for executing a random access process by using the first RACH information and/or the second RACH information.

a receiving module, configured to obtain at least two sets of RACH configuration parameters, where the at least two sets of RACH configuration parameters are configured by a system information block and/or dedicated signaling;

and the random access module is used for executing a random access process by using one group of RACH configuration parameters in the at least two groups of RACH configuration parameters under the condition that the trigger condition is met.

According to one aspect of the present application, there is provided a terminal comprising: a processor; a transceiver coupled to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the random access method as described in the above aspect.

According to one aspect of the present application, there is provided a computer readable storage medium having stored therein executable instructions that are loaded and executed by a processor to implement a random access method as described in the above aspects.

According to an aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium, the computer instructions being read from the computer readable storage medium by a processor of a computer device, the computer instructions being executed by the processor such that the computer device performs the random access method of the above aspect.

According to an aspect of the present application, there is provided a chip comprising a programmable logic circuit or program for implementing the random access method as described in the above aspect.

The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects:

under the condition that the first RACH information in the SIB and the second RACH information in the special signaling exist at the same time, the UE selects the first RACH information and/or the second RACH information to perform the random access process, so that the UE can better utilize RACH resources suitable for the UE in different RACH information to perform the random access process, the time consumption of the random access process is reduced, or the success rate of the random access process is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a communication system provided in an exemplary embodiment of the present application;

fig. 2 is a schematic diagram of a four-step random access procedure provided in an exemplary embodiment of the present application;

fig. 3 is a schematic diagram of a two-step random access procedure provided in an exemplary embodiment of the present application;

fig. 4 is a flowchart of a random access method provided in an exemplary embodiment of the present application;

fig. 5 is a flowchart of a random access method provided in an exemplary embodiment of the present application;

fig. 6 is a flowchart of a random access method provided in an exemplary embodiment of the present application;

fig. 7 is a flowchart of a random access method provided in an exemplary embodiment of the present application;

fig. 8 is a flowchart of a random access method provided in an exemplary embodiment of the present application;

fig. 9 is a flowchart of a random access method provided in an exemplary embodiment of the present application;

FIG. 10 is a flow chart of a priority determination method or conflict resolution method provided by an exemplary embodiment of the present application;

FIG. 11 is a flowchart of a priority determination method or conflict resolution method provided by an exemplary embodiment of the present application;

FIG. 12 illustrates a flow chart of a data transmission method provided by an exemplary embodiment of the present application;

Fig. 13 is a block diagram of a random access device according to an exemplary embodiment of the present application;

fig. 14 is a block diagram of a priority determining device or a conflict resolution device or a data transmission device provided in an exemplary embodiment of the present application;

fig. 15 is a schematic structural diagram of a terminal according to an exemplary embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In the embodiment of the present application, the "predefining" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the specific implementation of the present application is not limited. Such as predefined may refer to what is defined in the protocol.

Fig. 1 shows a schematic diagram of a system architecture provided in an embodiment of the present application. The system architecture may include: a terminal 10 and a network device 20.

The number of terminals 10 is typically plural and one or more terminals 10 may be distributed within a cell managed by each network device 20. The terminal 10 may include various handheld devices, vehicle mount devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of User Equipment (UE), mobile Station (MS), and the like, having wireless communication capabilities. For convenience of description, in the embodiment of the present application, the above-mentioned devices are collectively referred to as a terminal.

Network device 20 is a means deployed in an access network to provide wireless communication functionality for terminal 10. The network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. The names of network device-capable devices may vary in systems employing different radio access technologies, for example in 5G NR systems, called gndeb or gNB. As communication technology evolves, the name "network device" may change. For convenience of description, in the embodiments of the present application, the above-mentioned devices for providing the wireless communication function for the terminal 10 are collectively referred to as a network device.

The "5G NR system" in the embodiments of the present disclosure may also be referred to as a 5G system or an NR system, but a person skilled in the art may understand the meaning thereof. The technical scheme described in the embodiment of the disclosure can be applied to a 5G NR system and also can be applied to a subsequent evolution system of the 5G NR system.

In NR, two random access modes are mainly supported, which are respectively a 4-step random access mode, as shown in fig. 2; and 2 steps of random access mode.

The random access procedure shown in fig. 2 is divided into 4 steps. The detailed steps are as follows:

1. the terminal sends Msg1 (Message 1 ) to the network device.

The terminal selects PRACH (Physical Random Access Channel ) resources and transmits the selected preamble on the selected PRACH. The PRACH resources and preambles may be specified by the network device if non-contention based random access. The network device may estimate uplink Timing based on the preamble, and a grant size required for the terminal to transmit Msg3 (Message 3 ).

2. The network device sends a RAR (Random Access Response ) to the terminal.

After the terminal transmits Msg1, a random access response time window is opened, and a PDCCH (Physical Downlink Control Channel ) scrambled by RA-RNTI (Random Access Radio Network Temporary Identifier, random access radio network temporary identity) is monitored within the random access response time window. The RA-RNTI is calculated as follows:

RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id；

I.e. the RA-RNTI relates to the PRACH time-frequency resources used by the UE to transmit Msg 1.

After the terminal successfully receives the PDCCH scrambled by the RA-RNTI, the terminal can obtain the PDSCH scheduled by the PDCCH, where the PDSCH includes an RAR (random access response), and the RAR specifically includes the following information:

the sub header (packet header) of the RAR includes BI for indicating a backoff time for retransmitting Msg 1;

RAPID in RAR: the network device responds to the received preamble index (preamble indication);

the payload of the RAR comprises TAG for adjusting the uplink timing;

UL grant (Uplink grant): uplink resource indication for scheduling Msg 3;

a Temporary C-RNTI (Temporary Cell Radio Network Temporary Identifier, temporary cell radio network Temporary identity): PDCCH (initial access) for scrambling Msg 4.

If the terminal receives the PDCCH scrambled by the RAR-RNTI (Random Access Response Radio Network Temporary Identifier ) and the RAR contains the preamble index sent by the terminal, the terminal considers that the random access response is successfully received.

For non-contention based random access, after the terminal successfully receives Msg2 (Message 2), the random access procedure ends. For contention-based random access, after the terminal successfully receives the Msg2, it also needs to continue transmitting Msg3 and receiving Msg4 (Message 4 ).

3. The terminal transmits Msg3 on the network device scheduling resource.

Msg3 is mainly used to inform the network device what event the RACH (Random Access Channel ) procedure is triggered by. For example, if the initial access random procedure is performed, the Msg3 will carry the UE identifier and establishment cause (establishment cause); in the case of RRC reestablishment, the UE identity in connected state and establishment cause are carried.

4. The network device sends Msg4 to the terminal.

Msg4 has two roles, one is for contention conflict resolution and the second is for the network device to transmit RRC configuration messages to the terminal. The contention resolution is achieved in two ways: one is PDCCH scheduling with C-RNTI scrambling by Msg4 if the UE carries a C-RNTI (Cell Radio Network Temporary Identifier, cell radio network temporary identity) in Msg3. Another is PDCCH scheduling, if the UE does not carry a C-RNTI in the Msg3, such as initial access, with TC-RNTI (Temporary Cell Radio Network Temporary Identifier, temporary cell radio network temporary identity) scrambling for Msg4, the resolution of the collision is that the UE receives PDSCH (Physical Downlink Shared Channel ) of Msg4 by matching CCCH SDU (common control channel service data unit) in PDSCH.

Compared with fig. 2, the two-step random access method can improve the time delay and reduce the signaling overhead. In the two-step random access mode, msgA is used for transmitting msg1+msg3 of the four-step random access mode, and msgB is used for transmitting msg2+msg4 of the four-step random access mode.

The RACH resources are not configured in a radio resource control release (rrrelease) message in the related art. However, in the embodiment of the present application, it is desirable to introduce the configuration of RACH resources in the rrCreatase message, such as introducing the configuration of RACH resources for network Slice (Slice). At this time, the UE has a problem of selecting RACH resources configured in SIB or RACH resources in dedicated (allocated) RRC. Thus, the following examples are provided:

fig. 4 shows a flowchart of a random access method according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method being performed by a terminal. The method comprises the following steps:

step 420: receiving first RACH information in a system information block;

the first RACH information is configured with first RACH resources. The first RACH information is broadcast by the access network device of the first cell or the first RACH information is broadcast by the access network device of the second cell. In the scenario that no cell handover is performed, the first cell is the camping cell of the terminal. In the scene of cell switching, the first cell is the residence cell of the terminal before switching, and the second cell is the residence cell of the terminal after switching. In the case of cell reselection, the first cell is the resident cell of the terminal before reselection, and the second cell is the resident cell of the terminal after reselection.

The first RACH information is configured with first RACH resources. The system information block is also called a system broadcast or broadcast.

Wherein the system information block is SIB1; or, the system information block is other SIBs except SIB 1. For example, the first RACH information is carried in SIB1 and other broadcast information is carried in other SIBs.

Optionally, the system information block includes: at least one of a valid range (or a usage range), a cell, an area, a PLMN, a registration area, and a tracking area corresponding to the first RACH information. The representation of the range information includes, but is not limited to: at least one of cell identity, frequency point identity, RAN announcement area (RAN notification area), RAN area code (RAN area code), tracking area code (Tracking area code), public land mobile network (Public Land Mobile Network, PLMN) identity.

Optionally, the system information block includes: at least one of slice information, time-frequency resources of RACH, random access preamble. The slice information includes: slice identification, correspondence of slices and first RACH resources, etc.

Optionally, the Slice identifier may be a Slice group identifier, a parameter corresponding to the Slice identifier or the Slice group identifier, a specific parameter (corresponding to Slice information), a specified parameter or a predetermined parameter, a Slice/Service Type (SST), a Slice index (index) or a Slice group index, an access class (access category), or the like.

Optionally, the slice information may also include (common) frequency point priority information for slices and/or non-slices.

Optionally, the slice information is information supported by the local area and/or the neighboring area.

Alternatively, for a slice indicated by a network broadcast or dedicated information, i.e. the supported slice information, the corresponding behavior may be at least one of the following: with a slice served by the UE, the UE may correspondingly initiate or complete registration, the UE may establish a corresponding protocol data unit (Protocol Data Unit, PDU) session, the UE may establish corresponding air interface resources, such as data radio bearers (Data Radio Bearer, DRBs), and the UE may correspondingly activate the user plane.

Optionally, for the slices not supported indicated by the network broadcast or the dedicated information, or the slices not indicated by the network broadcast or the dedicated information, the corresponding actions may be at least one of the following: the UE may initiate or complete registration but fail to register, the UE may not trigger or establish a corresponding PDU session, the UE may establish a corresponding PDU session but not support data transmission, the UE may not establish a corresponding air interface resource (e.g., DRB), the UE may establish a corresponding air interface resource (e.g., DRB) but not support data transmission, the UE may correspond to an active user plane but not support data transmission, and the UE may not correspond to an active user plane.

Optionally, the system information block further includes: priority parameters. The priority parameter includes at least one of back-off indication (Backoff Indicator, BI) information and power ramp up information. The BI information may be a BI adjustment factor and the power boost information may be a power boost step size (power ramping step). Optionally, the priority parameters include slice-specific, and/or non-slice-specific (common). Optionally, the priority parameters include slice-specific, and/or non-slice-specific (common).

Optionally, the first RACH information includes: and a first RACH configuration for configuring at least one RACH configuration parameter of RACH resources, RACH types, RACH priorities. RACH resources include: RACH time-frequency resource, random access opportunity, random access preamble. Such as a random access opportunity (RACH) and/or a random access preamble. For example, one RO contains 64 random access preambles, and at most 8 ROs can be simultaneously aligned in the frequency domain.

Optionally, the system information block further includes: and first indication information for indicating whether to use second RACH information to cover (override) the first RACH information.

In a first possible design, the first RACH configuration is configured to configure at least two sets of RACH configuration parameters, the first RACH information further comprising: a selection threshold for selecting at least two sets of RACH configuration parameters. The selection threshold comprises at least one of:

a first threshold for selecting between the common RACH and the slice-specific RACH;

for example, if the channel quality is higher than the first threshold, selecting a dedicated RACH resource for slicing; the channel quality is below a first threshold and the common RACH resource is selected.

A second threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

for example, if the channel quality is higher than the second threshold, selecting a slice-specific RACH resource of the 2-step RACH; and if the channel quality is lower than the second threshold, selecting RACH resources corresponding to the 2-step RACH or the 4-step RACH. Here, "2-step slice dedicated RACH" is an abbreviation of slice dedicated RACH resource of 2-step RACH.

A third threshold for selecting between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

for example, if the channel quality is higher than the third threshold, selecting a slice-specific RACH resource of the 2-step RACH; and if the channel quality is lower than a third threshold, selecting the special RACH resources for the 4-step RACH. Here, "4-step slice dedicated RACH" is an abbreviation of slice dedicated RACH resource of 4-step RACH.

A fourth threshold for selecting between the 2-step slice specific RACH and the 2-step RACH;

for example, if the channel quality is higher than the fourth threshold, selecting a slice-specific RACH resource of the 2-step RACH; and if the channel quality is lower than the fourth threshold, selecting RACH resources corresponding to the 2-step RACH.

A fifth threshold for selecting a threshold of a slice-specific RACH between two sets of RACH resources;

for example, if the channel quality is higher than the fifth threshold, selecting a slice-specific RACH resource; and if the channel quality is lower than a fifth threshold, selecting RACH resources corresponding to the 2-step RACH or the 4-step RACH.

A sixth threshold for selecting between the 4-step slice specific RACH and the 4-step RACH.

For example, if the channel quality is higher than the sixth threshold, selecting a dedicated RACH resource for slicing of the 4-step RACH; and if the channel quality is lower than a sixth threshold, selecting RACH resources corresponding to the 4-step RACH.

It should be noted that any two of the six thresholds may be the same or different.

In a second possible design, the first RACH configuration is configured to configure at least two sets of RACH configuration parameters, the first RACH information further comprising: a selection indication for selecting at least two sets of RACH configuration parameters. The selection indication comprises at least one of the following:

Second indication information for selecting a slice-specific RACH between a common RACH and the slice-specific RACH;

third indication information for indicating a selection of a 2-step slice-specific RACH or a slice-specific RACH between two sets of RACH resources;

fourth indication information for selecting a common RACH between the common RACH and a slice-specific RACH;

fifth indication information for indicating selection of a 2-step slice-dedicated RACH or a RACH other than a slice-dedicated RACH between two sets of RACH resources;

sixth indication information for indicating a threshold for selecting a 2-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

seventh indication information for indicating a threshold for selecting a 4-step slice-dedicated RACH between a 2-step slice-dedicated RACH and a 4-step slice-dedicated RACH;

eighth indication information for indicating a selection of a 4-step slice-dedicated RACH or a slice-dedicated RACH between two sets of RACH resources;

ninth indication information for indicating selection of a 2-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 2-step RACH;

tenth indication information for indicating selection of a 2-step RACH between the 2-step slice dedicated RACH and the 2-step RACH;

eleventh indication information for indicating selection of the 4-step slice-dedicated RACH between the 4-step slice-dedicated RACH and the 4-step RACH;

Twelfth indication information for indicating that a 4-step RACH is selected between the 4-step slice dedicated RACH and the 4-step RACH.

In a third possible design, the first RACH configuration is configured to configure at least two sets of RACH configuration parameters, the first RACH information further including: selection conditions for selecting at least two sets of RACH configuration parameters. The selection condition includes at least one of:

selecting a non-slice dedicated RACH in case of a non-slice or non-designated slice or a designated slice and network support slice mismatch or a required slice and network support slice mismatch;

a specified slice (or a particular slice) refers to one or more slices specified in the plurality of slices.

The required slice refers to a slice that the terminal desires to use, or a slice that the terminal desires to use. Illustratively, the required slice is not the slice that the terminal is using.

Selecting a slice-specific RACH in case of slice or designated slice and network support slice matching or required slice and network support slice matching;

selecting a slice-specific RACH in case of a slice of a specified type or a match of a slice of a specified type and a network support slice;

the designated type of slice (or a specific type of slice) refers to a slice of a certain type or types among a plurality of types of slices.

Selecting the common RACH in case of a non-designated type of slice or a designated type of slice and a network support slice mismatch or a required slice and a network support slice mismatch;

selecting a 2-step slice dedicated RACH in case of a specified type of slice or a specified type of slice and network support slice match or a required slice and network support slice match;

selecting a 4-step slice dedicated RACH in case of non-specified type slices or specified type slices and network support slices do not match or demand slices and network support slices do not match;

in the case of a specified type of slice or a specified type of slice and network support slice match or a required slice and network support slice match, selecting a 2-step RACH;

in the case of a non-specified type of slice or a specified type of slice and a network support slice not matching or a required slice and a network support slice not matching, selecting a 4-step RACH;

selecting a common RACH in case of RACH failure of the first type or mismatch of a designated type slice and a network support slice or mismatch of a required slice and a network support slice;

in case the RACH of the first type fails and the RACH of the second type is not configured, selecting the common RACH;

In case of a failure of the RACH of the first type and a configuration of the RACH of the second type, selecting a 4-step slice-specific RACH;

in the case where the terminal supports slicing, selecting a slice-specific RACH or a 2-step slice-specific RACH or a 4-step slice-specific RACH;

in case the terminal does not support slicing, selecting a non-slice dedicated RACH or a common RACH or a 2-step RACH or a 4-step RACH;

in the case where the slice used by the terminal is the same as the network support slice, selecting a slice-specific RACH or a 2-step slice-specific RACH or a 4-step slice-specific RACH;

in the case where the slice used by the terminal is different from the network support slice, selecting a non-slice dedicated RACH or a common RACH or a 2-step RACH or a 4-step RACH;

in the case of a slice not supported by the network, selecting a non-slice dedicated RACH or a common RACH or a 2-or 4-step RACH;

in case of network supported slices, selecting a slice-specific RACH or a 2-step slice-specific RACH or a 4-step slice-specific RACH;

slice information differs including: the supported slice identifiers are different, the corresponding relations between the slices and the RACH resources are different, the corresponding relations between the slices and the frequency points are different, the corresponding relations between the slices and the frequency point priorities are different, and at least one of RACH information is different.

Selecting a slice-specific RACH or a 2-step slice-specific RACH or a 4-step slice-specific RACH in case the communication protocol release supported by the terminal is higher than the predetermined release;

illustratively, the predetermined release is the R17 release of the third generation partnership project (Third Generation Partnership Project,3 GPP).

In case the version of the communication protocol supported by the terminal is below a predetermined version, selecting a non-slice dedicated RACH or a common RACH or a 2-step RACH or a 4-step RACH;

in the case where the random access procedure is a contention random access procedure, selecting a slice-specific RACH or a 2-step slice-specific RACH or a 4-step slice-specific RACH;

in the case where the random access procedure is a non-contention random access procedure, a non-slice dedicated RACH or a common RACH or a 2-step RACH or a 4-step RACH is selected.

In the case where the random access procedure is a contention random access procedure, selecting a slice-specific RACH or a 2-step common RACH;

in the case where the random access procedure is a non-contention random access procedure, a non-slice dedicated RACH or a common RACH or a 2-step RACH or a 4-step slice dedicated RACH is selected.

In the case where the random access procedure is a non-contention random access procedure, selecting a slice-specific RACH or a 2-step slice-specific RACH or a 4-step slice-specific RACH;

In the case where the random access procedure is a contention random access procedure, a non-slice dedicated RACH or a common RACH or a 2-step RACH or a 4-step RACH is selected.

It should be noted that, according to at least one parameter of the selection threshold, the selection indication and the selection condition, a set of RACH configuration parameters can be selected from at least two sets of RACH configuration parameters to perform the random access procedure. The RACH configuration parameters include: at least one configuration parameter of RACH time-frequency resource, RACH type, RACH priority, random access opportunity and random access preamble.

Step 440: receiving second RACH information in the dedicated signaling;

the second RACH information is configured with second RACH resources. The second RACH information is transmitted by the access network device of the first cell or the second RACH information is transmitted by the access network device of the second cell. In the scenario that no cell handover is performed, the first cell is the camping cell of the terminal. In the scene of cell switching, the first cell is the residence cell of the terminal before switching, and the second cell is the residence cell of the terminal after switching.

Wherein the dedicated signaling includes: dedicated radio resource control (Radio Resource Control, RRC) messages;

wherein the dedicated RRC message includes: RRC reconfiguration (RRC Reconfiguration) message, or RRC Release (Release) message.

Optionally, the dedicated signaling includes: the effective duration or the use duration corresponding to the second RACH information. The effective duration includes: starting from the first time unit or starting from the first time unit to the second time unit. For another example, the first timer is valid before it times out, e.g., the first timer is a new timer or the first timer is a T320 timer, etc.

Optionally, the dedicated signaling includes: at least one of a valid range (or a usage range), a cell, an area, a PLMN, a registration area, and a tracking area corresponding to the second RACH information. The representation of the range information includes, but is not limited to: at least one of cell identity, frequency point identity, RAN announcement area (RAN notification area), RAN area code (RAN area code), tracking area code (Tracking area code), public land mobile network (Public Land Mobile Network, PLMN) identity.

Optionally, the dedicated signaling includes: at least one of slice information, time-frequency resources of RACH, random access preamble. The slice information includes: slice identification, correspondence of slices and second RACH resources, etc.

Alternatively, the Slice identifier may be a Slice group identifier, a parameter corresponding to the Slice identifier or the Slice group identifier, a specific parameter (corresponding to Slice information), a specified parameter or a predetermined parameter, a Slice/Service type (SST), a Slice index (index) or a Slice group index, an access class (access category), or the like.

Optionally, for a slice indicated by a network broadcast or dedicated information, i.e. the supported slice information, the corresponding behavior may be at least one of: with a slice served by the UE, the UE may correspondingly initiate or complete registration, the UE may establish a corresponding protocol data unit (Protocol Data Unit, PDU) session, the UE may establish corresponding air interface resources, such as data radio bearers (Data Radio Bearer, DRBs), and the UE may correspondingly activate the user plane.

Optionally, the dedicated signaling further comprises: priority parameters. The priority parameter includes at least one of BI information and power boost information. The BI information may be a BI adjustment factor and the power boost information may be a power boost step size. Optionally, the priority parameters include slice-specific, and/or non-slice-specific (common).

Optionally, the second RACH information includes: and a second RACH configuration for configuring at least one RACH configuration parameter of RACH resources, RACH type, RACH priority. RACH resources include: RACH time-frequency resource, random access opportunity, random access preamble.

In a first possible design, the second RACH configuration is used to configure at least two sets of RACH configuration parameters, the second RACH information further including at least one of:

a selection threshold for selecting at least two sets of RACH configuration parameters. A specific example of the selection threshold is seen in step 420.

In a second possible design, the second RACH configuration includes at least two sets, and the second RACH information further includes:

a selection indication for selecting at least two sets of RACH configuration parameters. A specific example of a selection indication is seen in step 420.

In a third possible design, the second RACH configuration includes at least two sets, and the second RACH information further includes:

Selection conditions for selecting at least two sets of RACH configuration parameters. Specific examples of selection conditions are seen in step 420.

Optionally, the dedicated signaling further comprises: and first indication information for indicating whether the first RACH information is covered with the second RACH information.

It should be noted that, according to at least one parameter of the selection threshold, the selection indication and the selection condition, a set of RACH configuration parameters can be selected from at least two sets of RACH configuration parameters to perform the random access procedure. The RACH configuration parameters include: at least one configuration parameter of RACH time-frequency resources, random access opportunity, random access preamble, RACH priority, and RACH type.

The execution sequence of step 420 and step 440 is not limited in this embodiment, and step 420 may be executed before step 440, may be executed after step 440, may be executed simultaneously with step 440, and is not limited in this regard.

Step 460: a random access procedure is performed using the first RACH information and/or the second RACH information.

The terminal selects or uses the first RACH information and/or the second RACH information by itself to perform a random access procedure. Or, the terminal selects or uses the first RACH information and/or the second RACH information according to an indication of the network to perform a random access procedure.

This step includes, but is not limited to, at least one of the following implementations:

the terminal performs a random access procedure using the first RACH information.

Illustratively, the terminal ignores the second RACH information in the dedicated signaling and/or considers the priority of the first RACH information in the SIB to be higher and/or applies only the second RACH information in the dedicated signaling. For example, when the dedicated signaling is an RRC reconfiguration message with respect to synchronization, the terminal considers that the second RACH information in the dedicated signaling has a high priority. For example, when the dedicated signaling is an RRC release message, the terminal considers that the priority of the first RACH information is high.

The terminal performs a random access procedure using the second RACH information.

Illustratively, the terminal ignores the first RACH information in the SIB and/or considers the second RACH information in the dedicated signaling to be higher in priority and/or applies only the second RACH information in the dedicated signaling. For example, when the dedicated signaling is an RRC reconfiguration message with respect to synchronization, the terminal considers that the second RACH information in the dedicated signaling has a high priority.

The terminal selects or uses the first RACH information to perform a random access procedure if the first condition is satisfied.

The terminal selects or uses the second RACH information to perform a random access procedure if the second condition is satisfied.

The terminal selects or uses the first RACH information and the second RACH information to perform a random access procedure if the third condition is satisfied.

Illustratively, the random access procedure is performed using a selection threshold or selection indication or selection condition configured by the first RACH information and RACH resources configured by the second RACH information.

The terminal uses one of the at least two sets of RACH configuration parameters depending on the slice information or support for network slices.

Wherein, at least two groups of RACH configuration parameters are configured by the first RACH information; or, at least two groups of RACH configuration parameters are configured by the second RACH information; or, the at least two sets of RACH configuration parameters are configured with first RACH information and second RACH information, i.e., the first RACH information configures a portion of the at least two sets of RACH configuration parameters and the second RACH information configures the remaining portion of the at least two sets of RACH configuration parameters.

In summary, in the method provided in this embodiment, when the first RACH information in the SIB and the second RACH information in the dedicated signaling exist at the same time, the terminal selects the first RACH information and/or the second RACH information to perform the random access procedure, so that the terminal can better utilize RACH resources suitable for itself in different RACH information to perform the random access procedure, thereby reducing time consumption of the random access procedure or improving success rate of the random access procedure.

For an embodiment in which the random access procedure is performed using the first RACH information:

fig. 5 shows a flowchart of a random access method according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method being performed by a terminal. The method comprises the following steps:

step 420: receiving first RACH information in a system information block;

the first RACH information is configured with first RACH resources. As described in step 420 in the embodiment of fig. 4, a detailed description is omitted.

Step 440: receiving second RACH information in the dedicated signaling;

the second RACH information is configured with second RACH resources. As described in step 440 in the embodiment of fig. 4, a detailed description is omitted.

Step 462: performing a random access procedure using the first RACH information if the first condition is satisfied;

mode 1. In a case where the priority of the first RACH information is higher than the priority of the second RACH information, performing a random access procedure using the first RACH information;

in the case where the priority of the first RACH information is higher than the priority of the second RACH information, the first RACH information is preferentially used and/or the random access procedure is performed by applying the first RACH information.

Mode 2. Performing a random access procedure using the first RACH information in case of not belonging to the use time and/or the effective range of the second RACH information;

in the case that the usage time and/or the valid range of the second RACH information do not belong, the first RACH information is preferentially used and/or the first RACH information is applied to perform a random access procedure.

For example, in a first period of time, performing a random access procedure using the first RACH information; during a second period (valid time of the second RACH information), a random access procedure is performed using the second RACH information.

Mode 3. When the first indication information indicates that the first RACH information is preferentially used, a random access procedure is performed using the first RACH information.

For example, in the case where the first indication information indicates that the first RACH information is always preferentially used, the random access procedure is performed using the first RACH information.

Mode 4. When the slice information in the first RACH information or the second RACH information is different, performing a random access procedure using the first RACH information;

a random access process is executed by using the first RACH information according to the supporting condition of the terminal equipment or the access network equipment to the network slice;

For example, the SIB of the first cell or the dedicated signaling carries RACH parameters other than the conventional RACH parameters, but the second cell does not carry RACH parameters other than the conventional RACH parameters, and the random access procedure is performed according to the first RACH information in the SIB regardless of the first cell or the second cell.

Mode 6. Random access procedure is performed using the first RACH information without being within coverage or service range of the cell or base station transmitting the second RACH information.

For example, the terminal performs a random access procedure using the first RACH information, which is located outside the coverage or service area of a cell or a base station transmitting the second RACH information, in a mobile procedure.

In summary, in the method provided in this embodiment, when the first RACH information in the SIB and the second RACH information in the dedicated signaling exist at the same time, the terminal uses the first RACH information to perform the random access procedure according to the currently satisfied trigger condition, so that the terminal can better utilize RACH resources suitable for itself in different RACH information to perform the random access procedure, thereby reducing the time consumption of the random access procedure or improving the success rate of the random access procedure.

For embodiments that perform a random access procedure using the second RACH information:

Fig. 6 shows a flowchart of a random access method according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method being performed by a terminal. The method comprises the following steps:

step 420: receiving first RACH information in a system information block;

Step 440: receiving second RACH information in the dedicated signaling;

Step 464: in case that the second condition is satisfied, a random access procedure is performed using the second RACH information.

mode 1. When the priority of the second RACH information is higher than the priority of the first RACH information, a random access procedure is performed using the second RACH information.

Mode 2. Performing a random access procedure using the second RACH information in case of belonging to the valid time of the second RACH information or belonging to the valid range of the second RACH or belonging to the valid time and the valid range of the second RACH information;

mode 3. In case the first indication information is used to indicate that the second RACH information is preferentially used, performing a random access procedure using the second RACH information;

Mode 4. Performing a random access procedure using the second RACH information in case that slice information in the first RACH information or the second RACH information is different and/or belongs to a valid time and/or a valid range of the second RACH information;

and 5, executing a random access process by using the second RACH information according to the supporting condition of the terminal equipment or the access network equipment to the network slice.

Illustratively, the enhanced base station B transmitting the SIB is a legacy base station but transmitting the dedicated signaling, and performs a random access procedure according to the second RACH information configured by the dedicated signaling.

For example, the RRC release message carries second RACH information, and the random access procedure is performed according to the second RACH information.

For another example, the SIB of the first cell or the dedicated signaling carries RACH parameters other than the conventional RACH parameters, but the second cell does not carry RACH parameters other than the conventional RACH parameters, and the random access procedure is performed according to the second RACH information in the dedicated signaling, regardless of the first cell or the second cell.

Mode 6. Random access procedure is performed using the second RACH information within the coverage area or service area of the cell or base station transmitting the second RACH information.

For example, the cell transmitting the second RACH information is a resident cell of the terminal, the terminal is located within a coverage area of the cell, and a random access procedure is performed using the second RACH information.

In summary, in the method provided in this embodiment, when the first RACH information in the SIB and the second RACH information in the dedicated signaling exist at the same time, the terminal uses the second RACH information to perform the random access procedure according to the currently satisfied trigger condition, so that the terminal can better utilize RACH resources suitable for itself in different RACH information to perform the random access procedure, thereby reducing the time consumption of the random access procedure or improving the success rate of the random access procedure.

For embodiments that perform a random access procedure using the first RACH information and the second RACH information:

fig. 7 shows a flowchart of a random access method according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method being performed by a terminal. The method comprises the following steps:

step 420: receiving first RACH information in a system information block;

Step 440: receiving second RACH information in the dedicated signaling;

Step 466: in the case that the third condition is satisfied, a random access procedure is performed using the first RACH information and the second RACH information.

Optionally, in case the first RACH information comprises at least two sets of RACH configuration parameters and the second RACH information comprises selection information of RACH configuration parameters, the random access procedure is performed using the at least two sets of RACH configuration parameters and the selection information of RACH configuration parameters.

Optionally, in case the second RACH information comprises at least two sets of RACH configuration parameters and the first RACH information comprises selection information of RACH configuration parameters, the random access procedure is performed using the at least two sets of RACH configuration parameters and the selection information of RACH configuration parameters.

Wherein the selection information includes: at least one of a selection threshold, a selection indication, and a selection condition.

The selection information is used for selecting a target configuration parameter in at least two groups of RACH configuration parameters. Target configuration parameters include, but are not limited to: at least one of RACH time-frequency resource, random access opportunity, random access preamble, RACH type, RACH priority.

In summary, in the method provided in this embodiment, when the first RACH information in the SIB and the second RACH information in the dedicated signaling exist at the same time, the terminal uses the first RACH information and the second RACH information to perform the random access procedure according to the currently satisfied trigger condition, so that the terminal can better utilize RACH resources suitable for itself in different RACH information to perform the random access procedure, thereby reducing the time consumption of the random access procedure or improving the success rate of the random access procedure.

For embodiments in which at least two sets of RACH configurations (or types) are configured simultaneously, the terminal performs a random access procedure using one of the at least two sets of RACH configurations:

fig. 8 shows a flowchart of a random access method according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method being performed by a terminal. The method comprises the following steps:

step 420: receiving first RACH information in a SIB;

the first RACH information is configured with a first RACH configuration. As described in step 420 in the embodiment of fig. 4, a detailed description is omitted.

Step 440: receiving second RACH information in the dedicated signaling;

the second RACH information is configured with a second RACH configuration. As described in step 440 in the embodiment of fig. 4, a detailed description is omitted.

Step 468: in case the trigger condition is met, performing a random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters.

At least two sets of RACH configuration parameters, which may also be referred to as: at least two sets of RACH configurations, or at least two sets of RACH types. Optionally, at least two sets of RACH configuration parameters are configured with the first RACH information; or, at least two sets of RACH configuration parameters are configured with the second RACH information; or, at least two sets of RACH configuration parameters are configured with the first RACH information and the second RACH information.

The at least two sets of RACH configuration parameters include at least two of:

common RACH;

slice-specific RACH;

non-slice specific RACH;

2 step slice specific RACH;

4 step slice specific RACH;

step 2 RACH;

4 steps RACH.

Random access preamble corresponding to RACH;

time-frequency resources or ROs corresponding to RACH;

priority parameters corresponding to RACH.

Optionally, the slice-specific RACH includes: at least one of a 2-step slice-specific RACH and a 4-step slice-specific RACH. Optionally, the non-slice specific RACH includes: at least one of the 2-step RACH and the 4-step RACH.

mode 1. At least two sets of RACH configuration parameters include a slice-specific RACH and a common RACH;

the slice-specific RACH is RACH resource specific to a network slice. For example, RACH resources dedicated to all network slices, a slice-dedicated RACH dedicated to a 2-step random access procedure (abbreviated as 2-step slice-dedicated RACH), and a slice-dedicated RACH dedicated to a 4-step random access procedure (abbreviated as 4-step slice-dedicated RACH).

The common RACH refers to non-dedicated RACH resources.

In case that the fourth condition is satisfied, the terminal performs a random access procedure using the slice-dedicated RACH; or, in case that the fifth condition is satisfied, the terminal performs a random access procedure using the common RACH.

Optionally, the fourth condition includes at least one of:

terminal support slice;

terminal use designated slice;

terminal uses slices of the specified type;

the slice used by the terminal is the same as the network support slice;

the required slice of the terminal is the same as the network support slice;

the communication protocol version supported by the terminal is higher than or equal to the predetermined version;

channel quality is above a first threshold, which is a threshold for selecting between the common RACH and the slice-specific RACH;

channel quality is above a second threshold, which is a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

receiving second indication information for indicating selection of a slice-specific RACH between the common RACH and the slice-specific RACH;

receiving third indication information indicating a selection of a 2-step slice-specific RACH or a slice-specific RACH between two sets of RACH resources;

the random access procedure is a contention random access procedure;

the channel quality is above a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources.

Optionally, the fifth condition includes at least one of:

Terminal does not support slicing;

terminal not using the designated slice;

terminal does not use slices of the specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is lower than the predetermined version;

the channel quality is below a first threshold, which is a threshold for selecting between the common RACH and the slice-specific RACN;

the channel quality is below a second threshold, which is a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

receiving fourth indication information for indicating selection of the common RACH between the common RACH and the slice-dedicated RACH;

receiving fifth indication information indicating that a 2-step slice-specific RACH or a RACH other than a slice-specific RACH is selected between two sets of RACH resources;

random access failure using a slice-specific RACH;

random access failure using 2-step slice-dedicated RACH, and 4-step slice-dedicated RACH is not configured;

the random access procedure is a non-contention random access procedure;

the channel quality is below a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources.

For example, in the case where the second RACH information is configured with a slice-dedicated RACH and the first RACH information is configured with a common RACH, the terminal performs a random access procedure using the slice-dedicated RACH. For example, the terminal supports slice 1, the second RACH information is configured with RACH corresponding to slice 1, the first RACH information is configured with common RACH, and the terminal selects RACH configured with the second RACH information.

For example, in the case where the first RACH information is configured with a slice-dedicated RACH and the second RACH information is configured with a common RACH, the terminal performs a random access procedure using the slice-dedicated RACH.

For example, in the case where the second RACH information is configured with the slice-dedicated RACH and the first RACH information is not configured with the slice-dedicated RACH, the terminal performs a random access procedure using the slice-dedicated RACH. For example, the terminal supports slice 1, the second RACH information does not configure RACH corresponding to slice or slice 1, the first RACH information configures RACH corresponding to slice information, and the terminal selects RACH configured in the first RACH information.

For example, in the case where the first RACH information is configured with a slice-dedicated RACH and the second RACH information is not configured with a slice-dedicated RACH, the terminal performs a random access procedure using the slice-dedicated RACH. For example, the terminal supports slice 1, the first RACH information does not configure RACH corresponding to slice or slice 1, the second RACH information configures RACH corresponding to slice information, and the terminal selects RACH configured in the second RACH information.

For example, in the case where the second RACH information is configured with a slice-dedicated RACH and belongs to the valid time and/or valid range of the second RACH information, the terminal performs a random access procedure using the slice-dedicated RACH. For example, the terminal supports slice 1, the second RACH information is configured with the RACH corresponding to slice 1, the second RACH information satisfies the effective duration and/or the effective area, and the terminal selects the RACH indicated in the dedicated information.

Mode 2. At least two sets of RACH configuration parameters include a 2-step slice specific RACH and a 4-step slice specific RACH;

in case that the sixth condition is satisfied, the terminal performs a random access procedure using the 2-step slice-dedicated RACH; or, in case that the seventh condition is satisfied, the terminal performs a random access procedure using the 4-step slice dedicated RACH.

Optionally, the sixth condition includes at least one of:

terminal uses slices of the specified type;

the slice used by the terminal is the same as the network support slice;

the required slice of the terminal is the same as the network support slice;

The channel quality is above a third threshold, which is a threshold for selecting between a 2-step slice specific RACH and a 4-step slice specific RACH;

receiving sixth indication information for indicating selection of the 2-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

the random access procedure is a contention random access procedure.

Optionally, the seventh condition includes at least one of:

terminal does not use slices of the specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the channel quality is below a third threshold, the second threshold being a threshold for selecting between a 2-step slice specific RACH and a 4-step slice specific RACH;

receiving seventh indication information for indicating selection of a 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

Random access failure using 2-step slice-specific RACH;

receiving eighth indication information for indicating a selection of a 4-step slice-dedicated RACH or a slice-dedicated RACH between two sets of RACH resources;

the random access procedure is a non-contention random access procedure.

Mode 3. At least two sets of RACH configuration parameters including a 2-step RACH and a 2-step slice dedicated RACH;

in case that the eighth condition is satisfied, the terminal performs a random access procedure using the 2-step slice-dedicated RACH; or, in case that the ninth condition is satisfied, the terminal performs a random access procedure using the 2-step RACH.

Optionally, the eighth condition includes at least one of:

terminal uses slices of the specified type;

the slice used by the terminal is the same as the network support slice;

the required slice of the terminal is the same as the network support slice;

channel quality is above a fourth threshold, which is a threshold for selecting between 2-step slice-specific RACH and 2-step RACH;

the channel quality is above a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving ninth indication information for indicating selection of the 2-step slice dedicated RACH between the 2-step slice dedicated RACH and the 2-step RACH;

the random access procedure is a contention random access procedure.

Optionally, the ninth condition includes at least one of:

terminal does not use slices of the specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the channel quality is below a third threshold, which is a threshold for selecting between 2-step slice-specific RACH and 2-step RACH;

receiving tenth indication information for indicating selection of a 2-step RACH between the 2-step slice dedicated RACH and the 2-step RACH;

random access failure using 2-step slice-specific RACH;

receiving fifth indication information for indicating a selection of a 2-step slice-specific RACH or a RACH other than a slice-specific RACH between two sets of RACH resources;

The random access procedure is a non-contention random access procedure.

Mode 4. At least two sets of RACH configuration parameters including a 4-step RACH and a 4-step slice dedicated RACH;

in case that the tenth condition is satisfied, performing a random access procedure using the 4-step slice-dedicated RACH; or, in case the eleventh condition is satisfied, performing a random access procedure using the 4-step RACH.

Optionally, the tenth condition includes at least one of:

terminal uses slices of the specified type;

the slice used by the terminal is the same as the network support slice;

the required slice of the terminal is the same as the network support slice;

the channel quality is above a sixth threshold, which is a threshold for selecting between 4-step slice-specific RACH and 4-step RACH;

receiving eleventh indication information for indicating a selection of the 4-step slice-dedicated RACH between the 4-step slice-dedicated RACH and the 4-step RACH;

The random access procedure is a contention random access procedure.

Optionally, the eleventh condition includes at least one of:

terminal does not use slices of the specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the channel quality is below a sixth threshold, which is a threshold for selecting between the 4-step slice-specific RACH and the 4-step RACH;

receiving twelfth indication information for indicating a selection of a 4-step RACH between the 4-step slice dedicated RACH and the 4-step RACH;

random access failure using 4-step slice-specific RACH;

the channel quality is below a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

random access failure using 2-step slice-specific RACH;

The random access procedure is a non-contention random access procedure.

Note that, the modes in this embodiment can be freely combined. Illustratively, any combination of two ways is performed, such as a combination of ways 1 and 2, a combination of ways 1 and 3, a combination of ways 1 and 4, and so on; illustratively, any three combinations are contemplated, such as mode 1, mode 2, and mode 3 combinations, mode 1, mode 3, and mode 4 combinations; schematically, all four modes are combined.

For example, at least two sets of RACH configurations include: the common RACH, the 2-step slice dedicated RACH, and the 4-step slice dedicated RACH are combined with the above-described modes 1 and 2. For another example, the at least two sets of RACH configurations include: the 2-step RACH, the 2-step dedicated RACH for slicing, and the 4-step dedicated RACH for slicing are combined in the above-described modes 2 and 3, which are easily understood by those skilled in the art according to the above disclosure, and are not described in detail.

In summary, in the method provided in this embodiment, when the first RACH information in the SIB and the second RACH information in the dedicated signaling exist at the same time, the terminal performs the random access procedure by using one set of RACH configuration parameters of at least two sets of RACH configuration parameters according to the slice information or support for the slice, so that the terminal can better utilize RACH resources suitable for itself in different RACH information to perform the random access procedure, thereby reducing the time consumption of the random access procedure or improving the success rate of the random access procedure.

Fig. 9 shows a flowchart of a random access method according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method being performed by a terminal. The method comprises the following steps:

step 430: acquiring at least two groups of RACH configuration parameters, wherein the at least two groups of RACH configuration parameters are configured by a system information block and/or a special signaling;

the at least two sets of RACH configuration parameters include at least two of:

common RACH;

slice-specific RACH;

non-slice specific RACH;

2 step slice specific RACH;

4 step slice specific RACH;

step 2 RACH;

4 steps RACH;

preamble corresponding to RACH;

time-frequency resources or ROs corresponding to RACH;

RACH corresponds to a priority parameter.

Optionally, the slice-specific RACH includes: at least one of a 2-step slice-specific RACH and a 4-step slice-specific RACH. Optionally, the non-slice specific RACH includes: 2-step RACH and 4-step RACH.

The terminal receives a SIB in which at least two sets of RACH configuration parameters are configured.

Or, the terminal receives the proprietary signaling, and at least two groups of RACH configuration parameters are configured in the proprietary signaling.

Or the terminal receives SIB and proprietary signaling, wherein a part of RACH resources in at least two groups of RACH configuration parameters are configured in the SIB, and the rest of RACH resources in at least two groups of RACH configuration parameters are configured in the proprietary signaling.

Wherein the SIB and the proprietary signaling are transmitted by the same cell or base station, or the SIB and the proprietary signaling are transmitted by different cells or base stations.

Step 468: in case the trigger condition is met, a random access procedure is performed using one of the at least two sets of RACH configurations.

This step may be described with reference to step 468 shown in fig. 8, and will not be described again.

In summary, in the method provided in this embodiment, under the condition that at least two sets of RACH configuration parameters exist at the same time, the terminal performs the random access procedure by using one set of RACH configuration parameters in the at least two sets of RACH configuration parameters according to slice information or support of slices, so that the terminal can better utilize RACH resources suitable for itself to perform the random access procedure, thereby reducing time consumption of the random access procedure or improving success rate of the random access procedure.

In alternative embodiments based on the above described fig. 4 or fig. 5 or fig. 6 or fig. 7 or fig. 8 or fig. 9, the random access behaviour of the terminal in different cells is the same or different. Specifically, the random access procedure is performed in different cells using the same behaviour, which comprises a behaviour using the first RACH information and/or the second RACH information; or, performing a random access procedure using different actions in different cells, the actions including an action of using the first RACH information and/or the second RACH information.

For example, the terminal performs a random access procedure in the second cell when moving within range of the second cell or when the terminal is handed over/redirected/cell selected/cell reselected to the second cell.

Illustratively, the terminal performs a random access procedure in the second cell using the same behavior as the first cell; or, the terminal performs a random access procedure in the second cell using a different behavior from the first cell. The actions in the random access process comprise: behavior of using the first RACH information and/or the second RACH information.

For example, in the first cell range, the terminal performs a related action according to the second RACH information. When the terminal moves to the range of the second cell, the terminal performs the related actions according to the first RACH information.

For example, in the second cell range, the terminal ignores the second RACH information in the dedicated signaling and/or considers the first RACH information in the SIB to be of a higher priority. For example, when the dedicated signaling is an RRC release message, the terminal considers that the information in the dedicated signaling has a high priority.

For example, the terminal ignores the first RACH information in the SIB, and/or considers the second RACH information in the dedicated signaling to be of a higher priority, and/or applies the second RACH information in the dedicated signaling, and/or applies other RACH indications (e.g., selection threshold, selection indication, selection condition, etc.) in the SIB.

If the valid time and/or valid range condition of the second RACH information is not satisfied, the terminal ignores the second RACH information in the dedicated signaling (or deletes the second RACH information in the dedicated signaling), considers that the priority of the first RACH information in the SIB is high, and/or applies the first RACH information in the SIB.

If the valid time and/or valid range condition of the second RACH information is satisfied, the UE considers that the second RACH information in the dedicated signaling is high in priority, and/or applies the second RACH information in the dedicated signaling.

For example, if the network indicates that the terminal uses the SIB preferentially, the terminal selects the first RACH information in the SIB and performs a random access procedure.

For example, the terminal reads the first RACH information in the SIB of the second cell, and performs a random access procedure in the second cell according to the first RACH information. The terminal can read the two RACH information first and then judge whether to use the first RACH information or the second RACH information; the terminal can also read the first RACH information again under the condition that the judging result is that the second RACH information is invalid; the terminal may also read when the first RACH information needs to be used.

For example, the terminal performs a random access procedure according to the second RACH information of the dedicated RRC of the first cell in the first time; and the terminal executes a random access process according to the first RACH information of the SIB of the second cell in the second time.

It should be noted that, the above method embodiments may be split or combined into other embodiments according to the understanding of those skilled in the art. This application is not repeated here.

Fig. 10 shows a flowchart of a priority determination method or a conflict resolution method provided in an exemplary embodiment of the present application. The method may be performed by a terminal. The method comprises the following steps:

step 520: if the priorities based on the logical channels are Configured, when a Dynamic Grant (DG) and at least one Configured Grant (CG) collide, and the priorities of the resources are the same or the priorities of the logical channels with the highest logical channel priority in the resources are the same, the Dynamic Grant is prioritized or considered as the priority Grant.

Or if the priorities based on the logical channels are configured, when there is a conflict between the dynamic grant and at least one configuration grant, and the priorities of the resources are the same or the priorities of the logical channels with the highest logical channel priority in the resources are the same, the priority of which grant is dependent on the UE implementation.

The relevant communication protocols are expressed as:

If the MAC entity is configured with lch-basedPrioritization and if there is overlapping PUSCH duration of dynamic grant and at least two configured uplink grants whose priorities are equal,the dynamic grant is the prioritized uplink grant.

optionally, the base station configures configuration information based on the priority of the logical channel to the terminal. For the same terminal, the base station may also schedule dynamic grants and configure grants simultaneously. When the dynamic grant and at least one configuration grant conflict, and the priority of the resources of the dynamic grant and the configuration grant with the conflict is the same, or the priority of the logic channel with the highest logic priority in the resources of the dynamic grant and the configuration grant with the conflict is the same, the terminal determines that one of the dynamic grant and the configuration grant with the conflict is the priority grant according to a first strategy or a first condition.

The first policy or first condition includes at least one of:

when the dynamic grant and at least one configuration grant conflict, and the priority of the resources of the dynamic grant and the configuration grant which conflict is the same, or the priority of the logic channel with the highest logic priority in the resources of the dynamic grant and the configuration grant which conflict is the same, the dynamic grant is prioritized or considered to be the priority grant.

If the priority based on the logic channel is configured, when the dynamic grant and at least one configuration grant conflict, and the resources of the dynamic grant with the conflict are the same as those of the configuration grant, or the priority of the logic channel with the highest logic priority in the resources of the dynamic grant with the conflict and the configuration grant is the same, the dynamic grant is prioritized or considered to be the priority grant.

When there is a conflict between the dynamic grant and at least one configuration grant, and the highest priority of the highest logic in the resource priorities of the dynamic grant and the configuration grant that are in conflict is the same, one of the grants is prioritized or the dynamic grant is considered to be prioritized or the configuration grant is prioritized depending on the UE implementation.

If the priority based on the logic channel is configured, when the dynamic grant and at least one configuration grant conflict, and the resources of the dynamic grant and the configuration grant which conflict are the same, or the priority of the logic channel with the highest logic priority in the resources of the dynamic grant and the configuration grant which conflict is the same, one of the grants is prioritized, or the dynamic grant is considered to be prioritized, or the configuration grant is prioritized, depending on the UE implementation.

When there is a conflict between the dynamic grant and at least one configuration grant, and the resources of the conflicting dynamic grant and configuration grant are the same, or the priority of the logic channel with the highest logic priority in the resources of the conflicting dynamic grant and configuration grant is the same, the UE prioritizes the dynamic grant, or considers the dynamic grant as the priority grant, or prioritizes the configuration grant as the priority grant based on the indication of the base station or the configuration of the base station. Wherein the configuration of the base station includes at least one of a selection condition and a selection threshold for preferentially selecting dynamic grants or configuring grants.

Fig. 11 shows a flowchart of a priority determination method or a conflict resolution method provided in an exemplary embodiment of the present application. The method may be performed by a terminal. The method comprises the following steps:

Step 620: if there are multiple resource collisions, such as multiple physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), PUSCH, or uplink scheduling (UL-grant) collisions, if at least some of the resources have no logical channels to be transmitted multiplexed or may be multiplexed on the resources, then the priority of the resources is the same and/or the priority of the resources is lower than the priority of the logical channels to be transmitted or may be multiplexed with other resources or the priority of the scheduling application (Scheduling Request, SR), and/or the priority of the resources is the lowest.

Alternatively, if a priority based on logical channels is configured, and if there are multiple resource collisions, such as multiple PUSCH or UL-grant collisions, if at least some of the resources have no logical channels to be transmitted multiplexed or can be multiplexed on the resources, then the priority of the resources is the same, and/or the priority of the resources is lower than the priority of the logical channels to be transmitted or can be multiplexed with other resources or the priority of SRs, and/or the priority of the resources is the lowest.

Optionally, if there are multiple resource (or uplink resource) conflicts, the terminal determines the priority between the first type of resources, or the priority between the first type of resources and the second type of resources, or the priority of the first type of resources according to the second policy or the second condition.

Wherein the first type of resource is a resource on which no logical channel to be transmitted is multiplexed among the plurality of resources where collision occurs. Alternatively, the first type of resource is a resource on which no logical channel to be transmitted can (or can) be multiplexed among the plurality of resources on which collision occurs.

Wherein the second type of resource is a resource on which a logical channel to be transmitted exists among a plurality of resources where collision occurs, which is multiplexed. Alternatively, the second type of resource is a resource on which a logical channel to be transmitted exists among a plurality of resources where collision occurs, and can be (or can be) multiplexed. Alternatively, the second type resource is an SR, or a PUCCH resource corresponding to an SR.

The second policy or second condition includes at least one of:

if there are multiple resource conflicts, the multiple resources include at least two first type resources, and the terminal determines that the priorities of the at least two first type resources are the same.

If there are multiple resource conflicts, the multiple resources include a first type resource and a second type resource, and the terminal determines that the priority of the first type resource is lower than that of the second type resource.

If there are multiple resource conflicts, the multiple resources include a first type resource and a second type resource, and the terminal determines that the priority of the first type resource is the lowest.

The resources in the plurality of resources may be PUSCH resources and/or resources indicated by uplink scheduling and/or PUCCH resources.

Optionally, the priority is the priority of the resource, or may be the priority of the logic channel with the highest priority in the resource.

Fig. 12 shows a flowchart of a data transmission method according to an exemplary embodiment of the present application. The method may be performed by a terminal. The method comprises the following steps:

step 720: in case of configuration with a configured grant weight transmission timer (cg-retransmission timer) or in case of unlicensed band access/operation, the prioritized transmission is determined according to a third policy or a third condition.

The method comprises at least one of the following three modes:

in one mode, in case of configuring cg-retransmission timer or unlicensed band access/operation, UE prioritizes transmission of uplink resources with low priority, or prioritizes transmission of hybrid automatic retransmission request (Hybrid Automatic Repeat Request, HARQ) process where MAC PDU is located, which is not completely transmitted, or prioritizes transmission of resources where MAC PDU is located, which is not completely transmitted, compared with new transmission. Or vice versa, the UE prioritizes the new transmission. Optionally, between the transmission and other retransmissions, which one of the priorities is prioritized depends on the UE implementation, or one of the priorities is predefined, or determined based on the logical channel priority (e.g., the priority that is higher).

Optionally, the first uplink transmission includes at least one of:

transmission of low priority uplink resources;

transmission of the HARQ process in which the incompletely transmitted MAC PDU is located;

and transmission of the resource where the incompletely transmitted MAC PDU is located.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is both a new transmission and a first uplink transmission, the UE prioritizes the first uplink transmission.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is both a new transmission and a first uplink transmission, the UE may implement to prioritize transmission of one of the new transmission and the first uplink transmission.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if there is both the new transmission and the first uplink transmission, the UE performs a priority transmission on one of the new transmission and the first uplink transmission according to the predefined information.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is both a new transmission and a first uplink transmission, the UE prioritizes one of the new transmission and the first uplink transmission based on a logical channel priority (e.g., the priority of the higher priority).

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is both retransmission and first uplink, the UE prioritizes the first uplink.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is both retransmission and first uplink transmission, one of the retransmission and the first uplink transmission is preferentially transmitted depending on the UE implementation.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if there is both retransmission and first uplink transmission, the UE performs priority transmission according to predefined information on one of the retransmission and the first uplink transmission.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is both retransmission and first uplink transmission, the UE prioritizes one of the retransmission and the first uplink transmission based on logical channel priority (e.g., the priority of the higher priority).

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if there is a new transmission, retransmission and first uplink transmission at the same time, the UE prioritizes the first uplink transmission.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is a new transmission, retransmission, and first uplink transmission at the same time, one of the new transmission, retransmission, and first uplink transmission is preferentially transmitted depending on the UE implementation.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if there is a new transmission, retransmission and first uplink transmission at the same time, the UE performs priority transmission on one of the new transmission, retransmission and first uplink transmission according to predefined information.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there is a new transmission, retransmission, and first uplink transmission at the same time, the UE prioritizes one of the new transmission, retransmission, and first uplink transmission based on the logical channel priority (e.g., the priority of the higher priority).

Wherein, the new transmission refers to the first transmission or the first transmission data in the (uplink) HARQ process, and the retransmission refers to the retransmission or the retransmission after failure of the non-first transmission or the failure in the (uplink) HARQ process.

Optionally, when there are multiple retransmissions, which one of the priorities is implemented by the UE, or one of the priorities is predefined, or is determined based on a logical channel priority (e.g., the priority with the highest priority);

In the second aspect, the first uplink transmission is considered to be one type of retransmission. The method specifically comprises the following optional implementation modes:

optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, UE preferably performs retransmission, or retransmission transmission of uplink resources.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if multiple retransmissions exist for the UE at the same time, one of the multiple retransmissions is implemented for priority transmission depending on the UE implementation.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if multiple retransmissions exist for the UE at the same time, the UE performs a priority transmission on one of the multiple retransmissions according to the predefined information.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if multiple retransmissions exist for the UE at the same time, the UE performs priority transmission on one of the multiple retransmissions based on a logical channel priority (e.g., priority with a high priority).

In the case of configuration cg-retransmission timer, or unlicensed band access/operation, the UE considers the transmission of the prioritized uplink resource as retransmission when selecting the prioritized HARQ process, optionally, when there are multiple retransmissions, which one of the priorities is implemented by the UE, or one of the priorities is predefined, or based on the logical channel priority (e.g., the priority of the one with higher priority).

In the third aspect, the first uplink transmission is considered to be one of retransmissions. The method specifically comprises the following optional implementation modes:

optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, the UE preferentially performs transmission of the first HARQ process, where there is retransmission or retransmission of uplink resources.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if the UE has multiple first HARQ processes at the same time, one of the multiple first HARQ processes is implemented for priority transmission depending on the UE implementation.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if the UE has multiple first HARQ processes at the same time, the UE performs priority transmission on one of the multiple first HARQ processes according to predefined information.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if the UE has multiple first HARQ processes at the same time, the UE performs priority transmission on one of the multiple first HARQ processes based on a logical channel priority (e.g., priority with high priority).

It should be noted that, in different embodiments, the UE may also consider the first uplink transmission as a new transmission.

The relevant communication protocols are expressed as:

Before initial transmissions,the UE shall prioritize the transmission forwhich MAC PDU is obtanied and the obtained MAC PDU has not been completely performed；

Or，

The UE shall prioritize the transmission forwhich the obtained MAC PDU has not been completely performed before initial transmissions。

fig. 13 shows a block diagram of a random access device according to an exemplary embodiment of the present application. The random access means may be implemented as or as part of the terminal. The device comprises:

a receiving module 920, configured to receive first RACH information in a system information block; and receiving second RACH information in the dedicated signaling;

a random access module 940, configured to perform a random access procedure in the first cell using the first RACH information and/or the second RACH information.

In one possible design of this embodiment, the random access module 940 is configured to perform the random access procedure using the first RACH information; or, performing the random access procedure using the second RACH information; or, in case that a first condition is satisfied, performing the random access procedure using the first RACH information; or, in case that a second condition is satisfied, performing the random access procedure using the second RACH information; or, in case that a third condition is satisfied, performing the random access procedure using the first RACH information and the second RACH information.

In one possible design of this embodiment, the random access module 940 is configured to perform the random access procedure using the first RACH information if the first RACH information has a higher priority than the second RACH information; or, in case that the second RACH information does not belong to a valid time and/or valid range, performing the random access procedure using the first RACH information; or, in case that first indication information is used to indicate that the first RACH information is preferentially used, performing the random access procedure using the first RACH information; or, in case that slice information in the first RACH information or the second RACH information is different, performing the random access procedure using the first RACH information; or, according to the supporting condition of the device or the access network equipment to the network slice, executing the random access process by using the first RACH information. Or, the random access procedure is performed using the first RACH information not within a coverage or service area of a cell or a base station transmitting the second RACH information.

In one possible design of this embodiment, the random access module 940 is configured to perform the random access procedure using the second RACH information if the second RACH information has a higher priority than the first RACH information; or, in the case of a valid time belonging to the second RACH information, or a valid range belonging to the second RACH, or a valid time and a valid range belonging to the second RACH information, performing the random access procedure using the second RACH information; or, in case that the first indication information is used to indicate that the second RACH information is preferentially used, performing the random access procedure using the second RACH information; or, in case that slice information in the first RACH information or the second RACH information is different and/or belongs to a valid time and/or a valid range of the second RACH information, performing the random access procedure using the second RACH information; or, according to the supporting condition of the device or the access network equipment to the network slice, executing the random access process by using the second RACH information; or, the random access procedure is performed using the second RACH information within a coverage or service area of a cell or a base station transmitting the second RACH information.

In one possible design of this embodiment, the random access module 940 is configured to perform the random access procedure using the at least two sets of RACH configurations and the selection information of RACH configuration parameters, in a case where the first RACH information includes at least two sets of RACH configurations and the second RACH information includes the selection information of RACH configuration parameters; or, in case the second RACH information includes at least two sets of RACH configurations and the first RACH information includes selection information of the RACH configuration parameters, performing the random access procedure using the at least two sets of RACH configurations and the selection information of the RACH configuration parameters; wherein the selection information includes: at least one of a selection threshold, a selection indication, and a selection condition.

In one possible design of this embodiment, the first RACH information and/or the second RACH information is configured with at least two sets of RACH configuration parameters;

the random access module 940 is configured to perform the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied.

In one possible design of this embodiment, the at least two sets of RACH configuration parameters include a slice-specific RACH and a common RACH;

The random access module 940 is configured to perform the random access procedure using the slice-specific RACH if a fourth condition is satisfied; or, in case that the fifth condition is satisfied, performing the random access procedure using the common RACH.

In one possible design of this embodiment, the fourth condition includes at least one of:

device support slicing;

the apparatus uses a designated slice;

the apparatus uses slices of a specified type;

the slice used by the device is the same as the network support slice;

the required slice of the device is the same as the network support slice;

the device supports a communication protocol version greater than or equal to a predetermined version;

the channel quality is above a first threshold, the first threshold being a threshold for selecting between the common RACH and the slice-specific RACH;

the channel quality is above a second threshold, the second threshold being a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

the channel quality is higher than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving second indication information for indicating selection of the slice-dedicated RACH between the common RACH and the slice-dedicated RACH;

Receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between two groups of RACH resources;

the random access procedure is a contention random access procedure.

In one possible design of this embodiment, the fifth condition includes at least one of:

the device does not support slicing;

the device does not use a designated slice;

the device does not use slices of a specified type;

the device uses a different slice than the network support slice;

the device's required slice is different from the network support slice;

the device supporting a communication protocol version below a predetermined version;

the channel quality being below a first threshold, said first threshold being a threshold for selecting between said common RACH and said slice-specific RACN;

the channel quality is lower than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

Receiving fifth indication information for indicating that the 2-step slice-dedicated RACH or RACH other than the slice-dedicated RACH is selected between two sets of RACH resources;

performing random access failure by using the RACH special for slicing;

using the 2-step slice dedicated RACH for random access failure, and not configuring a 4-step slice dedicated RACH;

the random access procedure is a non-contention random access procedure.

In one possible design of this embodiment, the at least two sets of RACH configuration parameters include a 2-step slice-specific RACH and a 4-step slice-specific RACH;

the random access module 940 is configured to perform the random access procedure using the 2-step slice dedicated RACH if a sixth condition is satisfied; or, in case that a seventh condition is satisfied, performing the random access procedure using the 4-step slice-dedicated RACH.

In one possible design of this embodiment, the sixth condition includes at least one of:

the apparatus uses slices of a specified type;

the slice used by the device is the same as the network support slice;

the required slice of the device is the same as the network support slice;

The channel quality is above a second threshold, which is a threshold for selecting the 2-step slice specific RACH between two sets of RACH resources;

the channel quality is above a third threshold, the third threshold being a threshold for selecting between the 2-step slice specific RACH and the 4-step slice specific RACH;

receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between the two groups of RACH resources;

the random access procedure is a contention random access procedure.

In one possible design of this embodiment, the seventh condition includes at least one of:

the device does not use slices of a specified type;

the device uses a different slice than the network support slice;

the device's required slice is different from the network support slice;

the channel quality is below a second threshold, which is a threshold for selecting the 2-step slice specific RACH between two sets of RACH resources;

The channel quality is below a third threshold, the second threshold being a threshold for selecting between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

receiving seventh indication information for indicating selection of the 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

performing random access failure by using the RACH special for the 2-step slicing;

receiving eighth indication information, wherein the eighth indication information is used for indicating that 4-step slice special RACH or slice special RACH is selected between the two groups of RACH resources;

the random access procedure is a non-contention random access procedure.

In one possible design of this embodiment, the at least two sets of RACH configuration parameters include a 2-step RACH and a 2-step slice dedicated RACH;

the random access module 940 is configured to perform the random access procedure using the 2-step slice dedicated RACH if an eighth condition is satisfied; or, in case that the ninth condition is satisfied, performing the random access procedure using the 2-step RACH.

In one possible design of this embodiment, the eighth condition includes at least one of:

the apparatus uses slices of a specified type;

The slice used by the device is the same as the network support slice;

the required slice of the device is the same as the network support slice;

the channel quality is above a fourth threshold, the fourth threshold being a threshold for selecting between the 2-step slice dedicated RACH and a 2-step RACH;

receiving third indication information, wherein the third indication information is used for indicating that 2-step slice special RACH or slice special RACH is selected between two groups of RACH resources;

the random access procedure is a contention random access procedure.

In one possible design of this embodiment, the ninth condition includes at least one of:

the device does not use slices of a specified type;

the device uses a different slice than the network support slice;

the device's required slice is different from the network support slice;

the channel quality is below a third threshold, the third threshold being a threshold for selecting between the 2-step slice dedicated RACH and a 2-step RACH;

receiving tenth indication information for indicating selection of the 2-step RACH between the 2-step slice dedicated RACH and the 2-step RACH;

receiving fifth indication information for indicating a selection of a 2-step slice-dedicated RACH or a RACH other than a slice-dedicated RACH between two sets of RACH resources;

the random access procedure is a non-contention random access procedure.

In one possible design of this embodiment, the at least two sets of RACH configuration parameters include a 4-step RACH and a 4-step slice dedicated RACH;

the random access module 940 is configured to perform the random access procedure using the 4-step slice dedicated RACH if a tenth condition is satisfied; or, in case that the eleventh condition is satisfied, performing the random access procedure using the 4-step RACH.

In one possible design of this embodiment, the tenth condition includes at least one of:

the apparatus uses slices of a specified type;

the slice used by the device is the same as the network support slice;

the required slice of the device is the same as the network support slice;

the channel quality is above a sixth threshold, the sixth threshold being a threshold for selecting between the 4-step slice dedicated RACH and a 4-step RACH;

an eleventh indication information for indicating selection of the 4-step slice dedicated RACH between the 4-step slice dedicated RACH and the 4-step RACH is received.

receiving eighth indication information, wherein the eighth indication information is used for indicating that 4-step slice special RACH or slice special RACH is selected between two groups of RACH resources;

the random access process is a contention random access process;

using a 2-step slicing dedicated RACH to perform random access failure;

random access failure is performed using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH is configured.

In one possible design of this embodiment, the eleventh condition includes at least one of:

the device does not use slices of a specified type;

the device uses a different slice than the network support slice;

the device's required slice is different from the network support slice;

the channel quality is below a sixth threshold, the sixth threshold being a threshold for selecting between the 4-step slice dedicated RACH and a 4-step RACH;

receiving twelfth indication information for indicating selection of the 4-step RACH between the 4-step slice dedicated RACH and the 4-step RACH;

performing random access failure by using the 4-step slice dedicated RACH;

The random access procedure is a non-contention random access procedure.

In one possible design of this embodiment, the at least two sets of RACH configuration parameters are configured with the first RACH information; or, the at least two sets of RACH configuration parameters are configured by the second RACH information; or, the at least two sets of RACH configuration parameters are configured by the first RACH information and the second RACH.

In one possible design of this embodiment, the random access module 940 is configured to perform the random access procedure using the same behavior in different cells, where the behavior includes a behavior of using the first RACH information and/or the second RACH information; or, performing the random access procedure using different actions in different cells, the actions including an action of using the first RACH information and/or the second RACH information.

In one possible design of this embodiment, the system information block is SIB1; or, the system information block is other SIBs except for the SIB1; or, the system information block is the SIB1 and other SIBs other than the SIB 1.

In one possible design of this embodiment, the system information block includes:

And at least one of a using range, a cell, an area, a PLMN, a registration area and tracking area information corresponding to the first RACH information.

In one possible design of this embodiment, the system information block includes at least one of:

slicing information;

rollback indication, BI, information;

power boost information;

time-frequency resources of RACH;

and randomly accessing the pilot frequency.

In one possible design of this embodiment, the first RACH information includes:

a first RACH configuration for configuring a first RACH resource.

In one possible design of this embodiment, the first RACH resource includes at least two sets of RACH configuration parameters, and the first RACH information includes at least one of:

a selection threshold for selecting at least two sets of RACH configuration parameters;

a selection indication for selecting the at least two sets of RACH configuration parameters;

selection conditions for selecting the at least two sets of RACH configuration parameters.

In one possible design of this embodiment, the dedicated signaling includes:

dedicated radio resource control, RRC, messages;

wherein the dedicated RRC message includes: RRC reconfiguration message, or RRC release message

In one possible design of this embodiment, the dedicated signaling includes:

And the effective duration corresponding to the second RACH information.

In one possible design of this embodiment, the dedicated signaling includes:

and at least one of effective range, cell, area, public land mobile network PLMN, registration area and tracking area information corresponding to the second RACH information.

In one possible design of this embodiment, the dedicated signaling includes:

slicing information;

rollback BI indication information;

power boost information;

time-frequency resources of RACH;

random access preamble.

In one possible design of this embodiment, the second RACH information includes:

and a second RACH configuration for configuring second RACH resources.

In one possible design of this embodiment, the second RACH resource includes at least two sets of RACH configuration parameters, and the second RACH information further includes:

a selection indication for selecting at least two sets of RACH configuration parameters;

selection conditions for selecting at least two sets of RACH configuration parameters.

In one possible design of this embodiment, the selection threshold includes at least one of:

A second threshold for selecting a 2-step slice-specific RACH threshold between two sets of RACH resources;

a fourth threshold for selecting between the 2-step slice-dedicated RACH and the 2-step RACH;

a fifth threshold for selecting a threshold of a slice-specific RACH between the two sets of RACH resources;

a sixth threshold for selecting between the 4-step slice-specific RACH and the 4-step RACH.

In one possible design of this embodiment, the selection indication includes at least one of:

third indication information for indicating selection of a 2-step slice-dedicated RACH or a slice-dedicated RACH between two sets of RACH resources;

fourth indication information for selecting a common RACH between the common RACH and a slice-dedicated RACH;

fifth indication information for indicating that a 2-step slice-dedicated RACH or a RACH other than a slice-dedicated RACH is selected between two sets of RACH resources;

sixth indication information for indicating a threshold for selecting a 2-step slice dedicated RACH between the 2-step slice dedicated RACH and the 4-step slice dedicated RACH;

Seventh indication information indicating a threshold for selecting a 4-step slice dedicated RACH between the 2-step slice dedicated RACH and the 4-step slice dedicated RACH;

eighth indication information for indicating that the 4-step slice-dedicated RACH or the slice-dedicated RACH is selected between two sets of RACH resources;

ninth indication information for indicating selection of the 2-step slice dedicated RACH between the 2-step slice dedicated RACH and the 2-step RACH;

tenth indication information for indicating selection of the 2-step RACH between the 2-step slice dedicated RACH and the 2-step RACH;

In one possible design of this embodiment, the selection condition includes at least one of:

selecting a non-slice dedicated RACH in case of a non-slice or non-designated slice or a designated slice and the network support slice do not match or a required slice and the network support slice do not match;

selecting a slice-specific RACH in case a slice or the designated slice and the network support slice match or the required slice and the network support slice match;

Selecting the slice-specific RACH in case of a slice of a specified type or matching of the specified type slice and the network support slice;

selecting a common RACH in case of a non-designated type of slice or a mismatch between the designated type of slice and the network support slice or a mismatch between the required slice and the network support slice;

selecting a 2-step slice-specific RACH in case the specified type of slice or the specified type of slice and the network support slice match or the required slice and the network support slice match;

selecting a 4-step slice dedicated RACH in case the non-designated type slice or the designated type slice and the network support slice do not match or the required slice and the network support slice do not match;

selecting a 2-step RACH in case the specified type of slice or the specified type of slice and the network support slice match or the required slice and the network support slice match;

selecting a 4-step RACH in the event that the non-designated type of slice or the designated type of slice and the network support slice do not match or the required slice and the network support slice do not match;

Selecting the common RACH in case of RACH failure of a first type or mismatching of the designated type slice and the network support slice or mismatching of the demand slice and the network support slice;

selecting the common RACH in case the first type RACH fails and the second type RACH is not configured;

selecting the 4-step slice specific RACH in case of a failure of the first type RACH and a configuration of the second type RACH;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the apparatus supports slice;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case the apparatus does not support slice;

in case of a network supporting slice, selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case of a slice not supported by the network;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the apparatus uses the same slice as a network-supported slice;

Selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case that a slice used by the apparatus is different from a network supported slice;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the communication protocol release supported by the apparatus is higher than a predetermined release;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case the version of the communication protocol supported by the apparatus is lower than a predetermined version;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the random access procedure is a contention random access procedure;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case the random access procedure is a non-contention random access procedure;

selecting the slice-dedicated RACH or the 2-step common RACH in case the random access procedure is a contention random access procedure;

in case the random access procedure is a non-contention random access procedure, the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step slice dedicated RACH is selected.

Selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the random access procedure is a non-contention random access procedure;

in case the random access procedure is a contention random access procedure, the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH is selected.

In another embodiment, the receiving module 920 is configured to obtain at least two sets of RACH configuration parameters configured by a system information block and/or dedicated signaling;

a random access module 940, configured to perform a random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied. The function of the random access module 940 in performing the random access procedure can refer to the embodiment of fig. 13, and will not be described again.

Fig. 14 shows a block diagram of a priority determining device or a conflict resolution device or a data transmission device according to an exemplary embodiment of the present application. The apparatus is implemented as a terminal or as part of a medium access control (Medium Access Control, MAC) entity or MAC entity in a terminal. The device comprises:

The processing module 1020 is Configured to prioritize Dynamic Grant (DG) or consider Dynamic Grant as a priority Grant if priorities based on logical channels are Configured, and when Dynamic Grant (DG) and at least one Configured Grant (CG) conflict, and the priorities of resources are the same or the priorities of logical channels with the highest logical channel priority in the resources are the same.

Alternatively, if the priorities based on the logical channels are configured, and when there is a conflict between the dynamic grant and at least one configured grant, and the priorities of the resources are the same or the priorities of the logical channels with the highest logical channel priority in the resources are the same, the processing module 1020 is configured to prioritize which grant depends on its implementation.

The relevant communication protocols are expressed as:

The first policy or first condition includes at least one of:

when there is a conflict between the dynamic grant and at least one configuration grant, and the priority of the resources of the dynamic grant and the configuration grant that are in conflict are the same, or the priority of the logic channel with the highest logic priority in the resources of the dynamic grant and the configuration grant that are in conflict is the same, the processing module 1020 is configured to prioritize the dynamic grant or consider the dynamic grant as the priority grant.

If the priority based on the logical channel is configured, when there is a conflict between the dynamic grant and at least one configuration grant, and the resources of the dynamic grant and the configuration grant that have the conflict are the same, or the priority of the logical channel with the highest logical priority in the resources of the dynamic grant and the configuration grant that have the conflict is the same, the processing module 1020 is configured to prioritize the dynamic grant or consider the dynamic grant as the priority grant.

When there is a conflict between the dynamic grant and at least one configuration grant, and the highest priority of the highest logic in the resource priorities of the conflicting dynamic grant and configuration grant is the same, the processing module 1020 is configured to prioritize one of the grants, or the grant considered to be the priority of the dynamic grant, or the priority configuration grant is the priority grant, depending on its implementation.

If the priority based on the logical channel is configured, when there is a conflict between the dynamic grant and at least one configuration grant, and the resources of the dynamic grant and the configuration grant that are in conflict are the same, or the priority of the logical channel with the highest logical priority in the resources of the dynamic grant and the configuration grant that are in conflict is the same, the processing module 1020 is configured to prioritize one of the grants, or the grant considered to be prioritized by the dynamic grant, or the grant configured by the priority is prioritized by the priority grant depending on the implementation.

When there is a conflict between the dynamic grant and at least one configuration grant, and the resources of the dynamic grant and the configuration grant that are in conflict are the same, or the priority of the logical channel with the highest logical priority in the resources of the dynamic grant and the configuration grant that are in conflict is the same, the processing module 1020 is configured to prioritize the dynamic grant, or the grant considered to be prioritized, or the configuration grant prioritized, depending on the implementation of the base station based on the indication of the base station or the configuration of the base station. Wherein the configuration of the base station includes at least one of a selection condition and a selection threshold for preferentially selecting dynamic grants or configuring grants.

In another embodiment, the processing module 1020 is configured to, if there are multiple resource conflicts, such as multiple physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) PUSCH or uplink scheduling (UL-grant) conflicts, if at least some of the resources have no logical channels to be transmitted multiplexed or can be multiplexed on the resources, then the priority of the resources is the same and/or the priority of the resources is lower than the priority of the logical channels to be transmitted or can be multiplexed with other resources or the priority of the scheduling application (Scheduling Request, SR).

Optionally, if there are multiple resource (or uplink resource) conflicts, the processing module 1020 is configured to determine a priority between the first type of resources, or a priority between the first type of resources and the second type of resources, or a priority of the first type of resources according to the second policy or the second condition.

The second policy or second condition includes at least one of:

if there are multiple resource conflicts, the multiple resources include at least two first type resources, and the processing module 1020 is configured to determine that the priorities of the at least two first type resources are the same.

If there are multiple resource conflicts, the multiple resources include a first type of resource and a second type of resource, and the processing module 1020 is configured to determine that the first type of resource has a priority that is lower than the priority of the second type of resource.

If there are multiple resource conflicts, the multiple resources include a first type of resource and a second type of resource, and the processing module 1020 is configured to determine that the first type of resource has the lowest priority.

The processing module 1020 is configured to determine a prioritized transmission according to a third policy or a third condition if cg-retransmission timer is configured or if unlicensed band is in/operating.

The method comprises at least one of the following three modes:

the processing module 1020 is configured to, in case of configuration cg-retransmission timer or unlicensed band access/operation, prioritize transmission of uplink resources with low priority or transmission of hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ) process where MAC PDU is located with incomplete transmission or transmission of resources where MAC PDU is located with incomplete transmission over new transmission. Or vice versa, the UE prioritizes the new transmission. Optionally, between the transmission and other retransmissions, which one of the priorities is prioritized depends on the UE implementation, or one of the priorities is predefined, or determined based on the logical channel priority (e.g., the priority that is higher).

Optionally, the first uplink transmission includes at least one of:

transmission of low priority uplink resources;

optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, the processing module 1020 is configured to perform retransmission preferentially, or retransmission transmission of uplink resources.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if multiple retransmissions are present at the same time, the processing module 1020 is configured to implement one of the multiple retransmissions for prioritized transmission depending on the UE implementation.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if there are multiple retransmissions at the same time, the processing module 1020 is configured to prioritize transmission of one of the multiple retransmissions according to predefined information.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there are multiple retransmissions at the same time, the processing module 1020 is configured to prioritize transmission of one of the multiple retransmissions based on a logical channel priority (e.g., a priority with a high priority).

In a third mode, in the case of cg-retransmission timer configuration, or in the case of unlicensed band access/operation, the processing module 1020 is configured to consider the transmission of the prioritized uplink resource as a retransmission when selecting a prioritized HARQ process.

optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, the processing module 1020 is configured to prioritize transmission of the first HARQ process, where the first HARQ process is a HARQ process with retransmission or retransmission of uplink resources.

Optionally, in case of configuring cg-retransmission timer, or in case of unlicensed band access/operation, if there are multiple first HARQ processes at the same time, the processing module 1020 is configured to implement, depending on UE implementation, one of the multiple first HARQ processes for priority transmission.

Optionally, in the case of configuring cg-retransmission timer or in the case of unlicensed band access/operation, if there are multiple first HARQ processes at the same time, the processing module 1020 is configured to perform priority transmission on one of the multiple first HARQ processes according to predefined information.

Optionally, in the case of configuring cg-retransmission timer, or in the case of unlicensed band access/operation, if there are multiple first HARQ processes at the same time, the processing module 1020 is configured to perform priority transmission on one of the multiple first HARQ processes based on the logical channel priority (e.g., priority with high priority).

It should be noted that, in different embodiments, the apparatus may also consider the first uplink transmission as a new transmission.

Fig. 15 shows a schematic structural diagram of a terminal according to an exemplary embodiment of the present application, where the terminal includes: a processor 101, a receiver 102, a transmitter 103, a memory 104, and a bus 105.

The processor 101 includes one or more processing cores, and the processor 101 executes various functional applications and information processing by running software programs and modules.

The receiver 102 and the transmitter 103 may be implemented as one communication component, which may be a communication chip.

The memory 104 is connected to the processor 101 via a bus 105.

The memory 104 may be used to store at least one instruction that the processor 101 is configured to execute to implement the various steps of the method embodiments described above. Wherein the transmitter 103 is configured to perform steps related to transmission; the receiver 104 is configured to perform steps related to reception; the processor 101 is configured to perform steps other than transmission and reception.

Further, the memory 104 may be implemented by any type of volatile or nonvolatile storage device or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-Only Memory (EEPROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), static random access Memory (Static Random Access Memory, SRAM), read-Only Memory (ROM), magnetic Memory, flash Memory, programmable Read-Only Memory (Programmable Read-Only Memory, PROM).

In an exemplary embodiment, there is also provided a computer readable storage medium having stored therein at least one instruction, at least one program, a code set, or an instruction set, which is loaded and executed by a processor to implement the random access method or the priority determining method or the conflict resolution method or the data transmission method provided by the above respective method embodiments.

In an exemplary embodiment, there is also provided a computer program product or a computer program comprising computer instructions stored in a computer readable storage medium, the computer instructions being read from the computer readable storage medium by a processor of a communication device, the computer instructions being executed by the processor, causing the communication device to perform the random access method or the priority determination method or the conflict resolution method or the data transmission method as described in the above aspects.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing description of the preferred embodiments is merely exemplary in nature and is in no way intended to limit the invention, since it is intended that all modifications, equivalents, improvements, etc. that fall within the spirit and scope of the invention.

Claims

A method for selecting a random access resource, the method comprising:

receiving first Random Access Channel (RACH) information in a system information block; receiving second RACH information in the dedicated signaling;

a random access procedure is performed using the first RACH information and/or the second RACH information.
The method according to claim 1, wherein said performing a random access procedure using said first RACH information and/or said second RACH information comprises:

performing the random access procedure using the first RACH information;

or, performing the random access procedure using the second RACH information;

or, in case that a first condition is satisfied, performing the random access procedure using the first RACH information;

or, in case that a second condition is satisfied, performing the random access procedure using the second RACH information;

or, in case that a third condition is satisfied, performing the random access procedure using the first RACH information and the second RACH information.
The method of claim 2, wherein the performing the random access procedure using the first RACH information if a first condition is satisfied comprises:

performing the random access procedure using the first RACH information in case that the first RACH information has a higher priority than the second RACH information;

or, in case that the second RACH information does not belong to a valid time and/or valid range, performing the random access procedure using the first RACH information;

or, in case that first indication information is used to indicate that the first RACH information is preferentially used, performing the random access procedure using the first RACH information;

or, in case that slice information in the first RACH information or the second RACH information is different, performing the random access procedure using the first RACH information;

or, according to the supporting condition of the terminal or the access network equipment to the network slice, executing the random access process by using the first RACH information;

or, the random access procedure is performed using the first RACH information not within a coverage or service area of a cell or a base station transmitting the second RACH information.
The method of claim 2, wherein the performing the random access procedure using the second RACH information if a second condition is satisfied comprises:

performing the random access procedure using the second RACH information in case the second RACH information has a higher priority than the first RACH information;

or, in the case of a valid time belonging to the second RACH information, or a valid range belonging to the second RACH, or a valid time and a valid range belonging to the second RACH information, performing the random access procedure using the second RACH information;

or, in case that the first indication information is used to indicate that the second RACH information is preferentially used, performing the random access procedure using the second RACH information;

or, in case that slice information in the first RACH information or the second RACH information is different and/or belongs to a valid time and/or a valid range of the second RACH information, performing the random access procedure using the second RACH information;

or, according to the supporting condition of the terminal or the access network equipment to the network slice, executing the random access process by using the second RACH information;

Or, the random access procedure is performed using the second RACH information within a coverage or service area of a cell or a base station transmitting the second RACH information.
The method according to claim 2, wherein said performing the random access procedure using the first RACH information and the second RACH information if a third condition is satisfied comprises:

performing the random access procedure using at least two sets of RACH configuration parameters and selection information of the RACH configuration parameters, in case the first RACH information includes at least two sets of RACH configuration parameters and the second RACH information includes selection information of the RACH configuration parameters;

or, in case the second RACH information includes at least two sets of RACH configuration parameters and the first RACH information includes selection information of the RACH configuration parameters, performing the random access procedure using the at least two sets of RACH configuration parameters and the selection information of the RACH configuration parameters;

wherein the selection information includes: at least one of a selection threshold, a selection indication, and a selection condition.
The method according to claim 1, wherein the first RACH information and/or the second RACH information is configured with at least two sets of RACH configuration parameters;

The performing the random access procedure using the first RACH information and/or the second RACH information includes:

and executing the random access procedure by using one set of RACH configuration parameters in the at least two sets of RACH configuration parameters when the trigger condition is met.
The method of claim 6, wherein the at least two sets of RACH configuration parameters include a slice-specific RACH and a common RACH;

the performing the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied, includes:

performing the random access procedure using the slice-specific RACH if a fourth condition is satisfied;

or, in case that the fifth condition is satisfied, performing the random access procedure using the common RACH.
The method of claim 7, wherein the fourth condition comprises at least one of:

terminal support slicing;

the terminal uses a designated slice;

the terminal uses slices of a specified type;

the slice used by the terminal is the same as the network support slice;

the demand slice of the terminal is the same as the network support slice;

The communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a first threshold, the first threshold being a threshold for selecting between the common RACH and the slice-specific RACH;

the channel quality is above a second threshold, the second threshold being a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

the channel quality is higher than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving second indication information for indicating selection of the slice-dedicated RACH between the common RACH and the slice-dedicated RACH;

receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between two groups of RACH resources;

the random access procedure is a contention random access procedure.
The method of claim 7, wherein the fifth condition comprises at least one of:

the terminal does not support slicing;

the terminal does not use a designated slice;

the terminal does not use slices of a specified type;

The slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is lower than a preset version;

the channel quality being below a first threshold, said first threshold being a threshold for selecting between said common RACH and said slice-specific RACN;

the channel quality is below a second threshold, which is a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

the channel quality is lower than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving fourth indication information for indicating selection of the common RACH between the common RACH and the slice-dedicated RACH;

receiving fifth indication information for indicating that the 2-step slice-dedicated RACH or RACH other than the slice-dedicated RACH is selected between two sets of RACH resources;

performing random access failure by using the RACH special for slicing;

using the 2-step slice dedicated RACH for random access failure, and not configuring a 4-step slice dedicated RACH;

The random access procedure is a non-contention random access procedure.
The method of claim 6, wherein the at least two sets of RACH configuration parameters include a 2-step slice-specific RACH and a 4-step slice-specific RACH;

the performing the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied, includes:

performing the random access procedure using the 2-step slice dedicated RACH if a sixth condition is satisfied;

or, in case that a seventh condition is satisfied, performing the random access procedure using the 4-step slice-dedicated RACH.
The method of claim 10, wherein the sixth condition comprises at least one of:

the terminal uses slices of a specified type;

the slice used by the terminal is the same as the network support slice;

the demand slice of the terminal is the same as the network support slice;

the communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a second threshold, which is a threshold for selecting the 2-step slice specific RACH between two sets of RACH resources;

The channel quality is above a third threshold, the third threshold being a threshold for selecting between the 2-step slice specific RACH and the 4-step slice specific RACH;

receiving sixth indication information for indicating selection of the 2-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between the two groups of RACH resources;

the random access procedure is a contention random access procedure.
The method of claim 10, wherein the seventh condition comprises at least one of:

the terminal does not use slices of a specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is lower than a preset version;

the channel quality is below a second threshold, which is a threshold for selecting the 2-step slice specific RACH between two sets of RACH resources;

the channel quality is below a third threshold, the second threshold being a threshold for selecting between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

Receiving seventh indication information for indicating selection of the 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

performing random access failure by using the RACH special for the 2-step slicing;

receiving eighth indication information, wherein the eighth indication information is used for indicating that the 4-step slice special RACH or the slice special RACH is selected between the two groups of RACH resources;

the random access procedure is a non-contention random access procedure.
The method of claim 6, wherein the at least two sets of RACH configuration parameters include a 2-step RACH and a 2-step slice-specific RACH;

the performing the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied, includes:

performing the random access procedure using the 2-step slice dedicated RACH if an eighth condition is satisfied;

or, in case that the ninth condition is satisfied, performing the random access procedure using the 2-step RACH.
The method of claim 13, wherein the eighth condition comprises at least one of:

the terminal uses slices of a specified type;

The slice used by the terminal is the same as the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a fourth threshold, the fourth threshold being a threshold for selecting between the 2-step slice dedicated RACH and a 2-step RACH;

the channel quality is above a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving ninth indication information for indicating selection of the 2-step slice dedicated RACH between the 2-step slice dedicated RACH and the 2-step RACH;

receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between two groups of RACH resources;

the random access procedure is a contention random access procedure.
The method of claim 13, wherein the ninth condition comprises at least one of:

the terminal does not use slices of a specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

The communication protocol version supported by the terminal is lower than a preset version;

the channel quality is below a third threshold, the third threshold being a threshold for selecting between the 2-step slice dedicated RACH and a 2-step RACH;

the channel quality is below a second threshold, which is a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

receiving tenth indication information for indicating selection of the 2-step RACH between the 2-step slice dedicated RACH and the 2-step RACH;

performing random access failure by using the RACH special for the 2-step slicing;

using the 2-step slice dedicated RACH for random access failure, and not configuring a 4-step slice dedicated RACH;

receiving fifth indication information for indicating a selection of a 2-step slice-dedicated RACH or a RACH other than a slice-dedicated RACH between two sets of RACH resources;

the random access procedure is a non-contention random access procedure.
The method of claim 6, wherein the at least two sets of RACH configuration parameters include a 4-step RACH and a 4-step slice-specific RACH;

the performing the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied, includes:

Performing the random access procedure using the 4-step slice-dedicated RACH if a tenth condition is satisfied;

or, in case that the eleventh condition is satisfied, performing the random access procedure using the 4-step RACH.
The method of claim 16, wherein the tenth condition comprises at least one of:

the terminal uses slices of a specified type;

the slice used by the terminal is the same as the network support slice;

the demand slice of the terminal is the same as the network support slice;

the communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a sixth threshold, the sixth threshold being a threshold for selecting between the 4-step slice dedicated RACH and a 4-step RACH;

receiving eleventh indication information for indicating selection of the 4-step slice dedicated RACH between the 4-step slice dedicated RACH and the 4-step RACH;

the channel quality is higher than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving eighth indication information, wherein the eighth indication information is used for indicating that the 4-step slice special RACH or the slice special RACH is selected between two groups of RACH resources;

The random access process is a contention random access process;

using a 2-step slicing dedicated RACH to perform random access failure;

random access failure is performed using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH is configured.
The method of claim 16, wherein the eleventh condition comprises at least one of:

the terminal does not use slices of a specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is lower than a preset version;

the channel quality is below a sixth threshold, the sixth threshold being a threshold for selecting between the 4-step slice dedicated RACH and a 4-step RACH;

receiving twelfth indication information for indicating selection of the 4-step RACH between the 4-step slice dedicated RACH and the 4-step RACH;

performing random access failure by using the 4-step slice dedicated RACH;

the channel quality is lower than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

performing random access failure by using the RACH special for the 2-step slicing;

Using the 2-step slice-dedicated RACH for random access failure, and not configuring the 4-step slice-dedicated RACH;

receiving fifth indication information, wherein the fifth indication information is used for indicating that the 2-step slice special RACH or RACH except the slice special RACH is selected between two groups of RACH resources;

the random access procedure is a non-contention random access procedure.
The method according to any one of claims 6 to 18, wherein,

the at least two sets of RACH configuration parameters are configured with the first RACH information;

or, the at least two sets of RACH configuration parameters are configured by the second RACH information;

or, the at least two sets of RACH configuration parameters are configured by the first RACH information and the second RACH.
The method according to any one of claims 1 to 18, wherein said performing a random access procedure using said first RACH information and/or said second RACH information comprises:

performing the random access procedure using the same behaviour in different cells, the behaviour comprising a behaviour using the first RACH information and/or the second RACH information;

or, performing the random access procedure using different actions in different cells, the actions including an action of using the first RACH information and/or the second RACH information.
The method according to any one of claims 1 to 18, wherein,

the system information block is a system information block SIB1;

or, the system information block is other SIBs except for the SIB1;

or, the system information block is the SIB1 and other SIBs other than the SIB 1.
The method according to any one of claims 1 to 18, wherein the system information block comprises:

and at least one of a using range, a cell, an area, a Public Land Mobile Network (PLMN), a registration area and tracking area information corresponding to the first RACH information.
The method according to any of claims 1 to 18, wherein the system information block comprises at least one of:

slicing information;

rollback indication, BI, information;

power boost information;

time-frequency resources of RACH;

and randomly accessing the pilot frequency.
The method according to any one of claims 1 to 18, wherein the first RACH information includes:

a first RACH configuration for configuring at least one RACH configuration parameter of RACH resources, RACH type, RACH priority.
The method of claim 24, wherein the first RACH configuration is used to configure at least two sets of RACH configuration parameters, the first RACH information further comprising at least one of:

A selection threshold for selecting the at least two sets of RACH configuration parameters;

a selection indication for selecting the at least two sets of RACH configuration parameters;

selection conditions for selecting the at least two sets of RACH configuration parameters.
The method according to any of the claims 1 to 18, wherein the dedicated signaling comprises:

dedicated radio resource control, RRC, messages;

wherein the dedicated RRC message includes: RRC reconfiguration message, or RRC release message.
The method according to any of the claims 1 to 18, wherein the dedicated signaling comprises:

and the effective duration corresponding to the second RACH information.
The method according to any of the claims 1 to 18, wherein the dedicated signaling comprises:

and at least one of effective range, cell, area, public land mobile network PLMN, registration area and tracking area information corresponding to the second RACH information.
The method according to any of the claims 1 to 18, wherein the dedicated signaling comprises:

slicing information;

rollback indication, BI, information;

power boost information;

time-frequency resources of RACH;

random access preamble.
The method according to any one of claims 1 to 18, wherein the second RACH information includes:

And a second RACH configuration for configuring at least one RACH configuration parameter of RACH resources, RACH type, RACH priority.
The method of claim 30, wherein the second RACH configuration is used to configure at least two sets of RACH configuration parameters, the second RACH information further comprising at least one of:

a selection threshold for selecting the at least two sets of RACH configuration parameters;

a selection indication for selecting the at least two sets of RACH configuration parameters;

selection conditions for selecting the at least two sets of RACH configuration parameters.
The method according to claim 25 or 31, wherein the selection threshold comprises at least one of:

a first threshold for selecting between the common RACH and the slice-specific RACH;

a second threshold for selecting a 2-step slice-specific RACH threshold between two sets of RACH resources;

a third threshold for selecting between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

a fourth threshold for selecting between the 2-step slice-dedicated RACH and the 2-step RACH;

a fifth threshold for selecting a threshold of a slice-specific RACH between the two sets of RACH resources;

A sixth threshold for selecting between the 4-step slice-specific RACH and the 4-step RACH.
The method of claim 25 or 31, wherein the selection indication comprises at least one of:

second indication information for selecting a slice-specific RACH between a common RACH and the slice-specific RACH;

third indication information for indicating a 2-step slice-dedicated RACH or the slice-dedicated RACH selected between two sets of RACH resources;

fourth indication information for selecting the common RACH between the common RACH and the slice-dedicated RACH;

fifth indication information for indicating that the 2-step slice-dedicated RACH or an RACH other than the slice-dedicated RACH is selected between two sets of RACH resources;

sixth indication information for indicating a threshold for selecting the 2-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

seventh indication information indicating a threshold for selecting a 4-step slice dedicated RACH between the 2-step slice dedicated RACH and the 4-step slice dedicated RACH;

eighth indication information for indicating that the 4-step slice-dedicated RACH or the slice-dedicated RACH is selected between two sets of RACH resources;

Ninth indication information for indicating selection of the 2-step slice dedicated RACH between the 2-step slice dedicated RACH and the 2-step RACH;

tenth indication information for indicating selection of the 2-step RACH between the 2-step slice dedicated RACH and the 2-step RACH;

eleventh indication information for indicating selection of a 4-step slice-dedicated RACH between the 4-step slice-dedicated RACH and the 4-step RACH;

twelfth indication information for indicating that a 4-step RACH is selected between the 4-step slice dedicated RACH and the 4-step RACH.
The method of claim 33, wherein the selection conditions include at least one of:

selecting a non-slice dedicated RACH in case of a non-slice or non-designated slice or a designated slice and the network support slice do not match or a required slice and the network support slice do not match;

selecting a slice-specific RACH in case a slice or the designated slice and the network support slice match or the required slice and the network support slice match;

selecting the slice-specific RACH in case of a slice of a specified type or matching of the specified type slice and the network support slice;

Selecting a common RACH in case of a non-designated type of slice or a mismatch between the designated type of slice and the network support slice or a mismatch between the required slice and the network support slice;

selecting a 2-step slice-specific RACH in case the specified type of slice or the specified type of slice and the network support slice match or the required slice and the network support slice match;

selecting a 4-step slice dedicated RACH in case the non-designated type slice or the designated type slice and the network support slice do not match or the required slice and the network support slice do not match;

selecting a 2-step RACH in case the specified type of slice or the specified type of slice and the network support slice match or the required slice and the network support slice match;

selecting a 4-step RACH in the event that the non-designated type of slice or the designated type of slice and the network support slice do not match or the required slice and the network support slice do not match;

selecting the common RACH in case of RACH failure of a first type or mismatching of the designated type slice and the network support slice or mismatching of the demand slice and the network support slice;

Selecting the common RACH in case the first type RACH fails and the second type RACH is not configured;

selecting the 4-step slice specific RACH in case of a failure of the first type RACH and a configuration of the second type RACH;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the terminal supports slicing;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case the terminal does not support slicing;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the network supports slicing;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case the network does not support slice;

selecting the slice-dedicated RACH or the 2-step slice-dedicated RACH or the 4-step slice-dedicated RACH in case that the slice used by the terminal is the same as a network-supported slice;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case that a slice used by the terminal is different from a network supported slice;

Selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case that the communication protocol version supported by the terminal is higher than a predetermined version;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case that a communication protocol version supported by the terminal is lower than a predetermined version;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the random access procedure is a contention random access procedure;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH in case the random access procedure is a non-contention random access procedure;

selecting the slice-dedicated RACH or the 2-step common RACH in case the random access procedure is a contention random access procedure;

selecting the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step slice dedicated RACH in case the random access procedure is a non-contention random access procedure;

selecting the slice-specific RACH or the 2-step slice-specific RACH or the 4-step slice-specific RACH in case the random access procedure is a non-contention random access procedure;

In case the random access procedure is a contention random access procedure, the non-slice dedicated RACH or the common RACH or the 2-step RACH or the 4-step RACH is selected.
The method according to any of the claims 1 to 18, wherein the system information block and/or the dedicated signaling further comprises:

and first indication information for indicating whether to cover the first RACH information with the second RACH information.
A random access method, the method comprising:

acquiring at least two groups of Random Access Channel (RACH) resources, wherein the at least two groups of RACH configuration parameters are configured by a system information block and/or a dedicated signaling;

and executing a random access procedure by using one set of RACH configuration parameters in the at least two sets of RACH configuration parameters when the trigger condition is met.
The method of claim 36, wherein the performing a random access procedure using one of the at least two sets of RACH configuration parameters if a trigger condition is met comprises:

performing the random access procedure using the slice-specific RACH if a fourth condition is satisfied;

or alternatively, the first and second heat exchangers may be,

In case that the fifth condition is satisfied, the random access procedure is performed using the common RACH.
The method of claim 37, wherein the fourth condition comprises at least one of:

terminal support slicing;

the terminal uses a designated slice;

the terminal uses slices of a specified type;

the slice used by the terminal is the same as the network support slice;

the demand slice of the terminal is the same as the network support slice;

the communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a first threshold, the first threshold being a threshold for selecting between the common RACH and the slice-specific RACH;

the channel quality is above a second threshold, the second threshold being a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

the channel quality is higher than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving second indication information for indicating selection of the slice-dedicated RACH between the common RACH and the slice-dedicated RACH;

Receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between two groups of RACH resources;

the random access procedure is a contention random access procedure.
The method of claim 37, wherein the fifth condition comprises at least one of:

the terminal does not support slicing;

the terminal does not use a designated slice;

the terminal does not use slices of a specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is lower than a preset version;

the channel quality being below a first threshold, said first threshold being a threshold for selecting between said common RACH and said slice-specific RACN;

the channel quality is below a second threshold, which is a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

the channel quality is lower than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving fourth indication information for indicating selection of the common RACH between the common RACH and the slice-dedicated RACH;

Receiving fifth indication information for indicating that the 2-step slice-dedicated RACH or RACH other than the slice-dedicated RACH is selected between two sets of RACH resources;

performing random access failure by using the RACH special for slicing;

using the 2-step slice dedicated RACH for random access failure, and not configuring a 4-step slice dedicated RACH;

the random access procedure is a non-contention random access procedure.
The method of claim 36, wherein the at least two sets of RACH configuration parameters include a 2-step slice-specific RACH and a 4-step slice-specific RACH;

the performing the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied, includes:

performing the random access procedure using the 2-step slice dedicated RACH if a sixth condition is satisfied;

or, in case that a seventh condition is satisfied, performing the random access procedure using the 4-step slice-dedicated RACH.
The method of claim 40, wherein the sixth condition comprises at least one of:

the terminal uses slices of a specified type;

the slice used by the terminal is the same as the network support slice;

The demand slice of the terminal is the same as the network support slice;

the communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a second threshold, which is a threshold for selecting the 2-step slice specific RACH between two sets of RACH resources;

the channel quality is above a third threshold, the third threshold being a threshold for selecting between the 2-step slice specific RACH and the 4-step slice specific RACH;

receiving sixth indication information for indicating selection of the 2-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between the two groups of RACH resources;

the random access procedure is a contention random access procedure.
The method of claim 40, wherein the seventh condition comprises at least one of:

the terminal does not use slices of a specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

The communication protocol version supported by the terminal is lower than a preset version;

the channel quality is below a second threshold, which is a threshold for selecting the 2-step slice specific RACH between two sets of RACH resources;

the channel quality is below a third threshold, the second threshold being a threshold for selecting between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

receiving seventh indication information for indicating selection of the 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

performing random access failure by using the RACH special for the 2-step slicing;

receiving eighth indication information, wherein the eighth indication information is used for indicating that the 4-step slice special RACH or the slice special RACH is selected between the two groups of RACH resources;

the random access procedure is a non-contention random access procedure.
The method of claim 36, wherein the at least two sets of RACH configuration parameters include a 2-step RACH and a 2-step slice-specific RACH;

the performing the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied, includes:

Performing the random access procedure using the 2-step slice dedicated RACH if an eighth condition is satisfied;

or alternatively, the first and second heat exchangers may be,

in the case where the ninth condition is satisfied, the random access procedure is performed using the 2-step RACH.
The method of claim 43, wherein the eighth condition comprises at least one of:

the terminal uses slices of a specified type;

the slice used by the terminal is the same as the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a fourth threshold, the fourth threshold being a threshold for selecting between the 2-step slice dedicated RACH and a 2-step RACH;

the channel quality is above a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving ninth indication information for indicating selection of the 2-step slice dedicated RACH between the 2-step slice dedicated RACH and the 2-step RACH;

receiving third indication information, wherein the third indication information is used for indicating that the 2-step slice special RACH or the slice special RACH is selected between two groups of RACH resources;

The random access procedure is a contention random access procedure.
The method of claim 43, wherein the ninth condition comprises at least one of:

the terminal does not use slices of a specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is lower than a preset version;

the channel quality is below a third threshold, the third threshold being a threshold for selecting between the 2-step slice dedicated RACH and a 2-step RACH;

the channel quality is below a second threshold, which is a threshold for selecting a 2-step slice dedicated RACH between two sets of RACH resources;

receiving tenth indication information for indicating selection of the 2-step RACH between the 2-step slice dedicated RACH and the 2-step RACH;

performing random access failure by using the RACH special for the 2-step slicing;

using the 2-step slice dedicated RACH for random access failure, and not configuring a 4-step slice dedicated RACH;

receiving fifth indication information for indicating a selection of a 2-step slice-dedicated RACH or a RACH other than a slice-dedicated RACH between two sets of RACH resources;

The random access procedure is a non-contention random access procedure.
The method of claim 36, wherein the at least two sets of RACH configuration parameters include a 4-step RACH and a 4-step slice-specific RACH;

the performing the random access procedure using one set of RACH configuration parameters of the at least two sets of RACH configuration parameters if a trigger condition is satisfied, includes:

performing the random access procedure using the 4-step slice-dedicated RACH if a tenth condition is satisfied;

or alternatively, the first and second heat exchangers may be,

in the case where the eleventh condition is satisfied, the random access procedure is performed using the 4-step RACH.
The method of claim 46, wherein the tenth condition comprises at least one of:

the terminal uses slices of a specified type;

the slice used by the terminal is the same as the network support slice;

the demand slice of the terminal is the same as the network support slice;

the communication protocol version supported by the terminal is higher than or equal to a preset version;

the channel quality is above a sixth threshold, the sixth threshold being a threshold for selecting between the 4-step slice dedicated RACH and a 4-step RACH;

receiving eleventh indication information for indicating selection of the 4-step slice dedicated RACH between the 4-step slice dedicated RACH and the 4-step RACH;

The channel quality is higher than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

receiving eighth indication information, wherein the eighth indication information is used for indicating that the 4-step slice special RACH or the slice special RACH is selected between two groups of RACH resources;

the random access process is a contention random access process;

using a 2-step slicing dedicated RACH to perform random access failure;

random access failure is performed using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH is configured.
The method of claim 46, wherein the eleventh condition comprises at least one of:

the terminal does not use slices of a specified type;

the slice used by the terminal is different from the network support slice;

the required slice of the terminal is different from the network support slice;

the communication protocol version supported by the terminal is lower than a preset version;

the channel quality is below a sixth threshold, the sixth threshold being a threshold for selecting between the 4-step slice dedicated RACH and a 4-step RACH;

receiving twelfth indication information for indicating selection of the 4-step RACH between the 4-step slice dedicated RACH and the 4-step RACH;

Performing random access failure by using the 4-step slice dedicated RACH;

the channel quality is lower than a fifth threshold, which is a threshold for selecting a slice-specific RACH between two sets of RACH resources;

performing random access failure by using the RACH special for the 2-step slicing;

using the 2-step slice-dedicated RACH for random access failure, and not configuring the 4-step slice-dedicated RACH;

receiving fifth indication information, wherein the fifth indication information is used for indicating that the 2-step slice special RACH or RACH except the slice special RACH is selected between two groups of RACH resources;

the random access procedure is a non-contention random access procedure.
The method of any one of claims 36 to 48, further comprising:

performing the random access procedure using the same behaviour in different cells, the behaviour comprising a behaviour using the first RACH information and/or the second RACH information;

or, performing the random access procedure using different actions in different cells, the actions including an action of using the first RACH information and/or the second RACH information.
A random access device, the device comprising:

A receiving module, configured to receive RACH information of a first random access channel in a system information block of a first cell; and receiving second RACH information in dedicated signaling of the first cell;

a random access module, configured to perform a random access procedure in the first cell using the first RACH information or the second RACH information.
A random access device, the device comprising:

a receiving module, configured to obtain at least two sets of RACH configuration parameters, where the at least two sets of RACH configuration parameters are configured by a system information block and/or dedicated signaling;

and the random access module is used for executing a random access process by using one group of RACH configuration parameters in the at least two groups of RACH configuration parameters under the condition that the trigger condition is met.
A terminal, the terminal comprising:

a processor;

a transceiver coupled to the processor;

a memory for storing executable instructions of the processor;

wherein the processor is configured to load and execute the executable instructions to implement the random access method of any one of claims 1 to 49.
A computer readable storage medium having stored therein executable instructions that are loaded and executed by a processor to implement the random access method of any one of claims 1 to 49.