Method and apparatus in node used for wireless communication

Abstract

The invention discloses a method and an apparatus in a node used for wireless communication. A first receiver which receives a first information block, the first information block indicating a reference time domain resource set, the reference time domain resource set comprising one or more symbols configured as DL by higher layer parameters; the first transmitter is used for transmitting a first random access preamble in a first PRACH opportunity, and the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set; when the transmission of the first random access preamble belongs to a first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to a second type random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set. The delay is reduced, and the system performance is improved.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a transmission method and device for wireless signals in a wireless communication system supporting a cellular network. Background Art

[0002] In the existing NR (New Radio) system, spectrum resources are divided into FDD (Frequency Division Duplexing) spectrum and TDD (Time Division Duplexing) spectrum. For TDD spectrum, both base stations and UE (User Equipment) operate in half-duplex mode. This half-duplex mode avoids self-interference and can alleviate the impact of cross-link interference, but it also brings about a decrease in resource utilization and an increase in latency. In response to these problems, supporting flexible duplex modes or variable link directions (uplink or downlink or flexible) on TDD spectrum or FDD spectrum has become a possible solution. In the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #88e meeting and 3GPP R (Release)-18workshop, supporting more flexible duplex mode or full-duplex mode in NR R-18 has received extensive attention and discussion, especially the subband non-overlapping full-duplex (SBFD) mode at the gNB (NR Node B) end. In this mode, the same symbol will be used for uplink in part of the frequency resources and for downlink in another part of the frequency resources, so resource utilization is improved and latency is reduced. Summary of the invention

[0003] The inventors have found through research that how to determine the timing of random access is a key issue.

[0004] In view of the above problems, the present application discloses a solution. It should be noted that in the description of the present application, only more flexible duplex mode, full-duplex mode and SBFD mode are used as examples, and the present application can also be applied to other duplex mode scenarios. Further, the use of a unified design scheme for different scenarios (including but not limited to more flexible duplex mode, full-duplex mode, SBFD mode, half-duplex mode, traditional duplex mode, network energy-saving mode, non-energy-saving mode, etc.) also helps to reduce hardware complexity and cost. In the absence of conflict, the embodiments of any node of the present application and the features in the embodiments can be applied to any other node. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other.

[0005] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the TS38 series of specification protocols of 3GPP.

[0006] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the TS37 series of specification protocols of 3GPP.

[0007] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0008] Receiving a first information block, where the first information block indicates a reference time domain resource set, where the reference time domain resource set includes one or more symbols configured as DL (Downlink) by a higher layer parameter;

[0009] Sending a first random access preamble in a first PRACH (Physical Random Access Channel) opportunity, the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain;

[0010] The sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0011] As an embodiment, the problem to be solved by the present application includes: when the reference time domain resource set is configured, how to determine the candidate set of the first PRACH opportunity.

[0012] As an embodiment, the benefits of the above method include: in a more flexible duplex mode / full-duplex mode / SBFD mode, the available uplink / downlink resources become more flexible, and how to determine the candidate set of the first PRACH timing.

[0013] As an embodiment, in the above method, the candidate set of the first PRACH opportunity depends on the type of random access process, which solves this problem.

[0014] As an embodiment, the benefits of the above method include: selecting a PRACH opportunity according to different types of random access procedures, ensuring the reliability of the selected PRACH opportunity, and improving system performance.

[0015] As an embodiment, the benefits of the above method include: supporting more flexible configuration of the reference time domain resource set and different types of random access processes, increasing the flexibility of system design, and optimizing system performance.

[0016] According to one aspect of the present application, it is characterized in that one of the first type of random access process and the second type of random access process is contention-based, and the other is contention-free-based.

[0017] According to one aspect of the present application, it is characterized in that one of the first type of random access process and the second type of random access process is a four-step random access process, and the other is a two-step random access process.

[0018] As an embodiment, the benefits of the above method include: flexible classification of random access process types, thereby improving configuration flexibility.

[0019] As an embodiment, the advantages of the above method include: simple implementation and minor changes to the standard.

[0020] According to one aspect of the present application, it is characterized in that the priority of the first type of random access process is lower than the priority of the second type of random access process.

[0021] As an embodiment, the benefits of the above method include: improving the access opportunity of high-priority random access procedures and reducing delays.

[0022] According to one aspect of the present application, it is characterized in that the first type of random access process is initiated for a first event set, and the second type of random access process is initiated for a second event set; the first event set includes one or more events, the second event set includes one or more events, and any event in the first event set does not belong to the second event set.

[0023] As an embodiment, the advantages of the above method include: simple implementation and good compatibility.

[0024] According to one aspect of the present application, it is characterized in that any characteristic applicable to the first type of random access procedure is not a characteristic applicable to the second type of random access procedure.

[0025] As an embodiment, the benefits of the above method include: different types of random access procedures are applicable to different characteristics, and the applicable characteristics implicitly indicate the type of random access procedure, thereby reducing signaling overhead.

[0026] According to one aspect of the present application, it is characterized in that, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one resource block (Resource Block, RB) is used for uplink transmission.

[0027] As an embodiment, the benefits of the above method include: supporting uplink transmission on DL symbols, increasing uplink capacity, improving resource utilization, and reducing delay.

[0028] According to one aspect of the present application, it is characterized by comprising:

[0029] receiving a second information block;

[0030] Among them, the second information block indicates a reference frequency domain resource set; the reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0031] As an embodiment, the benefits of the above method include: increasing the available PRACH opportunities and reducing the delay of random access.

[0032] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0033] Sending a first information block, where the first information block indicates a reference time domain resource set, where the reference time domain resource set includes one or more symbols configured as DL (Downlink) by a higher layer parameter;

[0034] receiving a first random access preamble in a first PRACH opportunity, where the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, where the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and where the second PRACH opportunity set and the reference time domain resource set overlap in the time domain;

[0035] The reception of the first random access preamble belongs to one of a first type of random access process or a second type of random access process; when the reception of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the reception of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0036] According to one aspect of the present application, it is characterized in that one of the first type of random access process and the second type of random access process is contention-based, and the other is contention-free-based.

[0037] According to one aspect of the present application, it is characterized in that one of the first type of random access process and the second type of random access process is a four-step random access process, and the other is a two-step random access process.

[0038] According to one aspect of the present application, it is characterized in that the priority of the first type of random access process is lower than the priority of the second type of random access process.

[0039] According to one aspect of the present application, it is characterized in that the first type of random access process is initiated for a first event set, and the second type of random access process is initiated for a second event set; the first event set includes one or more events, the second event set includes one or more events, and any event in the first event set does not belong to the second event set.

[0040] According to one aspect of the present application, it is characterized in that any characteristic applicable to the first type of random access procedure is not a characteristic applicable to the second type of random access procedure.

[0041] According to one aspect of the present application, it is characterized in that, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one resource block (Resource Block, RB) is used for uplink transmission.

[0042] According to one aspect of the present application, it is characterized by comprising:

[0043] sending a second information block;

[0044] Among them, the second information block indicates a reference frequency domain resource set; the reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0045] The present application discloses a first node device used for wireless communication, characterized in that it includes:

[0046] A first receiver receives a first information block, where the first information block indicates a reference time domain resource set, where the reference time domain resource set includes one or more symbols configured as DL (Downlink) by a higher layer parameter;

[0047] A first transmitter sends a first random access preamble in a first PRACH opportunity, where the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, where the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and where the second PRACH opportunity set and the reference time domain resource set overlap in the time domain;

[0048] The sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0049] The present application discloses a second node device used for wireless communication, characterized in that it includes:

[0050] A second transmitter sends a first information block, where the first information block indicates a reference time domain resource set, where the reference time domain resource set includes one or more symbols configured as DL (Downlink) by a higher layer parameter;

[0051] A second receiver receives a first random access preamble in a first PRACH opportunity, where the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, where the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and where the second PRACH opportunity set and the reference time domain resource set overlap in the time domain;

[0052] The reception of the first random access preamble belongs to one of a first type of random access process or a second type of random access process; when the reception of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the reception of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0053] As an embodiment, compared with the traditional solution, this application has the following advantages:

[0054] Improved system performance and flexibility;

[0055] Simple implementation, small changes to the standard, and good compatibility;

[0056] Reduced signaling overhead;

[0057] Reduced latency. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0059] Figure 1 A flowchart of a first information block and a first random access preamble according to an embodiment of the present application is shown;

[0060] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0061] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0062] Figure 4A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0063] Figure 5 A flow chart showing transmission according to an embodiment of the present application is shown;

[0064] Figure 6A-6B Schematic diagrams of a first type of random access process and a second type of random access process according to an embodiment of the present application are respectively shown;

[0065] Figure 7 A schematic diagram showing the priority of a first type of random access procedure and the priority of a second type of random access procedure according to an embodiment of the present application;

[0066] Figure 8 A schematic diagram showing a first event set and a second event set according to an embodiment of the present application is shown;

[0067] Fig. 9 A schematic diagram showing characteristics applicable to a first type of random access procedure and characteristics applicable to a second type of random access procedure according to an embodiment of the present application;

[0068] Fig.10 A schematic diagram showing a subcarrier or resource block used for uplink transmission according to an embodiment of the present application;

[0069] Fig.11 A schematic diagram showing a second information block and a reference frequency domain resource set according to an embodiment of the present application is shown;

[0070] Fig.12 A structural block diagram of a processing device used in a first node device according to an embodiment of the present application is shown;

[0071] Fig.13 A structural block diagram of a processing device used in a second node device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0072] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other without conflict. Based on considerations such as flexibility, complexity, overhead, and compatibility, those skilled in the art are motivated to flexibly combine the embodiments in different drawings without conflict, for example (but not limited to) the attached drawings. Figure 1 The embodiments and appendix Figure 5 -Attached Fig.11 The embodiments in Figure 5 The embodiments and accompanying drawings in Fig.11 The embodiments in , etc.

[0073] Example 1

[0074] Embodiment 1 illustrates a flowchart of a first information block and a first random access preamble according to an embodiment of the present application, as shown in the attached figure. Figure 1 As shown in the attached Figure 1 In the illustrated 100, each box represents a step. In particular, the order of the steps in the boxes does not represent a specific time sequence relationship between the steps.

[0075] In embodiment 1, the first node in the present application receives a first information block in step 101, where the first information block indicates a reference time domain resource set, and the reference time domain resource set includes one or more symbols configured as DL by higher layer parameters; in step 102, a first random access preamble is sent in a first PRACH opportunity, and the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; wherein the sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0076] As an embodiment, the first information block is carried by higher layer signaling.

[0077] As an embodiment, the first information block is carried by RRC (Radio Resource Control) signaling.

[0078] As an embodiment, the first information block includes all or part of a field in an RRC IE (Information Element).

[0079] As an embodiment, the first information block includes all or part of the fields in each RRC IE in multiple RRC IEs.

[0080] As an embodiment, the first information block includes all or part of the fields in the TDD-UL-DL-ConfigCommon IE.

[0081] As an embodiment, the first information block includes all or part of the fields in the TDD-UL-DL-ConfigDedicated IE.

[0082] As an embodiment, the first information block includes all or part of the fields in the ServingCellConfig IE.

[0083] As an embodiment, the first information block includes all or part of the fields in the ServingCellConfigCommonSIB IE.

[0084] As an embodiment, the first information block includes all or part of the fields in the ServingCellConfigCommon IE.

[0085] As an embodiment, the first information block is carried by at least one RRC IE.

[0086] As an embodiment, the first information block is carried by TDD-UL-DL-ConfigCommon IE.

[0087] As an embodiment, the first information block is carried by TDD-UL-DL-ConfigDedicated IE.

[0088] As an embodiment, the first information block is carried by ServingCellConfig IE.

[0089] As an embodiment, the first information block is carried by ServingCellConfigCommonSIB IE.

[0090] As an embodiment, the first information block is carried by ServingCellConfigCommon IE.

[0091] As an embodiment, a name of an IE carrying the first information block includes TDD-UL-DL-Config.

[0092] As an embodiment, the name of an IE carrying the first information block includes ServingCellConfig.

[0093] As an embodiment, the first information block is carried by a MAC CE (Medium Access Control layer Control Element).

[0094] As an embodiment, the first information block includes MAC CE.

[0095] As an embodiment, the first information block is carried by DCI (Downlink Control Information).

[0096] As an embodiment, the first information block includes DCI.

[0097] As an embodiment, the first information block includes one or more fields in a DCI.

[0098] As an embodiment, the first information block is carried by DCI format 2_0.

[0099] As an embodiment, the first information block includes DCI format 2_0.

[0100] As an embodiment, the first information block is carried jointly by RRC signaling and MAC CE.

[0101] As an embodiment, the first information block is carried jointly by higher layer signaling and DCI.

[0102] As an embodiment, the first information block is carried jointly by RRC signaling, MAC CE and DCI.

[0103] As an embodiment, for the specific definitions of TDD-UL-DL-ConfigCommon IE, TDD-UL-DL-ConfigDedicated IE, ServingCellConfig IE, ServingCellConfigCommonSIB IE, and ServingCellConfigCommonIE, please refer to Section 6.3.2 of 3GPP TS 38.331.

[0104] As an embodiment, the specific definition of DCI format 2_0 refers to Section 7.3.1 of 3GPP TS 38.212.

[0105] As an embodiment, the first information block is used to determine the reference time domain resource set.

[0106] As an embodiment, the first information block indicates the reference time domain resource set.

[0107] As an embodiment, the first information block is used to indicate the reference time domain resource set.

[0108] As an embodiment, the first information block explicitly indicates the reference time domain resource set.

[0109] As an embodiment, the first information block implicitly indicates the reference time domain resource set.

[0110] As an embodiment, the first information block indicates the period and time offset of the reference time domain resource set.

[0111] As an embodiment, the first information block indicates the time domain resources included in the reference time domain resource set within a period.

[0112] As an embodiment, the first information block indicates the symbols included in the reference time domain resource set within a period.

[0113] As an embodiment, the first information block indicates the time slots included in the reference time domain resource set within a period.

[0114] As an embodiment, the first information block indicates which time slots belong to the reference time domain resource set.

[0115] As an embodiment, the first information block indicates which symbols belong to the reference time domain resource set.

[0116] As an embodiment, the first information block indicates which time slots in a cycle belong to the reference time domain resource set.

[0117] As an embodiment, the first information block indicates which symbols within a period belong to the reference time domain resource set.

[0118] As an embodiment, the first information block indicates the position of the time slots included in the reference time domain resource set within a cycle.

[0119] As an embodiment, the first information block indicates the position of the symbols included in the reference time domain resource set within a period.

[0120] As an embodiment, the first information block explicitly configures the reference time domain resource set.

[0121] As an embodiment, the first information block explicitly configures the period of the reference time domain resource set.

[0122] As an embodiment, the first information block explicitly configures the period and time offset of the reference time domain resource set.

[0123] As an embodiment, the first information block explicitly configures the position of the time slots included in the reference time domain resource set within a cycle.

[0124] As an embodiment, the first information block explicitly configures the position of the symbols included in the reference time domain resource set within a period.

[0125] As an embodiment, the first information block configures the symbols in the reference time domain resource set as a first type.

[0126] As an embodiment, the first information block indicates the reference time domain resource set by configuring symbols in the reference time domain resource set as a first type.

[0127] As an embodiment, the first type is different from uplink (Uplink, UL) and downlink (Downlink, DL).

[0128] As an embodiment, the first type is different from uplink, downlink and Flexible.

[0129] As an embodiment, the first type is different from sidelink.

[0130] As an embodiment, the first type of symbol is a SBFD symbol.

[0131] As an embodiment, the first type of symbols is configured as DL or Flexible by a higher layer parameter.

[0132] As an embodiment, the first type of symbol is configured as DL by a higher layer parameter, and one or more subcarriers in the first type of symbol are used for UL transmission.

[0133] As an embodiment, the first type of symbol is configured as DL by a higher layer parameter, and one or more RBs in the first type of symbol are used for UL transmission.

[0134] As an embodiment, the first type of symbols is configured as DL by a higher layer parameter, and the first type of symbols supports UL transmission.

[0135] As an embodiment, if a symbol is configured or indicated as the first type, the symbol is used in full-duplex / SBFD mode.

[0136] As an embodiment, if a symbol is configured or indicated as the first type, the symbol is used for both uplink and downlink.

[0137] As an embodiment, if a symbol is configured or indicated as the first type, the symbol is used for uplink on a part of RBs and is used for downlink on another part of RBs.

[0138] As a sub-embodiment of the above embodiment, the part of RBs and the other part of RBs belong to the same serving cell.

[0139] As a sub-embodiment of the above embodiment, the part of RBs and the other part of RBs belong to the same BWP (Bandwidth part, bandwidth range).

[0140] As an embodiment, if a symbol is configured or indicated as a type different from the first type, the symbol is not used in full-duplex / SBFD mode.

