Random access method, apparatus, terminal and storage medium

Abstract

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

Description

Technical Field

[0001] This application relates to the field of mobile communications, and in particular to a random access method, apparatus, terminal and storage medium. Background Technology

[0002] The Radio Access Network (RAN) needs to be enhanced to support vertical services within the access network. For example, it needs to provide lower latency, more targeted, more flexible, and more scalable services for multiple services with different needs, based on network slicing. Summary of the Invention

[0003] This application provides a random access method, apparatus, terminal, and storage medium. A user equipment (UE) can choose to use the Random Access Channel (RACH) resource configured in the system information block, or it can use the RACH resource configured in the dedicated signaling. The technical solution is as follows.

[0004] According to one aspect of this application, a random access method is provided, the method comprising:

[0005] Receive the first RACH information in the System Information Block (SIB);

[0006] Receive the second RACH information in the dedicated signaling;

[0007] The random access procedure is performed using the first RACH information and / or the second RACH information.

[0008] According to one aspect of this application, a random access method is provided, the method comprising:

[0009] Acquire at least two sets of Random Access Channel (RACH) resources, wherein the configuration parameters of the at least two sets of RACH are configured by system information blocks and / or dedicated signaling;

[0010] If the triggering conditions are met, a random access procedure is performed using one of the at least two sets of RACH configuration parameters.

[0011] According to one aspect of this application, a random access device is provided, the device comprising:

[0012] The receiving module is used to receive the first RACH information in the system information block; and to receive the second RACH information in the dedicated signaling.

[0013] The random access module is used to perform a random access procedure using the first RACH information and / or the second RACH information.

[0014] According to one aspect of this application, a random access device is provided, the device comprising:

[0015] The receiving module is used to acquire at least two sets of random access channel (RACH) configuration parameters, wherein the at least two sets of RACH configuration parameters are configured by system information blocks and / or dedicated signaling;

[0016] The random access module is used to perform a random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering conditions are met.

[0017] According to one aspect of this application, a terminal is provided, the terminal comprising: a processor; a transceiver connected to the processor; and 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 above.

[0018] According to one aspect of this application, a computer-readable storage medium is provided that stores executable instructions which are loaded and executed by a processor to implement the random access method as described above.

[0019] According to one aspect of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium, a processor of a computer device reading the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to cause the computer device to perform the random access method described in the above aspect.

[0020] According to one aspect of this application, a chip is provided, the chip including programmable logic circuitry or a program, the chip being used to implement the random access method as described above.

[0021] The technical solutions provided in this application have at least the following beneficial effects:

[0022] When both the first RACH information in the SIB and the second RACH information in the dedicated signaling exist simultaneously, the UE selects the first RACH information and / or the second RACH information for the random access procedure. This allows the UE to better utilize the RACH resources suitable for itself among the different RACH information for the random access procedure, thereby reducing the time consumption of the random access procedure or improving the success rate of the random access procedure. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of a communication system provided in an exemplary embodiment of this application;

[0025] Figure 2 This is a schematic diagram of a four-step random access process provided in an exemplary embodiment of this application;

[0026] Figure 3 This is a schematic diagram of a two-step random access process provided in an exemplary embodiment of this application;

[0027] Figure 4 This is a flowchart of a random access method provided in an exemplary embodiment of this application;

[0028] Figure 5 This is a flowchart of a random access method provided in an exemplary embodiment of this application;

[0029] Figure 6 This is a flowchart of a random access method provided in an exemplary embodiment of this application;

[0030] Figure 7 This is a flowchart of a random access method provided in an exemplary embodiment of this application;

[0031] Figure 8 This is a flowchart of a random access method provided in an exemplary embodiment of this application;

[0032] Figure 9 This is a flowchart of a random access method provided in an exemplary embodiment of this application;

[0033] Figure 10 This is a flowchart of a priority determination method or conflict resolution method provided in an exemplary embodiment of this application;

[0034] Figure 11 This is a flowchart of a priority determination method or conflict resolution method provided in an exemplary embodiment of this application;

[0035] Figure 12 A flowchart illustrating a data transmission method provided in an exemplary embodiment of this application is shown;

[0036] Figure 13 This is a structural block diagram of a random access device provided in an exemplary embodiment of this application;

[0037] Figure 14 This is a block diagram of a priority determination apparatus, conflict resolution apparatus, or data transmission apparatus provided in an exemplary embodiment of this application;

[0038] Figure 15 This is a schematic diagram of the structure of a terminal provided in an exemplary embodiment of this application. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

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

[0041] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

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

[0043] Figure 1 A schematic diagram of a system architecture provided in one embodiment of this application is shown. This system architecture may include: a terminal 10 and a network device 20.

[0044] The number of terminals 10 is typically multiple, with one or more terminals 10 distributed within the cell managed by each network device 20. Terminals 10 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of user equipment (UE), mobile stations (MS), etc. For ease of description, in this embodiment, the devices mentioned above are collectively referred to as terminals.

[0045] Network device 20 is a device deployed in an access network to provide wireless communication functionality to terminal 10. Network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with network device functionality may differ; for example, in a 5G NR system, it is called gNodeB or gNB. As communication technologies evolve, the name "network device" may change. For ease of description, in this embodiment, the aforementioned device providing wireless communication functionality to terminal 10 is collectively referred to as a network device.

[0046] The "5G NR system" in this disclosure can also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in this disclosure are applicable to 5G NR systems and also to subsequent evolution systems of 5G NR systems.

[0047] In NR, two main random access methods are supported: a 4-step random access method, such as... Figure 2 As shown; and a 2-step random access method.

[0048] for Figure 2 The random access process shown consists of four steps. The detailed steps are as follows:

[0049] 1. The terminal sends Msg1(Message 1) to the network device.

[0050] The terminal selects a PRACH (Physical Random Access Channel) resource and transmits a selected preamble on the selected PRACH. If it is a non-contention-based random access method, the PRACH resource and preamble can be specified by the network device. Based on the preamble, the network device can estimate the uplink timing and the grant size required for the terminal to transmit Msg3 (Message 3).

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

[0052] After the terminal sends Msg1, it opens a random access response time window and monitors the PDCCH (Physical Downlink Control Channel) scrambled with RA-RNTI (Random Access Radio Network Temporary Identifier) ​​within this window. The RA-RNTI is calculated as follows:

[0053] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id;

[0054] That is, RA-RNTI is related to the PRACH time and frequency resources used by the UE to send Msg1.

[0055] After successfully receiving the RA-RNTI scrambled PDCCH, the terminal can obtain the PDSCH scheduled by the PDCCH, which contains the RAR (Random Access Response). The RAR specifically contains the following information:

[0056] The RAR subheader contains a BI, which indicates the backoff time for retransmitting Msg1.

[0057] RAPID in RAR: The preamble index received by the network device in response;

[0058] The RAR payload contains a TAG used to adjust the uplink timing;

[0059] UL grant (Uplink grant): Used to schedule uplink resource indications for Msg3;

[0060] Temporary C-RNTI (Temporary Cell Radio Network Temporary Identifier): Used to scramble Msg4 PDCCH (Initial Access).

[0061] If a terminal receives a PDCCH scrambled with RAR-RNTI (Random Access Response Radio Network Temporary Identifier) ​​and the RAR contains its own preamble index, then the terminal considers it to have successfully received the random access response.

[0062] For non-contention-based random access, the random access process ends after the terminal successfully receives Msg2 (Message 2). For contention-based random access, after successfully receiving Msg2, the terminal still needs to transmit Msg3 and receive Msg4 (Message 4).

[0063] 3. The terminal transmits Msg3 on network equipment scheduling resources.

[0064] Msg3 is primarily used to inform network devices what event triggered the RACH (Random Access Channel) procedure. For example, if it is an initial access random procedure, Msg3 will carry the UE identifier and establishment cause; if it is an RRC reconstruction, it will carry the connected UE identifier and establishment cause.

[0065] 4. The network device sends Msg4 to the terminal.

[0066] Msg4 serves two purposes: contention resolution and RRC configuration message transmission from the network device to the terminal. Contention resolution occurs in two ways: First, if the UE carries a C-RNTI (Cell Radio Network Temporary Identifier) ​​in Msg3, then Msg4 uses a PDCCH scrambled with the C-RNTI for scheduling. Second, if the UE does not carry a C-RNTI in Msg3 (e.g., during initial access), then Msg4 uses a PDCCH scrambled with a TC-RNTI (Temporary Cell Radio Network Temporary Identifier) ​​for scheduling. The conflict is resolved by the UE receiving the PDSCH (Physical Downlink Shared Channel) from Msg4 and matching the CCCH SDU (General Control Channel Service Data Unit) within the PDSCH.

[0067] Compared to Figure 2 Two-step random access can improve latency while reducing signaling overhead. In two-step random access, msgA is used to transmit msg1+msg3 of four-step random access, and msgB is used to transmit msg2+msg4 of four-step random access.

[0068] In related technologies, the Radio Resource Control (RRC release) message does not configure RACH resources. However, in this application embodiment, it is desirable to introduce RACH resource configuration into the RRC release message, such as introducing RACH resource configuration for a network slice. In this case, the UE faces the problem of choosing between the RACH resources configured in the SIB or the RACH resources in the dedicated RRC. Therefore, the following embodiment is provided:

[0069] Figure 4 A flowchart of a random access method provided in an exemplary embodiment of this application is shown. This embodiment illustrates the method by way of execution by a terminal. The method includes:

[0070] Step 420: Receive the first RACH information from the system information block;

[0071] The first RACH information is configured with first RACH resources. The first RACH information is broadcast by the access network equipment of the first cell, or by the access network equipment of the second cell. In a scenario where no cell handover occurs, the first cell is the terminal's camping cell. In a scenario where cell handover occurs, the first cell is the terminal's camping cell before the handover, and the second cell is the terminal's camping cell after the handover. In a scenario where cell reselection occurs, the first cell is the terminal's camping cell before the reselection, and the second cell is the terminal's camping cell after the reselection.

[0072] The first RACH information is configured with the first RACH resource. System information blocks are also called system broadcasts or broadcasts.

[0073] The system information block is SIB1; or, the system information block is any SIB other than SIB1. For example, the first RACH information is carried in SIB1, and other broadcast information is carried in other SIBs.

[0074] Optionally, the system information block includes at least one of the following range information: the effective range (or usage range) corresponding to the first RACH information, cell, area, PLMN, registration area, and tracking area. The representation of the above range information includes, but is not limited to, at least one of the following: cell identifier, frequency identifier, RAN notification area, RAN area code, tracking area code, and Public Land Mobile Network (PLMN) identifier.

[0075] Optionally, the system information block includes at least one of: slice information, RACH time-frequency resources, and random access preamble. Slice information includes: slice identifier, correspondence between slice and first RACH resources, etc.

[0076] Optionally, the slice identifier can also be a slice group identifier, a parameter corresponding to the slice identifier or slice group identifier, a specific parameter (corresponding to the slice information), a specified parameter or a predetermined parameter, a slice / service type (SST), a slice index or a slice group index, or an access category, etc.

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

[0078] Optionally, the slice information is information supported by this area and / or neighboring areas.

[0079] Optionally, for slices indicated by network broadcasts or dedicated information, i.e., the supported slice information, the corresponding behavior can be at least one of the following: for slices that provide services to the UE, the UE can initiate or complete registration, the UE can establish a corresponding Protocol Data Unit (PDU) session, the UE can establish corresponding air interface resources, such as Data Radio Bearer (DRB), and the UE can activate the user plane.

[0080] Optionally, for a slice that is not supported as indicated by a network broadcast or dedicated information, or a slice that is not indicated by a network broadcast or dedicated information, or a slice that is not indicated by a network broadcast or dedicated information, the corresponding behavior can be at least one of the following: the slice is not provided with services by the UE, the UE can initiate or complete registration but the registration fails, the UE cannot initiate or complete registration, the UE cannot trigger or establish the corresponding PDU session, the UE can establish the corresponding PDU session but does not support data transmission, the UE cannot establish the corresponding air interface resources (such as DRB), the UE can establish the corresponding air interface resources (such as DRB) but does not support data transmission, the UE can activate the user plane but does not support data transmission, or the UE cannot activate the user plane.

[0081] Optionally, the system information block further includes: priority parameters. Priority parameters include at least one of BackoffIndicator (BI) information and power ramp-up information. BI information can be a BI adjustment factor, and power ramp-up information can be a power ramping step. Optionally, priority parameters may be slice-specific and / or non-slice-specific (common).

[0082] Optionally, the first RACH information includes: a first RACH configuration, which is used to configure at least one RACH configuration parameter among RACH resources, RACH type, and RACH priority. RACH resources include: at least one of RACH time-frequency resources, random access opportunities, and random access preambles. For example, a random access opportunity (RACH Occasion, RO) and / or a random access preamble. For instance, an RO contains 64 random access preambles, and a maximum of eight such ROs can be arranged simultaneously in the frequency domain.

[0083] Optionally, the system information block further includes: first indication information, used to indicate whether to use second RACH information to override the first RACH information.

[0084] In a first possible design, the first RACH configuration is used to configure at least two sets of RACH configuration parameters. The first RACH information also includes a selection threshold for selecting between the at least two sets of RACH configuration parameters. This selection threshold includes at least one of the following:

[0085] • The first threshold is used to select between public RACH and slice-specific RACH;

[0086] For example, if the channel quality is higher than the first threshold, then the dedicated RACH resource for the slice is selected; if the channel quality is lower than the first threshold, then the public RACH resource is selected.

[0087] • The second threshold is used to select a 2-step slice-specific RACH between two sets of RACH resources;

[0088] For example, if the channel quality is higher than the second threshold, then the RACH resources for slices of 2-step RACH are selected; if the channel quality is lower than the second threshold, then the RACH resources corresponding to 2-step or 4-step RACH are selected. Here, "2-step slice-dedicated RACH" is an abbreviation for RACH resources for slices of 2-step RACH.

[0089] • A third threshold, used to select between 2-step slice-specific RACH and 4-step slice-specific RACH;

[0090] For example, if the channel quality is above the third threshold, then a 2-step RACH slice-dedicated RACH resource is selected; if the channel quality is below the third threshold, then a 4-step RACH slice-dedicated RACH resource is selected. Here, "4-step slice-dedicated RACH" is an abbreviation for 4-step RACH slice-dedicated RACH resource.

[0091] • A fourth threshold, used to select between a 2-step slice-specific RACH and a 2-step RACH;

[0092] For example, if the channel quality is higher than the fourth threshold, then the dedicated RACH resource for the 2-step RACH is selected; if the channel quality is lower than the fourth threshold, then the RACH resource corresponding to the 2-step RACH is selected.

[0093] • The fifth threshold is used to select a slice-specific RACH between two sets of RACH resources;

[0094] For example, if the channel quality is higher than the fifth threshold, then the RACH resource dedicated to the slice is selected; if the channel quality is lower than the fifth threshold, then the RACH resource corresponding to the 2-step or 4-step RACH is selected.

[0095] • The sixth threshold is used to select between 4-step slice-specific RACH and 4-step RACH.

[0096] For example, if the channel quality is higher than the sixth threshold, then the dedicated RACH resource for the 4-step RACH is selected; if the channel quality is lower than the sixth threshold, then the RACH resource corresponding to the 4-step RACH is selected.

[0097] It should be noted that any two of the six thresholds mentioned above can be the same or different.

[0098] In the second possible design, the first RACH configuration is used to configure at least two sets of RACH configuration parameters. The first RACH information also includes a selection indication for selecting the at least two sets of RACH configuration parameters. This selection indication includes at least one of the following:

[0099] • Second indication information, used to select the slice-specific RACH between a public RACH and a slice-specific RACH;

[0100] • The third instruction information is used to indicate whether to select a 2-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0101] • Fourth instruction information, used to select the public RACH between a public RACH and a slice-specific RACH;