[0141] As an embodiment, if a symbol is configured or indicated as a type different from the first type, the symbol is used only for uplink or only for downlink.

[0142] As an embodiment, the first information block indicates the reference time domain resource set by configuring frequency domain resources used for uplink for symbols configured as DL or Flexible by higher layer parameters.

[0143] As an embodiment, the first information block indicates the reference time domain resource set by configuring frequency domain resources used for uplink for symbols configured as DL by higher layer parameters.

[0144] As an embodiment, the higher layer parameter is an RRC parameter.

[0145] As an embodiment, the higher layer parameters include tdd-UL-DL-ConfigurationCommon.

[0146] As an embodiment, the higher layer parameter includes tdd-UL-DL-ConfigurationDedicated.

[0147] As an embodiment, the higher layer parameters include tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0148] As an embodiment, the higher layer parameter includes at least one of tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0149] As an embodiment, the specific definition of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated refers to Chapter 11 of 3GPP TS38.213.

[0150] As an embodiment, the reference time domain resource set includes one or more symbols.

[0151] As an embodiment, the reference time domain resource set includes a symbol.

[0152] As an embodiment, the reference time domain resource set includes multiple symbols.

[0153] As an embodiment, the reference time domain resource set includes one or more symbols of the first type.

[0154] As an embodiment, the reference time domain resource set consists of one or more symbols of the first type.

[0155] As an embodiment, the reference time domain resource set includes at least one time slot.

[0156] As an embodiment, the reference time domain resource set includes at least one subframe.

[0157] As an embodiment, the symbol is a single carrier symbol.

[0158] As an embodiment, the symbol is a multi-carrier symbol.

[0159] As an embodiment, the multi-carrier symbol is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0160] As an embodiment, the multi-carrier symbol is obtained by subjecting the output of a transform precoding device to OFDM symbol generation.

[0161] As an embodiment, the multi-carrier symbol is an SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol.

[0162] As an embodiment, the multi-carrier symbol is a DFT-S-OFDM (Discrete Fourier Transform Spread OFDM) symbol.

[0163] As an embodiment, the multi-carrier symbol is a FBMC (Filter Bank Multi Carrier) symbol.

[0164] As an embodiment, the multi-carrier symbol includes a CP (Cyclic Prefix).

[0165] As an embodiment, the reference time domain resource set includes symbols used for both uplink transmission and downlink transmission.

[0166] As an embodiment, any symbol in the reference time domain resource set can be used for uplink transmission and downlink transmission at the same time.

[0167] As an embodiment, any symbol in the reference time domain resource set is used for both uplink transmission and downlink transmission.

[0168] As an embodiment, at least one symbol in the reference time domain resource set is used for both uplink transmission and downlink transmission.

[0169] As an embodiment, at least one symbol in the reference time domain resource set is configured for both uplink and downlink.

[0170] As an embodiment, at least one symbol in the reference time domain resource set is used for both uplink and downlink.

[0171] As an embodiment, each symbol in the reference time domain resource set is used for both uplink transmission and downlink transmission.

[0172] As an embodiment, each symbol in the reference time domain resource set is configured for both uplink and downlink.

[0173] As an embodiment, each symbol in the reference time domain resource set is used for both uplink and downlink.

[0174] As an embodiment, at least one symbol in the reference time domain resource set is configured for uplink in part of RBs, and is configured for downlink in another part of RBs.

[0175] As an embodiment, at least one symbol in the reference time domain resource set is used for uplink in part of RBs, and is used for downlink in another part of RBs.

[0176] As an embodiment, each symbol in the reference time domain resource set is configured for uplink in part of RBs, and is configured for downlink in another part of RBs.

[0177] As an embodiment, each symbol in the reference time domain resource set is used for uplink in part of RBs, and is used for downlink in another part of RBs.

[0178] As an embodiment, at least one symbol in the reference time domain resource set is configured for uplink in part of RBs in a serving cell, and is configured for downlink in another part of RBs.

[0179] As an embodiment, at least one symbol in the reference time domain resource set is used for uplink in part of RBs in a serving cell, and is used for downlink in another part of RBs.

[0180] As an embodiment, each symbol in the reference time domain resource set is configured for uplink in part of RBs in a serving cell, and is configured for downlink in another part of RBs.

[0181] As an embodiment, each symbol in the reference time domain resource set is used for uplink in part of RBs in a serving cell, and is used for downlink in another part of RBs.

[0182] As an embodiment, at least one symbol in the reference time domain resource set is configured for uplink in part of RBs in one BWP, and is configured for downlink in another part of RBs.

[0183] As an embodiment, at least one symbol in the reference time domain resource set is used for uplink in part of RBs in one BWP, and is used for downlink in another part of RBs.

[0184] As an embodiment, each symbol in the reference time domain resource set is configured for uplink in part of RBs in one BWP, and is configured for downlink in another part of RBs.

[0185] As an embodiment, each symbol in the reference time domain resource set is used for uplink in part of RBs in one BWP, and is used for downlink in another part of RBs.

[0186] As an embodiment, any symbol in the reference time domain resource set is configured as DL by a higher layer parameter.

[0187] As an embodiment, any symbol in the reference time domain resource set is configured as DL or Flexible by a higher layer parameter.

[0188] As an embodiment, each symbol in the reference time domain resource set is configured as DL by a higher layer parameter.

[0189] As an embodiment, each symbol in the reference time domain resource set is configured as DL or Flexible by a higher layer parameter.

[0190] As an embodiment, the reference time domain resource set includes multiple symbols, at least one symbol in the reference time domain resource set is configured as DL by a higher layer parameter, and at least one symbol in the reference time domain resource set is configured as Flexible by a higher layer parameter.

[0191] As an embodiment, the reference time domain resource set is configured for a service cell; on the service cell, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one RB is used for uplink transmission.

[0192] As an embodiment, the reference time domain resource set is configured to at least one BWP; on the at least one BWP, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0193] As an embodiment, the reference time domain resource set is configured to a BWP; on the one BWP, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one RB is used for uplink transmission.

[0194] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and ULBWP, and on the UL BWP in the pair of DL BWP and UL BWP, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0195] As an embodiment, the reference time domain resource set is configured to a DL BWP; the first UL BWP is the UL BWP in a pair of DL BWP and UL BWP to which the DL BWP belongs; on the first ULBWP, in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0196] As an embodiment, the reference time domain resource set is configured for a service cell; on the service cell, in each symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0197] As an embodiment, the reference time domain resource set is configured to at least one BWP; on the at least one BWP, in each symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0198] As an embodiment, the reference time domain resource set is configured to a BWP; on the one BWP, in each symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0199] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and ULBWP, and on the UL BWP in the pair of DL BWP and UL BWP, in each symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0200] As an embodiment, the reference time domain resource set is configured to a DL BWP; the first UL BWP is the UL BWP in a pair of DL BWP and UL BWP to which the DL BWP belongs; on the first ULBWP, in each symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0201] As an embodiment, the RB includes a positive integer number of subcarriers.

[0202] As an embodiment, the RB includes a positive integer number of consecutive subcarriers.

[0203] As an embodiment, the RB includes 12 consecutive subcarriers.

[0204] As an embodiment, the specific definition of the RB refers to Chapter 4 of 3GPP TS 38.211.

[0205] As an embodiment, the one serving cell is a cell where the first information block is transmitted.

[0206] As an embodiment, the one serving cell is a cell in which the first information block is configured.

[0207] As an embodiment, the one serving cell is a cell to which the first information block is applied.

[0208] As an embodiment, the one serving cell is a cell including the first information block.

[0209] As an embodiment, the at least one BWP is a BWP in the one serving cell.

[0210] As an embodiment, the at least one BWP belongs to the one service cell.

[0211] As an embodiment, the one BWP is a BWP in the one serving cell.

[0212] As an embodiment, the pair of DL BWP and UL BWP is a pair of DL BWP and UL BWP in the one serving cell.

[0213] As an embodiment, the reference time domain resource set includes symbols used for full duplex / SBFD.

[0214] As an embodiment, each symbol in the reference time domain resource set is used for full duplex / SBFD.

[0215] As an embodiment, any symbol that does not belong to the reference time domain resource set is used only for uplink or only for downlink.

[0216] As an embodiment, any symbol that does not belong to the reference time domain resource set is configured only for uplink or only for downlink.

[0217] As an embodiment, any symbol that does not belong to the reference time domain resource set is only used for uplink or only used for downlink in the one serving cell.

[0218] As an embodiment, any symbol that does not belong to the reference time domain resource set is configured only for uplink or only for downlink in the one serving cell.

[0219] As an embodiment, any symbol that does not belong to the reference time domain resource set is only used for uplink or only used for downlink in the at least one BWP.

[0220] As an embodiment, any symbol that does not belong to the reference time domain resource set is configured only for uplink or only for downlink in the at least one BWP.

[0221] As an embodiment, any symbol that does not belong to the reference time domain resource set is only used for uplink or only used for downlink in the one BWP.

[0222] As an embodiment, any symbol that does not belong to the reference time domain resource set is configured only for uplink or only for downlink in the one BWP.

[0223] As an embodiment, any symbol that does not belong to the reference time domain resource set is only used for uplink on the UL BWP in the pair of DL BWP and UL BWP, and is only used for downlink on the DL BWP in the pair of DL BWP and UL BWP.

[0224] As an embodiment, any symbol that does not belong to the reference time domain resource set is configured only for uplink on the UL BWP in the pair of DL BWP and UL BWP, and is configured only for downlink on the DL BWP in the pair of DL BWP and UL BWP.

[0225] As an embodiment, the first PRACH occasion is a PRACH occasion.

[0226] As an embodiment, the first PRACH opportunity is a valid PRACH opportunity.

[0227] As a sub-embodiment of the above embodiment, the meaning of "valid PRACH opportunity" includes: a PRACH opportunity that can be used to transmit a random access preamble.

[0228] As a sub-embodiment of the above embodiment, the meaning of "valid PRACH opportunity" includes: a PRACH opportunity allowed to be used for transmitting a random access preamble.

[0229] As a sub-embodiment of the above embodiment, the meaning of "valid PRACH opportunity" includes: only when a PRACH opportunity is a valid PRACH opportunity, can this PRACH opportunity be used to transmit a random access preamble.

[0230] As an embodiment, the first PRACH opportunity is a transmission opportunity.

[0231] As an embodiment, the first PRACH opportunity is a transmission opportunity of a random access preamble.

[0232] As an embodiment, the first PRACH opportunity is an available transmission opportunity of a random access preamble.

[0233] As an embodiment, the first PRACH opportunity is a valid transmission opportunity of a random access preamble.

[0234] As an embodiment, the first PRACH opportunity is a transmission opportunity of a random access preamble.

[0235] As an embodiment, the first PRACH opportunity is a transmission of a random access preamble.

[0236] As an embodiment, the first PRACH opportunity includes resources occupied by one transmission of a random access preamble.

[0237] As an embodiment, the first PRACH opportunity is the resources occupied by one transmission of a random access preamble.

[0238] As an embodiment, the first PRACH opportunity includes time resources occupied by one transmission of a random access preamble.

[0239] As an embodiment, the first PRACH opportunity is a time resource occupied by a transmission of a random access preamble.

[0240] As an embodiment, the first PRACH opportunity includes frequency resources occupied by one transmission of a random access preamble.

[0241] As an embodiment, the first PRACH opportunity is a frequency resource occupied by a transmission of a random access preamble.

[0242] As an embodiment, the first PRACH opportunity includes the time resources and frequency resources occupied by one transmission of a random access preamble.

[0243] As an embodiment, the first PRACH opportunity is the time resources and frequency resources occupied by one transmission of a random access preamble.

[0244] As an embodiment, the first PRACH opportunity includes resources that can be occupied by one transmission of a random access preamble.

[0245] As an embodiment, the first PRACH opportunity is a resource that can be occupied by one transmission of a random access preamble.

[0246] As an embodiment, the first PRACH opportunity includes time resources that can be occupied by one transmission of a random access preamble.

[0247] As an embodiment, the first PRACH opportunity is a time resource that can be occupied by one transmission of a random access preamble.

[0248] As an embodiment, the first PRACH opportunity includes frequency resources that can be occupied by one transmission of a random access preamble.

[0249] As an embodiment, the first PRACH opportunity is a frequency resource that can be occupied by one transmission of a random access preamble.

[0250] As an embodiment, the first PRACH opportunity includes time resources and frequency resources that can be occupied by one transmission of a random access preamble.

[0251] As an embodiment, the first PRACH opportunity is the time resources and frequency resources that can be occupied by one transmission of a random access preamble.

[0252] As an embodiment, the first PRACH opportunity is a transmission opportunity of the first random access preamble.

[0253] As an embodiment, the first PRACH opportunity is an available transmission opportunity of the first random access preamble.

[0254] As an embodiment, the first PRACH opportunity is a valid transmission opportunity of the first random access preamble.

[0255] As an embodiment, the first PRACH opportunity is a transmission opportunity of the first random access preamble.

[0256] As an embodiment, the first PRACH opportunity includes resources occupied by transmitting the first random access preamble.

[0257] As an embodiment, the first PRACH opportunity is the resources occupied by transmitting the first random access preamble.

[0258] As an embodiment, the first PRACH opportunity includes the time resources occupied by transmitting the first random access preamble.

[0259] As an embodiment, the first PRACH opportunity is the time resource occupied by transmitting the first random access preamble.

[0260] As an embodiment, the first PRACH opportunity includes the frequency resources occupied by transmitting the first random access preamble.

[0261] As an embodiment, the first PRACH opportunity is the frequency resources occupied by transmitting the first random access preamble.

[0262] As an embodiment, the first PRACH opportunity includes the time resources and frequency resources occupied by transmitting the first random access preamble.

[0263] As an embodiment, the first PRACH opportunity is the time resources and frequency resources occupied by transmitting the first random access preamble.

[0264] As an embodiment, the transmission includes: sending.

[0265] As an embodiment, the transmission refers to: sending.

[0266] As an embodiment, the first random access preamble is a random access preamble.

[0267] As an embodiment, the format of the first random access preamble includes: Format 0, Format 1, Format 2, Format 3.

[0268] As an embodiment, the format of the first random access preamble is one of Format 0, Format 1, Format 2, and Format 3.

[0269] As an embodiment, the formats of the first random access preamble include: Format A1, Format A2, Format A3, Format B1, Format B2, Format B3, Format B4, Format C0, and FormatC2.

[0270] As an embodiment, the format of the first random access preamble is one of Format A1, Format A2, Format A3, Format B1, Format B2, Format B3, Format B4, Format C0, and Format C2.

[0271] As an embodiment, the format of the first random access preamble also includes: Format A1 / B1, Format A2 / B2, Format A3 / B3.

[0272] As an embodiment, the format of the first random access preamble is one of Format A1 / B1, Format A2 / B2, and Format A3 / B3.

[0273] As an embodiment, the specific definition of the format of the first random access preamble mentioned above refers to Section 6.3.3 of 3GPP TS 38.211.

[0274] As an embodiment, the first root sequence set is used to generate N random access preambles.

[0275] As an embodiment, N is an integer.

[0276] As an embodiment, N is a positive integer.

[0277] As an embodiment, the value of N is not greater than 64.

[0278] As an embodiment, the value of N is equal to 64.

[0279] As an embodiment, the first random access preamble is a random access preamble among the N random access preambles.

[0280] As an embodiment, the first random access preamble is which random access preamble among the N random access preambles is selected by a MAC entity.

[0281] As an embodiment, the first random access preamble is which random access preamble among the N random access preambles is selected by a MAC entity of the first node.

[0282] As an embodiment, the first random access preamble is which random access preamble among the N random access preambles is randomly selected by a MAC entity of the first node.

[0283] As an embodiment, the first random access preamble is which random access preamble among the N random access preambles is randomly selected with equal probability by the MAC entity of the first node.

[0284] As an embodiment, which random access preamble among the N random access preambles the first random access preamble is is configured by a third higher layer parameter.

[0285] As an embodiment, the name of the third higher layer parameter includes "ra-Preamble".

[0286] As an embodiment, the third higher layer parameter is ra-PreambleStartIndex.

[0287] As an embodiment, the third higher layer parameter is ra-PreambleIndex.

[0288] As an embodiment, the first root sequence set includes one or more root sequences.

[0289] As an embodiment, the first root sequence set includes only one root sequence.

[0290] As an embodiment, the first root sequence set includes multiple root sequences.

[0291] As an embodiment, the lengths of the root sequences in the first root sequence set are the same.

[0292] As an embodiment, the length of the root sequence in the first root sequence set is L.

[0293] As an embodiment, the length of each root sequence in the first root sequence set is L.

[0294] As an embodiment, L is a positive integer.

[0295] As an embodiment, the value of L is one of 839, 139, 1151, and 571.

[0296] As an embodiment, the value of L is 839.

[0297] As an embodiment, the value of L is 139.

[0298] As an embodiment, said L is configured by a second higher layer parameter.

[0299] As an embodiment, the root sequences in the first root sequence set have continuous logical indexes.

[0300] As an embodiment, the value range of the logical index is a continuous integer from 0 to (the L-2).

[0301] As an embodiment, the logical index of the root sequence with the smallest logical index in the first root sequence set is configured by the second higher layer parameter.

[0302] As an embodiment, the name of the second higher layer parameter includes "RootSequenceIndex".

[0303] As an embodiment, the name of the second higher layer parameter includes "rootSequenceIndex".

[0304] As an embodiment, the second higher layer parameter includes one of prach-RootSequenceIndex, rootSequenceIndex-BFR or msgA-PRACH-RootSequenceIndex.

[0305] As an embodiment, the second higher layer parameter is prach-RootSequenceIndex.

[0306] As an embodiment, the second higher layer parameter is rootSequenceIndex-BFR.

[0307] As an embodiment, the second higher layer parameter is msgA-PRACH-RootSequenceIndex.

[0308] As an embodiment, the number of root sequences included in the first root sequence set is sufficient to generate the N random access preambles.

[0309] As an embodiment, the number of root sequences included in the first root sequence set is the minimum number sufficient to generate the N random access preambles.

[0310] As an embodiment, the root sequences in the first root sequence set generate the N random access preambles through cyclic shift.

[0311] As an embodiment, a root sequence in the first root sequence set is a random access preamble.

[0312] As an embodiment, a root sequence in the first root sequence set generates a random access preamble through a cyclic shift.

[0313] As an embodiment, a root sequence in the first root sequence set generates v random access preambles through v cyclic shifts, where v is a positive integer.

[0314] As an embodiment, starting from the root sequence with the smallest logical index in the first root sequence set, the root sequences in the first root sequence set are incremented by logical index, and random access preambles are generated in sequence through cyclic shift until the N random access preambles are generated.

[0315] As an embodiment, any root sequence in the first root sequence set is a pseudo-random sequence.

[0316] As an embodiment, any root sequence in the first root sequence set is a ZC (Zadoff-Chu) sequence.

[0317] As an embodiment, for the specific definitions of ra-PreambleIndex, ra-PreambleStartIndex, prach-RootSequenceIndex, rootSequenceIndex-BFR, and msgA-PRACH-RootSequenceIndex, refer to Section 6.3.2 of 3GPP TS 38.331, and for the specific process of generating a random access preamble, refer to Section 6.3.3 of 3GPP TS38.211.

[0318] As an embodiment, the candidate set of the first PRACH opportunity is one of the first PRACH opportunity set or the second PRACH opportunity set.

[0319] As an embodiment, the candidate set of the first PRACH opportunity is the first PRACH opportunity set, and the first PRACH opportunity is a PRACH opportunity in the first PRACH opportunity set.

[0320] As an embodiment, the candidate set of the first PRACH opportunity is the second PRACH opportunity set, and the first PRACH opportunity is a PRACH opportunity in the second PRACH opportunity set.

[0321] As an embodiment, the first PRACH opportunity set includes at least one PRACH opportunity.

[0322] As an embodiment, the first PRACH opportunity set includes at least one valid PRACH opportunity.

[0323] As an embodiment, the second PRACH opportunity set includes at least one PRACH opportunity.

[0324] As an embodiment, the second PRACH opportunity set includes at least one valid PRACH opportunity.

[0325] As an embodiment, the first PRACH opportunity set is configured by higher layer signaling.

[0326] As an embodiment, the first PRACH opportunity set is configured by RRC signaling.

[0327] As an embodiment, the first PRACH opportunity set is configured by part or all of the fields in an RRC IE.

[0328] As an embodiment, the first PRACH opportunity set is configured by part or all of the fields of each RRC IE in multiple RRC IEs.

[0329] As an embodiment, the first PRACH opportunity set is configured by one or more RRC IEs.

[0330] As an embodiment, the name of the RRC IE configuring the first PRACH opportunity set includes "RACH-Config".

[0331] As an embodiment, the name of the RRC IE configuring the first PRACH opportunity set includes "RACH-ConfigGeneric".

[0332] As an embodiment, the RACH-ConfigGeneric IE configures the first PRACH opportunity set.

[0333] As an embodiment, the RACH-ConfigGenericTwoStepRA IE configures the first PRACH opportunity set.

[0334] As an embodiment, the second PRACH opportunity set is configured by higher layer signaling.

[0335] As an embodiment, the second PRACH opportunity set is configured by RRC signaling.

[0336] As an embodiment, the second PRACH opportunity set is configured by part or all of the fields in an RRC IE.

[0337] As an embodiment, the second PRACH opportunity set is configured by part or all of the fields of each RRC IE in multiple RRC IEs.

[0338] As an embodiment, the second PRACH opportunity set is configured by one or more RRC IEs.

[0339] As an embodiment, the name of the RRC IE configuring the second PRACH opportunity set includes "RACH-Config".

[0340] As an embodiment, the name of the RRC IE configuring the second PRACH opportunity set includes "RACH-ConfigGeneric".

[0341] As an embodiment, RACH-ConfigGeneric IE configures the second PRACH opportunity set.

[0342] As an embodiment, the RACH-ConfigGenericTwoStepRA IE configures the second PRACH opportunity set.

[0343] As an embodiment, the first PRACH opportunity set and the second PRACH opportunity set are configured by the same RRC IE.

[0344] As an embodiment, the first PRACH opportunity set and the second PRACH opportunity set are configured by the same RACH-ConfigGeneric IE.

[0345] As an embodiment, the first PRACH opportunity set and the second PRACH opportunity set are configured by the same RACH-ConfigGenericTwoStepRA IE.

[0346] As an embodiment, the first PRACH opportunity set and the second PRACH opportunity set are configured by different RRC IEs.

[0347] As an embodiment, the first PRACH opportunity set and the second PRACH opportunity set are configured by two different RACH-ConfigGeneric IEs.

[0348] As an embodiment, the first PRACH opportunity set and the second PRACH opportunity set are configured by two different RACH-ConfigGenericTwoStepRA IEs.

[0349] As an embodiment, part or all of the PRACH opportunities in the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain.

[0350] As an embodiment, all PRACH opportunities in the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain.

[0351] As an embodiment, at least one PRACH opportunity in the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain.

[0352] As an embodiment, the time slot where at least one PRACH opportunity in the first PRACH opportunity set is located is orthogonal to the reference time domain resource set in the time domain.

[0353] As an embodiment, the symbols occupied by at least one PRACH opportunity in the first PRACH opportunity set are orthogonal to the reference time domain resource set in the time domain.

[0354] As an embodiment, symbols occupied by at least one PRACH opportunity in the first PRACH opportunity set do not belong to the reference time domain resource set.

[0355] As an embodiment, any PRACH opportunity in the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain.

[0356] As an embodiment, the time slot where any PRACH opportunity in the first PRACH opportunity set is located is orthogonal to the reference time domain resource set in the time domain.

[0357] As an embodiment, the symbols occupied by any PRACH opportunity in the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain.

[0358] As an embodiment, the symbols occupied by any PRACH opportunity in the first PRACH opportunity set do not belong to the reference time domain resource set.

[0359] As an embodiment, part or all of the PRACH opportunities in the second PRACH opportunity set overlap with the reference time domain resource set in the time domain.

[0360] As an embodiment, all PRACH opportunities in the second PRACH opportunity set and the reference time domain resource set overlap in the time domain.

[0361] As an embodiment, the second PRACH opportunity set belongs to the reference time domain resource set.

[0362] As an embodiment, at least one PRACH opportunity in the second PRACH opportunity set belongs to the reference time domain resource set in the time domain, and at least one PRACH opportunity in the second PRACH opportunity set is orthogonal to the reference time domain resource set in the time domain.

[0363] As an embodiment, at least one PRACH opportunity in the second PRACH opportunity set overlaps with the reference time domain resource set in the time domain.

[0364] As an embodiment, the time slot where at least one PRACH opportunity in the second PRACH opportunity set is located overlaps with the reference time domain resource set in the time domain.

[0365] As an embodiment, symbols occupied by at least one PRACH opportunity in the second PRACH opportunity set overlap with the reference time domain resource set in the time domain.

[0366] As an embodiment, part or all of the symbols occupied by at least one PRACH opportunity in the second PRACH opportunity set overlap with the reference time domain resource set in the time domain.

[0367] As an embodiment, only a portion of the symbols occupied by at least one PRACH opportunity in the second PRACH opportunity set overlaps with the reference time domain resource set in the time domain.

[0368] As an embodiment, symbols occupied by at least one PRACH opportunity in the second PRACH opportunity set belong to the reference time domain resource set.

[0369] As an embodiment, any PRACH opportunity in the second PRACH opportunity set overlaps with the reference time domain resource set in the time domain.

[0370] As an embodiment, the time slot where any PRACH opportunity in the second PRACH opportunity set is located overlaps with the reference time domain resource set in the time domain.

[0371] As an embodiment, the symbols occupied by any PRACH opportunity in the second PRACH opportunity set overlap with the reference time domain resource set in the time domain.

[0372] As an embodiment, part or all of the symbols occupied by any PRACH opportunity in the second PRACH opportunity set overlap with the reference time domain resource set in the time domain.

[0373] As an embodiment, only a portion of the symbols occupied by any PRACH opportunity in the second PRACH opportunity set overlaps with the reference time domain resource set in the time domain.

[0374] As an embodiment, the symbols occupied by any PRACH opportunity in the second PRACH opportunity set belong to the reference time domain resource set.

[0375] As an embodiment, the reference time domain resource set is configured for one serving cell, and the first PRACH opportunity set and the second PRACH opportunity set both belong to the one serving cell.

[0376] As an embodiment, the reference time domain resource set is configured for one serving cell, and the first PRACH opportunity set and the second PRACH opportunity set both belong to the same BWP in the one serving cell.

[0377] As an embodiment, the reference time domain resource set is configured for one serving cell, and the first PRACH opportunity set and the second PRACH opportunity set both belong to the same UL BWP in the one serving cell.

[0378] As an embodiment, the reference time domain resource set is configured to at least one BWP, and the first PRACH opportunity set and the second PRACH opportunity set both belong to the at least one BWP.

[0379] As an embodiment, the reference time domain resource set is configured for at least one BWP, and the first PRACH opportunity set and the second PRACH opportunity set both belong to the same BWP in the at least one BWP.

[0380] As an embodiment, the reference time domain resource set is configured to a BWP, and the first PRACH opportunity set and the second PRACH opportunity set both belong to the one BWP.

[0381] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and UL BWP, and the first PRACH opportunity set and the second PRACH opportunity set both belong to the UL BWP in the pair of DL BWP and UL BWP.

[0382] As an embodiment, the reference time domain resource set is configured to a DL BWP, the first PRACH opportunity set and the second PRACH opportunity set belong to the same UL BWP, and the same UL BWP and the one DLBWP are a pair of DL BWP and UL BWP.

[0383] As an embodiment, center frequencies of the DL BWP and the UL BWP in a pair of DL BWP and UL BWP are aligned.

[0384] As an embodiment, the center frequencies of the DL BWP and the UL BWP in a pair of DL BWP and UL BWP are the same.

[0385] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of subcarriers included in the DL BWP in the pair of DL BWP and UL BWP is different from the number of subcarriers included in the UL BWP in the pair of DL BWP and UL BWP.

[0386] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of subcarriers included in the DL BWP in the pair of DL BWP and UL BWP is the same as the number of subcarriers included in the UL BWP in the pair of DL BWP and UL BWP.

[0387] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of subcarriers included in the DL BWP in the pair of DL BWP and UL BWP is greater than the number of subcarriers included in the UL BWP in the pair of DL BWP and UL BWP.

[0388] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of subcarriers included in the DL BWP in the pair of DL BWP and UL BWP is smaller than the number of subcarriers included in the UL BWP in the pair of DL BWP and UL BWP.

[0389] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of RBs included in the DL BWP in the pair of DL BWP and UL BWP is different from the number of RBs included in the UL BWP in the pair of DL BWP and UL BWP.

[0390] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of RBs included in the DL BWP in the pair of DL BWP and UL BWP is the same as the number of RBs included in the UL BWP in the pair of DL BWP and UL BWP.

[0391] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of RBs included in the DL BWP in the pair of DL BWP and UL BWP is greater than the number of RBs included in the UL BWP in the pair of DL BWP and UL BWP.

[0392] As an embodiment, center frequencies of a DL BWP and a UL BWP in a pair of DL BWP and UL BWP are aligned, and the number of RBs included in the DL BWP in the pair of DL BWP and UL BWP is smaller than the number of RBs included in the UL BWP in the pair of DL BWP and UL BWP.

[0393] As an embodiment, the sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process.

[0394] As an embodiment, the sending of the first random access preamble belongs only to one of the first type of random access process or the second type of random access process.

[0395] As an embodiment, the sending of the first random access preamble belongs to the first type of random access process.

[0396] As an embodiment, the sending of the first random access preamble belongs to the second type of random access process.

[0397] As an embodiment, the first type of random access procedure is contention based.

[0398] As an embodiment, the second type of random access process is contention free.

[0399] As an embodiment, the first type of random access process is contention-free.

[0400] As an embodiment, the second type of random access process is contention-based.

[0401] As an embodiment, the first type of random access process is a four-step random access process.

[0402] As an embodiment, the second type of random access process is a two-step random access process.

[0403] As an embodiment, the first type of random access process is a two-step random access process.

[0404] As an embodiment, the second type of random access process is a four-step random access process.

[0405] As an embodiment, the first type of random access process is a Type-1 random access process.

[0406] As an embodiment, the second type of random access process is a Type-2 random access process.

[0407] As an embodiment, the first type of random access process is a Type-2 random access process.

[0408] As an embodiment, the second type of random access process is a Type-1 random access process.

[0409] As an embodiment, the specific definition of Type-1 random access process and Type-2 random access process refers to Chapter 8 of 3GPP TS 38.213.

[0410] As an embodiment, the first type of random access procedure and the second type of random access procedure have different priorities.

[0411] As an embodiment, the priority of the second type of random access process is higher than that of the first type of random access process.

[0412] As an embodiment, the priority of any random access process in the second type of random access process is higher than the priority of any random access process in the first type of random access process.

[0413] As an embodiment, the event set for initiating the first type of random access procedure is different from the event set for initiating the second type of random access procedure.

[0414] As an embodiment, any event in the event set for initiating the second type of random access process does not belong to the event set for initiating the first type of random access process.

[0415] As an embodiment, the characteristics applicable to the first type of random access procedure are different from the characteristics applicable to the second type of random access procedure.

[0416] As an embodiment, any characteristic applicable to the first type of random access procedure is not a characteristic applicable to the second type of random access procedure.

[0417] As an embodiment, at least one characteristic applies to the first type of random access process, at least one characteristic applies to the second type of random access process, and any one of the at least one characteristic applicable to the second type of random access process is not a characteristic of the at least one characteristic applicable to the second type of random access process.

[0418] As an embodiment, when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set.

[0419] As an embodiment, the essence of the above method includes: when the sending of the first random access preamble belongs to the first type of random access process, the first PRACH opportunity cannot occupy the time domain resources in the reference time domain resource set.

[0420] As an embodiment, the essence of the above method includes: when the sending of the first random access preamble belongs to the first type of random access process, the first PRACH opportunity cannot occupy the SBFD symbol.

[0421] As an embodiment, the essence of the above method includes: when the sending of the first random access preamble belongs to the first type of random access process, the first random access preamble cannot be sent in a SBFD symbol.

[0422] As an embodiment, when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0423] As an embodiment, the essence of the above method includes: when the sending of the first random access preamble belongs to the second type of random access process, the first PRACH opportunity is allowed to occupy the time domain resources in the reference time domain resource set.

[0424] As an embodiment, the essence of the above method includes: when the sending of the first random access preamble belongs to the second type of random access process, the first PRACH opportunity is allowed to occupy the SBFD symbol.

[0425] As an embodiment, the essence of the above method includes: when the sending of the first random access preamble belongs to the second type of random access process, the first random access preamble is allowed to be sent in a SBFD symbol.

[0426] As an embodiment, the first receiver receives a SS / PBCH (Synchronization Signal / Physical Broadcast Channel) block.

[0427] As an embodiment, before sending the first random access preamble, the first receiver receives a SS / PBCH block.

[0428] As an embodiment, the random access process to which the sending of the first random access preamble belongs includes: sending the first random access preamble, receiving a random access response (random access response, RAR) of the first random access preamble, sending a PUSCH (Physical Uplink Shared Channel) scheduled by the random access response of the first random access preamble, and receiving a PDSCH for contention resolution.

[0429] As an embodiment, the first receiver receives a response to the first random access preamble.

[0430] As an embodiment, after sending the first random access preamble, the first receiver receives a response to the first random access preamble.