[0102] • The fifth instruction information is used to indicate whether to select a 2-step slice-specific RACH or a RACH other than slice-specific RACH between the two sets of RACH resources;

[0103] The sixth instruction information is used to indicate the threshold for selecting a 2-step slice-specific RACH between a 2-step slice-specific RACH and a 4-step slice-specific RACH;

[0104] • The seventh instruction information is used to indicate the threshold for selecting the 4-step RACH between the 2-step RACH and the 4-step RACH.

[0105] • The eighth instruction message indicates whether to select a 4-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0106] • Ninth instruction information, used to indicate whether to select a 2-step slice-specific RACH between the 2-step slice-specific RACH and the 2-step RACH;

[0107] • The tenth instruction information is used to indicate whether to select 2-step RACH between 2-step slice-specific RACH and 2-step RACH;

[0108] • Eleventh instruction message, used to indicate whether to select a 4-step slice-specific RACH between the 4-step slice-specific RACH and the 4-step RACH;

[0109] • The twelfth instruction message indicates whether to select 4-step RACH between 4-step slice-specific RACH and 4-step RACH.

[0110] In the third possible design, the first RACH configuration is used to configure at least two sets of RACH configuration parameters. The first RACH information also includes selection criteria for selecting the at least two sets of RACH configuration parameters. These selection criteria include at least one of the following:

[0111] • In cases where there is no slice, no specified slice, a mismatch between the specified slice and the network-supported slice, or a mismatch between the required slice and the network-supported slice, select the non-slice dedicated RACH.

[0112] A specified slice (or a particular slice) refers to one or more slices specified among a plurality of slices.

[0113] A demand slice refers to a slice that the terminal expects to use, or a slice that is required to be used. Illustratively, a demand slice is not a slice that the terminal is currently using.

[0114] • Select the slice-specific RACH when the slice or specified slice and network-supported slice match, or when the required slice and network-supported slice match.

[0115] • Select the slice-specific RACH when the slice of a specified type or when the slice of a specified type matches the slice supported by the network;

[0116] A specified type slice (or a specific type slice) refers to a slice of one or more specified types among a variety of slice types.

[0117] • In cases where a slice of a non-specified type, a slice of a specified type, and a network-supported slice do not match, or a required slice and a network-supported slice do not match, select the common RACH.

[0118] • Select the 2-step RACH for slices if the specified slice type or the specified slice type and the network-supported slice match, or the required slice and the network-supported slice match.

[0119] • In cases where the slice is not of the specified type, or the specified type slice does not match the network-supported slice, or the required slice does not match the network-supported slice, select the 4-step slice-specific RACH.

[0120] • Select 2-step RACH if a slice of a specified type or a slice of a specified type matches a network-supported slice or a required slice matches a network-supported slice;

[0121] • In cases where a slice of a non-specified type, a slice of a specified type, or a slice of a network-supported type do not match, or a slice of a required type does not match, select 4-step RACH;

[0122] • In the event that the first type of RACH fails, or the specified type slice and the network-supported slice do not match, or the required slice and the network-supported slice do not match, select the common RACH;

[0123] • If the first type of RACH fails and the second type of RACH is not configured, select the public RACH;

[0124] • In the event that the first type of RACH fails and the second type of RACH is configured, select the 4-step slice-specific RACH;

[0125] • If the terminal supports slicing, select the slicing-specific RACH, the 2-step slicing-specific RACH, or the 4-step slicing-specific RACH.

[0126] • If the terminal does not support slicing, select non-slicing dedicated RACH, public RACH, 2-step RACH, or 4-step RACH;

[0127] • When the slice used by the terminal is the same as the slice supported by the network, select slice-specific RACH, 2-step slice-specific RACH, or 4-step slice-specific RACH.

[0128] • When the slice used by the terminal is different from the slice supported by the network, select a non-slice-specific RACH, a public RACH, a 2-step RACH, or a 4-step RACH.

[0129] • In the case of a slice that is not supported by the network, select a non-slice-specific RACH, a public RACH, a 2-step RACH, or a 4-step RACH;

[0130] • If the network supports slicing, select a slicing-specific RACH, a 2-step slicing-specific RACH, or a 4-step slicing-specific RACH;

[0131] Differences in slice information include at least one of the following: different supported slice identifiers, different correspondences between slices and RACH resources, different correspondences between slices and frequency points, different correspondences between slices and frequency point priorities, and different RACH information.

[0132] • If the terminal supports a communication protocol version higher than the predetermined version, select either a dedicated RACH for slicing, a 2-step dedicated RACH for slicing, or a 4-step dedicated RACH for slicing.

[0133] The illustrative, intended version is Release 17 of the Third Generation Partnership Project (3GPP).

[0134] • If the terminal supports a communication protocol version lower than the predetermined version, select non-slice dedicated RACH, public RACH, 2-step RACH, or 4-step RACH.

[0135] • In the case of a contention-based random access procedure, select a slice-specific RACH, a 2-step slice-specific RACH, or a 4-step slice-specific RACH.

[0136] • In the case of a non-contention-based random access procedure, select a non-slice-dedicated RACH, a public RACH, a 2-step RACH, or a 4-step RACH.

[0137] • In the case of a contention-based random access procedure, choose either a slice-specific RACH, a two-step slice-specific RACH, or a two-step common RACH.

[0138] • In the case of a non-contention-based random access procedure, select a non-slice-dedicated RACH, a public RACH, a 2-step RACH, a 4-step RACH, or a 4-step slice-dedicated RACH.

[0139] • In the case of a non-contention-based random access procedure, select a slice-specific RACH, a 2-step slice-specific RACH, or a 4-step slice-specific RACH.

[0140] • In the case of a contention-based random access procedure, choose a non-slice-specific RACH, a public RACH, a 2-step RACH, or a 4-step RACH.

[0141] It should be noted that, based on at least one parameter among the selection threshold, selection indication, and selection conditions, a set of RACH configuration parameters can be selected from at least two sets for the random access procedure. RACH configuration parameters include at least one of the following: RACH time-frequency resources, RACH type, RACH priority, random access opportunity, and random access preamble.

[0142] Step 440: Receive the second RACH information in the dedicated signaling;

[0143] The second RACH information is configured with second RACH resources. The second RACH information is sent by the access network equipment of the first cell, or vice versa. In a scenario where no cell handover occurs, the first cell is the terminal's camping cell. In a scenario where cell handover occurs, the first cell is the terminal's camping cell before the handover, and the second cell is the terminal's camping cell after the handover.

[0144] The dedicated signaling includes: dedicated Radio Resource Control (RRC) messages;

[0145] The dedicated RRC messages include: RRC Reconfiguration messages, or RRC Release messages.

[0146] Optionally, the dedicated signaling includes: the validity period or usage period corresponding to the second RACH information. This validity period includes: starting from the first time unit, or starting from the first time unit and ending at the end of the second time unit. For example, it may be valid before the first timer expires, such as when the first timer is a new timer or a T320 timer.

[0147] Optionally, the dedicated signaling includes at least one of the following range information: the effective range (or usage range) corresponding to the second RACH information, cell, area, PLMN, registration area, and tracking area. The representation of the aforementioned range information includes, but is not limited to, at least one of the following: cell identifier, frequency identifier, RAN notification area, RAN area code, tracking area code, and Public Land Mobile Network (PLMN) identifier.

[0148] Optionally, the dedicated signaling includes at least one of: slice information, RACH time and frequency resources, and random access preamble. Slice information includes: slice identifier, the correspondence between the slice and the second RACH resources, etc.

[0149] Optionally, the slice identifier can also be a slice group identifier, a parameter corresponding to the slice identifier or slice group identifier, a specific parameter (corresponding to the slice information), a specified parameter, or a predetermined parameter. It can also be a slice / service type (SST), a slice index or a slice group index, or an access category, etc.

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

[0151] Optionally, the slice information is information supported by this area and / or neighboring areas.

[0152] Optionally, for a slice indicated by network broadcast or dedicated information, i.e. the supported slice information, the corresponding behavior can be at least one of the following: for a slice that provides services to the UE, the UE can initiate or complete registration, the UE can establish a corresponding Protocol Data Unit (PDU) session, the UE can establish corresponding air interface resources, such as Data Radio Bearer (DRB), and the UE can activate the user plane.

[0153] Optionally, for a slice that is not supported as indicated by a network broadcast or dedicated information, or a slice that is not indicated by a network broadcast or dedicated information, or a slice that is not indicated by a network broadcast or dedicated information, the corresponding behavior can be at least one of the following: the slice is not provided with services by the UE, the UE can initiate or complete registration but the registration fails, the UE cannot initiate or complete registration, the UE cannot trigger or establish the corresponding PDU session, the UE can establish the corresponding PDU session but does not support data transmission, the UE cannot establish the corresponding air interface resources (such as DRB), the UE can establish the corresponding air interface resources (such as DRB) but does not support data transmission, the UE can activate the user plane but does not support data transmission, or the UE cannot activate the user plane.

[0154] Optionally, the dedicated signaling also includes: priority parameters. Priority parameters include at least one of BI information and power boost information. BI information can be a BI adjustment factor, and power boost information can be a power boost step size. Optionally, priority parameters may be slice-specific, and / or non-slice-specific (common).

[0155] Optionally, the second RACH information includes: a second RACH configuration, which is used to configure at least one of the following RACH configuration parameters: RACH resources, RACH type, and RACH priority. RACH resources include at least one of the following: RACH time-frequency resources, random access opportunities, and random access preambles.

[0156] In the first possible design, the second RACH configuration is used to configure at least two sets of RACH configuration parameters, and the second RACH information also includes at least one of the following:

[0157] A selection threshold used to select from at least two sets of RACH configuration parameters. See step 420 for a specific example of the selection threshold.

[0158] In the second possible design, the second RACH configuration includes at least two sets, and the second RACH information also includes:

[0159] Selection indications are used to select from at least two sets of RACH configuration parameters. A specific example of a selection indication is shown in step 420.

[0160] In the third possible design, the second RACH configuration includes at least two sets, and the second RACH information also includes:

[0161] Selection criteria used to select at least two sets of RACH configuration parameters. See step 420 for a specific example of the selection criteria.

[0162] Optionally, the dedicated signaling may further include: a first indication message for indicating whether to use the second RACH message to override the first RACH message.

[0163] It should be noted that, based on at least one parameter among the selection threshold, selection indication, and selection conditions, a set of RACH configuration parameters can be selected from at least two sets for the random access procedure. RACH configuration parameters include at least one of the following: RACH time-frequency resources, random access opportunity, random access preamble, RACH priority, and RACH type.

[0164] This embodiment does not limit the execution order of steps 420 and 440. Step 420 can be executed before step 440, after step 440, or simultaneously with step 440. There is no limitation on this.

[0165] Step 460: Perform a random access procedure using the first RACH information and / or the second RACH information.

[0166] The terminal may independently select or use the first RACH information and / or the second RACH information to perform a random access procedure. Alternatively, the terminal may select or use the first RACH information and / or the second RACH information to perform a random access procedure according to instructions from the network.

[0167] This step includes, but is not limited to, at least one of the following implementation methods:

[0168] The terminal uses the first RACH information to perform a random access procedure.

[0169] Schematic illustration: The terminal ignores the second RACH information in the dedicated signaling, and / or considers the first RACH information in the SIB to have higher priority, and / or applies only the second RACH information in the dedicated signaling. For example, when the dedicated signaling is an RRC reconfiguration message about synchronization, the terminal considers the second RACH information in the dedicated signaling to have higher priority. For example, when the dedicated signaling is an RRC release message, the terminal considers the first RACH information to have higher priority.

[0170] The terminal uses the second RACH information to perform a random access procedure.

[0171] Schematic illustration: The terminal ignores the first RACH information in the SIB, and / or considers the second RACH information in the dedicated signaling to have higher priority, and / or applies only the second RACH information in the dedicated signaling. For example, when the dedicated signaling is an RRC reconfiguration message about synchronization, the terminal considers the second RACH information in the dedicated signaling to have higher priority.

[0172] • If the first condition is met, the terminal selects or uses the first RACH information to perform a random access procedure.

[0173] • If the second condition is met, the terminal selects or uses the second RACH information to perform a random access procedure.

[0174] • If the third condition is met, the terminal selects or uses the first RACH information and the second RACH information to perform a random access procedure.

[0175] Indicatively, a random access procedure is performed using the selection threshold, selection indication, or selection condition configured with the first RACH information and the RACH resources configured with the second RACH information.

[0176] • The terminal uses one set of RACH configuration parameters from at least two sets of RACH configuration parameters, based on the slice information or support for network slices.

[0177] Wherein, at least two sets of RACH configuration parameters are configured by the first RACH information; or, at least two sets of RACH configuration parameters are configured by the second RACH information; or, at least two sets of RACH configuration parameters are configured by the first RACH information and the second RACH information, that is, the first RACH information configures a part of the at least two sets of RACH configuration parameters, and the second RACH information configures the remaining part of the at least two sets of RACH configuration parameters.

[0178] In summary, the method provided in this embodiment allows the terminal to select the first RACH information and / or the second RACH information in the dedicated signaling when both the first RACH information in the SIB and the second RACH information in the dedicated signaling exist simultaneously. This enables the terminal to better utilize the RACH resources suitable for itself among the 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.

[0179] For an embodiment that uses the first RACH information to perform a random access procedure:

[0180] Figure 5 A flowchart of a random access method provided in an exemplary embodiment of this application is shown. This embodiment illustrates the method by way of execution by a terminal. The method includes:

[0181] Step 420: Receive the first RACH information from the system information block;

[0182] The first RACH information is configured with the first RACH resource. For example... Figure 4 Step 420 in the embodiments is described herein and will not be repeated.

[0183] Step 440: Receive the second RACH information in the dedicated signaling;

[0184] The second RACH information is configured with second RACH resources. For example... Figure 4 Step 440 in the embodiment is described herein and will not be repeated here.

[0185] Step 462: If the first condition is met, use the first RACH information to perform the random access procedure;

[0186] This step includes, but is not limited to, at least one of the following implementation methods:

[0187] Method 1. If the priority of the first RACH information is higher than that of the second RACH information, the first RACH information is used to perform the random access procedure;

[0188] If the priority of the first RACH information is higher than that of the second RACH information, the first RACH information shall be used first, and / or the first RACH information shall be applied to perform the random access procedure.

[0189] Method 2. If the usage time and / or validity period of the second RACH information are not within the scope of its use, use the first RACH information to perform a random access procedure;

[0190] In cases where the usage time and / or validity range of the second RACH information are not within the scope of use, the first RACH information shall be used first, and / or the first RACH information shall be applied to perform the random access procedure.

[0191] For example, during the first time period, the first RACH information is used for the random access procedure; during the second time period (the effective time of the second RACH information), the second RACH information is used for the random access procedure.

[0192] Method 3: If the first indication information is used to indicate that the first RACH information should be used first, the first RACH information is used to perform the random access procedure.

[0193] For example, the first indication information is used to indicate that, if the first RACH information is always given priority, the first RACH information should be used to perform the random access procedure.

[0194] Method 4. If the slice information in the first RACH information or the second RACH information is different, the first RACH information is used to perform the random access procedure;

[0195] Method 5. Based on the network slicing support of the terminal device or access network device, use the first RACH information to perform a random access procedure;

[0196] For example, the SIB or dedicated signaling of the first cell carries RACH parameters other than the traditional RACH parameters, but the second cell does not carry RACH parameters other than the traditional RACH parameters. Regardless of whether it is the first cell or the second cell, the random access procedure is performed according to the first RACH information in the SIB.

[0197] Method 6. If the cell or base station sending the second RACH information is not within its coverage or service range, use the first RACH information to perform a random access procedure.

[0198] For example, when a terminal is moving and is located outside the coverage or service range of the cell or base station that sends the second RACH information, it uses the first RACH information to perform a random access procedure.