[0431] As an embodiment, the first transmitter sends a PUSCH scheduled by a response to the first random access preamble.

[0432] As an embodiment, the first receiver receives a PDSCH for contention resolution.

[0433] As an embodiment, the random access process to which the sending of the first random access preamble belongs includes: sending the first random access preamble and a PUSCH, and receiving a random access response.

[0434] As an embodiment, the first transmitter sends the first random access preamble and a PUSCH.

[0435] As an embodiment, the first receiver receives a random access response.

[0436] Example 2

[0437] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 shown.

[0438] Attached Figure 2The network architecture 200 of LTE (Long-Term Evolution), LTE-A (Long-Term Evolution Advanced) and future 5G systems is illustrated. The network architecture 200 of LTE, LTE-A and future 5G systems is called EPS (Evolved Packet System) 200. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. 5GS / EPS200 may include one or more UEs (User Equipment) 201, a UE 241 communicating with UE 201 via a sidelink, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet service 230. 5GS / EPS200 may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. Figure 2As shown, 5GS / EPS200 provides packet switching services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks that provide circuit switching services. NG-RAN202 includes NR (New Radio) Node B (gNB) 203 and other gNBs204. gNB203 provides user and control plane protocol terminations toward UE201. gNB203 can be connected to other gNBs204 via an Xn interface (e.g., backhaul). gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmit receive point), or some other suitable term. gNB203 provides an access point to 5GC / EPC210 for UE201. Examples of UE 201 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband physical network devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. gNB203 is connected to 5GC / EPC210 via S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is a control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management.All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which is itself connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and Packet switching services.

[0439] As an embodiment, the first node in the present application includes the UE201.

[0440] As an embodiment, the second node in the present application includes the gNB203.

[0441] As an embodiment, the wireless link between the UE201 and the gNB203 includes a cellular network link.

[0442] As an embodiment, the sender of the first information block includes the gNB203.

[0443] As an embodiment, the receiver of the first information block includes the UE201.

[0444] As an embodiment, the sender of the second information block includes the gNB203.

[0445] As an embodiment, the receiver of the second information block includes the UE201.

[0446] As an embodiment, the recipient of the first random access preamble includes the gNB203.

[0447] As an embodiment, the sender of the first random access preamble includes the UE201.

[0448] As an embodiment, the gNB203 supports SBFD.

[0449] As an embodiment, the gNB203 supports a more flexible duplex mode or a full-duplex mode.

[0450] As an embodiment, the UE 201 supports SBFD.

[0451] As an embodiment, the UE 201 supports a more flexible duplex mode or a full-duplex mode.

[0452] Example 3

[0453] Embodiment 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application, as shown in the attached figure. Figure 3 shown.

[0454] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 between a first communication node device (UE, gNB or RSU in V2X) and a second communication node device (gNB, UE or RSU in V2X), or between two UEs is shown with three layers: Layer 1, Layer 2 and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY301 in this article. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first communication node device and the second communication node device, or between two UEs. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second communication node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first communication node device between the second communication node device. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layer using RRC signaling between the second communication node device and the first communication node device. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The radio protocol architecture used for the first communication node device and the second communication node device in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. Although not shown in the figure, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., an IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

[0455] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0456] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0457] As an embodiment, the higher layer in the present application refers to a layer above the physical layer.

[0458] As an embodiment, the first information block is generated in the RRC sublayer 306.

[0459] As an embodiment, the first information block is generated in the MAC sublayer 302 or the MAC sublayer 352.

[0460] As an embodiment, the first information block is generated in the PHY301 or the PHY351.

[0461] As an embodiment, the second information block is generated in the RRC sublayer 306.

[0462] As an embodiment, the second information block is generated in the MAC sublayer 302 or the MAC sublayer 352.

[0463] As an embodiment, the second information block is generated in the PHY301 or the PHY351.

[0464] As an embodiment, the first random access preamble is generated in the PHY301.

[0465] As an embodiment, the first random access preamble is generated in the PHY351.

[0466] Example 4

[0467] Embodiment 4 illustrates a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in the attached figure. Figure 4 Attached Figure 4 is a block diagram of a first communication device 410 and a second communication device 450 communicating with each other in an access network.

[0468] The first communication device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 and an antenna 420 .

[0469] The second communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0470] In transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 layer. In the DL, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and allocation of radio resources to the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, as well as constellation mapping based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM). The multi-antenna transmit processor 471 performs digital spatial precoding on the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing to generate one or more parallel The transmit processor 416 then maps each parallel stream to a subcarrier, multiplexes the modulated symbols with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to different antennas 420.

[0471] In the transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any parallel stream destined for the second communication device 450. The symbols on each parallel stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 storing program codes and data. The memory 460 may be referred to as a computer-readable medium. In DL (DownLink, downlink), the controller / processor 459 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing. The controller / processor 459 is also responsible for error detection using confirmation (ACK) and / or negative confirmation (NACK) protocols to support HARQ operations.

[0472] In the transmission from the second communication device 450 to the first communication device 410, at the second communication device 450, a data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function at the first communication device 410 described in DL, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on the radio resource allocation of the first communication device 410, and implements L2 layer functions for the user plane and the control plane. The controller / processor 459 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the first communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated parallel stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0473] In the transmission from the second communication device 450 to the first communication device 410, the function at the first communication device 410 is similar to the reception function at the second communication device 450 described in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer-readable medium. The controller / processor 475 provides demultiplexing between transmission and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the second communication device 450. The upper layer data packets from the controller / processor 475 can be provided to the core network. The controller / processor 475 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0474] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The second communication device 450 device at least: receives a first information block, the first information block indicates a reference time domain resource set, the reference time domain resource set includes one or more symbols configured as DL by higher layer parameters; sends a first random access preamble in a first PRACH opportunity, the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; wherein the sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0475] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: receiving a first information block, the first information block indicating a reference time domain resource set, the reference time domain resource set including one or more symbols configured as DL by higher layer parameters; sending a first random access preamble in a first PRACH opportunity, the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; wherein the sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0476] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, wherein the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends a first information block, the first information block indicates a reference time domain resource set, the reference time domain resource set includes one or more symbols configured as DL by higher layer parameters; receives a first random access preamble in a first PRACH opportunity, the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; wherein, the reception of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the reception of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the reception of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0477] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: sending a first information block, the first information block indicating a reference time domain resource set, the reference time domain resource set including one or more symbols configured as DL by higher layer parameters; receiving a first random access preamble in a first PRACH opportunity, the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; wherein the reception of the first random access preamble belongs to one of a first type of random access process or a second type of random access process; when the reception of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the reception of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0478] As an embodiment, the first node in the present application includes the second communication device 450.

[0479] As an embodiment, the second node in the present application includes the first communication device 410.

[0480] As an embodiment, at least one of {the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460, and the data source 467} is used to receive the first information block in the present application; and at least one of {the antenna 420, the transmitter 418, the transmitting processor 416, the multi-antenna transmitting processor 471, the controller / processor 475, and the memory 476} is used to send the first information block in the present application.

[0481] As an embodiment, at least one of {the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460, and the data source 467} is used to receive the second information block in the present application; and at least one of {the antenna 420, the transmitter 418, the transmitting processor 416, the multi-antenna transmitting processor 471, the controller / processor 475, and the memory 476} is used to send the second information block in the present application.

[0482] As an embodiment, at least one of {the antenna 452, the transmitter 454, the transmit processor 468, the multi-antenna transmit processor 457, the controller / processor 459, and the memory 460} is used to send the first random access preamble in the present application; at least one of {the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller / processor 475, and the memory 476} is used to receive the first random access preamble in the present application.

[0483] Example 5

[0484] Embodiment 5 illustrates a flow chart of transmission according to an embodiment of the present application, as shown in the attached Figure 5 As shown in the attached Figure 5 In the embodiment, the first node U01 and the second node N02 are two communication nodes transmitted via an air interface, respectively, wherein the steps in the dotted box F51 are optional.

[0485] for First node U01 , receiving a first information block in step S5101; receiving a second information block in step S5102; and sending a first random access preamble in a first PRACH opportunity in step S5103.

[0486] for Second node N02 , sending a first information block in step S5201; sending a second information block in step S5202; receiving a first random access preamble in a first PRACH opportunity in step S5203.

[0487] In embodiment 5, the first information block indicates a reference time domain resource set, and the reference time domain resource set includes one or more symbols configured as DL by higher layer parameters; the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; wherein, the sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0488] As an embodiment, the first node U01 is the first node in this application.

[0489] As an embodiment, the second node N02 is the second node in this application.

[0490] As an embodiment, the air interface between the second node N02 and the first node U01 includes a wireless interface between a base station device and a user equipment.

[0491] As an embodiment, the air interface between the second node N02 and the first node U01 includes a wireless interface between a relay node device and a user equipment.

[0492] As an embodiment, the air interface between the second node N02 and the first node U01 includes a wireless interface between user equipments.

[0493] As an embodiment, the second node N02 is a service cell maintaining base station of the first node U01.

[0494] As an embodiment, the steps in the dashed box F51 do not exist.

[0495] As an embodiment, the steps in the dashed box F51 exist.

[0496] As an embodiment, the steps in the dotted box F51 exist, and the method in the first node U01 used for wireless communication includes: receiving a second information block; wherein the second information block indicates a reference frequency domain resource set; the reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameters; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0497] As an embodiment, the steps in the dotted box F51 exist, and the method in the second node N02 used for wireless communication includes: sending a second information block; wherein the second information block indicates a reference frequency domain resource set; the reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameters; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0498] As an embodiment, the first information block is received no later than the second information block is received.

[0499] As an embodiment, the first information block is received earlier than the second information block.

[0500] As an embodiment, the second information block is received no later than the first information block is received.

[0501] As an embodiment, the second information block is received earlier than the first information block.

[0502] As an embodiment, the first information block and the second information block are received simultaneously.

[0503] As an embodiment, the first information block and the second information block are received together.

[0504] As an embodiment, the first information block and the second information block are carried by the same signaling.

[0505] As an embodiment, the first information block and the second information block are carried by the same higher layer signaling.

[0506] As an embodiment, the first information block and the second information block are carried by the same RRC signaling.

[0507] As an embodiment, the first information block and the second information block are carried by different signaling.

[0508] As an embodiment, the first information block and the second information block are carried by the same RRC IE.

[0509] As an embodiment, the first information block and the second information block are respectively carried by two different RRC IEs.

[0510] As an embodiment, the first information block is transmitted on PDSCH.

[0511] As an embodiment, the first information block is transmitted on PDCCH.

[0512] As an embodiment, the second information block is transmitted on PDSCH.

[0513] As an embodiment, the second information block is transmitted on PDCCH.

[0514] As an embodiment, the first information block and the second information block are transmitted on the same PDSCH.

[0515] As an embodiment, the first information block and the second information block are transmitted on different PDSCHs.

[0516] Examples 6A-6B

[0517] Embodiments 6A-6B respectively illustrate schematic diagrams of a first type of random access process and a second type of random access process according to an embodiment of the present application; Figure 6A-6B shown.

[0518] In embodiment 6A, one of the first type of random access procedure and the second type of random access procedure is contention-based, and the other is contention-free-based.

[0519] As an embodiment, the first type of random access procedure is contention based, and the second type of random access procedure is contention free.

[0520] In the above implementation, the first type of random access process is contention-based, which avoids contention-based random access on symbols configured as DL by higher-layer parameters, and reduces cross-link interference (Cross-Link Interference, CLI) between UEs; the second type of random access process is contention-free, allowing contention-free random access on symbols configured as DL by higher-layer parameters, reducing delay and improving coverage.

[0521] As an embodiment, the first type of random access procedure is contention-free, and the second type of random access procedure is contention-based.

[0522] In the above implementation, contention-based random access is allowed on symbols configured as DL by higher layer parameters, which reduces the probability of collision, improves the access probability, and reduces delay.

[0523] As an embodiment, the specific definitions of contention-based random access (CBRA) and contention-free random access (CFRA) refer to Section 9.2.6 of 3GPP TS 38.300.

[0524] In embodiment 6B, one of the first type of random access procedure and the second type of random access procedure is a four-step random access procedure, and the other is a two-step random access procedure.

[0525] Typically, the four-step random access process includes: sending a random access preamble, receiving a random access response (RAR), sending a PUSCH scheduled by an RAR uplink grant (UL grant), and receiving a PDSCH for contention resolution; the two-step random access process includes: sending a random access preamble and a PUSCH, and receiving a random access response (RAR).

[0526] As an embodiment, the specific definitions of the four-step random access process and the two-step random access process refer to Section 9.2.6 of 3GPP TS 38.300.

[0527] As an embodiment, the first type of random access process is the four-step random access process, and the second type of random access process is the two-step random access process.

[0528] In the above implementation, a two-step random access process is allowed on symbols configured as DL by higher layer parameters, thereby reducing delay.

[0529] As an embodiment, the first type of random access process is the two-step random access process, and the second type of random access process is the four-step random access process.

[0530] In the above implementation, a four-step random access process is allowed on symbols configured as DL by higher layer parameters, which reduces the probability of collision, improves the access probability, and reduces delay.

[0531] As an embodiment, the four-step random access process is contention-based.

[0532] As an embodiment, the four-step random access process is contention-free.

[0533] As an embodiment, the two-step random access process is contention-based.

[0534] As an embodiment, the two-step random access process is contention-free.

[0535] As an embodiment, the first type of random access process includes a contention-based four-step random access process and a contention-free two-step random access process, and the second type of random access process includes a contention-free four-step random access process and a contention-based two-step random access process.

[0536] As an embodiment, the first type of random access process includes a contention-free four-step random access process and a contention-based two-step random access process, and the second type of random access process includes a contention-based four-step random access process and a contention-free two-step random access process.

[0537] Example 7

[0538] Embodiment 7 illustrates a schematic diagram of the priority of the first type of random access process and the priority of the second type of random access process according to an embodiment of the present application; Figure 7 shown.

[0539] In Embodiment 7, the priority of the first type of random access procedure is lower than the priority of the second type of random access procedure.

[0540] In the above implementation, high-priority random access is allowed on symbols configured as DL by higher-layer parameters, thereby improving access probability and reducing delay.

[0541] As an embodiment, the priority value of the random access process is configured by a higher layer parameter, and the priority value is a non-negative integer or a positive integer; the smaller the priority value, the higher the priority.

[0542] As an embodiment, the priority value is an integer not less than 0.

[0543] As an embodiment, the priority value is an integer not greater than 7.

[0544] As an embodiment, the priority value is a non-negative integer not greater than 7.

[0545] As an embodiment, the priority value ranges from 0 to 7 consecutive integers.

[0546] As an embodiment, the priority value is an integer from 0 to 7.

[0547] As an embodiment, the priority value of a random access procedure is configured by a higher layer parameter whose name includes "featurePriorities".

[0548] As an embodiment, the priority value of a random access procedure is configured by a higher layer parameter featurePriorities-r17.

[0549] As an embodiment, the priority value of a random access procedure is configured by a higher layer parameter whose name includes "FeaturePriority".

[0550] As an embodiment, the priority value of a random access procedure is configured by a higher layer parameter FeaturePriority-r17.

[0551] As an embodiment, the priority value of a random access procedure is configured by a higher layer parameter whose name includes "redCapPriority", a higher layer parameter whose name includes "slicingPriority", a higher layer parameter whose name includes "msg3-Repetitions-Priority", or a higher layer parameter whose name includes "sdt-Priority".

[0552] As an embodiment, the priority value of a random access procedure is configured by a higher layer parameter redCapPriority-r17, a higher layer parameter slicingPriority-r17, a higher layer parameter msg3-Repetitions-Priority-r17, or a higher layer parameter sdt-Priority-r17.

[0553] As an embodiment, for the specific definitions of featurePriorities-r17, FeaturePriority-r17, redCapPriority-r17, slicingPriority-r17, msg3-Repetitions-Priority-r17, and sdt-Priority-r17, please refer to 3GPP TS 38.331.

[0554] As an embodiment, the priority value of the first type of random access process is equal to or greater than a first threshold, and the priority value of the second type of random access process is less than the first threshold; the smaller the priority value, the higher the priority; the first threshold is a positive integer.

[0555] As a sub-embodiment of the above embodiment, the first threshold is an integer between 0 and 7.

[0556] As a sub-embodiment of the above embodiment, the first threshold is a positive integer not greater than 7.

[0557] As a sub-embodiment of the above embodiment, the first threshold is a positive integer less than 7.

[0558] As a sub-embodiment of the above embodiment, the first threshold is a positive integer greater than 0 and less than 7.

[0559] As a sub-embodiment of the above embodiment, the first threshold is configurable.

[0560] As a sub-embodiment of the above embodiment, the first threshold is fixed.

[0561] As a sub-embodiment of the above embodiment, the first threshold is preset.