[0199] In summary, the method provided in this embodiment, when both the first RACH information in the SIB and the second RACH information in the dedicated signaling exist simultaneously, allows the terminal to use the first RACH information to perform a random access procedure based on the currently met triggering conditions. This enables the terminal to better utilize the RACH resources suitable for itself among different RACH information to perform the random access procedure, thereby reducing the time consumed by the random access procedure or improving the success rate of the random access procedure.

[0200] An example of performing a random access procedure using second RACH information:

[0201] Figure 6 A flowchart of a random access method provided in an exemplary embodiment of this application is shown. This embodiment illustrates the method by way of execution by a terminal. The method includes:

[0202] Step 420: Receive the first RACH information from the system information block;

[0203] The first RACH information is configured with the first RACH resource. For example... Figure 4 Step 420 in the embodiments is described herein and will not be repeated.

[0204] Step 440: Receive the second RACH information in the dedicated signaling;

[0205] The second RACH information is configured with second RACH resources. For example... Figure 4 Step 440 in the embodiment is described herein and will not be repeated here.

[0206] Step 464: If the second condition is met, use the second RACH information to perform the random access procedure.

[0207] This step includes, but is not limited to, at least one of the following implementation methods:

[0208] Method 1: If the priority of the second RACH information is higher than that of the first RACH information, the second RACH information is used to perform the random access procedure.

[0209] Method 2. If the second RACH information is valid during the time period of the second RACH information, or within the valid range of the second RACH information, or within the valid time period and valid range of the second RACH information, the second RACH information is used to perform the random access procedure;

[0210] Method 3. If the first indication information indicates that the second RACH information should be used first, the second RACH information shall be used to perform the random access procedure;

[0211] Method 4. If the slice information in the first RACH information or the second RACH information is different, and / or falls within the valid time and / or valid range of the second RACH information, the second RACH information shall be used to perform the random access procedure;

[0212] Method 5. Based on the network slicing support of the terminal device or access network device, use the second RACH information to perform the random access procedure.

[0213] For example, the SIB is sent by a conventional base station, but the enhanced base station B, which sends dedicated signaling, performs a random access procedure according to the second RACH information configured in the dedicated signaling.

[0214] For example, if the RRC release message carries second RACH information, the random access procedure is performed according to the second RACH information.

[0215] For example, if the SIB or special signaling of the first cell carries RACH parameters other than the traditional RACH parameters, but the second cell does not carry RACH parameters other than the traditional RACH parameters, then regardless of whether it is the first cell or the second cell, the random access procedure is performed according to the second RACH information in the special signaling.

[0216] Method 6. Within the coverage or service area of ​​the cell or base station that sends the second RACH information, use the second RACH information to perform a random access procedure.

[0217] For example, if the cell sending the second RACH information is the cell where the terminal is camped, and the terminal is within the coverage area of ​​that cell, it uses the second RACH information to perform a random access procedure.

[0218] In summary, the method provided in this embodiment, when both the first RACH information in the SIB and the second RACH information in the dedicated signaling exist simultaneously, allows the terminal to use the second RACH information to perform a random access procedure based on the currently met triggering conditions. This enables the terminal to better utilize the RACH resources suitable for itself among different RACH information to perform the random access procedure, thereby reducing the time consumed by the random access procedure or improving the success rate of the random access procedure.

[0219] An embodiment for performing a random access procedure using first RACH information and second RACH information:

[0220] Figure 7 A flowchart of a random access method provided in an exemplary embodiment of this application is shown. This embodiment illustrates the method by way of execution by a terminal. The method includes:

[0221] Step 420: Receive the first RACH information from the system information block;

[0222] The first RACH information is configured with the first RACH resource. For example... Figure 4 Step 420 in the embodiments is described herein and will not be repeated.

[0223] Step 440: Receive the second RACH information in the dedicated signaling;

[0224] The second RACH information is configured with second RACH resources. For example... Figure 4 Step 440 in the embodiment is described herein and will not be repeated here.

[0225] Step 466: If the third condition is met, perform a random access procedure using the first RACH information and the second RACH information.

[0226] Optionally, if the first RACH information includes at least two sets of RACH configuration parameters and the second RACH information includes selection information for RACH configuration parameters, the random access procedure is performed using the at least two sets of RACH configuration parameters and the selection information for RACH configuration parameters.

[0227] Optionally, if the second RACH information includes at least two sets of RACH configuration parameters and the first RACH information includes selection information for RACH configuration parameters, the random access procedure is performed using the at least two sets of RACH configuration parameters and the selection information for RACH configuration parameters.

[0228] The selection information includes at least one of the following: selection threshold, selection instruction, and selection condition.

[0229] The selection information is used to select a target configuration parameter from at least two sets of RACH configuration parameters. The target configuration parameter includes, but is not limited to, at least one of the following: RACH time-frequency resources, random access opportunity, random access preamble, RACH type, and RACH priority.

[0230] In summary, the method provided in this embodiment, when both the first RACH information in the SIB and the second RACH information in the dedicated signaling exist simultaneously, allows the terminal to use the first RACH information and the second RACH information to perform a random access procedure based on the currently met triggering conditions. This enables the terminal to better utilize the RACH resources suitable for itself among different RACH information to perform the random access procedure, thereby reducing the time consumed by the random access procedure or improving the success rate of the random access procedure.

[0231] An example of a terminal performing a random access procedure using one of at least two RACH configurations (or types) configured simultaneously:

[0232] Figure 8A flowchart of a random access method provided in an exemplary embodiment of this application is shown. This embodiment illustrates the method by way of execution by a terminal. The method includes:

[0233] Step 420: Receive the first RACH information from the SIB;

[0234] The first RACH information is configured with the first RACH configuration. For example... Figure 4 Step 420 in the embodiments is described herein and will not be repeated.

[0235] Step 440: Receive the second RACH information in the dedicated signaling;

[0236] The second RACH information is configured with a second RACH configuration. For example... Figure 4 Step 440 in the embodiment is described herein and will not be repeated here.

[0237] Step 468: If the triggering conditions are met, perform a random access procedure using one of the two sets of RACH configuration parameters.

[0238] At least two sets of RACH configuration parameters, also 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 first RACH information; or, at least two sets of RACH configuration parameters are configured with second RACH information; or, at least two sets of RACH configuration parameters are configured with both first RACH information and second RACH information.

[0239] At least two sets of RACH configuration parameters include at least two of the following:

[0240] • Public RACH;

[0241] • Rach for slicing;

[0242] · Non-slicing RACH;

[0243] • RACH for 2-step sectioning;

[0244] • RACH for 4-step sectioning;

[0245] • 2-step RACH;

[0246] • 4-step RACH.

[0247] • The random access preamble corresponding to RACH;

[0248] • The time-frequency resources or RO corresponding to RACH;

[0249] The priority parameter corresponding to RACH.

[0250] Optionally, the section-specific RACH includes at least one of a 2-step section-specific RACH and a 4-step section-specific RACH. Optionally, the non-section-specific RACH includes at least one of a 2-step RACH and a 4-step RACH.

[0251] This step includes, but is not limited to, at least one of the following implementation methods:

[0252] Method 1. At least two sets of RACH configuration parameters, including slice-specific RACH and public RACH;

[0253] A slice-specific RACH is a RACH resource dedicated to network slices. For example, there is a RACH resource dedicated to all network slices, a slice-specific RACH dedicated to the 2-step random access procedure (referred to as 2-step slice-specific RACH), and a slice-specific RACH dedicated to the 4-step random access procedure (referred to as 4-step slice-specific RACH).

[0254] Public RACH refers to non-private RACH resources.

[0255] If the fourth condition is met, the terminal performs a random access procedure using a slice-specific RACH; or, if the fifth condition is met, the terminal performs a random access procedure using a public RACH.

[0256] Optionally, the fourth condition includes at least one of the following:

[0257] • The terminal supports slicing;

[0258] • The terminal uses the specified slice;

[0259] • The terminal uses slices of a specified type;

[0260] The terminal uses the same slices as the network-supported slices;

[0261] • The terminal's required slicing is the same as the network's supported slicing;

[0262] • The terminal supports a communication protocol version that is higher than or equal to the predetermined version;

[0263] • The channel quality is above the first threshold, which is used to select between public RACH and slice-specific RACH;

[0264] • The channel quality is higher than the second threshold, which is used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0265] • Receive a second instruction message, which indicates whether to select a slice-specific RACH between a public RACH and a slice-specific RACH;

[0266] • Received third instruction information, which indicates whether to select a 2-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0267] • The random access procedure is a contention-based random access procedure;

[0268] • Channel quality is above the fifth threshold, which is used to select slice-specific RACHs between two sets of RACH resources.

[0269] Optionally, the fifth condition includes at least one of the following:

[0270] • The terminal does not support slicing;

[0271] The terminal did not use the specified slice;

[0272] • The terminal is not using a slice of the specified type;

[0273] The slices used by the terminal are different from the slices supported by the network;

[0274] • The slicing required by the terminal differs from the slicing supported by the network;

[0275] • The terminal supports a communication protocol version that is lower than the predetermined version;

[0276] • Channel quality is below the first threshold, which is used to select between public RACH and slice-specific RACN;

[0277] • Channel quality is below the second threshold, which is used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0278] • Received a fourth instruction message, which indicates whether to select a public RACH or a slice-specific RACH;

[0279] • Received the fifth instruction message, which is used to indicate whether to select a 2-step slice-specific RACH or a RACH other than slice-specific RACH between the two sets of RACH resources;

[0280] • Random access failed using a slice-specific RACH;

[0281] • Random access failed when using a 2-step slice-dedicated RACH, and a 4-step slice-dedicated RACH was not configured;

[0282] • The random access procedure is a non-contention-based random access procedure;

[0283] • Channel quality is below the fifth threshold, which is the threshold used to select slice-specific RACHs between two sets of RACH resources.

[0284] For example, if the second RACH information is configured with a slice-specific RACH and the first RACH information is configured with a public RACH, the terminal uses the slice-specific RACH to perform the random access procedure. For instance, if the terminal supports slice 1, the second RACH information is configured with the RACH corresponding to slice 1, and the first RACH information is configured with a public RACH, the terminal selects the RACH configured in the second RACH information.

[0285] For example, if the first RACH information is configured with a slice-specific RACH and the second RACH information is configured with a public RACH, the terminal uses the slice-specific RACH to perform a random access procedure.

[0286] For example, if the second RACH information is configured with a slice-specific RACH and the first RACH information is not configured with a slice-specific RACH, the terminal uses the slice-specific RACH to perform the random access procedure. For instance, if the terminal supports slice 1, the second RACH information is not configured with a RACH corresponding to slice 1, but the first RACH information is configured with a RACH corresponding to the slice information, the terminal selects the RACH configured in the first RACH information.

[0287] For example, if the first RACH information is configured with a slice-specific RACH but the second RACH information is not configured with a slice-specific RACH, the terminal uses the slice-specific RACH to perform the random access procedure. For instance, if the terminal supports slice 1, the first RACH information does not configure a RACH corresponding to slice 1, but the second RACH information configures a RACH corresponding to the slice information, the terminal selects the RACH configured in the second RACH information.

[0288] For example, if the second RACH information is configured with a slice-specific RACH and falls within the valid time and / or valid range of the second RACH information, the terminal uses the slice-specific RACH to perform a random access procedure. For instance, if the terminal supports slice 1, the second RACH information is configured with the RACH corresponding to slice 1, and the second RACH information meets the valid duration and / or valid area requirements, the terminal selects the RACH indicated in the dedicated information.

[0289] Method 2. At least two sets of RACH configuration parameters, including a 2-step slice-specific RACH and a 4-step slice-specific RACH;

[0290] If the sixth condition is met, the terminal performs a random access procedure using a 2-step slice-dedicated RACH; or, if the seventh condition is met, the terminal performs a random access procedure using a 4-step slice-dedicated RACH.

[0291] Optionally, the sixth condition includes at least one of the following:

[0292] • The terminal uses slices of a specified type;

[0293] The terminal uses the same slices as the network-supported slices;

[0294] • The terminal's required slicing is the same as the network's supported slicing;

[0295] • The terminal supports a communication protocol version that is higher than or equal to the predetermined version;

[0296] • The channel quality is higher than the second threshold, which is used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0297] • The channel quality is above the third threshold, which is used to select between 2-step slice-dedicated RACH and 4-step slice-dedicated RACH;

[0298] • Received the sixth instruction message, which indicates whether to select the 2-step slice-specific RACH between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

[0299] • Received third instruction information, which indicates whether to select a 2-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0300] • The random access procedure is a contention-based random access procedure.

[0301] Optionally, the seventh condition includes at least one of the following:

[0302] • The terminal is not using a slice of the specified type;

[0303] The slices used by the terminal are different from the slices supported by the network;

[0304] • The slicing required by the terminal differs from the slicing supported by the network;

[0305] • The terminal supports a communication protocol version that is lower than the predetermined version;

[0306] • Channel quality is below the second threshold, which is used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0307] • Channel quality is below the third threshold, the second threshold being used to select between 2-step slice-dedicated RACH and 4-step slice-dedicated RACH;

[0308] • Received the seventh instruction message, which indicates whether to select the 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

[0309] Random access failed using a 2-step slice-specific RACH.

[0310] • Received the eighth instruction message, which is used to indicate whether to select a 4-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0311] • The random access procedure is a non-contention-based random access procedure.

[0312] Method 3. At least two sets of RACH configuration parameters, including a 2-step RACH and a 2-step slice-specific RACH;

[0313] If the eighth condition is met, the terminal performs a random access procedure using a 2-step slice-dedicated RACH; or, if the ninth condition is met, the terminal performs a random access procedure using a 2-step RACH.

[0314] Optionally, the eighth condition includes at least one of the following:

[0315] • The terminal uses slices of a specified type;

[0316] The terminal uses the same slices as the network-supported slices;

[0317] • The terminal's required slicing is the same as the network's supported slicing;

[0318] • The terminal supports a communication protocol version that is higher than or equal to the predetermined version;

[0319] • Channel quality is above the fourth threshold, which is used to select between 2-step slice-dedicated RACH and 2-step RACH;

[0320] • Channel quality is above the fifth threshold, which is the threshold used to select slice-specific RACHs between two sets of RACH resources;

[0321] • Received the ninth instruction message, which indicates whether to select the 2-step slice-specific RACH between the 2-step slice-specific RACH and the 2-step RACH;

[0322] • Received third instruction information, which indicates whether to select a 2-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0323] • The random access procedure is a contention-based random access procedure.

[0324] Optionally, the ninth condition includes at least one of the following:

[0325] • The terminal is not using a slice of the specified type;

[0326] The slices used by the terminal are different from the slices supported by the network;

[0327] • The slicing required by the terminal differs from the slicing supported by the network;

[0328] • The terminal supports a communication protocol version that is lower than the predetermined version;

[0329] • Channel quality is below the third threshold, which is the threshold used to select between 2-step slice-dedicated RACH and 2-step RACH;

[0330] • Channel quality is below the second threshold, which is used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0331] • Received the tenth instruction message, which indicates whether to select a 2-step RACH between a 2-step slice-specific RACH and a 2-step RACH;

[0332] Random access failed using a 2-step slice-specific RACH.

[0333] • Random access failed when using a 2-step slice-dedicated RACH, and a 4-step slice-dedicated RACH was not configured;

[0334] • Received the fifth instruction information, which is used to indicate whether to choose between two sets of RACH resources: a 2-step slice-specific RACH or a RACH other than a slice-specific RACH.

[0335] • The random access procedure is a non-contention-based random access procedure.

[0336] Method 4. At least two sets of RACH configuration parameters, including a 4-step RACH and a 4-step slice-specific RACH;

[0337] If the tenth condition is met, a random access procedure is performed using a 4-step slice-specific RACH; or, if the eleventh condition is met, a random access procedure is performed using a 4-step RACH.

[0338] Optionally, the tenth condition includes at least one of the following:

[0339] • The terminal uses slices of a specified type;

[0340] The terminal uses the same slices as the network-supported slices;

[0341] • The terminal's required slicing is the same as the network's supported slicing;

[0342] • The terminal supports a communication protocol version that is higher than or equal to the predetermined version;

[0343] • Channel quality is above the sixth threshold, which is the threshold used to select between 4-step slice-dedicated RACH and 4-step RACH;

[0344] • Received the eleventh instruction message, which is used to indicate whether to select the 4-step slice-specific RACH between the 4-step slice-specific RACH and the 4-step RACH.

[0345] • Channel quality is above the fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources;

[0346] • Received the eighth instruction message, which indicates whether to choose between two sets of RACH resources: 4-step slice-specific RACH or slice-specific RACH.

[0347] • The random access procedure is a contention-based random access procedure.

[0348] Optionally, the eleventh condition includes at least one of the following:

[0349] • The terminal is not using a slice of the specified type;

[0350] The slices used by the terminal are different from the slices supported by the network;

[0351] • The slicing required by the terminal differs from the slicing supported by the network;

[0352] • The terminal supports a communication protocol version that is lower than the predetermined version;

[0353] • Channel quality is below the sixth threshold, which is the threshold used to select between 4-step slice-dedicated RACH and 4-step RACH;

[0354] • Received the twelfth instruction message, which indicates whether to select the 4-step RACH between the 4-step slice-specific RACH and the 4-step RACH;

[0355] Random access failed when using a 4-step slice-specific RACH.

[0356] • Channel quality is below the fifth threshold, which is the threshold used to select slice-specific RACH between two sets of RACH resources;

[0357] Random access failed using a 2-step slice-specific RACH.

[0358] • Random access failed when using a 2-step slice-dedicated RACH, and a 4-step slice-dedicated RACH was not configured;

[0359] • Received the fifth instruction information, which is used to indicate whether to choose between two sets of RACH resources: a 2-step slice-specific RACH or a RACH other than a slice-specific RACH.

[0360] • The random access procedure is a non-contention-based random access procedure.

[0361] It should be noted that the various methods in this embodiment can be freely combined. For example, any two methods can be combined, such as method 1 and method 2, method 1 and method 3, method 1 and method 4, etc.; for example, any three methods can be combined, such as method 1, method 2 and method 3, method 1, method 3 and method 4; for example, all four methods can be combined.

[0362] For example, if at least two RACH configurations include a public RACH, a 2-step slice-specific RACH, and a 4-step slice-specific RACH, then method 1 and method 2 described above will be combined. Or, if at least two RACH configurations include a 2-step RACH, a 2-step slice-specific RACH, and a 4-step slice-specific RACH, then method 2 and method 3 described above will be combined. These are concepts readily understood by those skilled in the art based on the above disclosure and will not be elaborated further.

[0363] In summary, the method provided in this embodiment, when both the first RACH information in the SIB and the second RACH information in the dedicated signaling exist simultaneously, allows the terminal to perform a random access procedure using one set of RACH configuration parameters from at least two sets of RACH configuration parameters based on the slice information or support for the slice. This enables the terminal to better utilize the RACH resources suitable for itself in different RACH information to perform the random access procedure, thereby reducing the time consumed by the random access procedure or improving the success rate of the random access procedure.

[0364] Figure 9 A flowchart of a random access method provided in an exemplary embodiment of this application is shown. This embodiment illustrates the method by way of execution by a terminal. The method includes:

[0365] Step 430: Obtain at least two sets of RACH configuration parameters, which are configured by system information blocks and / or dedicated signaling;

[0366] At least two sets of RACH configuration parameters include at least two of the following:

[0367] • Public RACH;

[0368] • Rach for slicing;

[0369] · Non-slicing RACH;

[0370] • RACH for 2-step sectioning;

[0371] • RACH for 4-step sectioning;

[0372] • 2-step RACH;

[0373] • 4-step RACH;

[0374] ·The preamble corresponding to RACH;

[0375] • The time-frequency resources or RO corresponding to RACH;

[0376] ·RACH corresponds to the priority parameter.

[0377] Optionally, the section-specific RACH includes at least one of a 2-step section-specific RACH and a 4-step section-specific RACH. Optionally, the non-section-specific RACH includes a 2-step RACH and a 4-step RACH.

[0378] The terminal receives an SIB, which contains at least two sets of RACH configuration parameters.

[0379] Alternatively, the terminal receives proprietary signaling, which contains at least two sets of RACH configuration parameters.

[0380] Alternatively, the terminal receives an SIB and dedicated signaling, wherein the SIB is configured with a portion of the RACH resources from at least two sets of RACH configuration parameters, and the dedicated signaling is configured with the remaining portion of the RACH resources from at least two sets of RACH configuration parameters.

[0381] In this case, the SIB and the proprietary signaling are sent from the same cell or base station, or the SIB and the proprietary signaling are sent from different cells or base stations.

[0382] Step 468: If the triggering conditions are met, perform a random access procedure using one of the at least two RACH configurations.

[0383] This step can be referred to. Figure 8 The details of step 468 shown will not be repeated here.

[0384] In summary, the method provided in this embodiment, when at least two sets of RACH configuration parameters exist simultaneously, allows the terminal to perform a random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters based on slice information or support for slices. This enables the terminal to better utilize RACH resources suitable for itself for the random access procedure, reducing the time consumed by the random access procedure or improving the success rate of the random access procedure.

[0385] Based on the above Figure 4 or Figure 5 or Figure 6 or Figure 7 or Figure 8 or Figure 9In an optional embodiment, the terminal's random access behavior in different cells may be the same or different. Specifically, the same behavior may be used to perform the random access procedure in different cells, including the use of first RACH information and / or second RACH information; or, different behavior may be used to perform the random access procedure in different cells, including the use of first RACH information and / or second RACH information.

[0386] For example, when a terminal moves to the second cell range, or when the terminal is handed over / redirected / cell selected / cell reselected to the second cell, the terminal performs a random access procedure in the second cell.

[0387] Schematic illustration: The terminal performs a random access procedure in the second cell using the same behavior as in the first cell; or, the terminal performs a random access procedure in the second cell using different behavior than in the first cell. The behavior during the random access procedure includes: using first RACH information and / or second RACH information.

[0388] For example, within the first cell range, the terminal performs related actions according to the second RACH information. When the terminal moves to the second cell range, it performs related actions according to the first RACH information.

[0389] For example, within the second cell range, the terminal ignores the second RACH information in the proprietary signaling and / or considers the first RACH information in the SIB to have a higher priority. For instance, when the proprietary signaling is an RRC release message, the terminal considers the information in the proprietary signaling to have a higher priority.

[0390] For example, the terminal may ignore the first RACH information in the SIB, and / or consider the second RACH information in the proprietary signaling to have higher priority, and / or apply the second RACH information in the proprietary signaling, and / or apply other RACH indications in the SIB (such as selection thresholds, selection indications, selection conditions, etc.).

[0391] If the validity time and / or validity range conditions of the second RACH information are not met, the terminal ignores the second RACH information in the dedicated signaling (or deletes the second RACH information in the dedicated signaling), considers the first RACH information in the SIB to have higher priority, and / or applies the first RACH information in the SIB.

[0392] If the validity time and / or validity range conditions of the second RACH information are met, the UE considers the second RACH information in the dedicated signaling to have a higher priority, and / or applies the second RACH information in the dedicated signaling.

[0393] For example, if the network instructs the terminal to use the SIB first, the terminal selects the first RACH information in the SIB and performs a random access procedure.

[0394] For example, the terminal reads the first RACH information from 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 first read two types of RACH information and then determine whether to use the first RACH information or the second RACH information; the terminal can also read the first RACH information only if the second RACH information is invalid; the terminal can also read the first RACH information only when it is necessary to use it.

[0395] For example, the terminal performs a random access procedure according to the second RACH information of the proprietary RRC of the first cell in the first time period; the terminal performs a random access procedure according to the first RACH information of the SIB of the second cell in the second time period.

[0396] It should be noted that the above-described method embodiments can be further divided or combined into other embodiments based on the understanding of those skilled in the art. This application will not elaborate on each of these embodiments.

[0397] Figure 10 A flowchart illustrating a priority determination method or conflict resolution method provided in an exemplary embodiment of this application is shown. The method can be executed by a terminal. The method includes:

[0398] Step 520: If a logical channel-based priority is configured, when there is a conflict between a dynamic grant (DG) and at least one configured grant (CG), and the resource priorities are the same or the logical channels with the highest logical channel priority in the resources have the same priority, then the dynamic grant shall be given priority or the dynamic grant shall be considered the priority grant.

[0399] Alternatively, if a logical channel-based priority is configured, when there is a conflict between dynamic authorization and at least one configured authorization, and the resource priorities are the same or the logical channels with the highest logical channel priority in the resources have the same priority, then which authorization takes precedence depends on the UE implementation.

[0400] The relevant communication protocol is described as follows:

[0401] If the MAC entity is configured with lch-basedPrioritization and ifthere 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.

[0402] Optionally, the base station configures configuration information based on logical channel priorities to the terminal. For the same terminal, the base station can also schedule dynamic authorization and configuration authorization simultaneously. When there is a conflict between dynamic authorization and at least one configuration authorization, and the resource priorities of the conflicting dynamic authorization and configuration authorization are the same, or the logical channel with the highest logical priority among the resources of the conflicting dynamic authorization and configuration authorization has the same priority, the terminal determines one of the conflicting dynamic authorization and configuration authorization as the priority authorization according to a first strategy or a first condition.

[0403] The first strategy or first condition includes at least one of the following:

[0404] When there is a conflict between dynamic authorization and at least one configuration authorization, and the conflicting dynamic authorization and configuration authorization have the same resource priority, or the conflicting dynamic authorization and configuration authorization have the same logical channel priority of the highest logical priority among the resources, then dynamic authorization shall take precedence or be considered as the priority authorization.

[0405] If a logical channel-based priority is configured, when there is a conflict between dynamic authorization and at least one configured authorization, and the conflicting dynamic authorization and configured authorization use the same resource, or the conflicting dynamic authorization and configured authorization use the same logical channel with the highest logical priority among the resources, then dynamic authorization shall be given priority or dynamic authorization shall be considered the priority authorization.

[0406] When there is a conflict between dynamic authorization and at least one configuration authorization, and the highest logical priority of the resource priority of the conflicting dynamic authorization and configuration authorization is the same, then it depends on the UE implementation to prioritize one of the authorizations, or to consider the dynamic authorization as the priority authorization, or to prioritize the configuration authorization, or to prioritize the configuration authorization as the priority authorization.

[0407] If a logical channel-based priority is configured, when there is a conflict between a dynamic grant and at least one configured grant, and the conflicting dynamic grant and configured grant have the same resource, or the logical channel with the highest logical priority among the conflicting dynamic grant and configured grant resources has the same priority, then it depends on the UE implementation to prioritize one of the grants, or consider the dynamic grant as the priority grant, or prioritize the configured grant, or prioritize the configured grant as the priority grant.

[0408] When there is a conflict between dynamic granting and at least one configuration granting, and the conflicting dynamic granting and configuration granting use the same resource, or the logical channel with the highest logical priority among the conflicting dynamic granting and configuration granting resources has the same priority, then the UE, based on the base station's indication or configuration, will prioritize dynamic granting, or consider dynamic granting as the priority granting, or prioritize configuration granting, or prioritize configuration granting as the priority granting. The base station's configuration includes at least one of selection conditions and selection thresholds for prioritizing dynamic granting or configuration granting.

[0409] Figure 11 A flowchart illustrating a priority determination method or conflict resolution method provided in an exemplary embodiment of this application is shown. The method can be executed by a terminal. The method includes:

[0410] Step 620: If multiple resource conflicts exist, such as multiple Physical Uplink Shared Channel (PUSCH) or Uplink Scheduling (UL-grant) conflicts, and if at least some of these resources do not have logical channels to be transmitted that are multiplexed or can be multiplexed on these resources, then these resources have the same priority, and / or, these resources have a lower priority than the priority of other resources whose logical channels to be transmitted are multiplexed or can be multiplexed, or the priority of scheduling requests (SRs), and / or, these resources have the lowest priority.

[0411] Alternatively, if a logical channel-based priority is configured, and if there are multiple resource conflicts, such as multiple PUSCH or UL-grant conflicts, if at least some of these resources do not have logical channels to be transmitted that are multiplexed or can be multiplexed on that resource, then these resources have the same priority, and / or, these resources have a lower priority than the priority of other resources whose logical channels to be transmitted are multiplexed or can be multiplexed, or the priority of the SR, and / or, these resources have the lowest priority.

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

[0413] The first type of resource is a resource in which no logical channel to be transmitted is multiplexed among multiple conflicting resources. Alternatively, the first type of resource is a resource in which no logical channel to be transmitted can (or is able to) be multiplexed among multiple conflicting resources.

[0414] The second type of resource is a resource in which, among multiple conflicting resources, a logical channel to be transmitted is multiplexed on that resource. Alternatively, the second type of resource is a resource in which, among multiple conflicting resources, a logical channel to be transmitted can (or is able to) be multiplexed on that resource. Alternatively, the second type of resource is an SR, or the PUCCH resource corresponding to an SR.

[0415] The second strategy or second condition includes at least one of the following:

[0416] If multiple resource conflicts exist, including at least two Type I resources, the terminal determines that at least two Type I resources have the same priority.

[0417] If multiple resource conflicts exist, including Type I resources and Type II resources, the terminal determines that the priority of Type I resources is lower than that of Type II resources.

[0418] If multiple resource conflicts exist, including Type I resources and Type II resources, the terminal determines that Type I resources have the lowest priority.

[0419] Among these resources, the resources can be PUSCH resources and / or resources indicated by uplink scheduling and / or PUCCH resources.

[0420] Optionally, the priority can be the priority of a resource, the priority of a logical channel, or the priority of the logical channel with the highest priority among the resources.

[0421] Figure 12 A flowchart illustrating a data transmission method provided in an exemplary embodiment of this application is shown. This method can be executed by a terminal. The method includes:

[0422] Step 720: If a configuration licensed retransmission timer (cg-RetransmissionTimer) is configured, or if access / operation is in an unlicensed band, determine the preferred transmission according to the third strategy or third condition.

[0423] This step includes at least one of the following three methods:

[0424] Method 1. When cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, the UE prioritizes the transmission of low-priority uplink resources, or the transmission of Hybrid Automatic Repeat Request (HARQ) processes containing incompletely transmitted Medium Access Control Protocol Data Units (MAC PDUs), or the transmission of resources containing incompletely transmitted MAC PDUs. Alternatively, the UE prioritizes new transmissions. Optionally, the priority between this transmission and other retransmissions depends on the UE implementation, or one of them is predefined, or it is determined based on logical channel priority (e.g., the one with higher priority takes precedence).

[0425] Optionally, the first uplink transmission includes at least one of the following:

[0426] Transmission of low-priority uplink resources;

[0427] The transmission of the HARQ process containing the incompletely transmitted MAC PDU;

[0428] Transfer of resources containing incompletely transferred MAC PDUs.

[0429] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both new transmission and first uplink transmission exist simultaneously, the UE shall prioritize the first uplink transmission.

[0430] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case of simultaneous new transmission and first uplink transmission, the UE implementation may prioritize one of the new transmission and the first uplink transmission.

[0431] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both new transmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission and first uplink transmission according to predefined information.

[0432] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both new transmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission and first uplink transmission based on logical channel priority (e.g., the one with higher priority takes precedence).

[0433] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both retransmission and first uplink transmission exist simultaneously, the UE shall prioritize the first uplink transmission.

[0434] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case of simultaneous retransmission and first uplink transmission, the UE implementation may prioritize either the retransmission or the first uplink transmission.

[0435] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if both retransmission and the first uplink transmission exist simultaneously, the UE will prioritize one of the retransmission and the first uplink transmission according to predefined information.

[0436] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if retransmission and first uplink transmission exist simultaneously, the UE will prioritize one of the retransmission and first uplink transmission based on logical channel priority (e.g., the one with higher priority takes precedence).

[0437] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if new transmission, retransmission and first uplink transmission exist simultaneously, the UE shall prioritize the first uplink transmission.

[0438] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case of simultaneous new transmission, retransmission and first uplink transmission, the UE implementation will prioritize one of the new transmission, retransmission and first uplink transmission.

[0439] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if new transmission, retransmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission, retransmission and first uplink transmission according to predefined information.

[0440] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if new transmission, retransmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission, retransmission and first uplink transmission based on logical channel priority (e.g., the one with higher priority takes precedence).

[0441] Among them, new transmission refers to the first transmission or initial transmission of data in the (uplink) HARQ process, while retransmission refers to data that is not the first transmission in the (uplink) HARQ process, or data that is retransmitted after a failure or retransmitted after a failure.

[0442] Method 2. When cg-RetransmissionTimer is configured, or when the unlicensed band is accessing / operating, the UE considers the transmission of the preferred uplink resource as a retransmission. Optionally, when multiple retransmissions exist, which one is prioritized depends on the UE implementation, or one of them is predefined, or it is determined based on logical channel priority (such as the one with higher priority).

[0443] In Method 2, the first uplink transmission is considered a retransmission. Specific optional implementations include the following:

[0444] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, the UE prioritizes retransmission or retransmission of uplink resources.

[0445] Optionally, when configuring cg-RetransmissionTimer, or when unlicensed band access / operation is enabled, if the UE has multiple retransmissions at the same time, the implementation of the UE will prioritize one of the multiple retransmissions.

[0446] Optionally, when cg-RetransmissionTimer is configured, or when the unlicensed band is accessing / operating, if the UE has multiple retransmissions at the same time, the UE will prioritize one of the multiple retransmissions according to predefined information.

[0447] Optionally, when cg-RetransmissionTimer is configured, or when the unlicensed band is accessing / operating, if the UE has multiple retransmissions at the same time, the UE will prioritize one of the multiple retransmissions based on logical channel priority (e.g., higher priority takes precedence).

[0448] Method 3. When configuring cg-RetransmissionTimer, or when unlicensed band access / operation is enabled, the UE considers the transmission of the preferred uplink resource as a retransmission when selecting the preferred HARQ process. Optionally, when multiple retransmissions exist, which one is prioritized depends on the UE implementation, or one of them is predefined, or it is based on logical channel priority (e.g., the one with higher priority is prioritized).

[0449] In method three, the first uplink transmission is considered a retransmission. Specific optional implementations include the following:

[0450] Optionally, when cg-RetransmissionTimer is configured, or when the unlicensed band is accessing / operating, the UE prioritizes the transmission of the first HARQ process, which is a HARQ process with retransmission or uplink resource retransmission.

[0451] Optionally, when configuring cg-RetransmissionTimer, or when unlicensed band access / operation is enabled, if the UE has multiple first HARQ processes simultaneously, the implementation of the UE will determine which of the multiple first HARQ processes will be prioritized for transmission.

[0452] Optionally, when cg-RetransmissionTimer is configured, or when the unlicensed band is accessing / operating, if the UE has multiple first HARQ processes at the same time, the UE will prioritize the transmission of one of the multiple first HARQ processes according to predefined information.

[0453] Optionally, when cg-RetransmissionTimer is configured, or when the UE is accessing / operating in an unlicensed band, if the UE has multiple first HARQ processes at the same time, the UE will prioritize one of the multiple first HARQ processes for transmission based on logical channel priority (e.g., higher priority takes precedence).

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

[0455] The relevant communication protocol is described as follows:

[0456] Before initial transmissions, the UE shall prioritize the transmission for which MAC PDU is obtanied and the obtained MAC PDU has not been completely performed;

[0457] Or,

[0458] The UE shall prioritize the transmission for which the obtained MACPDU has not been completely performed before initial transmissions.

[0459] Figure 13 A block diagram of a random access device provided in an exemplary embodiment of this application is shown. This random access device can be implemented as a terminal or part of a terminal. The device includes:

[0460] The receiving module 920 is used to receive the first RACH information in the system information block; and to receive the second RACH information in the dedicated signaling.

[0461] The random access module 940 is used to perform a random access procedure in the first cell using the first RACH information and / or the second RACH information.

[0462] In one possible design of this embodiment, the random access module 940 is configured to execute the random access procedure using the first RACH information; or, using the second RACH information; or, if a first condition is met, to execute the random access procedure using the first RACH information; or, if a second condition is met, to execute the random access procedure using the second RACH information; or, if a third condition is met, to execute the random access procedure using both the first RACH information and the second RACH information.

[0463] In one possible design of this embodiment, the random access module 940 is configured to: execute the random access procedure using the first RACH information when the priority of the first RACH information is higher than the priority of the second RACH information; or execute the random access procedure using the first RACH information when it is not within the valid time and / or valid range of the second RACH information; or execute the random access procedure using the first RACH information when first indication information indicates that the first RACH information should be used preferentially; or execute the random access procedure using the first RACH information when the slice information in the first RACH information or the second RACH information is different; or execute the random access procedure using the first RACH information according to the network slice support of the device or access network equipment; or execute the random access procedure using the first RACH information when it is not within the coverage or service range of the cell or base station sending the second RACH information.

[0464] In one possible design of this embodiment, the random access module 940 is configured to: execute the random access procedure using the second RACH information when the priority of the second RACH information is higher than that of the first RACH information; or execute the random access procedure using the second RACH information when it falls within the valid time or valid range of the second RACH information; or execute the random access procedure using the second RACH information when the first indication information indicates that the second RACH information should be used preferentially; or execute the random access procedure using the second RACH information when the slice information in the first RACH information or the second RACH information is different, and / or falls within the valid time and / or valid range of the second RACH information; or execute the random access procedure using the second RACH information according to the network slice support of the device or access network equipment; or execute the random access procedure using the second RACH information within the coverage or service range of the cell or base station that sent the second RACH information.

[0465] 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 the RACH configuration parameters when the first RACH information includes at least two sets of RACH configurations and the second RACH information includes selection information of the RACH configuration parameters; or, when 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, it uses the at least two sets of RACH configurations and the selection information of the RACH configuration parameters to perform the random access procedure; wherein the selection information includes at least one of: selection threshold, selection indication, and selection condition.

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

[0467] The random access module 940 is used to execute the random access process using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering conditions are met.

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

[0469] The random access module 940 is configured to perform the random access procedure using the slice-specific RACH when the fourth condition is met; or, when the fifth condition is met, to perform the random access procedure using the public RACH.

[0470] In one possible design of this embodiment, the fourth condition includes at least one of the following:

[0471] The device supports slicing;

[0472] The device uses a specified slice;

[0473] The device uses a specified type of slice;

[0474] The device uses the same slices as the network-supported slices;

[0475] The required slices for the device are the same as the network-supported slices;

[0476] The device supports a communication protocol version that is higher than or equal to a predetermined version;

[0477] The channel quality is higher than a first threshold, which is a threshold used to select between the public RACH and the slice-specific RACH;

[0478] The channel quality is higher than a second threshold, which is a threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0479] The channel quality is higher than a fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources;

[0480] Upon receiving a second instruction message, the second instruction message is used to instruct the selection of the slice-specific RACH between the public RACH and the slice-specific RACH;

[0481] Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or the slice-specific RACH between the two sets of RACH resources;

[0482] The random access procedure is a contention-based random access procedure.

[0483] In one possible design of this embodiment, the fifth condition includes at least one of the following:

[0484] The device does not support slicing;

[0485] The device did not use the specified slice;

[0486] The device does not use the specified type of slice;

[0487] The slicing used by the device is different from the network-supported slicing;

[0488] The required slices of the device are different from the network-supported slices;

[0489] The device supports a communication protocol version that is lower than the predetermined version;

[0490] The channel quality is below a first threshold, which is a threshold used to select between the public RACH and the slice-specific RACN;

[0491] The channel quality is below a second threshold, which is a threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0492] The channel quality is below a fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources;

[0493] A fourth instruction message is received, the fourth instruction message being used to instruct the selection of the public RACH between the public RACH and the slice-specific RACH;

[0494] Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select the two-step slice-specific RACH or a RACH other than the slice-specific RACH between the two sets of RACH resources;

[0495] Random access using the slice-specific RACH failed;

[0496] Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured.

[0497] The random access procedure is a non-contention-based random access procedure.

[0498] 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;

[0499] The random access module 940 is used to execute the random access procedure using the 2-step slice-dedicated RACH when the sixth condition is met; or, when the seventh condition is met, to execute the random access procedure using the 4-step slice-dedicated RACH.

[0500] In one possible design of this embodiment, the sixth condition includes at least one of the following:

[0501] The device uses a specified type of slice;

[0502] The device uses the same slices as the network-supported slices;

[0503] The required slices for the device are the same as the network-supported slices;

[0504] The device supports a communication protocol version that is higher than or equal to a predetermined version;

[0505] The channel quality is higher than the second threshold, which is a threshold used to select the two-step slice-specific RACH between two sets of RACH resources;

[0506] The channel quality is higher than a third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

[0507] Upon receiving a sixth instruction message, the sixth instruction message is used to indicate that the 2-step slice-dedicated RACH be selected between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

[0508] Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or slice-specific RACH between the two sets of RACH resources;

[0509] The random access procedure is a contention-based random access procedure.

[0510] In one possible design of this embodiment, the seventh condition includes at least one of the following:

[0511] The device does not use the specified type of slice;

[0512] The slicing used by the device is different from the network-supported slicing;

[0513] The required slices of the device are different from the network-supported slices;

[0514] The device supports a communication protocol version that is lower than the predetermined version;

[0515] The channel quality is below a second threshold, which is a threshold used to select the two-step slice-dedicated RACH between two sets of RACH resources;

[0516] The channel quality is below the third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH;

[0517] Upon receiving a seventh instruction message, the seventh instruction message is used to instruct the selection of the 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH.

[0518] Random access using the two-step slice-specific RACH failed;

[0519] Upon receiving the eighth instruction information, the eighth instruction information is used to indicate whether to select a 4-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0520] The random access procedure is a non-contention-based random access procedure.

[0521] 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-specific RACH;

[0522] The random access module 940 is used to execute the random access procedure using the 2-step slice-specific RACH when the eighth condition is met; or, when the ninth condition is met, to execute the random access procedure using the 2-step RACH.

[0523] In one possible design of this embodiment, the eighth condition includes at least one of the following:

[0524] The device uses a specified type of slice;

[0525] The device uses the same slices as the network-supported slices;

[0526] The required slices for the device are the same as the network-supported slices;

[0527] The device supports a communication protocol version that is higher than or equal to a predetermined version;

[0528] The channel quality is above a fourth threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 2-step RACH;

[0529] The channel quality is above the fifth threshold, which is a threshold used to select a slice-specific RACH between two sets of RACH resources;

[0530] Upon receiving a ninth instruction message, the ninth instruction message is used to instruct the selection of the two-step slice-specific RACH between the two-step slice-specific RACH and the two-step RACH;

[0531] Upon receiving a third instruction, the third instruction is used to indicate whether to select a two-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0532] The random access procedure is a contention-based random access procedure.

[0533] In one possible design of this embodiment, the ninth condition includes at least one of the following:

[0534] The device does not use the specified type of slice;

[0535] The slicing used by the device is different from the network-supported slicing;

[0536] The required slices of the device are different from the network-supported slices;

[0537] The device supports a communication protocol version that is lower than the predetermined version;

[0538] The channel quality is below a third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 2-step RACH;

[0539] The channel quality is below the second threshold, which is the threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources;

[0540] Upon receiving a tenth instruction message, the tenth instruction message is used to indicate the selection of the two-step RACH between the two-step slice-specific RACH and the two-step RACH;

[0541] Random access using the two-step slice-specific RACH failed;

[0542] Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured.

[0543] Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select between two sets of RACH resources a 2-step slice-specific RACH or a RACH other than a slice-specific RACH.

[0544] The random access procedure is a non-contention-based random access procedure.

[0545] 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-specific RACH;

[0546] The random access module 940 is used to execute the random access procedure using the 4-step slice-specific RACH when the tenth condition is met; or, when the eleventh condition is met, to execute the random access procedure using the 4-step RACH.

[0547] In one possible design of this embodiment, the tenth condition includes at least one of the following:

[0548] The device uses a specified type of slice;

[0549] The device uses the same slices as the network-supported slices;

[0550] The required slices for the device are the same as the network-supported slices;

[0551] The device supports a communication protocol version that is higher than or equal to a predetermined version;

[0552] The channel quality is above the sixth threshold, which is a threshold used to select between the 4-step slice-dedicated RACH and the 4-step RACH;

[0553] Upon receiving the eleventh instruction message, the eleventh instruction message is used to indicate the selection of the four-step slice-specific RACH between the four-step slice-specific RACH and the four-step RACH.

[0554] The channel quality is above the fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources;

[0555] Upon receiving the eighth instruction information, the eighth instruction information is used to indicate whether to select between two sets of RACH resources: 4-step slice-specific RACH or slice-specific RACH.

[0556] The random access procedure is a contention-based random access procedure.

[0557] Random access failed when using a 2-step slice-specific RACH.

[0558] Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH is configured.

[0559] In one possible design of this embodiment, the eleventh condition includes at least one of the following:

[0560] The device does not use the specified type of slice;

[0561] The slicing used by the device is different from the network-supported slicing;

[0562] The required slices of the device are different from the network-supported slices;

[0563] The device supports a communication protocol version that is lower than the predetermined version;

[0564] The channel quality is below the sixth threshold, which is a threshold used to select between the 4-step slice-dedicated RACH and the 4-step RACH;

[0565] Upon receiving the twelfth instruction message, the twelfth instruction message is used to indicate the selection of the 4-step RACH between the 4-step slice-specific RACH and the 4-step RACH;

[0566] Random access failed when using the 4-step slice-specific RACH.

[0567] The channel quality is below the fifth threshold, which is a threshold used to select slice-specific RACH between two sets of RACH resources;

[0568] Random access using the two-step slice-specific RACH failed;

[0569] Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured.

[0570] Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select between two sets of RACH resources a 2-step slice-specific RACH or a RACH other than a slice-specific RACH.

[0571] The random access procedure is a non-contention-based random access procedure.

[0572] In one possible design of this embodiment, the at least two sets of RACH configuration parameters are configured by 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 configuration.

[0573] 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, the behavior including the behavior of using the first RACH information and / or the second RACH information; or, to perform the random access procedure using different behaviors in different cells, the behavior including the behavior of using the first RACH information and / or the second RACH information.

[0574] In one possible design of this embodiment, the system information block is SIB1; or, the system information block is another SIB besides SIB1; or, the system information block is SIB1 and other SIBs besides SIB1.

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

[0576] The first RACH information corresponds to at least one of the following: usage range, cell, region, PLMN, registration area, and tracking area information.

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

[0578] Slice information;

[0579] Rollback instruction BI information;

[0580] Power boost information;

[0581] RACH time and frequency resources;

[0582] Random access pilot.

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

[0584] The first RACH configuration is used to configure the first RACH resource.

[0585] 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 the following:

[0586] A selection threshold used to select at least two sets of RACH configuration parameters;

[0587] Selection indication for selecting the at least two sets of RACH configuration parameters;

[0588] Selection criteria used to select the at least two sets of RACH configuration parameters.

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

[0590] Dedicated Radio Resource Control (RRC) messages;

[0591] The dedicated RRC message includes: an RRC reconfiguration message, or an RRC release message.

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

[0593] The effective duration corresponding to the second RACH information.

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

[0595] The second RACH information corresponds to at least one of the following: effective range, cell, region, public land mobile network (PLMN), registration area, and tracking area information.

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