[0562] As an embodiment, the priority value of the first type of random access process is greater than a first threshold, and the priority value of the second type of random access process is equal to or less than the first threshold; the smaller the priority value, the higher the priority; the first threshold is a positive integer.

[0563] As a sub-embodiment of the above embodiment, the first threshold is an integer between 0 and 7.

[0564] As a sub-embodiment of the above embodiment, the first threshold is an integer not less than 0.

[0565] As a sub-embodiment of the above embodiment, the first threshold is an integer greater than 0.

[0566] As a sub-embodiment of the above embodiment, the first threshold is a positive integer greater than 0 and less than 7.

[0567] As a sub-embodiment of the above embodiment, the first threshold is configurable.

[0568] As a sub-embodiment of the above embodiment, the first threshold is fixed.

[0569] As a sub-embodiment of the above embodiment, the first threshold is preset.

[0570] As an embodiment, the priority of a random access procedure is the priority of an applicable feature of the random access procedure.

[0571] As an embodiment, when only one characteristic is applicable to one random access procedure, the priority of the one random access procedure is the priority of the only one characteristic.

[0572] As an embodiment, when a random access procedure is applicable to multiple characteristics, the priority of the random access procedure is the highest priority among the multiple characteristics.

[0573] As an embodiment, the features include network slicing, RedCap (ReducedCapability), SDT (Small Data Transmission), and NR (NewRadio) coverage enhancement.

[0574] As an embodiment, the characteristics include at least one of network slicing, RedCap (ReducedCapability), SDT (Small Data Transmission), or NR (NewRadio) coverage enhancement.

[0575] As an embodiment, the features include Network Slicing, RedCap (Reduced Capability), SDT (Small Data Transmission), and MSG3 repetition.

[0576] As an embodiment, the characteristics include at least one of network slicing, RedCap (ReducedCapability), SDT (Small Data Transmission), or MSG3 repetition.

[0577] In the above implementation, for the specific definitions of network slicing (Network Slicing), RedCap (Reduced Capability), and SDT (Small Data Transmission), please refer to 3GPP TS38.300 or 3GPP TS 38.321 or 3GPP TS 38.331.

[0578] In the above implementation manner, for the specific definition of NR (New Radio) coverage enhancement, refer to 3GPP TS 38.300.

[0579] In the above implementation, for the specific definition of MSG3 repetition, refer to 3GPP TS 38.321 or 3GPP TS 38.331.

[0580] Typically, the lower the priority value of a feature, the higher the priority of that feature.

[0581] As an embodiment, the priority value of a feature is configured by a higher layer parameter whose name includes "featurePriorities".

[0582] As an embodiment, the priority value of a feature is configured by a higher layer parameter featurePriorities-r17.

[0583] As an example, the priority value of a feature is configured by a higher layer parameter whose name includes "FeaturePriority".

[0584] As an embodiment, the priority value of a feature is configured by a higher layer parameter FeaturePriority-r17.

[0585] As an embodiment, the priority value of the Network Slicing feature is configured by a higher layer parameter whose name includes "slicingPriority".

[0586] As an embodiment, the priority value of the network slicing feature is configured by a higher layer parameter slicingPriority-r17.

[0587] As an embodiment, the priority value of the RedCap feature is configured by a higher layer parameter whose name includes "redCapPriority".

[0588] As an embodiment, the priority value of the RedCap feature is configured by a higher layer parameter redCapPriority-r17.

[0589] As an embodiment, the priority value of this characteristic of SDT is configured by a higher layer parameter whose name includes "sdt-Priority".

[0590] As an embodiment, the priority value of this SDT feature is configured by a higher layer parameter sdt-Priority-r17.

[0591] As an embodiment, the priority value of the NR (New Radio) coverage enhancement feature is configured by a higher layer parameter whose name includes "msg3-Repetitions-Priority".

[0592] As an embodiment, the priority value of the NR (New Radio) coverage enhancement feature is configured by a higher layer parameter msg3-Repetitions-Priority-r17.

[0593] As an embodiment, the priority value of the MSG3 repetition feature is configured by a higher layer parameter whose name includes "msg3-Repetitions-Priority".

[0594] As an embodiment, the priority value of the MSG3 repetition feature is configured by a higher layer parameter msg3-Repetitions-Priority-r17.

[0595] As an embodiment, the priority value of any characteristic applicable to the first type of random access process is equal to or greater than a first threshold, and the priority value of any characteristic applicable to the second type of random access process is less than the first threshold; the smaller the priority value, the higher the priority; the first threshold is a positive integer.

[0596] As a sub-embodiment of the above embodiment, the first threshold is an integer between 0 and 7.

[0597] As a sub-embodiment of the above embodiment, the first threshold is a positive integer not greater than 7.

[0598] As a sub-embodiment of the above embodiment, the first threshold is a positive integer less than 7.

[0599] As a sub-embodiment of the above embodiment, the first threshold is a positive integer greater than 0 and less than 7.

[0600] As a sub-embodiment of the above embodiment, the first threshold is configurable.

[0601] As a sub-embodiment of the above embodiment, the first threshold is fixed.

[0602] As a sub-embodiment of the above embodiment, the first threshold is preset.

[0603] As an embodiment, the priority value of any characteristic applicable to the first type of random access process is greater than a first threshold, and the priority value of any characteristic applicable to the second type of random access process is equal to or less than the first threshold; the smaller the priority value, the higher the priority; the first threshold is a positive integer.

[0604] As a sub-embodiment of the above embodiment, the first threshold is an integer between 0 and 7.

[0605] As a sub-embodiment of the above embodiment, the first threshold is an integer not less than 0.

[0606] As a sub-embodiment of the above embodiment, the first threshold is an integer greater than 0.

[0607] As a sub-embodiment of the above embodiment, the first threshold is a positive integer greater than 0 and less than 7.

[0608] As a sub-embodiment of the above embodiment, the first threshold is configurable.

[0609] As a sub-embodiment of the above embodiment, the first threshold is fixed.

[0610] As a sub-embodiment of the above embodiment, the first threshold is preset.

[0611] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that: the priority value of the first type of random access process is not less than the priority value of the second type of random access process.

[0612] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that: the priority value of the first type of random access process is greater than the priority value of the second type of random access process.

[0613] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that the priority value of a random access process belonging to the first type of random access process is greater than the priority value of a random access process belonging to the second type of random access process.

[0614] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that the priority value of any random access process belonging to the first type of random access process is greater than the priority value of any random access process belonging to the second type of random access process.

[0615] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that the priority value of a characteristic applicable to the first type of random access process is greater than the priority value of a characteristic applicable to the second type of random access process.

[0616] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that the priority value of any characteristic applicable to the first type of random access process is not less than the priority value of any characteristic applicable to the second type of random access process.

[0617] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that the priority value of any characteristic applicable to the first type of random access process is greater than the priority value of any characteristic applicable to the second type of random access process.

[0618] As an embodiment, "the priority of the first type of random access process is lower than the priority of the second type of random access process" means that the priority value of the characteristic applicable to any random access process belonging to the first type of random access process is greater than the priority value of the characteristic applicable to any random access process belonging to the second type of random access process.

[0619] Example 8

[0620] Embodiment 8 illustrates a schematic diagram of a first event set and a second event set according to an embodiment of the present application; Figure 8 shown.

[0621] In Example 8, the first type of random access process is initiated for a first event set, and the second type of random access process is initiated for a second event set; the first event set includes one or more events, the second event set includes one or more events, and any event in the first event set does not belong to the second event set.

[0622] As an embodiment, the first event set and the second event set respectively include at least one event in a reference event set, and the reference event set includes multiple events.

[0623] As an embodiment, the second event set includes some events in a reference event set, the first event set includes at least one event in the reference event set other than the second event set, and the reference event set includes multiple events.

[0624] As an embodiment, the second event set includes some events in a reference event set, the first event set includes all events in the reference event set except the second event set, and the reference event set includes multiple events.

[0625] As an embodiment, the reference event set includes at least multiple events including PDCCH order, SI (System Information) request, Beam failure recovery, reconfiguration with sync, or scheduling request (SR).

[0626] As an embodiment, the reference event set includes at least PDCCH order (command), SI (System Information) request, Beam failure recovery, reconfiguration with sync (synchronous reconfiguration), scheduling request (scheduling request, SR), or multiple events of Initial access.

[0627] As an embodiment, the reference event set includes at least PDCCH order, SI (System Information) request, Beam failure recovery, reconfiguration with sync, scheduling request (SR), Initial access, or multiple events in handover.

[0628] As an embodiment, the reference event set includes at least PDCCH order, SI (System Information) request, Beam failure recovery, reconfiguration with sync, scheduling request (SR), Initial access, or multiple events in DAPS (Dual Active Protocol Stack) handover.

[0629] As an embodiment, the first event set includes Initial access.

[0630] As an embodiment, the first event set includes a scheduling request.

[0631] As an embodiment, the first event set includes SI request.

[0632] As an embodiment, the first event set includes at least one of a scheduling request, an SI request, or an Initialaccess.

[0633] As an embodiment, the first event set includes a scheduling request and an SI request.

[0634] As an embodiment, the first event set includes scheduling request and Initial access.

[0635] As an embodiment, the first event set includes SI request and Initial access.

[0636] As an embodiment, the first event set includes scheduling request, SI request, and Initialaccess.

[0637] As an embodiment, the first event set includes at least a scheduling request, an SI request, and an Initialaccess.

[0638] As an embodiment, the second event set includes PDCCH order.

[0639] In the above implementation, for the PDCCH order, random access is allowed on symbols configured as DL by higher layer parameters, thereby achieving flexibility in system scheduling.

[0640] As an embodiment, the second event set includes Beam failure recovery.

[0641] In the above implementation, in order to recover from beam failure, random access is allowed on symbols configured as DL by higher-layer parameters, thereby achieving beam recovery more quickly.

[0642] As an embodiment, the second event set includes reconfiguration with sync.

[0643] In the above implementation, for reconfiguration with sync, random access is allowed on symbols configured as DL by higher layer parameters, so that synchronous reconfiguration is achieved more quickly and cell switching is achieved more quickly.

[0644] As an embodiment, the second event set includes handover.

[0645] In the above implementation, for handover, random access is allowed on symbols configured as DL by higher layer parameters, so that handover is completed faster and delay is reduced.

[0646] As an embodiment, the second event set includes at least one of PDCCH order, Beam failure recovery, or reconfiguration with sync.

[0647] As an embodiment, the second event set includes PDCCH order, Beam failure recovery, and reconfiguration with sync.

[0648] As an embodiment, the second event set includes at least PDCCH order, Beam failure recovery, and reconfiguration with sync.

[0649] As an embodiment, the second event set includes at least one of PDCCH order, Beam failure recovery, reconfiguration with sync, or handover.

[0650] As an embodiment, the second event set includes PDCCH order, Beam failure recovery, reconfiguration with sync, and handover.

[0651] As an embodiment, the second event set includes at least PDCCH order, Beam failure recovery, reconfiguration with sync, and handover.

[0652] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, and reconfiguration with sync; the first event set includes: scheduling request, SI request, and Initial access.

[0653] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, and reconfiguration with sync; the first event set includes: scheduling request, SI request.

[0654] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, and reconfiguration with sync; the first event set includes: scheduling request, Initial access.

[0655] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, and reconfiguration with sync; the first event set includes: SI request, Initial access.

[0656] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery; the first event set includes: scheduling request, SI request, and Initial access.

[0657] As an embodiment, the second event set includes: PDCCH order, reconfiguration withsync; the first event set includes: scheduling request, SI request, and Initial access.

[0658] As an embodiment, the second event set includes: Beam failure recovery, and reconfiguration with sync; the first event set includes: scheduling request, SI request, and Initial access.

[0659] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, reconfiguration with sync, and handover; the first event set includes: scheduling request, SI request, and Initial access.

[0660] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, reconfiguration with sync, and handover; the first event set includes: scheduling request, SI request.

[0661] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, reconfiguration with sync, and handover; the first event set includes: scheduling request, Initial access.

[0662] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, reconfiguration with sync, and handover; the first event set includes: SI request, and Initial access.

[0663] As an embodiment, the second event set includes: PDCCH order, Beam failure recovery, reconfiguration with sync; the first event set includes: scheduling request, SI request, Initial access, handover.

[0664] As an embodiment, the reference event set includes at least multiple events of the following events:

[0665] - Initial access from RRC_IDLE (RRC idle);

[0666] -RRC connection re-establishment process;

[0667] -When the uplink synchronization state is "out of sync" and in RRC_CONNECTED (RRC connected) or RRC_INACTIVE (RRC inactive)

[0668] When the SDT process is in progress, downlink or uplink data arrives;

[0669] - When there is no PUCCH (Physical Uplink Control Channel) resource available for SR and the SDT procedure in RRC_CONNECTED or RRC_INACTIVE is in progress, uplink data arrives;

[0670] - Scheduling request (SR) failed;

[0671] -RRC request during synchronous reconfiguration;

[0672] -RRC connection recovery procedure from RRC_INACTIVE;

[0673] - Establish time alignment for the secondary Timing Advance Group;

[0674] - Request additional SI;

[0675] -Beam failure recovery;

[0676] -Consistent uplink LBT (Listen Before Talk) failure on SpCell (Special Cell);

[0677] - SDT in RRC_INACTIVE;

[0678] - Positioning purposes during RRC_CONNECTED where a random access procedure is required;

[0679] As an embodiment, the first event set includes: initial access from RRC_IDLE.

[0680] As an embodiment, the first event set includes: RRC connection re-establishment process.

[0681] As an embodiment, the first event set includes: when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, downlink or uplink data arrives.

[0682] As an embodiment, the first event set includes: uplink data arrives when there is no PUCCH resource available for SR and an SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress.

[0683] As an embodiment, the first event set includes: scheduling request failure.

[0684] As an embodiment, the first event set includes: establishing time alignment for the secondary timing advance group.

[0685] As an embodiment, the first event set includes: requesting other SIs.

[0686] As an embodiment, the first event set includes: consistent uplink LBT failure on SpCell.

[0687] As an embodiment, the first event set includes: SDT under RRC_INACTIVE.

[0688] As an embodiment, the first event set includes: positioning purposes during RRC_CONNECTED requiring a random access process.

[0689] As an embodiment, the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection re-establishment process, (3) downlink or uplink data arrival when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrival when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) establishing time alignment for the secondary timing advance group, (7) requesting other SI, (8) consistent uplink LBT failure on SpCell, (9) SDT under RRC_INACTIVE, (10) at least one of the positioning purposes during RRC_CONNECTED that requires a random access process.

[0690] As an embodiment, the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection re-establishment process, (3) downlink or uplink data arrival when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrival when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) establishing time alignment for the secondary timing advance group, (7) requesting other SI, (8) consistent uplink LBT failure on SpCell, (9) SDT under RRC_INACTIVE, (10) positioning purpose during RRC_CONNECTED requiring a random access process.

[0691] As an embodiment, the first event set includes at least: (1) initial access from RRC_IDLE, (2) RRC connection re-establishment process, (3) downlink or uplink data arrival when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrival when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) establishing time alignment for the secondary timing advance group, (7) requesting other SI, (8) consistent uplink LBT failure on SpCell, (9) SDT under RRC_INACTIVE, (10) positioning purpose during RRC_CONNECTED requiring a random access process.

[0692] As an embodiment, the second event set includes: when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, downlink or uplink data arrives.

[0693] In the above implementation, in order for downlink or uplink data to arrive, random access is allowed on symbols configured as DL by higher layer parameters, thereby reducing the delay in transmitting downlink or uplink data.

[0694] As an embodiment, the second event set includes: uplink data arrives when there is no PUCCH resource available for SR and an SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress.

[0695] In the above implementation, in order to ensure the arrival of uplink data, random access is allowed on symbols configured as DL by higher layer parameters, thereby reducing the delay in transmitting uplink data and enhancing uplink performance.

[0696] As an embodiment, the second event set includes: RRC request during synchronous reconfiguration.

[0697] In the above implementation, in order to meet the request of RRC during synchronization reconfiguration, random access is allowed on symbols configured as DL by higher layer parameters, so that RRC synchronization reconfiguration is completed more quickly.

[0698] As an embodiment, the second event set includes: RRC connection recovery process from RRC_INACTIVE.

[0699] In the above embodiment, for the RRC connection recovery process from RRC_INACTIVE, random access is allowed on symbols configured as DL by higher layer parameters, so that the RRC connection can be recovered faster.

[0700] As an embodiment, the second event set includes: establishing time alignment for the secondary timing advance group.

[0701] In the above implementation, in order to establish time alignment for the secondary timing advance group, random access is allowed on symbols configured as DL by higher layer parameters, so that time alignment is established faster and delay is reduced.

[0702] As an embodiment, the second event set includes: beam failure recovery.

[0703] In the above implementation, in order to recover from beam failure, random access is allowed on symbols configured as DL by higher-layer parameters, which achieves beam recovery more quickly and improves communication reliability.

[0704] As an embodiment, the second event set includes: consistent uplink LBT failure on SpCell.

[0705] In the above implementation, in order to ensure consistent uplink LBT failure on the SpCell, random access is allowed on symbols configured as DL by higher layer parameters, so that uplink LBT can be restored in a more timely manner.

[0706] As an embodiment, the second event set includes: SDT under RRC_INACTIVE.

[0707] In the above implementation, for SDT in RRC_INACTIVE, random access is allowed on symbols configured as DL by higher layer parameters, thereby improving the performance of SDT.

[0708] As an embodiment, the second event set includes: positioning purposes during RRC_CONNECTED requiring a random access process.

[0709] In the above implementation, for positioning purposes, random access is allowed on symbols configured as DL by higher layer parameters, so as to obtain positioning information more timely and improve communication quality.

[0710] As an embodiment, the second event set includes: (1) downlink or uplink data arrives when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (2) uplink data arrives when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (3) RRC request during synchronization reconfiguration, (4) RRC connection recovery process from RRC_INACTIVE, (5) establishing time alignment for the secondary timing advance group, (6) beam failure recovery, (7) consistent uplink LBT failure on SpCell, (8) SDT under RRC_INACTIVE, (9) at least one of the positioning purposes during RRC_CONNECTED that requires a random access process.

[0711] As an embodiment, the second event set includes: (1) downlink or uplink data arrives when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (2) uplink data arrives when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (3) RRC request during synchronization reconfiguration, (4) RRC connection recovery process from RRC_INACTIVE, (5) establishing time alignment for the secondary timing advance group, (6) beam failure recovery, (7) consistent uplink LBT failure on SpCell, (8) SDT under RRC_INACTIVE, (9) positioning purposes during RRC_CONNECTED that requires a random access process.

[0712] As an embodiment, the second event set includes at least: (1) downlink or uplink data arrives when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (2) uplink data arrives when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (3) RRC request during synchronization reconfiguration, (4) RRC connection recovery process from RRC_INACTIVE, (5) establishing time alignment for the secondary timing advance group, (6) beam failure recovery, (7) consistent uplink LBT failure on SpCell, (8) SDT under RRC_INACTIVE, (9) positioning purpose during RRC_CONNECTED requiring a random access process.

[0713] As an embodiment, the second event set includes: (1) when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, downlink or uplink data arrives, (2) when there is no PUCCH resource available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, uplink data arrives, (3) RRC request during synchronization reconfiguration, (4) RRC connection recovery process from RRC_INACTIVE, (5) establishing time alignment for the auxiliary timing advance group, (6) beam failure recovery, (7) consistent uplink LBT failure on SpCell, (8) SDT under RRC_INACTIVE, (9) positioning purpose during RRC_CONNECTED requiring a random access process; the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection reestablishment process, (3) scheduling request failure, (4) request for other SI.

[0714] As an embodiment, the second event set includes: (1) RRC request during synchronization reconfiguration, (2) RRC connection recovery process from RRC_INACTIVE, (3) establishing time alignment for the auxiliary timing advance group, (4) beam failure recovery, (5) consistent uplink LBT failure on SpCell, (6) SDT under RRC_INACTIVE, (7) positioning purpose during RRC_CONNECTED requiring a random access process; the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection reestablishment process, (3) downlink or uplink data arrives when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrives when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) request for other SI.

[0715] As an embodiment, the second event set includes: (1) RRC request during synchronization reconfiguration, (2) RRC connection recovery process from RRC_INACTIVE, (3) beam failure recovery, (4) consistent uplink LBT failure on SpCell, (5) SDT under RRC_INACTIVE, (6) positioning purpose during RRC_CONNECTED requiring a random access process; the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection reestablishment process, (3) downlink or uplink data arrives when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrives when there are no PUCCH resources available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) request for other SI, and (7) establishing time alignment for the auxiliary timing advance group.

[0716] As an embodiment, the second event set includes: (1) RRC request during synchronization reconfiguration, (2) RRC connection recovery process from RRC_INACTIVE, (3) beam failure recovery, (4) SDT under RRC_INACTIVE, (5) positioning purpose during RRC_CONNECTED requiring a random access process; the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection reestablishment process, (3) downlink or uplink data arrival when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrival when there is no PUCCH resource available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) request for other SI, (7) establishment of time alignment for the auxiliary timing advance group, (8) failure of consistent uplink LBT on SpCell.

[0717] As an embodiment, the second event set includes: (1) RRC request during synchronization reconfiguration, (2) RRC connection recovery process from RRC_INACTIVE, (3) beam failure recovery, (4) positioning purpose during RRC_CONNECTED requiring a random access process; the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection reestablishment process, (3) downlink or uplink data arrival when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrival when there is no PUCCH resource available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) request for other SI, (7) establishment of time alignment for the auxiliary timing advance group, (8) consistent uplink LBT failure on SpCell, (9) SDT under RRC_INACTIVE.

[0718] As an embodiment, the second event set includes: (1) RRC request during synchronization reconfiguration, (2) RRC connection recovery process from RRC_INACTIVE, and (3) beam failure recovery; the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection reestablishment process, (3) downlink or uplink data arrival when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (4) uplink data arrival when there is no PUCCH resource available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, (5) scheduling request failure, (6) request for other SI, (7) establishing time alignment for the auxiliary timing advance group, (8) consistent uplink LBT failure on SpCell, (9) SDT under RRC_INACTIVE, and (10) positioning purpose during RRC_CONNECTED requiring a random access process.

[0719] As an embodiment, the second event set includes: (1) RRC request during synchronization reconfiguration, (2) beam failure recovery; the first event set includes: (1) initial access from RRC_IDLE, (2) RRC connection reestablishment process, (3) when the uplink synchronization state is "out of synchronization" and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, downlink or uplink data arrives, (4) when there is no PUCCH resource available for SR and the SDT process under RRC_CONNECTED or RRC_INACTIVE is in progress, uplink data arrives, (5) scheduling request failure, (6) request for other SI, (7) establishing time alignment for the auxiliary timing advance group, (8) consistent uplink LBT failure on SpCell, (9) SDT under RRC_INACTIVE, (10) positioning purpose during RRC_CONNECTED requiring a random access process, (11) RRC connection recovery process from RRC_INACTIVE.

[0720] Example 9

[0721] Embodiment 9 illustrates a schematic diagram of the characteristics applicable to the first type of random access procedure and the characteristics applicable to the second type of random access procedure according to an embodiment of the present application; Fig. 9 shown.

[0722] In Embodiment 9, any characteristic applicable to the first type of random access procedure is not a characteristic applicable to the second type of random access procedure,

[0723] As an embodiment, the reference characteristic set includes multiple characteristics, the first type of random access process applies to some characteristics in the reference characteristic set, the second type of random access process applies to some characteristics in the reference characteristic set, and any characteristic applicable to the first type of random access process is not a characteristic applicable to the second type of random access process.

[0724] As an embodiment, the reference characteristic set includes multiple characteristics, the first type of random access process is applicable to a part of the characteristics in the reference characteristic set, and the second type of random access process is applicable to characteristics other than the part of the characteristics in the reference characteristic set that are applicable to the first type of random access process.

[0725] As an embodiment, the reference characteristic set includes multiple characteristics, the first type of random access process is applicable to a part of the characteristics in the reference characteristic set, and the second type of random access process is applicable to all characteristics in the reference characteristic set other than the part of the characteristics applicable to the first type of random access process.

[0726] As an embodiment, the reference feature set includes network slicing, RedCap (Reduced Capability), SDT (Small Data Transmission), and NR (New Radio) coverage enhancement.

[0727] As an embodiment, the reference feature set includes multiple features in network slicing (Network Slicing), RedCap (Reduced Capability), SDT (Small Data Transmission), or NR (New Radio) coverage enhancement.

[0728] As an embodiment, the reference feature set includes network slicing, RedCap (Reduced Capability), SDT (Small Data Transmission), and MSG3 repetition.

[0729] As an embodiment, the reference feature set includes network slicing (Network Slicing), RedCap (Reduced Capability), SDT (Small Data Transmission), or multiple features in MSG3 repetition.

[0730] As an embodiment, the characteristics applicable to the first type of random access process include network slicing.

[0731] As an embodiment, the characteristics applicable to the first type of random access process include RedCap.

[0732] In the above implementation, for the RedCap feature, random access is not allowed on symbols configured as DL by higher layer parameters, which reduces UE capabilities.

[0733] As an embodiment, the applicable characteristics of the first type of random access process include SDT.

[0734] As an embodiment, the characteristics applicable to the first type of random access process include at least one of network slicing, RedCap, and SDT.

[0735] As an embodiment, the characteristics applicable to the first type of random access process include network slicing, RedCap, and SDT.

[0736] As an embodiment, the characteristics applicable to the first type of random access process include at least RedCap.

[0737] As an embodiment, the characteristics applicable to the second type of random access process include network slicing.

[0738] As an embodiment, the applicable characteristics of the second type of random access process include SDT.

[0739] In the above implementation, for the SDT feature, random access is allowed on symbols configured as DL by higher layer parameters, which reduces the delay of SDT and improves the performance of SDT.

[0740] As an embodiment, the characteristics applicable to the second type of random access procedure include NR coverage enhancement.

[0741] In the above implementation, for the NR coverage enhancement feature, random access is allowed on symbols configured as DL by higher-layer parameters, thereby improving coverage.

[0742] As an embodiment, the applicable characteristics of the second type of random access procedure include MSG3 repetition.

[0743] In the above implementation, the repetition characteristic of MSG3 allows random access on symbols configured as DL by higher layer parameters, thereby improving the transmission reliability of MSG3 and enhancing the coverage.

[0744] As an embodiment, the characteristics applicable to the second type of random access process include at least one of network slicing, SDT, and NR coverage enhancement.

[0745] As an embodiment, the characteristics applicable to the second type of random access process include network slicing, SDT, and NR coverage enhancement.

[0746] As an embodiment, the characteristics applicable to the second type of random access process include at least NR coverage enhancement.

[0747] As an embodiment, the characteristics applicable to the second type of random access process include at least one of network slicing, SDT, and MSG3 repetition.

[0748] As an embodiment, the characteristics applicable to the second type of random access process include network slicing, SDT, and MSG3 repetition.

[0749] As an embodiment, the applicable characteristics of the second type of random access process include at least MSG3 repetition.

[0750] As an embodiment, the characteristics applicable to the second type of random access process include: network slicing, SDT, and NR coverage enhancement; the characteristics applicable to the first type of random access process include: RedCap.

[0751] As an embodiment, the characteristics applicable to the second type of random access process include: SDT, NR coverage enhancement; the characteristics applicable to the first type of random access process include: network slicing, RedCap.

[0752] As an embodiment, the characteristics applicable to the second type of random access process include: NR coverage enhancement; the characteristics applicable to the first type of random access process include: network slicing, RedCap, and SDT.

[0753] As an embodiment, the characteristics applicable to the second type of random access process include: network slicing, SDT, and MSG3 repetition; the characteristics applicable to the first type of random access process include: RedCap.

[0754] As an embodiment, the characteristics applicable to the second type of random access process include: SDT, MSG3 repetition; the characteristics applicable to the first type of random access process include: network slicing, RedCap.

[0755] As an embodiment, the characteristics applicable to the second type of random access process include: MSG3 repetition; the characteristics applicable to the first type of random access process include: network slicing, RedCap, SDT.

[0756] As an embodiment, a characteristic applicable to a random access procedure is associated with at least one PRACH resource in the random access procedure.

[0757] As an embodiment, the applicable characteristics of a random access procedure are associated with at least one valid PRACH resource in the random access procedure.

[0758] As an embodiment, the applicable characteristics of a random access procedure are associated with the valid PRACH resources in the random access procedure.

[0759] As an embodiment, the characteristics applicable to a random access procedure are characteristics associated with valid PRACH resources in the random access procedure.

[0760] As an embodiment, a random access procedure is applicable to a characteristic, and a valid PRACH resource in the random access procedure is associated with the characteristic.

[0761] As an embodiment, only one characteristic is applicable to one random access procedure, and the valid PRACH resources in the one random access procedure are associated with the only one characteristic.

[0762] As an embodiment, a random access process is applicable to multiple characteristics, and the valid PRACH resources in the random access process are associated with the multiple characteristics.

[0763] As an embodiment, a random access process is applicable to multiple characteristics, and the effective PRACH resources in the random access process are associated with at least one characteristic among the multiple characteristics.

[0764] As an embodiment, a random access process is applicable to multiple characteristics, and the valid PRACH resources in the random access process are associated with one of the multiple characteristics.

[0765] As an embodiment, a random access procedure is applicable to multiple characteristics, and the valid PRACH resources in the random access procedure are associated with all the characteristics of the multiple characteristics.

[0766] As an embodiment, the meaning of a characteristic being associated with at least one PRACH resource includes: the characteristic is applicable to a random access process, and the at least one PRACH resource is a PRACH resource of the random access process.

[0767] As an embodiment, the meaning of a characteristic being associated with at least one PRACH resource includes: the characteristic is applicable to a random access process, and the at least one PRACH resource is a PRACH resource configured for the random access process.

[0768] As an embodiment, the meaning of a characteristic being associated with at least one PRACH resource includes: the characteristic is applicable to a random access process, and the at least one PRACH resource is a valid PRACH resource of the random access process.

[0769] As an embodiment, the meaning of a characteristic being associated with at least one PRACH resource includes: the characteristic is applicable to a random access process, and the at least one PRACH resource is a valid PRACH resource configured for the random access process.

[0770] As an embodiment, the meaning of associating a characteristic with at least one PRACH resource includes: the characteristic is applicable to a random access process, the at least one PRACH resource is a valid PRACH resource for the random access process, and the at least one PRACH resource is configured for the characteristic.

[0771] As an embodiment, the meaning of associating a characteristic with at least one PRACH resource includes: the one characteristic is applicable to a random access process, the at least one PRACH resource is a valid PRACH resource for the one random access process, and any one of the at least one PRACH resource is configured for the one characteristic.

[0772] As an embodiment, any valid PRACH resource in a random access procedure is configured with a characteristic applicable to the random access procedure.

[0773] As an embodiment, one characteristic is configured with at least one PRACH resource, and the characteristic associated with the at least one PRACH resource is the one characteristic.

[0774] As an embodiment, at least one PRACH resource is associated with a characteristic, and only when the characteristic is a characteristic applicable to a random access procedure, the at least one PRACH resource is a valid PRACH resource for the random access procedure.

[0775] As an embodiment, at least one PRACH resource is associated with a characteristic, and only when the characteristic is a characteristic applicable to a random access procedure, the at least one PRACH resource is a valid PRACH resource for the random access procedure.

[0776] As an embodiment, at least one PRACH resource is associated with a characteristic, and only when the characteristic is one of multiple characteristics applicable to a random access procedure, the at least one PRACH resource is a valid PRACH resource for the random access procedure.

[0777] As an embodiment, at least one PRACH resource is associated with multiple characteristics, and only when the multiple characteristics are characteristics applicable to a random access procedure, the at least one PRACH resource is a valid PRACH resource for the random access procedure.

[0778] As an embodiment, at least one PRACH resource is associated with multiple characteristics, and only when each of the multiple characteristics is a characteristic applicable to a random access process, the at least one PRACH resource is a valid PRACH resource for the random access process.

[0779] As an embodiment, at least one PRACH resource is associated with multiple characteristics, and only when all the characteristics among the multiple characteristics are characteristics applicable to a random access process, the at least one PRACH resource is a valid PRACH resource for the random access process.

[0780] As an embodiment, the PRACH resource includes at least one of a PRACH opportunity and a random access preamble.

[0781] As an embodiment, the PRACH resources include a PRACH opportunity and a random access preamble.

[0782] Example 10

[0783] Embodiment 10 illustrates a schematic diagram of a subcarrier or resource block being used for uplink transmission according to an embodiment of the present application; Fig.10 shown.

[0784] In Embodiment 10, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one resource block is used for uplink transmission.

[0785] As an embodiment, at least one symbol in the reference time domain resource set is configured as DL by the higher layer parameter.

[0786] As an embodiment, any symbol in the reference time domain resource set is configured as DL by the higher layer parameters.

[0787] As an embodiment, any symbol in the reference time domain resource set is configured as DL or Flexible by the higher layer parameters.

[0788] As an embodiment, each symbol in the reference time domain resource set is configured as DL by the higher layer parameters.

[0789] As an embodiment, each symbol in the reference time domain resource set is configured as DL or Flexible by the higher layer parameters.

[0790] As an embodiment, at least one symbol in the reference time domain resource set is configured as DL by the higher layer parameter, and at least one symbol in the reference time domain resource set is configured as Flexible by the higher layer parameter.

[0791] As an embodiment, the reference time domain resource set is configured for a serving cell.