[0597] Slice information;

[0598] Revert BI instruction information;

[0599] Power boost information;

[0600] RACH time and frequency resources;

[0601] Random access preamble.

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

[0603] The second RACH configuration is used to configure the second RACH resource.

[0604] 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:

[0605] A selection threshold used to select at least two sets of RACH configuration parameters;

[0606] Selection indicator used to select at least two sets of RACH configuration parameters;

[0607] Selection criteria used to choose from at least two sets of RACH configuration parameters.

[0608] In one possible design of this embodiment, the selection threshold includes at least one of the following:

[0609] The first threshold is used to select between public RACH and slice-specific RACH;

[0610] The second threshold is used to select a 2-step slice-specific RACH between two sets of RACH resources;

[0611] The third threshold is used to select between 2-step slice-specific RACH and 4-step slice-specific RACH;

[0612] The fourth threshold is used to select between a 2-step slice-specific RACH and a 2-step RACH.

[0613] The fifth threshold is used to select a slice-specific RACH between two sets of RACH resources;

[0614] The sixth threshold is used to select between a 4-step slice-specific RACH and a 4-step RACH.

[0615] In one possible design of this embodiment, the selection indication includes at least one of the following:

[0616] The second instruction information is used to select the slice-specific RACH between the public RACH and the slice-specific RACH;

[0617] The third instruction information is used to indicate whether to choose a 2-step slice-specific RACH or a slice-specific RACH between the two sets of RACH resources;

[0618] The fourth instruction information is used to select the public RACH between the public RACH and the slice-specific RACH;

[0619] The fifth instruction is used to indicate whether to select a 2-step slice-specific RACH or a RACH other than slice-specific RACH between the two sets of RACH resources;

[0620] The sixth instruction information is used to indicate the threshold for selecting the 2-step slice-specific RACH between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

[0621] The seventh instruction information is used to indicate the threshold for selecting the 4-step slice-specific RACH between the 2-step slice-specific RACH and the 4-step slice-specific RACH;

[0622] The eighth instruction information is used to indicate whether to select the 4-step slice-specific RACH or slice-specific RACH between the two sets of RACH resources;

[0623] The ninth instruction information is used to indicate the selection of the two-step slice-specific RACH between the two-step slice-specific RACH and the two-step RACH;

[0624] The tenth instruction information is used to indicate the selection of the two-step RACH between the two-step slice-specific RACH and the two-step RACH;

[0625] The eleventh instruction is used to indicate whether to select a 4-step slice-specific RACH between the 4-step slice-specific RACH and the 4-step RACH.

[0626] The twelfth instruction is used to indicate whether to select 4-step RACH between 4-step slice-specific RACH and 4-step RACH.

[0627] In one possible design of this embodiment, the selection conditions include at least one of the following:

[0628] In cases where a non-slice, a non-specified slice, a specified slice and a network-supported slice do not match, or a required slice and a network-supported slice do not match, select a non-slice dedicated RACH.

[0629] In the case where the slice or the specified slice or the specified slice and the network-supported slice match, or the required slice and the network-supported slice match, select a slice-specific RACH;

[0630] In the case of a slice of a specified type or a slice of the specified type that matches a slice supported by the network, select the slice-specific RACH;

[0631] In the event that a slice of a non-specified type, a slice of the specified type, and a network-supported slice do not match, or a required slice and a network-supported slice do not match, select the common RACH.

[0632] In the case of a slice of the specified type, or a slice of the specified type and a network-supported slice, or a required slice and a network-supported slice, select a 2-step slice-specific RACH;

[0633] In the event that the non-specified type of slice, the specified type of slice, and the network-supported slice do not match, or the required slice and the network-supported slice do not match, select the 4-step slice-specific RACH;

[0634] In the case that the specified type of slice, or the specified type of slice, and the network-supported slice match, or the required slice and the network-supported slice match, select 2-step RACH;

[0635] In the event that the non-specified type slice, the specified type slice, and the network-supported slice do not match, or the required slice and the network-supported slice do not match, select 4-step RACH;

[0636] In the event that the first type of RACH fails, or the specified type slice and the network-supported slice do not match, or the required slice and the network-supported slice do not match, the public RACH is selected;

[0637] If the first type of RACH fails and the second type of RACH is not configured, the public RACH is selected;

[0638] In the event that the first type of RACH fails and the second type of RACH is configured, the 4-step slice-specific RACH is selected;

[0639] When the device supports slicing, select the slicing-specific RACH, the 2-step slicing-specific RACH, or the 4-step slicing-specific RACH;

[0640] If the device does not support slicing, select the non-slicing dedicated RACH, the common RACH, the 2-step RACH, or the 4-step RACH;

[0641] If the network supports slicing, select the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH;

[0642] In the case of a slice not supported by the network, select the non-slice-specific RACH, the public RACH, the 2-step RACH, or the 4-step RACH;

[0643] When the slice used by the device is the same as the network-supported slice, select the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH;

[0644] If the slice used by the device is different from the network-supported slice, select the non-slice-specific RACH, the public RACH, the 2-step RACH, or the 4-step RACH;

[0645] If the communication protocol version supported by the device is higher than the predetermined version, select the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH.

[0646] If the communication protocol version supported by the device is lower than the predetermined version, select the non-slice dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH;

[0647] When the random access procedure is a contention-based random access procedure, the slice-specific RACH, the two-step slice-specific RACH, or the four-step slice-specific RACH shall be selected.

[0648] When the random access procedure is a non-contention-based random access procedure, the non-slice-dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH are selected.

[0649] In the case that the random access procedure is a contention-based random access procedure, the slice-specific RACH, the two-step slice-specific RACH, or the two-step common RACH shall be selected;

[0650] In the case that the random access procedure is a non-contention-based random access procedure, the non-slice-dedicated RACH, the public RACH, the 2-step RACH, the 4-step RACH, or the 4-step slice-dedicated RACH are selected.

[0651] When the random access procedure is a non-contention-based random access procedure, the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH shall be selected.

[0652] In the case that the random access procedure is a contention-based random access procedure, the non-slice-dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH are selected.

[0653] In another embodiment, the receiving module 920 is configured to acquire at least two sets of RACH configuration parameters, wherein the at least two sets of RACH configuration parameters are configured by system information blocks and / or dedicated signaling;

[0654] The random access module 940 is used to execute a random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when a triggering condition is met. The function of the random access module 940 during the execution of the random access procedure can be found in [reference needed]. Figure 13 The details of the implementation examples will not be repeated here.

[0655] Figure 14 This illustration shows a block diagram of a priority determination apparatus, conflict resolution apparatus, or data transmission apparatus provided in an exemplary embodiment of this application. The apparatus is implemented as part of a terminal or a Medium Access Control (MAC) entity within the terminal. The apparatus includes:

[0656] The processing module 1020 is configured to prioritize dynamic grant or consider dynamic grant as the priority grant if a priority based on logical channels is configured, and there is a conflict between dynamic grant (DG) and at least one configured grant (CG), and the resource priorities are the same or the logical channels with the highest logical channel priority in the resources have the same priority.

[0657] Alternatively, if a logical channel-based priority is configured, when there is a conflict between dynamic authorization and at least one configured authorization, and the resource priorities are the same or the logical channels with the highest logical channel priority in the resources have the same priority, then the processing module 1020 determines which authorization to prioritize based on its own implementation.

[0658] The relevant communication protocol is described as follows:

[0659] If the MAC entity is configured with lch-basedPrioritization and ifthere 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.

[0660] Optionally, the base station configures configuration information based on logical channel priorities to the terminal. For the same terminal, the base station can also schedule dynamic authorization and configuration authorization simultaneously. When there is a conflict between dynamic authorization and at least one configuration authorization, and the resource priorities of the conflicting dynamic authorization and configuration authorization are the same, or the logical channel with the highest logical priority among the resources of the conflicting dynamic authorization and configuration authorization has the same priority, the terminal determines one of the conflicting dynamic authorization and configuration authorization as the priority authorization according to a first strategy or a first condition.

[0661] The first strategy or first condition includes at least one of the following:

[0662] When there is a conflict between dynamic authorization and at least one configuration authorization, and the resource priorities of the conflicting dynamic authorization and configuration authorization are the same, or the logical channel with the highest logical priority among the conflicting dynamic authorization and configuration authorization resources has the same priority, then the processing module 1020 is used to prioritize dynamic authorization or consider dynamic authorization as the priority authorization.

[0663] If a priority based on logical channels is configured, when there is a conflict between dynamic authorization and at least one configuration authorization, and the conflicting dynamic authorization and configuration authorization have the same resource, or the conflicting dynamic authorization and configuration authorization have the same priority of the logical channel with the highest logical priority among the resources, then the processing module 1020 is used to prioritize dynamic authorization or consider dynamic authorization as the priority authorization.

[0664] When there is a conflict between dynamic authorization and at least one configuration authorization, and the highest logical priority of the resource priority of the conflicting dynamic authorization and configuration authorization is the same, the processing module 1020 is used to prioritize one of the authorizations, or consider the dynamic authorization as the priority authorization, or prioritize the configuration authorization, or prioritize the configuration authorization as the priority authorization, depending on its own implementation.

[0665] If a logical channel-based priority is configured, when there is a conflict between a dynamic authorization and at least one configuration authorization, and the conflicting dynamic authorization and configuration authorization have the same resource, or the logical channel with the highest logical priority among the conflicting dynamic authorization and configuration authorization resources has the same priority, then the processing module 1020 is used to prioritize one of the authorizations, or consider the dynamic authorization as the priority authorization, or prioritize the configuration authorization, or prioritize the configuration authorization as the priority authorization, depending on its own implementation.

[0666] When there is a conflict between dynamic authorization and at least one configuration authorization, and the conflicting dynamic authorization and configuration authorization involve the same resource, or the logical channel with the highest logical priority among the conflicting dynamic authorization and configuration authorization resources has the same priority, then the processing module 1020 is configured to, depending on its own implementation based on the base station's indication or configuration, prioritize dynamic authorization, or consider dynamic authorization as the priority authorization, or prioritize configuration authorization, or prioritize configuration authorization as the priority authorization. The base station configuration includes at least one of selection conditions and selection thresholds for prioritizing dynamic authorization or configuration authorization.

[0667] In another embodiment, the processing module 1020 is configured to, if there are multiple resource conflicts, such as multiple Physical Uplink Shared Channel (PUSCH) or Uplink-grant conflicts, and if at least some of these resources do not have logical channels to be transmitted that are multiplexed or can be multiplexed on the resource, then these resources have the same priority, and / or, these resources have a lower priority than the priority of other resources whose logical channels to be transmitted are multiplexed or can be multiplexed, or the priority of scheduling requests (SRs).

[0668] Alternatively, if a logical channel-based priority is configured, and if there are multiple resource conflicts, such as multiple PUSCH or UL-grant conflicts, if at least some of these resources do not have logical channels to be transmitted that are multiplexed or can be multiplexed on that resource, then these resources have the same priority, and / or, these resources have a lower priority than the priority of other resources whose logical channels to be transmitted are multiplexed or can be multiplexed, or the priority of the SR, and / or, these resources have the lowest priority.

[0669] Optionally, if there are multiple resource (or uplink resource) conflicts, the processing module 1020 is used to determine the priority between the first type of resources according to the second strategy or the second condition, or the priority between the first type of resources and the second type of resources, or to determine the priority of the first type of resources.

[0670] The first type of resource is a resource in which no logical channel to be transmitted is multiplexed among multiple conflicting resources. Alternatively, the first type of resource is a resource in which no logical channel to be transmitted can (or is able to) be multiplexed among multiple conflicting resources.

[0671] The second type of resource is a resource in which, among multiple conflicting resources, a logical channel to be transmitted is multiplexed on that resource. Alternatively, the second type of resource is a resource in which, among multiple conflicting resources, a logical channel to be transmitted can (or is able to) be multiplexed on that resource. Alternatively, the second type of resource is an SR, or the PUCCH resource corresponding to an SR.

[0672] The second strategy or second condition includes at least one of the following:

[0673] If there are multiple resource conflicts, including at least two first-type resources, the processing module 1020 is used to determine that at least two first-type resources have the same priority.

[0674] If there are multiple resource conflicts, including first-type resources and second-type resources, the processing module 1020 is used to determine that the priority of the first-type resources is lower than the priority of the second-type resources.

[0675] If there are multiple resource conflicts, including first-type resources and second-type resources, the processing module 1020 is used to determine that the first-type resources have the lowest priority.

[0676] Among these resources, the resources can be PUSCH resources and / or resources indicated by uplink scheduling and / or PUCCH resources.

[0677] Optionally, the priority can be the priority of a resource, the priority of a logical channel, or the priority of the logical channel with the highest priority among the resources.

[0678] The processing module 1020 is used to determine the preferred transmission according to a third strategy or third condition when cg-RetransmissionTimer is configured, or when an unlicensed band is accessed / operating.

[0679] This step includes at least one of the following three methods:

[0680] Method 1. Processing module 1020, when configuring cg-RetransmissionTimer or in the case of unlicensedband access / operation, compares new transmissions and prioritizes the transmission of low-priority uplink resources, or prioritizes the transmission of Hybrid Automatic Repeat Request (HARQ) processes containing incompletely transmitted Medium Access Control Protocol Data Units (MACPDUs), or prioritizes the transmission of resources containing incompletely transmitted MAC PDUs. Alternatively, the UE prioritizes new transmissions. Optionally, the priority between this transmission and other retransmissions depends on the UE implementation, or is predefined, or determined based on logical channel priority (e.g., the higher-priority one takes precedence).

[0681] Optionally, the first uplink transmission includes at least one of the following:

[0682] Transmission of low-priority uplink resources;

[0683] The transmission of the HARQ process containing the incompletely transmitted MAC PDU;

[0684] Transfer of resources containing incompletely transferred MAC PDUs.

[0685] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both new transmission and first uplink transmission exist simultaneously, the UE shall prioritize the first uplink transmission.

[0686] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case of simultaneous new transmission and first uplink transmission, the UE implementation may prioritize one of the new transmission and the first uplink transmission.

[0687] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both new transmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission and first uplink transmission according to predefined information.

[0688] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both new transmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission and first uplink transmission based on logical channel priority (e.g., the one with higher priority takes precedence).

[0689] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if both retransmission and first uplink transmission exist simultaneously, the UE shall prioritize the first uplink transmission.

[0690] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case of simultaneous retransmission and first uplink transmission, the UE implementation may prioritize either the retransmission or the first uplink transmission.

[0691] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if both retransmission and the first uplink transmission exist simultaneously, the UE will prioritize one of the retransmission and the first uplink transmission according to predefined information.

[0692] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case of simultaneous retransmission and first uplink transmission, the UE will prioritize one of the retransmission and first uplink transmission based on logical channel priority (e.g., the one with higher priority takes precedence).

[0693] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if new transmission, retransmission and first uplink transmission exist simultaneously, the UE shall prioritize the first uplink transmission.

[0694] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case of simultaneous new transmission, retransmission and first uplink transmission, the UE implementation will prioritize one of the new transmission, retransmission and first uplink transmission.

[0695] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if new transmission, retransmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission, retransmission and first uplink transmission according to predefined information.

[0696] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, if new transmission, retransmission and first uplink transmission exist simultaneously, the UE will prioritize one of the new transmission, retransmission and first uplink transmission based on logical channel priority (e.g., the one with higher priority takes precedence).

[0697] Among them, new transmission refers to the first transmission or initial transmission of data in the (uplink) HARQ process, while retransmission refers to data that is not the first transmission in the (uplink) HARQ process, or data that is retransmitted after a failure or retransmitted after a failure.

[0698] Method 2. When cg-RetransmissionTimer is configured, or when the unlicensed band is accessing / operating, the UE considers the transmission of the preferred uplink resource as a retransmission. Optionally, when multiple retransmissions exist, which one is prioritized depends on the UE implementation, or one of them is predefined, or it is determined based on logical channel priority (such as the one with higher priority).