[0792] As an embodiment, the reference time domain resource set is configured for at least one BWP.

[0793] As an embodiment, the reference time domain resource set is configured for a BWP.

[0794] As an embodiment, the reference time domain resource set is configured for a DL BWP.

[0795] As an embodiment, the reference time domain resource set is configured for a pair of DL BWP and ULBWP.

[0796] As an embodiment, the reference time domain resource set is configured for a service cell; on the service cell, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one RB is used for uplink transmission.

[0797] As an embodiment, the reference time domain resource set is configured to at least one BWP; on the at least one BWP, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0798] As an embodiment, the reference time domain resource set is configured to a BWP; on the one BWP, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one RB is used for uplink transmission.

[0799] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and ULBWP, and on the UL BWP in the pair of DL BWP and UL BWP, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0800] As an embodiment, the reference time domain resource set is configured to a DL BWP; the first UL BWP is the UL BWP in a pair of DL BWP and UL BWP to which the DL BWP belongs; on the first ULBWP, in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameters, at least one subcarrier or at least one RB is used for uplink transmission.

[0801] As an embodiment, the uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameters includes at least one of PUSCH (Physical Uplink Shared Channel), PUCCH (Physical Uplink Control Channel), PRACH (Physical Random-Access Channel) or SRS (Sounding Reference Signal).

[0802] As an embodiment, the uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter includes PUSCH.

[0803] As an embodiment, the uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter includes PUCCH.

[0804] As an embodiment, the uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter includes PRACH.

[0805] As an embodiment, the uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter includes SRS.

[0806] Embodiment 11

[0807] Embodiment 11 illustrates a schematic diagram of a second information block and a reference frequency domain resource set according to an embodiment of the present application; Fig.11 shown.

[0808] In embodiment 11, the first receiver receives a second information block; wherein the second information block indicates a reference frequency domain resource set; the reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameters; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0809] As an embodiment, the second information block is carried by higher layer signaling.

[0810] As an embodiment, the second information block is carried by RRC signaling.

[0811] As an embodiment, the second information block includes all or part of the fields in an RRC IE.

[0812] As an embodiment, the second information block includes a partial field in an RRC IE.

[0813] As an embodiment, the second information block includes all or part of the fields in each RRC IE in multiple RRC IEs.

[0814] As an embodiment, the second information block includes all or part of the fields in the ServingCellConfig IE.

[0815] As an embodiment, the second information block includes all or part of the fields in the ServingCellConfigCommonSIB IE.

[0816] As an embodiment, the second information block includes all or part of the fields in the ServingCellConfigCommon IE.

[0817] As an embodiment, the second information block includes all or part of the fields in the DownlinkConfigCommon IE.

[0818] As an embodiment, the second information block includes all or part of the fields in the DownlinkConfigCommonSIB IE.

[0819] As an embodiment, the second information block includes all or part of the fields in the UplinkConfigCommon IE.

[0820] As an embodiment, the second information block includes all or part of the fields in the UplinkConfigCommonSIB IE.

[0821] As an embodiment, the second information block includes all or part of the fields in the RRC IE whose name includes "BWP-Uplink".

[0822] As an embodiment, the second information block includes all or part of the fields in the BWP-UplinkCommon IE.

[0823] As an embodiment, the second information block includes all or part of the fields in the BWP-UplinkDedicated IE.

[0824] As an embodiment, the second information block includes all or part of the fields in the RRC IE whose name includes "BWP-Downlink".

[0825] As an embodiment, the second information block includes all or part of the fields in the BWP-DownlinkCommon IE.

[0826] As an embodiment, the second information block includes all or part of the fields in the BWP-DownlinkDedicated IE.

[0827] As an embodiment, the second information block is carried by at least one RRC IE.

[0828] As an embodiment, the second information block is carried by ServingCellConfig IE.

[0829] As an embodiment, the second information block is carried by ServingCellConfigCommonSIB IE.

[0830] As an embodiment, the second information block is carried by ServingCellConfigCommon IE.

[0831] As an embodiment, the second information block is carried by DownlinkConfigCommon IE.

[0832] As an embodiment, the second information block is carried by DownlinkConfigCommonSIB IE.

[0833] As an embodiment, the second information block is carried by UplinkConfigCommon IE.

[0834] As an embodiment, the second information block is carried by UplinkConfigCommonSIB IE.

[0835] As an embodiment, the second information block is carried by BWP-UplinkCommon IE.

[0836] As an embodiment, the second information block is carried by BWP-UplinkDedicated IE.

[0837] As an embodiment, the second information block is carried by BWP-DownlinkCommon IE.

[0838] As an embodiment, the second information block is carried by BWP-DownlinkDedicated IE.

[0839] As an embodiment, the name of an IE carrying the second information block includes "ServingCellConfig".

[0840] As an embodiment, a name of an IE carrying the second information block includes "DownlinkConfig".

[0841] As an embodiment, a name of an IE carrying the second information block includes "UplinkConfig".

[0842] As an embodiment, a name of an IE carrying the second information block includes "BWP-Downlink".

[0843] As an embodiment, a name of an IE carrying the second information block includes "BWP-Uplink.

[0844] As an embodiment, a name of an IE carrying the second information block includes "BWP".

[0845] As an embodiment, the second information block is carried by MAC CE signaling.

[0846] As an embodiment, the second information block is carried by physical layer signaling.

[0847] As an embodiment, the second information block is carried by DCI signaling.

[0848] As an embodiment, the second information block is carried jointly by RRC signaling and MAC CE.

[0849] As an embodiment, the second information block is carried jointly by higher layer signaling and DCI.

[0850] As an embodiment, the second information block and the first information block are carried by the same RRC IE.

[0851] As an embodiment, the second information block and the first information block are respectively carried by two RRC IEs.

[0852] As an embodiment, for the specific definitions of DownlinkConfigCommon IE, DownlinkConfigCommonSIB IE, UplinkConfigCommon IE, UplinkConfigCommonSIB IE, BWP-UplinkCommon IE, BWP-UplinkDedicated IE, BWP-DownlinkCommon IE, and BWP-DownlinkDedicated IE, please refer to Section 6.3.2 of 3GPP TS 38.331.

[0853] As an embodiment, the second information block explicitly indicates the reference frequency domain resource set.

[0854] As an embodiment, the second information block implicitly indicates the reference frequency domain resource set.

[0855] As an embodiment, the second information block indicates the subcarriers included in the reference frequency domain resource set.

[0856] As an embodiment, the second information block indicates each subcarrier included in the reference frequency domain resource set.

[0857] As an embodiment, the second information block indicates the index of the subcarriers included in the reference frequency domain resource set.

[0858] As an embodiment, the second information block indicates the index of each subcarrier included in the reference frequency domain resource set.

[0859] As an embodiment, the second information block indicates the index of the starting subcarrier of the reference frequency domain resource set.

[0860] As an embodiment, the second information block indicates the number of subcarriers included in the reference frequency domain resource set.

[0861] As an embodiment, the second information block indicates the number of consecutive subcarriers included in the reference frequency domain resource set.

[0862] As an embodiment, the second information block indicates the index of the starting subcarrier of the reference frequency domain resource set and the number of consecutive subcarriers included.

[0863] As an embodiment, the second information block indicates the RBs included in the reference frequency domain resource set.

[0864] As an embodiment, the second information block indicates each RB included in the reference frequency domain resource set.

[0865] As an embodiment, the second information block indicates the index of the RB included in the reference frequency domain resource set.

[0866] As an embodiment, the second information block indicates the index of each RB included in the reference frequency domain resource set.

[0867] As an embodiment, the second information block indicates the index of the starting RB of the reference frequency domain resource set.

[0868] As an embodiment, the second information block indicates the number of RBs included in the reference frequency domain resource set.

[0869] As an embodiment, the second information block indicates the number of consecutive RBs included in the reference frequency domain resource set.

[0870] As an embodiment, the second information block indicates the index of the starting RB of the reference frequency domain resource set and the number of consecutive RBs included.

[0871] As an embodiment, the second information block indicates the position of the RBs included in the reference frequency domain resource set relative to a CRB (Common Resource Block).

[0872] As an embodiment, the second information block indicates the position of each RB included in the reference frequency domain resource set relative to a CRB.

[0873] As an embodiment, the second information block indicates the position of the starting RB of the reference frequency domain resource set relative to a CRB.

[0874] As an embodiment, the second information block indicates the offset of the RBs included in the reference frequency domain resource set relative to a CRB.

[0875] As an embodiment, the second information block indicates the offset of each RB included in the reference frequency domain resource set relative to a CRB.

[0876] As an embodiment, the second information block indicates the offset of the starting RB of the reference frequency domain resource set relative to a CRB.

[0877] As an embodiment, the second information block indicates the position of the RBs included in the reference frequency domain resource set relative to CRB 0.

[0878] As an embodiment, the second information block indicates the position of each RB included in the reference frequency domain resource set relative to CRB 0.

[0879] As an embodiment, the second information block indicates the position of the starting RB of the reference frequency domain resource set relative to CRB 0.

[0880] As an embodiment, the second information block indicates the offset of the RBs included in the reference frequency domain resource set relative to CRB 0.

[0881] As an embodiment, the second information block indicates the offset of each RB included in the reference frequency domain resource set relative to CRB 0.

[0882] As an embodiment, the second information block indicates the offset of the starting RB of the reference frequency domain resource set relative to CRB 0.

[0883] As an embodiment, for the specific definition of CRB, CRB 0, refer to Chapter 4 of 3GPP TS 38.211.

[0884] As an embodiment, the second information block indicates a reference frequency domain resource pool, and the reference frequency domain resource set belongs to the reference frequency domain resource pool.

[0885] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes at least one RB in the reference frequency domain resource pool that overlaps with at least one BWP.

[0886] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes all RBs in the reference frequency domain resource pool that overlap with at least one BWP.

[0887] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes at least one RB in the reference frequency domain resource pool that overlaps with a BWP.

[0888] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes all RBs in the reference frequency domain resource pool that overlap with one BWP.

[0889] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes at least one RB in the reference frequency domain resource pool that overlaps with a DL BWP.

[0890] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes all RBs in the reference frequency domain resource pool that overlap with a DL BWP.

[0891] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes at least one RB in the reference frequency domain resource pool that overlaps with a UL BWP in a pair of DL BWP and UL BWP.

[0892] As an embodiment, the second information block indicates the reference frequency domain resource pool, and the reference frequency domain resource set includes all RBs in the reference frequency domain resource pool that overlap with the UL BWP in a pair of DL BWP and UL BWP.

[0893] As an embodiment, the reference frequency domain resource pool includes one or more RBs.

[0894] As an embodiment, the reference frequency domain resource pool includes multiple consecutive RBs.

[0895] As an embodiment, the second information block indicates each RB of the reference frequency domain resource pool.

[0896] As an embodiment, the second information block indicates the starting RB of the reference frequency domain resource pool.

[0897] As an embodiment, the second information block indicates the number of consecutive RBs included in the reference frequency domain resource pool.

[0898] As an embodiment, the second information block indicates the starting RB of the reference frequency domain resource pool and the number of consecutive RBs included.

[0899] As an embodiment, the reference time domain resource set is configured for a service cell, and the reference frequency domain resource set is configured for the one service cell; on the one service cell, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the reference frequency domain resource set in the frequency domain.

[0900] As an embodiment, the reference time domain resource set is configured for a service cell, and the reference frequency domain resource set is configured for the service cell; on a BWP of the service cell, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the frequency domain resources that overlap with the reference frequency domain resource set and the BWP of the service cell in the frequency domain.

[0901] As an embodiment, the reference time domain resource set is configured for a service cell, and the reference frequency domain resource set is configured for the service cell; on a UL BWP of the service cell, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the frequency domain resources that overlap with the reference frequency domain resource set and the UL BWP of the service cell in the frequency domain.

[0902] As an embodiment, the reference time domain resource set is configured for a service cell, and the reference frequency domain resource set is configured for the one service cell; the first PRACH timing set and the second PRACH timing set both belong to the one service cell; on the one service cell, the PRACH timings in the second PRACH timing set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0903] As an embodiment, the reference time domain resource set is configured for a service cell, and the reference frequency domain resource set is configured for the one service cell; the first PRACH opportunity set and the second PRACH opportunity set both belong to the same BWP in the one service cell; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the frequency domain resources that overlap with the reference frequency domain resource set and the same BWP in the frequency domain.

[0904] As an embodiment, the reference time domain resource set is configured for a service cell, and the reference frequency domain resource set is configured for the one service cell; the first PRACH opportunity set and the second PRACH opportunity set both belong to the same UL BWP in the one service cell; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the frequency domain resources that overlap with the reference frequency domain resource set and the same ULBWP in the frequency domain.

[0905] As an embodiment, "the reference time domain resource set is configured to a serving cell" includes: information indicating that the reference time domain resource set belongs to configuration information of the serving cell.

[0906] As an embodiment, "the reference time domain resource set is configured for one serving cell" includes: the reference time domain resource set is applied to all BWPs of the one serving cell.

[0907] As an embodiment, "the reference time domain resource set is configured for a serving cell" includes: information indicating that the reference time domain resource set belongs to an IEServingCellConfig used to configure the serving cell.

[0908] As an embodiment, "the reference time domain resource set is configured for a serving cell" includes: information indicating that the reference time domain resource set belongs to an IEServingCellConfigCommon used to configure the serving cell.

[0909] As an embodiment, "the reference time domain resource set is configured for a serving cell" includes: information indicating that the reference time domain resource set belongs to at least one of IEServingCellConfig or IE ServingCellConfigCommon used to configure the serving cell.

[0910] As an embodiment, "the reference frequency domain resource set is configured for the one serving cell" includes: information indicating that the reference frequency domain resource set belongs to configuration information of the one serving cell.

[0911] As an embodiment, "the reference frequency domain resource set is configured for the one serving cell" includes: the reference frequency domain resource set is applied to all BWPs of the one serving cell.

[0912] As an embodiment, "the reference frequency domain resource set is configured for the one serving cell" includes: the reference frequency domain resource set and the BWP of the one serving cell are configured separately.

[0913] As an embodiment, "the reference frequency domain resource set is configured for the one serving cell" includes: information indicating that the reference frequency domain resource set belongs to an IEServingCellConfig used to configure the one serving cell.

[0914] As an embodiment, "the reference frequency domain resource set is configured for the one serving cell" includes: information indicating that the reference frequency domain resource set belongs to an IEServingCellConfigCommon used to configure the one serving cell.

[0915] As an embodiment, "the reference frequency domain resource set is configured to the one serving cell" includes: information indicating that the reference frequency domain resource set belongs to at least one of IEServingCellConfig or IE ServingCellConfigCommon used to configure the one serving cell.

[0916] As an embodiment, "the reference time domain resource set is configured for a service cell" includes: information indicating that the reference time domain resource set belongs to the configuration information of the service cell; "the reference frequency domain resource set is configured for the service cell" includes: information indicating that the reference frequency domain resource set belongs to the configuration information of the service cell.

[0917] As an embodiment, "the reference time domain resource set is configured for a service cell" includes: the reference time domain resource set is applied to all BWPs of the service cell; "the reference frequency domain resource set is configured for the service cell" includes: the reference frequency domain resource set is applied to all BWPs of the service cell.

[0918] As an embodiment, "the reference time domain resource set is configured for a serving cell" includes: information indicating that the reference time domain resource set belongs to an IEServingCellConfig used to configure the one serving cell; "the reference frequency domain resource set is configured for the one serving cell" includes: information indicating that the reference frequency domain resource set belongs to an IEServingCellConfig used to configure the one serving cell.

[0919] As an embodiment, "the reference time domain resource set is configured for a serving cell" includes: information indicating that the reference time domain resource set belongs to an IEServingCellConfigCommon used to configure the one serving cell; "the reference frequency domain resource set is configured for the one serving cell" includes: information indicating that the reference frequency domain resource set belongs to an IEServingCellConfigCommon used to configure the one serving cell.

[0920] As an embodiment, the reference time domain resource set is configured to at least one BWP, and the reference frequency domain resource set is configured to the at least one BWP; on any BWP of the at least one BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the reference frequency domain resource set in the frequency domain.

[0921] As an embodiment, the reference time domain resource set is configured to at least one BWP, and the reference frequency domain resource set is configured to the at least one BWP; the given BWP is any BWP among the at least one BWP, and on the given BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameters belongs to the frequency domain resources overlapping the reference frequency domain resource set and the given BWP in the frequency domain.

[0922] As an embodiment, the reference time domain resource set is configured to at least one BWP, and the reference frequency domain resource set is configured to the at least one BWP; on a UL BWP in the at least one BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameters belongs to the reference frequency domain resource set in the frequency domain.

[0923] As an embodiment, the reference time domain resource set is configured to at least one BWP, and the reference frequency domain resource set is configured to the at least one BWP; the given BWP is a UL BWP in the at least one BWP, and on the given BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the frequency domain resources that overlap the reference frequency domain resource set and the given BWP in the frequency domain.