[0699] In Method 2, the first uplink transmission is considered a retransmission. Specific optional implementations include the following:

[0700] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is enabled, the processing module 1020 is used to prioritize retransmission or retransmission of uplink resources.

[0701] Optionally, when configuring cg-RetransmissionTimer, or in the case of unlicensed band access / operation, if multiple retransmissions exist simultaneously, the processing module 1020 is used to prioritize one of the multiple retransmissions depending on the UE implementation.

[0702] Optionally, when cg-RetransmissionTimer is configured, or when an unlicensed band is accessed / operating, if multiple retransmissions exist simultaneously, the processing module 1020 is used to prioritize the transmission of one of the multiple retransmissions based on predefined information.

[0703] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if multiple retransmissions exist simultaneously, the processing module 1020 is used to prioritize one of the multiple retransmissions based on logical channel priority (e.g., higher priority takes precedence).

[0704] Method 3. When configuring cg-RetransmissionTimer, or when unlicensed band access / operation is enabled, the processing module 1020 is used to consider the transmission of the preferred uplink resource as a retransmission when selecting the preferred HARQ process. Optionally, when multiple retransmissions exist, which one is prioritized depends on the UE implementation, or one of them is predefined, or it is based on logical channel priority (e.g., the one with higher priority is prioritized).

[0705] In method three, the first uplink transmission is considered a retransmission. Specific optional implementations include the following:

[0706] Optionally, when cg-RetransmissionTimer is configured, or when an unlicensed band is accessed / operating, the processing module 1020 is used to prioritize the transmission of the first HARQ process, which is a HARQ process with retransmission or retransmission of uplink resources.

[0707] Optionally, when configuring cg-RetransmissionTimer, or when unlicensed band access / operation is in the case of multiple first HARQ processes existing simultaneously, the processing module 1020 is used to prioritize the transmission of one of the multiple first HARQ processes, depending on the UE implementation.

[0708] Optionally, when cg-RetransmissionTimer is configured, or when an unlicensed band is accessed / operating, if multiple first HARQ processes exist simultaneously, the processing module 1020 is used to prioritize the transmission of one of the multiple first HARQ processes according to predefined information.

[0709] Optionally, when cg-RetransmissionTimer is configured, or when unlicensed band access / operation is in the case, if multiple first HARQ processes exist simultaneously, the processing module 1020 is used to prioritize the transmission of one of the multiple first HARQ processes based on logical channel priority (e.g., higher priority takes precedence).

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

[0711] Figure 15 The diagram shows a schematic of the structure of a terminal provided in an exemplary embodiment of this application. The terminal includes: a processor 101, a receiver 102, a transmitter 103, a memory 104, and a bus 105.

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

[0713] The receiver 102 and the transmitter 103 can be implemented as a communication component, which can be a communication chip.

[0714] The memory 104 is connected to the processor 101 via the bus 105.

[0715] The memory 104 can be used to store at least one instruction, and the processor 101 is used to execute the at least one instruction to implement the various steps in the above method embodiments. Specifically, the transmitter 103 is used to perform steps related to transmission; the receiver 104 is used to perform steps related to reception; and the processor 101 is used to perform steps other than transmission and reception.

[0716] Furthermore, the memory 104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic storage, flash memory, and programmable read-only memory (PROM).

[0717] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the random access method, priority determination method, conflict resolution method, or data transmission method provided in the above-described method embodiments.

[0718] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to perform the random access method, priority determination method, conflict resolution method, or data transmission method described above.

[0719] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0720] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for selecting random access resources, characterized in that, The method includes: Receive the first random access channel (RACH) information in the system information block; receive the second RACH information in the dedicated signaling; The random access procedure is performed using the first RACH information and / or the second RACH information; The first RACH information and / or the second RACH information are configured with at least two sets of RACH configuration parameters, and the at least two sets of RACH configuration parameters include slice-specific RACH and public RACH; The random access procedure performed using the first RACH information and / or the second RACH information includes: If the fourth condition is met, the random access procedure is performed using the slice-specific RACH, the fourth condition including the terminal using a specified slice or the terminal using a specified type of slice; Alternatively, if the fifth condition is met, the random access procedure is performed using the public RACH, the fifth condition including that the terminal is not using a specified slice or that the terminal is not using a specified type of slice.

2. The method according to claim 1, characterized in that, The step of performing a random access procedure using the first RACH information and / or the second RACH information includes: The random access procedure is performed using the first RACH information; Alternatively, the random access procedure may be performed using the second RACH information; Alternatively, if the first condition is met, the first RACH information is used to perform the random access procedure; Alternatively, if the second condition is met, the random access procedure may be performed using the second RACH information; Alternatively, if the third condition is met, the random access procedure may be performed using the first RACH information and the second RACH information.

3. The method according to claim 2, characterized in that, The step of performing the random access procedure using the first RACH information when the first condition is met includes: If the priority of the first RACH information is higher than the priority of the second RACH information, the first RACH information is used to perform the random access procedure; Alternatively, if the random access procedure is performed using the first RACH information when the second RACH information is not within its valid time and / or valid range; Alternatively, if the first indication information is used to indicate that the first RACH information should be used first, the random access procedure shall be performed using the first RACH information; Alternatively, if the slice information in the first RACH information or the second RACH information is different, the first RACH information is used to perform the random access procedure; Alternatively, depending on the terminal or access network device's support for network slicing, the first RACH information may be used to execute the random access procedure; Alternatively, if the random access procedure is performed using the first RACH information, even if the cell or base station sending the second RACH information is not within its coverage or service range, the random access procedure may be performed using the first RACH information.

4. The method according to claim 2, characterized in that, The step of performing the random access procedure using the second RACH information when the second condition is met includes: If the priority of the second RACH information is higher than the priority of the first RACH information, the second RACH information is used to perform the random access procedure; Alternatively, if the second RACH information is valid during the validity period of the second RACH information, or within the validity range of the second RACH information, or within the validity period and range of the second RACH information, the second RACH information is used to perform the random access procedure; Alternatively, if the first indication information is used to indicate that the second RACH information should be used first, the second RACH information shall be used to perform the random access procedure; Alternatively, if the slice information in the first RACH information or the second RACH information is different, and / or if it falls within the valid time and / or valid range of the second RACH information, the second RACH information shall be used to perform the random access procedure; Alternatively, depending on the terminal or access network device's support for network slicing, the second RACH information may be used to execute the random access procedure; Alternatively, within the coverage or service range of the cell or base station that sent the second RACH information, the second RACH information can be used to perform the random access procedure.

5. The method according to claim 2, characterized in that, The step of performing the random access procedure using the first RACH information and the second RACH information when the third condition is met includes: When the first RACH information includes at least two sets of RACH configuration parameters and the second RACH information includes selection information for the RACH configuration parameters, the random access procedure is performed using the at least two sets of RACH configuration parameters and the selection information for the RACH configuration parameters. Alternatively, if the second RACH information includes at least two sets of RACH configuration parameters and the first RACH information includes selection information for the RACH configuration parameters, the random access procedure is performed using the at least two sets of RACH configuration parameters and the selection information for the RACH configuration parameters. The selection information includes at least one of the following: selection threshold, selection indication, and selection conditions.

6. The method according to claim 1, characterized in that, The step of performing the random access procedure using the first RACH information and / or the second RACH information includes: If the triggering conditions are met, the random access procedure is executed using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters.

7. The method according to claim 1, characterized in that, The fourth condition includes at least one of the following: The terminal supports slicing; The terminal uses the same slice as the network-supported slice; The terminal's required slice is the same as the network's supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is higher than a first threshold, which is a threshold used to select between the public RACH and the slice-specific RACH; The channel quality is higher than a second threshold, which is a threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources; The channel quality is above a fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources; Upon receiving a second instruction message, the second instruction message is used to instruct the selection of the slice-specific RACH between the public RACH and the slice-specific RACH; Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or the slice-specific RACH between the two sets of RACH resources; The random access procedure is a contention-based random access procedure.

8. The method according to claim 1, characterized in that, The fifth condition includes at least one of the following: The terminal does not support slicing; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below a first threshold, which is a threshold used to select between the public RACH and the slice-specific RACN; The channel quality is below a second threshold, which is a threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources; The channel quality is below a fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources; A fourth instruction message is received, the fourth instruction message being used to instruct the selection of the public RACH between the public RACH and the slice-specific RACH; Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select the two-step slice-specific RACH or a RACH other than the slice-specific RACH between the two sets of RACH resources; Random access using the slice-specific RACH failed; Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured. The random access procedure is a non-contention-based random access procedure.

9. The method according to claim 6, characterized in that, The at least two sets of RACH configuration parameters include a 2-step slice-specific RACH and a 4-step slice-specific RACH; The step of performing the random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering condition is met includes: If the sixth condition is met, the random access procedure is performed using the two-step slice-specific RACH. Alternatively, if the seventh condition is met, the random access procedure may be performed using the four-step slice-specific RACH.

10. The method according to claim 9, characterized in that, The sixth condition includes at least one of the following: The terminal uses slices of the specified type; The terminal uses the same slice as the network-supported slice; The terminal's required slice is the same as the network's supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is higher than the second threshold, which is a threshold used to select the two-step slice-specific RACH between two sets of RACH resources; The channel quality is higher than a third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH; Upon receiving a sixth instruction message, the sixth instruction message is used to indicate that the 2-step slice-dedicated RACH be selected between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH; Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or slice-specific RACH between the two sets of RACH resources; The random access procedure is a contention-based random access procedure.

11. The method according to claim 9, characterized in that, The seventh condition includes at least one of the following: The terminal is not using a slice of the specified type; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below a second threshold, which is a threshold used to select the two-step slice-dedicated RACH between two sets of RACH resources; The channel quality is below the third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH; Upon receiving a seventh instruction message, the seventh instruction message is used to instruct the selection of the 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH. Random access using the two-step slice-specific RACH failed; Upon receiving the eighth instruction information, the eighth instruction information is used to indicate the selection of the 4-step slice-specific RACH or slice-specific RACH between the two sets of RACH resources; The random access procedure is a non-contention-based random access procedure.

12. The method according to claim 6, characterized in that, The at least two sets of RACH configuration parameters include 2-step RACH and 2-step slice-specific RACH; The step of performing the random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering condition is met includes: If the eighth condition is met, the random access procedure is performed using the two-step slice-specific RACH. Alternatively, if the ninth condition is met, the random access procedure is performed using the two-step RACH.

13. The method according to claim 12, characterized in that, The eighth condition includes at least one of the following: The terminal uses slices of the specified type; The terminal uses the same slice as the network-supported slice; The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is above a fourth threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 2-step RACH; The channel quality is above the fifth threshold, which is a threshold used to select a slice-specific RACH between two sets of RACH resources; Upon receiving a ninth instruction message, the ninth instruction message is used to instruct the selection of the two-step slice-specific RACH between the two-step slice-specific RACH and the two-step RACH; Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or the slice-specific RACH between the two sets of RACH resources; The random access procedure is a contention-based random access procedure.

14. The method according to claim 12, characterized in that, The ninth condition includes at least one of the following: The terminal is not using a slice of the specified type; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below a third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 2-step RACH; The channel quality is below the second threshold, which is the threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources; Upon receiving a tenth instruction message, the tenth instruction message is used to indicate the selection of the two-step RACH between the two-step slice-specific RACH and the two-step RACH; Random access using the two-step slice-specific RACH failed; Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured. Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select between two sets of RACH resources a 2-step slice-specific RACH or a RACH other than a slice-specific RACH. The random access procedure is a non-contention-based random access procedure.

15. The method according to claim 6, characterized in that, The at least two sets of RACH configuration parameters include a 4-step RACH and a 4-step slice-specific RACH; The step of performing the random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering condition is met includes: Under the condition of the tenth condition, the random access procedure is performed using the four-step slice-specific RACH. Alternatively, if the eleventh condition is met, the random access procedure is performed using the four-step RACH.

16. The method according to claim 15, characterized in that, The tenth condition includes at least one of the following: The terminal uses slices of the specified type; The terminal uses the same slice as the network-supported slice; The terminal's required slice is the same as the network's supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is above the sixth threshold, which is a threshold used to select between the 4-step slice-dedicated RACH and the 4-step RACH; Upon receiving the eleventh instruction message, the eleventh instruction message is used to indicate that the 4-step slice-specific RACH should be selected between the 4-step slice-specific RACH and the 4-step RACH. The channel quality is above the fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources; Upon receiving the eighth instruction information, the eighth instruction information is used to indicate the selection between the two sets of RACH resources: the 4-step slice-specific RACH or the slice-specific RACH. The random access procedure is a contention-based random access procedure. Random access failed when using a 2-step slice-specific RACH. Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH is configured.

17. The method according to claim 15, characterized in that, The eleventh condition includes at least one of the following: The terminal did not use the specified type of slice; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below the sixth threshold, which is a threshold used to select between the 4-step slice-dedicated RACH and the 4-step RACH; Upon receiving the twelfth instruction message, the twelfth instruction message is used to indicate the selection of the 4-step RACH between the 4-step slice-specific RACH and the 4-step RACH; Random access failed when using the 4-step slice-specific RACH. The channel quality is below the fifth threshold, which is a threshold used to select slice-specific RACH between two sets of RACH resources; Random access failed when using a 2-step slice-specific RACH. Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured. Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select between the two sets of RACH resources the two-step slice-specific RACH or a RACH other than the slice-specific RACH. The random access procedure is a non-contention-based random access procedure.

18. The method according to any one of claims 6 to 17, characterized in that, The at least two sets of RACH configuration parameters are configured using the first RACH information; Alternatively, the at least two sets of RACH configuration parameters are configured using the second RACH information; Alternatively, the at least two sets of RACH configuration parameters are the first RACH information and the second RACH configuration.

19. The method according to any one of claims 1 to 17, characterized in that, The step of performing a random access procedure using the first RACH information and / or the second RACH information includes: The random access procedure is performed using the same behavior in different cells, including the behavior of using the first RACH information and / or the second RACH information; Alternatively, the random access procedure may be performed using different behaviors in different cells, including behaviors using the first RACH information and / or the second RACH information.

20. The method according to any one of claims 1 to 17, characterized in that, The system information block is system information block SIB1; Alternatively, the system information block may be a different SIB than SIB1; Alternatively, the system information block may be SIB1 or other SIBs besides SIB1.

21. The method according to any one of claims 1 to 17, characterized in that, The system information block includes: The first RACH information corresponds to at least one of the following: usage range, cell, region, public land mobile network (PLMN), registration area, and tracking area information.

22. The method according to any one of claims 1 to 17, characterized in that, The system information block includes at least one of the following: Slice information; Rollback instruction BI information; Power boost information; RACH time and frequency resources; Random access pilot.

23. The method according to any one of claims 1 to 17, characterized in that, The first RACH information includes: The first RACH configuration is used to configure at least one of the following RACH configuration parameters: RACH resource, RACH type, and RACH priority.

24. The method according to claim 23, characterized in that, The first RACH configuration is used to configure at least two sets of RACH configuration parameters, and the first RACH information also includes at least one of the following: Selection thresholds used to select from the at least two sets of RACH configuration parameters; Selection indication for selecting the at least two sets of RACH configuration parameters; Selection criteria used to select the at least two sets of RACH configuration parameters.

25. The method according to any one of claims 1 to 17, characterized in that, The dedicated signaling includes: Dedicated Radio Resource Control (RRC) messages; The dedicated RRC messages include: RRC reconfiguration messages, or RRC release messages.

26. The method according to any one of claims 1 to 17, characterized in that, The dedicated signaling includes: The effective duration corresponding to the second RACH information.

27. The method according to any one of claims 1 to 17, characterized in that, The dedicated signaling includes: The second RACH information corresponds to at least one of the following: effective range, cell, region, public land mobile network (PLMN), registration area, and tracking area information.