[0924] As an embodiment, the reference time domain resource set is configured to at least one BWP, and the reference frequency domain resource set is configured to the at least one BWP; the first PRACH opportunity set and the second PRACH opportunity set both belong to the at least one BWP; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0925] As an embodiment, the reference time domain resource set is configured to at least one BWP, and the reference frequency domain resource set is configured to the at least one BWP; the first PRACH opportunity set and the second PRACH opportunity set both belong to the same BWP in the at least one BWP; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the frequency domain resources that overlap with the reference frequency domain resource set and the same BWP in the frequency domain.

[0926] As an embodiment, "the reference time domain resource set is configured to at least one BWP" includes: information indicating that the reference time domain resource set belongs to configuration information of the at least one BWP.

[0927] As an embodiment, "the reference time domain resource set is configured to at least one BWP" includes: the reference time domain resource set is applied to the at least one BWP.

[0928] As an embodiment, "the reference frequency domain resource set is configured to the at least one BWP" includes: information indicating that the reference frequency domain resource set belongs to configuration information of the at least one BWP.

[0929] As an embodiment, "the reference frequency domain resource set is configured to the at least one BWP" includes: the reference frequency domain resource set is applied to the at least one BWP.

[0930] As an embodiment, "the reference frequency domain resource set is configured for the at least one BWP" includes: the reference frequency domain resource set belongs to the at least one BWP.

[0931] As an embodiment, "the reference frequency domain resource set is configured for the at least one BWP" includes: the reference frequency domain resource set includes part or all of the frequency domain resources in each BWP in the at least one BWP.

[0932] As an embodiment, "the reference time domain resource set is configured to at least one BWP" includes: information indicating that the reference time domain resource set belongs to the configuration information of the at least one BWP; "the reference frequency domain resource set is configured to the at least one BWP" includes: information indicating that the reference frequency domain resource set belongs to the configuration information of the at least one BWP.

[0933] As an embodiment, "the reference time domain resource set is configured to at least one BWP" includes: the reference time domain resource set is applied to the at least one BWP; "the reference frequency domain resource set is configured to the at least one BWP" includes: the reference frequency domain resource set is applied to the at least one BWP.

[0934] As an embodiment, the reference time domain resource set is configured to a BWP, and the reference frequency domain resource set is configured to the one BWP; on the one BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the reference frequency domain resource set in the frequency domain.

[0935] As an embodiment, the reference time domain resource set is configured to a BWP, and the reference frequency domain resource set is configured to the one BWP; on the one BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the frequency domain resources that overlap the reference frequency domain resource set and the one BWP in the frequency domain.

[0936] As an embodiment, the reference time domain resource set is configured to a BWP, and the reference frequency domain resource set is configured to the one BWP; the first PRACH opportunity set and the second PRACH opportunity set both belong to the one BWP; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0937] As an embodiment, the reference time domain resource set is configured to a BWP, and the reference frequency domain resource set is configured to the one BWP; the first PRACH opportunity set and the second PRACH opportunity set both belong to the one BWP; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the frequency domain resources that overlap with the reference frequency domain resource set and the one BWP in the frequency domain.

[0938] As an embodiment, "the reference time domain resource set is configured to a BWP" includes: information indicating that the reference time domain resource set belongs to configuration information of the BWP.

[0939] As an embodiment, "the reference time domain resource set is configured to one BWP" includes: the reference time domain resource set is applied to the one BWP.

[0940] As an embodiment, "the reference frequency domain resource set is configured to the one BWP" includes: information indicating that the reference frequency domain resource set belongs to configuration information of the one BWP.

[0941] As an embodiment, "the reference frequency domain resource set is configured to the one BWP" includes: the reference frequency domain resource set is applied to the one BWP.

[0942] As an embodiment, "the reference frequency domain resource set is configured for the one BWP" includes: the reference frequency domain resource set belongs to the one BWP.

[0943] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and ULBWP, and the reference frequency domain resource set is configured to the pair of DL BWP and UL BWP; on the UL BWP in the pair of DL BWP and ULBWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the reference frequency domain resource set in the frequency domain.

[0944] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and ULBWP, and the reference frequency domain resource set is configured to the pair of DL BWP and UL BWP; the given UL BWP is the UL BWP in the pair of DLBWP and UL BWP, and on the given UL BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the frequency domain resources overlapping the reference frequency domain resource set and the given UL BWP in the frequency domain.

[0945] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and ULBWP, and the reference frequency domain resource set is configured to the pair of DL BWP and UL BWP; the first PRACH opportunity set and the second PRACH opportunity set both belong to the UL BWP in the pair of DL BWP and UL BWP; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0946] As an embodiment, the reference time domain resource set is configured to a pair of DL BWP and ULBWP, and the reference frequency domain resource set is configured to the pair of DL BWP and UL BWP; the given UL BWP is the UL BWP in the pair of DLBWP and UL BWP, and the first PRACH timing set and the second PRACH timing set both belong to the given UL BWP; the PRACH timings in the second PRACH timing set that belong to the reference time domain resource set in the time domain belong to the frequency domain resources that overlap with the reference frequency domain resource set and the given UL BWP in the frequency domain.

[0947] As an embodiment, "the reference time domain resource set is configured to a pair of DL BWP and ULBWP" includes: information indicating that the reference time domain resource set belongs to the configuration information of the DL BWP in the pair of DL BWP and UL BWP, or the configuration information of the UL BWP in the pair of DL BWP and UL BWP.

[0948] As an embodiment, “the reference time domain resource set is configured to a pair of DL BWP and UL BWP” includes: the reference time domain resource set is applied to the pair of DL BWP and UL BWP.

[0949] As an embodiment, "the reference frequency domain resource set is configured to the pair (a pair of) DL BWP and UL BWP" includes: information indicating that the reference frequency domain resource set belongs to the configuration information of the DL BWP in the pair (a pair of) DL BWP and ULBWP, or the configuration information of the UL BWP in the pair (a pair of) DL BWP and UL BWP.

[0950] As an embodiment, “the reference frequency domain resource set is configured to the pair of DL BWP and UL BWP” includes: the reference frequency domain resource set is applied to the pair of DL BWP and UL BWP.

[0951] As an embodiment, “the reference frequency domain resource set is configured to the pair of DL BWP and UL BWP” includes: the reference frequency domain resource set belongs to the DLBWP in the pair of DL BWP and UL BWP.

[0952] As an embodiment, “the reference frequency domain resource set is configured to the pair of DL BWP and UL BWP” includes: the reference frequency domain resource set belongs to the ULBWP in the pair of DL BWP and UL BWP.

[0953] As an embodiment, the reference time domain resource set is configured to a DL BWP, and the reference frequency domain resource set is configured to the one DL BWP; the first UL BWP is the UL BWP in a pair of DL BWP and UL BWP to which the one DL BWP belongs; on the first UL BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the reference frequency domain resource set in the frequency domain.

[0954] As an embodiment, the reference time domain resource set is configured to a DL BWP, and the reference frequency domain resource set is configured to the one DL BWP; the first UL BWP is the UL BWP in a pair of DL BWP and UL BWP to which the one DL BWP belongs; on the first UL BWP, the uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameter belongs to the frequency domain resources overlapping the reference frequency domain resource set and the first UL BWP in the frequency domain.

[0955] As an embodiment, the reference time domain resource set is configured to a DL BWP, the reference frequency domain resource set is configured to the one DL BWP, the first PRACH opportunity set and the second PRACH opportunity set belong to the same UL BWP, the same UL BWP and the one DL BWP are a pair of DL BWP and ULBWP; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0956] As an embodiment, the reference time domain resource set is configured to a DL BWP, the reference frequency domain resource set is configured to the one DL BWP, the first PRACH opportunity set and the second PRACH opportunity set belong to the same UL BWP, the same UL BWP and the one DL BWP are a pair of DL BWP and ULBWP; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the frequency domain resources that overlap with the reference frequency domain resource set and the same UL BWP in the frequency domain.

[0957] As an embodiment, "the reference time domain resource set is configured to a DL BWP" includes: information indicating that the reference time domain resource set belongs to configuration information of the one DL BWP.

[0958] As an embodiment, "the reference time domain resource set is configured to one DL BWP" includes: the reference time domain resource set is applied to the one DL BWP.

[0959] As an embodiment, "the reference frequency domain resource set is configured to the one DL BWP" includes: information indicating that the reference frequency domain resource set belongs to configuration information of the one DL BWP.

[0960] As an embodiment, "the reference frequency domain resource set is configured to the one DL BWP" includes: the reference frequency domain resource set is applied to the one DL BWP.

[0961] As an embodiment, "the reference frequency domain resource set is configured for the one DL BWP" includes: the reference frequency domain resource set belongs to the one DL BWP.

[0962] Example 12

[0963] Embodiment 12 illustrates a structural block diagram of a processing device used in a first node device according to an embodiment of the present application; Fig.12 As shown in the attached Fig.12 In the embodiment, the processing device 1200 in the first node device includes a first receiver 1201 and a first transmitter 1202.

[0964] As an embodiment, the first node device is a user equipment.

[0965] As an embodiment, the first node device is a relay node device.

[0966] As an embodiment, the first receiver 1201 includes at least one of {antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, data source 467} in Embodiment 4.

[0967] As an embodiment, the first transmitter 1202 includes at least one of {antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller / processor 459, memory 460, data source 467} in Embodiment 4.

[0968] The first receiver 1201 receives a first information block, where the first information block indicates a reference time domain resource set, where the reference time domain resource set includes one or more symbols configured as DL by higher layer parameters.

[0969] The first transmitter 1202 sends a first random access preamble in a first PRACH opportunity, the candidate set of the first PRACH opportunity is the first PRACH opportunity set or the second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain.

[0970] In embodiment 12, the sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0971] As an embodiment, one of the first type of random access process and the second type of random access process is contention-based, and the other is contention-free-based.

[0972] As an embodiment, one of the first type of random access process and the second type of random access process is a four-step random access process, and the other is a two-step random access process.

[0973] As an embodiment, the priority of the first type of random access process is lower than the priority of the second type of random access process.

[0974] As an embodiment, the first type of random access process is initiated for a first event set, and the second type of random access process is initiated for a second event set; the first event set includes one or more events, the second event set includes one or more events, and any event in the first event set does not belong to the second event set.

[0975] As an embodiment, any characteristic applicable to the first type of random access procedure is not a characteristic applicable to the second type of random access procedure.

[0976] As an embodiment, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one resource block is used for uplink transmission.

[0977] As an embodiment, it includes:

[0978] The first receiver 1201 receives a second information block;

[0979] Among them, the second information block indicates a reference frequency domain resource set; the reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0980] Example 13

[0981] Embodiment 13 illustrates a structural block diagram of a processing device used in a second node device according to an embodiment of the present application; Fig.13 As shown in the attached Fig.13 In the embodiment, the processing device 1300 in the second node device includes a second transmitter 1301 and a second receiver 1302.

[0982] As an embodiment, the second node device is a base station device.

[0983] As an embodiment, the second node device is a user equipment.

[0984] As an embodiment, the second node device is a relay node device.

[0985] As an embodiment, the second transmitter 1301 includes at least one of {antenna 420, transmitter 418, transmit processor 416, multi-antenna transmit processor 471, controller / processor 475, memory 476} in Embodiment 4.

[0986] As an embodiment, the second receiver 1302 includes at least one of {antenna 420, receiver 418, receiving processor 470, multi-antenna receiving processor 472, controller / processor 475, memory 476} in Embodiment 4.

[0987] The second transmitter 1301 sends a first information block, where the first information block indicates a reference time domain resource set, and the reference time domain resource set includes one or more symbols configured as DL by higher layer parameters.

[0988] The second receiver 1302 receives a first random access preamble in a first PRACH opportunity, the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain.

[0989] In Embodiment 13, the reception of the first random access preamble belongs to one of a first type of random access procedure or a second type of random access procedure; when the reception of the first random access preamble belongs to the first type of random access procedure, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the reception of the first random access preamble belongs to the second type of random access procedure, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

[0990] As an embodiment, one of the first type of random access process and the second type of random access process is contention-based, and the other is contention-free-based.

[0991] As an embodiment, one of the first type of random access process and the second type of random access process is a four-step random access process, and the other is a two-step random access process.

[0992] As an embodiment, the priority of the first type of random access process is lower than the priority of the second type of random access process.

[0993] As an embodiment, the first type of random access process is initiated for a first event set, and the second type of random access process is initiated for a second event set; the first event set includes one or more events, the second event set includes one or more events, and any event in the first event set does not belong to the second event set.

[0994] As an embodiment, any characteristic applicable to the first type of random access procedure is not a characteristic applicable to the second type of random access procedure.

[0995] As an embodiment, in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one resource block is used for uplink transmission.

[0996] As an embodiment, it includes:

[0997] The second transmitter 1301 sends a second information block;

[0998] Among them, the second information block indicates a reference frequency domain resource set; the reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

[0999] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication, Machine Type Communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B), TRP (Transmitter Receiver Point), GNSS, relay satellites, satellite base stations, aerial base stations, RSU (Road Side Unit), drones, test equipment (such as a transceiver or signaling tester that simulates some functions of a base station), and other wireless communication equipment.

[1000] The above is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any changes and modifications made based on the embodiments described in the specification, if similar partial or complete technical effects can be obtained, should be considered obvious and fall within the scope of protection of the present invention.

Claims

1. A first node device used for wireless communication, characterized in that: include: A first receiver receives a first information block, wherein the first information block indicates a reference time domain resource set, wherein the reference time domain resource set includes one or more symbols configured as DL by a higher layer parameter; A first transmitter sends a first random access preamble in a first PRACH opportunity, where the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, where the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and where the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; The sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

2. The first node device according to claim 1, characterized in that: One of the first type of random access process and the second type of random access process is contention-based, and the other is contention-free based; or, one of the first type of random access process and the second type of random access process is a four-step random access process, and the other is a two-step random access process.

3. The first node device according to claim 1 or 2, characterized in that: The priority of the first type of random access procedure is lower than the priority of the second type of random access procedure.

4. The first node device according to any one of claims 1 to 3, characterized in that: The first type of random access process is initiated for a first event set, and the second type of random access process is initiated for a second event set; the first event set includes one or more events, the second event set includes one or more events, and any event in the first event set does not belong to the second event set.

5. The first node device according to any one of claims 1 to 4, characterized in that: Any characteristic applicable to the first type of random access procedure is not a characteristic applicable to the second type of random access procedure.

6. The first node device according to any one of claims 1 to 5, characterized in that: In at least one symbol of the reference time domain resource set configured as DL by the higher layer parameter, at least one subcarrier or at least one resource block is used for uplink transmission.

7. The first node device according to claim 6, characterized in that: include: The first receiver receives a second information block; The second information block indicates a reference frequency domain resource set; The reference frequency domain resource set includes at least one subcarrier or at least one RB used for uplink transmission in at least one symbol of the reference time domain resource set that is configured as DL by the higher layer parameters; the PRACH opportunities in the second PRACH opportunity set that belong to the reference time domain resource set in the time domain belong to the reference frequency domain resource set in the frequency domain.

8. A second node device used for wireless communication, characterized in that: include: A second transmitter sends a first information block, where the first information block indicates a reference time domain resource set, where the reference time domain resource set includes one or more symbols configured as DL by a higher layer parameter; A second receiver receives a first random access preamble in a first PRACH opportunity, where the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, where the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and where the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; The reception of the first random access preamble belongs to one of a first type of random access process or a second type of random access process; when the reception of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the reception of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

9. A method in a first node device used for wireless communication, characterized in that: include: receiving a first information block, the first information block indicating a reference time domain resource set, the reference time domain resource set including one or more symbols configured as DL by a higher layer parameter; Sending a first random access preamble in a first PRACH opportunity, the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; The sending of the first random access preamble belongs to one of the first type of random access process or the second type of random access process; when the sending of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the sending of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

10. A method in a second node device used for wireless communication, characterized in that: include: Sending a first information block, where the first information block indicates a reference time domain resource set, where the reference time domain resource set includes one or more symbols configured as DL by a higher layer parameter; receiving a first random access preamble in a first PRACH opportunity, where the candidate set of the first PRACH opportunity is a first PRACH opportunity set or a second PRACH opportunity set, where the first PRACH opportunity set and the reference time domain resource set are orthogonal in the time domain, and where the second PRACH opportunity set and the reference time domain resource set overlap in the time domain; The reception of the first random access preamble belongs to one of a first type of random access process or a second type of random access process; when the reception of the first random access preamble belongs to the first type of random access process, the candidate set of the first PRACH opportunity is the first PRACH opportunity set; when the reception of the first random access preamble belongs to the second type of random access process, the candidate set of the first PRACH opportunity is the second PRACH opportunity set.

Images