28. The method according to any one of claims 1 to 17, characterized in that, The dedicated signaling includes: Slice information; Rollback instruction BI information; Power boost information; RACH time and frequency resources; Random access preamble.

29. The method according to any one of claims 1 to 17, characterized in that, The second RACH information includes: The second RACH configuration is used to configure at least one of the following RACH configuration parameters: RACH resource, RACH type, and RACH priority.

30. The method according to claim 29, characterized in that, The second RACH configuration is used to configure at least two sets of RACH configuration parameters, and the second RACH information also includes at least one of the following: Selection thresholds used to select from the at least two sets of RACH configuration parameters; Selection indication for selecting the at least two sets of RACH configuration parameters; Selection criteria used to select the at least two sets of RACH configuration parameters.

31. The method according to claim 24 or 30, characterized in that, The selection threshold includes at least one of the following: The first threshold is used to select between public RACH and slice-specific RACH; The second threshold is used to select a 2-step slice-specific RACH between two sets of RACH resources; The third threshold is used to select between 2-step slice-specific RACH and 4-step slice-specific RACH; The fourth threshold is used to select between a 2-step slice-specific RACH and a 2-step RACH. The fifth threshold is used to select a slice-specific RACH between two sets of RACH resources; The sixth threshold is used to select between 4-step slice-specific RACH and 4-step RACH.

32. The method according to claim 24 or 30, characterized in that, The selection instruction includes at least one of the following: The second instruction information is used to select the slice-specific RACH between the public RACH and the slice-specific RACH; The third instruction information is used to indicate whether to select a 2-step slice-specific RACH or the slice-specific RACH between the two sets of RACH resources; The fourth instruction information is used to select the public RACH between the public RACH and the slice-specific RACH; The fifth instruction information is used to indicate whether to select the two-step slice-specific RACH or a RACH other than the slice-specific RACH between the two sets of RACH resources; The sixth instruction information is used to indicate the threshold for selecting the 2-step slice-specific RACH between the 2-step slice-specific RACH and the 4-step slice-specific RACH; The seventh instruction information is used to indicate the threshold for selecting the 4-step slice-specific RACH between the 2-step slice-specific RACH and the 4-step slice-specific RACH; The eighth instruction information is used to indicate whether to select the 4-step slice-specific RACH or slice-specific RACH between the two sets of RACH resources; The ninth instruction information is used to indicate the selection of the two-step slice-specific RACH between the two-step slice-specific RACH and the two-step RACH; The tenth instruction information is used to indicate the selection of the two-step RACH between the two-step slice-specific RACH and the two-step RACH; The eleventh instruction is used to indicate the selection of a 4-step slice-specific RACH between the 4-step slice-specific RACH and the 4-step RACH. The twelfth instruction is used to indicate the selection of a 4-step RACH between the 4-step slice-specific RACH and the 4-step RACH.

33. The method according to claim 32, characterized in that, The selection criteria include at least one of the following: In cases where a non-slice, a non-specified slice, a specified slice and a network-supported slice do not match, or a required slice and the network-supported slice do not match, a non-slice dedicated RACH is selected. In the case where the slice or the specified slice or the specified slice and the network-supported slice match, or the required slice and the network-supported slice match, select a slice-specific RACH; In the case of a slice of a specified type or a slice of the specified type that matches a slice supported by the network, select the slice-specific RACH; In the event that a slice of a non-specified type, a slice of the specified type, and a network-supported slice do not match, or a required slice and a network-supported slice do not match, select the common RACH. In the case of a slice of the specified type, or a slice of the specified type and a network-supported slice, or a required slice and a network-supported slice, select a 2-step slice-specific RACH; In the event that the non-specified type of slice, the specified type of slice, and the network-supported slice do not match, or the required slice and the network-supported slice do not match, select the 4-step slice-specific RACH; In the case that the specified type of slice, or the specified type of slice, and the network-supported slice match, or the required slice and the network-supported slice match, select 2-step RACH; In the event that the non-specified type slice, the specified type slice, and the network-supported slice do not match, or the required slice and the network-supported slice do not match, select 4-step RACH; In the event that the first type of RACH fails, or the specified type slice and the network-supported slice do not match, or the required slice and the network-supported slice do not match, the public RACH is selected; If the first type of RACH fails and the second type of RACH is not configured, the public RACH is selected; In the event that the first type of RACH fails and the second type of RACH is configured, the 4-step slice-specific RACH is selected; If the terminal supports slicing, select the slicing-specific RACH, the 2-step slicing-specific RACH, or the 4-step slicing-specific RACH; If the terminal does not support slicing, select the non-slicing dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH; If the network supports slicing, select the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH; If the network does not support slicing, select the non-slicing dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH; If the slice used by the terminal is the same as the slice supported by the network, select the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH. If the slice used by the terminal is different from the slice supported by the network, the non-slice-specific RACH, the public RACH, the 2-step RACH, or the 4-step RACH shall be selected. If the communication protocol version supported by the terminal is higher than the predetermined version, select the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH. If the communication protocol version supported by the terminal is lower than the predetermined version, select the non-slice dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH; When the random access procedure is a contention-based random access procedure, the slice-specific RACH, the two-step slice-specific RACH, or the four-step slice-specific RACH shall be selected. When the random access procedure is a non-contention-based random access procedure, the non-slice-dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH are selected. In the case that the random access procedure is a contention-based random access procedure, the slice-specific RACH, the two-step slice-specific RACH, or the two-step common RACH shall be selected; When the random access procedure is a non-contention-based random access procedure, the non-slice-dedicated RACH, the public RACH, the 2-step RACH, the 4-step RACH, or the 4-step slice-dedicated RACH are selected. When the random access procedure is a non-contention-based random access procedure, the slice-specific RACH, the 2-step slice-specific RACH, or the 4-step slice-specific RACH shall be selected. In the case that the random access procedure is a contention-based random access procedure, the non-slice-dedicated RACH, the public RACH, the 2-step RACH, or the 4-step RACH are selected.

34. The method according to any one of claims 1 to 17, characterized in that, The system information block and / or the dedicated signaling also include: The first indication information is used to indicate whether the second RACH information is used to overwrite the first RACH information.

35. A random access method, characterized in that, The method includes: Obtain at least two sets of random access channel (RACH) configuration parameters, wherein the at least two sets of RACH configuration parameters include slice-specific RACH and public RACH, and the at least two sets of RACH configuration parameters are configured by system information blocks and / or dedicated signaling; If the triggering conditions are met, a random access procedure is performed using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters. The random access procedure, performed using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters, includes: If the fourth condition is met, the random access procedure is performed using the slice-specific RACH, the fourth condition including the terminal using a specified slice or the terminal using a specified type of slice; Alternatively, if the fifth condition is met, the random access procedure is performed using the public RACH, the fifth condition including that the terminal is not using a specified slice or that the terminal is not using a specified type of slice.

36. The method according to claim 35, characterized in that, The fourth condition includes at least one of the following: The terminal supports slicing; The terminal uses the same slice as the network-supported slice; The terminal's required slice is the same as the network's supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is higher than a first threshold, which is a threshold used to select between the public RACH and the slice-specific RACH; The channel quality is higher than a second threshold, which is a threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources; The channel quality is above a fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources; Upon receiving a second instruction message, the second instruction message is used to instruct the selection of the slice-specific RACH between the public RACH and the slice-specific RACH; Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or the slice-specific RACH between the two sets of RACH resources; The random access procedure is a contention-based random access procedure.

37. The method according to claim 35, characterized in that, The fifth condition includes at least one of the following: The terminal does not support slicing; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below a first threshold, which is a threshold used to select between the public RACH and the slice-specific RACN; The channel quality is below a second threshold, which is a threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources; The channel quality is below a fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources; A fourth instruction message is received, the fourth instruction message being used to instruct the selection of the public RACH between the public RACH and the slice-specific RACH; Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select the two-step slice-specific RACH or a RACH other than the slice-specific RACH between the two sets of RACH resources; Random access using the slice-specific RACH failed; Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured. The random access procedure is a non-contention-based random access procedure.

38. The method according to claim 35, characterized in that, The at least two sets of RACH configuration parameters include a 2-step slice-specific RACH and a 4-step slice-specific RACH; The step of performing the random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering condition is met includes: If the sixth condition is met, the random access procedure is performed using the two-step slice-specific RACH. Alternatively, if the seventh condition is met, the random access procedure may be performed using the four-step slice-specific RACH.

39. The method according to claim 38, characterized in that, The sixth condition includes at least one of the following: The terminal uses slices of the specified type; The terminal uses the same slice as the network-supported slice; The terminal's required slice is the same as the network's supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is higher than the second threshold, which is a threshold used to select the two-step slice-specific RACH between two sets of RACH resources; The channel quality is higher than a third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH; Upon receiving a sixth instruction message, the sixth instruction message is used to indicate that the 2-step slice-dedicated RACH be selected between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH; Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or slice-specific RACH between the two sets of RACH resources; The random access procedure is a contention-based random access procedure.

40. The method according to claim 38, characterized in that, The seventh condition includes at least one of the following: The terminal is not using a slice of the specified type; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below a second threshold, which is a threshold used to select the two-step slice-dedicated RACH between two sets of RACH resources; The channel quality is below the third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH; Upon receiving a seventh instruction message, the seventh instruction message is used to instruct the selection of the 4-step slice-dedicated RACH between the 2-step slice-dedicated RACH and the 4-step slice-dedicated RACH. Random access using the two-step slice-specific RACH failed; Upon receiving the eighth instruction information, the eighth instruction information is used to indicate the selection of the 4-step slice-specific RACH or slice-specific RACH between the two sets of RACH resources; The random access procedure is a non-contention-based random access procedure.

41. The method according to claim 35, characterized in that, The at least two sets of RACH configuration parameters include 2-step RACH and 2-step slice-specific RACH; The step of performing the random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering condition is met includes: If the eighth condition is met, the random access procedure is performed using the two-step slice-specific RACH. or, If the ninth condition is met, the random access procedure is performed using the two-step RACH.

42. The method according to claim 41, characterized in that, The eighth condition includes at least one of the following: The terminal uses slices of the specified type; The terminal uses the same slice as the network-supported slice; The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is above a fourth threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 2-step RACH; The channel quality is above the fifth threshold, which is a threshold used to select a slice-specific RACH between two sets of RACH resources; Upon receiving a ninth instruction message, the ninth instruction message is used to instruct the selection of the two-step slice-specific RACH between the two-step slice-specific RACH and the two-step RACH; Upon receiving a third instruction, the third instruction is used to indicate whether to select the two-step slice-specific RACH or the slice-specific RACH between the two sets of RACH resources; The random access procedure is a contention-based random access procedure.

43. The method according to claim 41, characterized in that, The ninth condition includes at least one of the following: The terminal is not using a slice of the specified type; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below a third threshold, which is a threshold used to select between the 2-step slice-dedicated RACH and the 2-step RACH; The channel quality is below the second threshold, which is the threshold used to select a 2-step slice-dedicated RACH between two sets of RACH resources; Upon receiving a tenth instruction message, the tenth instruction message is used to indicate the selection of the two-step RACH between the two-step slice-specific RACH and the two-step RACH; Random access using the two-step slice-specific RACH failed; Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured. Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select between two sets of RACH resources a 2-step slice-specific RACH or a RACH other than a slice-specific RACH. The random access procedure is a non-contention-based random access procedure.

44. The method according to claim 35, characterized in that, The at least two sets of RACH configuration parameters include a 4-step RACH and a 4-step slice-specific RACH; The step of performing the random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering condition is met includes: Under the condition of the tenth condition, the random access procedure is performed using the four-step slice-specific RACH. or, If the eleventh condition is met, the random access procedure is performed using the four-step RACH.

45. The method according to claim 44, characterized in that, The tenth condition includes at least one of the following: The terminal uses slices of the specified type; The terminal uses the same slice as the network-supported slice; The terminal's required slice is the same as the network's supported slice; The terminal supports a communication protocol version that is higher than or equal to a predetermined version; The channel quality is above the sixth threshold, which is a threshold used to select between the 4-step slice-dedicated RACH and the 4-step RACH; Upon receiving the eleventh instruction message, the eleventh instruction message is used to indicate that the 4-step slice-specific RACH should be selected between the 4-step slice-specific RACH and the 4-step RACH. The channel quality is above the fifth threshold, which is a threshold used to select slice-specific RACHs between two sets of RACH resources; Upon receiving the eighth instruction information, the eighth instruction information is used to indicate the selection between the two sets of RACH resources: the 4-step slice-specific RACH or the slice-specific RACH. The random access procedure is a contention-based random access procedure. Random access failed when using a 2-step slice-specific RACH. Random access using the 2-step slice-dedicated RACH failed, and the 4-step slice-dedicated RACH was configured.

46. ​​The method according to claim 44, characterized in that, The eleventh condition includes at least one of the following: The terminal did not use the specified type of slice; The terminal uses a different slice than the network-supported slice. The required slice of the terminal is different from the network-supported slice; The terminal supports a communication protocol version that is lower than the predetermined version; The channel quality is below the sixth threshold, which is a threshold used to select between the 4-step slice-dedicated RACH and the 4-step RACH; Upon receiving the twelfth instruction message, the twelfth instruction message is used to indicate the selection of the 4-step RACH between the 4-step slice-specific RACH and the 4-step RACH; Random access failed when using the 4-step slice-specific RACH. The channel quality is below the fifth threshold, which is a threshold used to select slice-specific RACH between two sets of RACH resources; Random access failed when using a 2-step slice-specific RACH. Random access failed when using the 2-step slice-dedicated RACH, and the 4-step slice-dedicated RACH was not configured. Upon receiving a fifth instruction message, the fifth instruction message is used to indicate whether to select between the two sets of RACH resources the two-step slice-specific RACH or a RACH other than the slice-specific RACH. The random access procedure is a non-contention-based random access procedure.

47. A random access device, characterized in that, The device includes: The receiving module is configured to receive first random access channel (RACH) information in the system information block of the first cell; and to receive second RACH information in the dedicated signaling of the first cell. The random access module is used to perform a random access procedure in the first cell using the first RACH information or the second RACH information. The first RACH information or the second RACH information is configured with at least two sets of RACH configuration parameters, and the at least two sets of RACH configuration parameters include slice-specific RACH and public RACH; The random access procedure performed using the first RACH information or the second RACH information includes: If the fourth condition is met, the random access procedure is performed using the slice-specific RACH, the fourth condition including the terminal using a specified slice or the terminal using a specified type of slice; Alternatively, if the fifth condition is met, the random access procedure is performed using the public RACH, the fifth condition including that the terminal is not using a specified slice or that the terminal is not using a specified type of slice.

48. A random access device, characterized in that, The device includes: The receiving module is used to acquire at least two sets of random access channel (RACH) configuration parameters, wherein the at least two sets of RACH configuration parameters include slice-specific RACH and common RACH, and the at least two sets of RACH configuration parameters are configured by system information blocks and / or dedicated signaling; The random access module is used to perform a random access procedure using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters when the triggering conditions are met. The random access procedure, performed using one set of RACH configuration parameters from the at least two sets of RACH configuration parameters, includes: If the fourth condition is met, the random access procedure is performed using the slice-specific RACH, the fourth condition including the terminal using a specified slice or the terminal using a specified type of slice; Alternatively, if the fifth condition is met, the random access procedure is performed using the public RACH, the fifth condition including that the terminal is not using a specified slice or that the terminal is not using a specified type of slice.

49. A terminal, characterized in that, The terminal includes: processor; A transceiver connected to the processor; Memory for storing the executable instructions of the processor; The processor is configured to load and execute the executable instructions to implement the random access method as described in any one of claims 1 to 46.

50. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores executable instructions that are loaded and executed by a processor to implement the random access method as described in any one of claims 1 to 46.

Images