Random access method and apparatus, and communication system

Abstract

The embodiments of the present application provide a random access method and apparatus, and a communication system. The method comprises: within a cell, sending a random access preamble (PRACH) in a first valid RO and / or a second valid RO, wherein the first valid RO is within a flexible time-domain resource and / or an uplink time-domain resource, and the second valid RO is within a downlink time-domain resource that overlaps with a first time-domain resource and / or a flexible time-domain resource that overlaps with the first time-domain resource, or, the first valid RO is located within a flexible time-domain resource and / or an uplink time-domain resource that does not overlap with the first time-domain resource, and the second valid RO is located within the first time-domain resource.

Description

Random access methods, devices and communication systems Technical Field

[0001] This application relates to the field of communication technology. Background Technology

[0002] Random access procedures include contention-based random access procedures and non-contention-based random access procedures. In a contention-based random access procedure, the UE selects preamble and PRACH resources from available preamble and PRACH resources configured by the network side (e.g., the base station) for random access. In a non-contention-based random access procedure, the User Equipment (UE) uses specific preamble and Physical Random Access Channel (PRACH) resources configured by the network side (e.g., the base station) for random access.

[0003] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application.

[0004] Summary of the Invention

[0005] Currently, with the increasing number of new services and equipment types, the requirements for random access coverage, capacity, and latency are becoming increasingly stringent, necessitating further enhancements to random access. For example, in Time Division Duplex (TDD) frequency bands, uplink transmission during random access can only occur within the uplink time slot. When limited or small uplink time slots are allocated, the random access will suffer from small coverage, low capacity, and high latency. Similarly, in Frequency Division Duplex (FDD) frequency bands, uplink transmission during random access can only occur on the uplink carrier. When limited or small uplink carrier bandwidth is allocated, the random access may also suffer from small coverage, low capacity, and high latency.

[0006] To address at least one of the above-mentioned problems, embodiments of this application provide a random access method, apparatus, and communication system.

[0007] According to another aspect of the embodiments of this application, a random access device is provided, applied to a terminal device, comprising: transmitting a random access preamble (PRACH) in a cell at a first valid RO and / or a second valid RO;

[0008] Wherein, the first effective RO is within flexible time domain resources and / or uplink time domain resources, the second effective RO is in downlink time domain resources and / or flexible time domain resources that overlap with the first time domain resources, or the first effective RO is located in flexible time domain resources and / or uplink time domain resources that do not overlap with the first time domain resources, and the second effective RO is located in the first time domain resources.

[0009] According to another aspect of the embodiments of this application, a random access device is provided, applied to a network device, comprising: receiving a random access preamble at a first valid RO and / or a second valid RO; the first valid RO being within flexible time domain resources and / or uplink time domain resources, and the second valid RO being within downlink time domain resources overlapping with the first time domain resources and / or flexible time domain resources overlapping with the first time domain resources.

[0010] According to another aspect of the embodiments of this application, a communication system is provided, including: a terminal device and / or a network device, wherein the terminal device includes the means of the aforementioned aspect, and the network device includes the means of the aforementioned aspect.

[0011] One of the beneficial effects of this application embodiment is that it provides a method for a terminal device to perform random access, which enables the terminal device to send a random access preamble to the network device in flexible time domain resources and / or uplink time domain resources and / or downlink time domain resources overlapping with the first time domain resources, or in flexible time domain resources and / or uplink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or flexible resources overlapping with the first time domain resources. In other words, it supports the use of the resources mentioned above to send uplink transmissions for random access, thereby increasing the coverage and capacity of random access and reducing latency.

[0012] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0013] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with or replacing features in other embodiments.

[0014] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0015] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0016] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without creative effort.

[0017] In the picture:

[0018] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0019] Figure 2 is a schematic diagram of time-domain resource types according to an embodiment of this application;

[0020] Figure 3 is a schematic diagram of time-domain resources according to an embodiment of this application;

[0021] Figures 4A to 4D are schematic diagrams of frequency domain resources according to embodiments of this application;

[0022] Figure 5 is a schematic diagram of a random access method according to an embodiment of this application;

[0023] Figure 6 is a schematic diagram of information configuration according to an embodiment of this application;

[0024] Figures 7A to 7G are schematic diagrams of information configuration according to an embodiment of this application;

[0025] Figures 8A to 8F are schematic diagrams illustrating the determination of valid RO according to embodiments of this application;

[0026] Figure 9 is a schematic diagram of information configuration according to an embodiment of this application;

[0027] Figure 10 is a schematic diagram of SSB-RO mapping according to an embodiment of this application;

[0028] Figure 11 is a schematic diagram of a random access device according to an embodiment of this application;

[0029] Figure 12 is a schematic diagram of a random access method according to an embodiment of this application;

[0030] Figure 13 is a schematic diagram of a random access device according to an embodiment of this application;

[0031] Figure 14 is a schematic diagram of a terminal device according to an embodiment of this application;

[0032] Figure 15 is a schematic diagram of a network device according to an embodiment of this application;

[0033] Figure 16 is a schematic diagram of the random access process according to an embodiment of this application. Detailed Implementation

[0034] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

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

[0036] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0037] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0038] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), 6G, etc., and / or other currently known or future communication protocols.

[0039] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transceiver node (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0040] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" can include some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0041] In the embodiments of this application, the term "User Equipment" (UE) refers to a device that accesses a communication network and receives network services through a network device, and can also be called "Terminal Equipment" (TE). Terminal equipment can be fixed or mobile, and can also be called a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, mobile terminal (MT), etc.

[0042] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0043] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0044] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0045] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.

[0046] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.

[0047] Additionally, uplink signals can include uplink data signals and / or uplink control signals and / or PRACH and / or SRS, etc., and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending / receiving uplink transmission on uplink resources can be understood as using that uplink resource to send / receive the uplink transmission. Downlink signals can include downlink data signals and / or downlink control signals and / or synchronization signals (SS, such as PSS / SSS) and / or broadcast channel (PBCH) and / or SSB (SS / PBCH block, including PSS, SSS, and PBCH and their DMRS) and / or CSI-RS, etc., and can also be referred to as downlink transmission (DL transmission), downlink information, or downlink channel. Sending / receiving downlink transmission on downlink resources can be understood as using that downlink resource to send / receive the downlink transmission.

[0048] In the embodiments of this application, each indication information or information may be carried by higher layer signaling and / or physical layer signaling. When carried by higher layer signaling, the indication information or information may also be referred to as higher layer parameters. The embodiments of this application do not limit this.

[0049] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; RRC signaling may include, for example, RRC messages, such as broadcast / public RRC messages / signaling (e.g., Master Information Block (MIB), system information), dedicated RRC messages / signaling; or RRC information elements (RRC IE); or information fields (or information fields included in information fields) included in RRC messages or RRC information elements. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as MAC control elements (MAC CE). However, this application is not limited to these. The names of signaling (e.g., RRC message, information element IE, information field, higher-layer parameters, etc.) used in the embodiments of this application are only examples and may be other names, and the embodiments of this application are not intended to limit them.

[0050] In the embodiments of this application, "multiple" refers to at least two, or two or more.

[0051] In this application embodiment, "predefined" refers to what is specified by the protocol or determined according to the rules specified by the protocol, and does not require additional configuration. "Configuration / instruction" refers to what the network device directly or indirectly configures / instructs through higher-layer signaling and / or physical layer signaling. Configuration / instruction can be achieved by introducing higher-layer parameters into the higher-layer signaling. Higher-layer parameters refer to information fields and / or information elements / information units / information cells (IEs) in the higher-layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical downlink control channel or control information carried by the sequence, but is not limited to these.

[0052] In the embodiments of this application, "overlapping" includes complete / full overlap and / or partial overlap and / or at least partial overlap. "Located in" includes complete / full location and / or partial location and / or at least partial location, and "located within" includes complete location.

[0053] For ease of description, the following description uses a base station as an example of an access network device. In the following descriptions, "if…", "in the case of…", and "when…" are used interchangeably unless there is confusion. For resources in the frequency domain, "carrier" and "resource grid" are interchangeable; "subcarrier spacing configuration (μ)" and "subcarrier spacing (SCS) (Δf)" are interchangeable; "subcarrier spacing" and "numerology" are interchangeable; "resource block," "RB," and "PRB," "physical resource block," and "common resource block (CRB)" are interchangeable; "configuration / indication / providance / given" are interchangeable; "index" and "identifier (ID)" are interchangeable.

[0054] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0055] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

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

[0057] Terminal device 102 can send data to network device 101, for example, using authorized or unauthorized transmission methods. Network device 101 can receive data sent by one or more terminal devices 102 and provide feedback to terminal devices 102, such as ACK / NACK confirmation information. Based on the feedback information, terminal device 102 can confirm the end of the transmission process, or can initiate new data transmission, or can retransmit the data.

[0058] Network device 101 can send data to terminal device 102 and / or terminal device 103 using unicast, multicast, or broadcast. Terminal device 102 can receive data sent by one or more network devices (e.g., dual-connection or multi-connection) via a downlink or by terminal device 103 via a sidelink.

[0059] It is worth noting that Figure 1 shows that both terminal devices 102 and 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Both terminal devices 102 and 103 may be outside the coverage area of ​​network device 101, or one terminal device 102 may be within the coverage area of ​​network device 101 while the other terminal device 103 may be outside the coverage area of ​​network device 101.

[0060] The following describes the terminology used in the embodiments of this application.

[0061] --Subcarrier spacing

[0062] The subcarrier spacing of a BWP is configurable, and the candidate subcarrier spacings are shown in Table 1 below. The BWP includes an integer number of PRBs using the SCS.

[0063] For uplink and downlink transmissions on a BWP, the SCS configured for a downlink BWP applies to downlink signals or channels in that DL BWP except for the SSB, and the SCS configured for an uplink BWP applies to uplink signals or channels in that UL BWP except for the PRACH.

[0064] Table 1

[0065] --PRACH preamble format (or PRACH format, or preamble format)

[0066] As shown in Table 4, the SCS of a PRACH is bound to its format. Therefore, if one of these formats is configured, there is no need to specify the SCS of the PRACH separately.

[0067] Table 4

[0068] PRACH preamble formats for L RA =839 andΔf RA ∈{1.25,5}kHz.

[0069] Table 5

[0070] Preamble formats for L RA ∈{139,571,1151}andΔf RA =15·2μkHz whereμ∈{0,1,2,3,5,6}.

[0071] As shown in Table 5, a format corresponds to multiple possible sequence lengths and SCSs. Therefore, if a format is configured, its corresponding sequence length and SCS need to be indicated.

[0072] In some embodiments, to improve uplink capacity and coverage, and reduce uplink latency, network devices may operate in full-duplex mode (e.g., simultaneously receiving and transmitting on different frequency domain resources) at certain time points in the downlink band of a TDD or FDD band. This operating mode is, for example, called Subband Non-overlapping Full Duplex (SBFD), but is not limited thereto. For example, a first time domain resource is a time domain resource used to (support / perform) full-duplex (e.g., SBFD) operation. The first and second time domain resources are located at different time points. In some embodiments, a second time domain resource is a time domain resource not used to (support / perform) full-duplex operation (or, not used for full-duplex operation, e.g., non-SBFD). For example, in the first time domain resource, the network device simultaneously receives and transmits on different frequency domain resources in the corresponding carrier (in the downlink band of the TDD or FDD band), while in the second time domain resource, the network device only receives or transmits on a carrier.

[0073] In some embodiments, the first time-domain resource refers to the time-domain resource that has / corresponds to SBFD subbands, or the time-domain resource where the SBFD subbands are located, and the second time-domain resource refers to the time-domain resource that does not have / correspond to SBFD subbands. SBFD subbands include, for example, DL subband(s) and / or uplink subband(s).

[0074] In some embodiments, a thirteenth time interval exists between the first time domain resource and the second time domain resource; or, a fourteenth time interval exists between the transmission of an uplink signal from the first time domain resource and the transmission of an uplink signal from the second time domain resource; and / or a fifteenth time interval exists between the reception of a downlink signal from the first time domain resource and the reception of a downlink signal from the second time domain resource. The thirteenth and / or fourteenth time intervals are not less than the (minimum) time period for the terminal device to switch bandwidth and / or beam and / or transmit power. This thirteenth and / or fifteenth time intervals are not less than the (minimum) time period for the terminal device to switch bandwidth and / or beam. This (minimum) time period can be predefined or reported, and this embodiment of the application does not limit it.

[0075] In some embodiments, the thirteenth time interval and / or the fourteenth time interval and / or the fifteenth time interval are predefined and / or reported and / or indicated. For example, the terminal device carries information indicating the above time intervals in the capability information sent to the network device. This application embodiment does not limit this.

[0076] In some embodiments, each time-domain resource and / or time interval includes one or more time-domain resource units.

[0077] In some embodiments, time-domain resource units include, for example, symbols and / or slots and / or sub-slots and / or mini-slots and / or symbol groups and / or slot groups and / or subframes and / or frames and / or ms and / or s, etc., and are not limited thereto.

[0078] In some embodiments, a time slot may include SBFD symbols and non-SBFD symbols, or only SBFD symbols, or only non-SBFD symbols.

[0079] In some embodiments, each frequency domain resource may include one or more consecutive frequency domain resource units or multiple discontinuous frequency domain resource units, or each frequency domain resource may be composed of one or more consecutive frequency domain resource units or multiple discontinuous frequency domain resource units. The frequency domain resource unit includes one or more of the following: subcarrier, subcarrier set / group, RB, RB set / group, etc.

[0080] The following describes the time-domain resource types and frequency-domain resource types involved in the embodiments of this application.

[0081] Time-domain resource types:

[0082] Figure 2 is a schematic diagram of time-domain resource types according to an embodiment of this application. As shown in Figure 2, it is assumed that one time slot includes 14 symbols, but this embodiment of the application does not limit this.

[0083] Downlink time-domain resources: such as DL symbols (downlink symbols), including symbols configured as downlink by public uplink / downlink configuration information;

[0084] Uplink time domain resources: such as UL symbols (uplink symbols), including symbols configured as uplink by public uplink / downlink configuration information;

[0085] Flexible time-domain resources: For example, referred to as Flexible symbols, including symbols that are not configured as downlink or uplink by the common uplink / downlink configuration information, or symbols that are configured as flexible. For example, when the UE is provided with common uplink / downlink configuration information, it includes symbols that are not configured as downlink or uplink by tdd-UL-DL-ConfigurationCommon or symbols that are configured as flexible by tdd-UL-DL-ConfigurationCommon. When the UE is not provided with tdd-UL-DL-ConfigurationCommon, it includes all symbols.

[0086] First time-domain resources: such as SBFD symbols, configured by second indication information for configuring (cell-specific) first time-domain resources and / or second time-domain resources, such as SBFD symbols including DL SBFD symbols and / or Flexible SBFD symbols, but not limited to these.

[0087] Second time-domain resources: For example, referred to as Non-SBFD symbols, configured, for example, by second indication information for configuring (cell-specific) first time-domain resources and / or second time-domain resources, such as Non-SBFD symbols including Full-DL symbols and / or Full-UL symbols and / or Full-Flexible symbols, but not limited to these.

[0088] Downlink time domain resources overlapping with the first time domain resources: or, in other words, the first time domain resources overlapping with the downlink time domain resources, or the downlink time domain resources configured as the first time domain resources, or the first time domain resources configured within the downlink time domain resources, for example, referred to as DL SBFD symbols / SBFD DL symbols (DL SBFD symbols / SBFD DL symbols), such as including SBFD symbols configured within DL symbols by the second indication information, or SBFD symbols configured as downlink by the common uplink and downlink configuration information.

[0089] Flexible time domain resources overlapping with the first time domain resources: or, in other words, the first time domain resources overlapping with flexible time domain resources, or flexible time domain resources configured as the first time domain resources, or first time domain resources configured within flexible time domain resources, such as Flexible SBFD symbols / SBFD Flexible symbols, for example, SBFD symbols configured within Flexible symbols by the second indication information, or SBFD symbols configured as Flexible by the common uplink and downlink configuration information.

[0090] Downlink time domain resources that do not overlap with first time domain resources: or, for example, downlink time domain resources that are not configured as first time domain resources, or second time domain resources that overlap with downlink time domain resources, or downlink time domain resources that overlap with second time domain resources, or downlink time domain resources configured as second time domain resources, or second time domain resources configured in downlink time domain resources, including, for example, symbols referred to as Full-DL symbols / DL-only symbols / DL non-SBFD symbols / non-SBFD DL symbols (Full-DL symbols / DL-only symbols / DL non-SBFD symbols / non-SBFD DL symbols), which are configured as downlink in the common uplink and downlink configuration information and are not configured with SBFD subbands.

[0091] Uplink time domain resources that do not overlap with the first time domain resources: These include uplink time domain resources not configured as first time domain resources, or second time domain resources overlapping with uplink time domain resources, or uplink time domain resources configured as second time domain resources, or second time domain resources configured within uplink time domain resources. Examples include Full-UL symbols / UL-only symbols / UL non-SBFD symbols / non-SBFD UL symbols (Full-UL symbols / UL-only symbols / UL non-SBFD symbols / non-SBFD UL symbols), including symbols configured as uplink by common uplink / downlink configuration information and not configured with SBFD subbands. In some embodiments, the terminal device does not expect uplink time domain resources to overlap with the first time domain resources; that is, uplink time domain resources that do not overlap with the first time domain resources are equal to uplink time domain resources, and the two can be interchanged.

[0092] Flexible time-domain resources that do not overlap with first time-domain resources: such as flexible time-domain resources that are not configured as first time-domain resources, or second time-domain resources that overlap with flexible time-domain resources, or flexible time-domain resources that overlap with second time-domain resources, or flexible time-domain resources configured as second time-domain resources, or second time-domain resources configured within flexible time-domain resources, for example referred to as Full-flexible symbols / Flexible-only symbols / Flexible non-SBFD symbols / non-SBFD Flexible symbols (Full-flexible symbols / Flexible-only symbols / Flexible non-SBFD symbols / non-SBFD Flexible symbols), for example including symbols that are configured as flexible and are not configured with SBFD subbands.

[0093] Among them, public uplink and downlink configuration information is, for example, tdd-UL-DL-ConfigurationCommon, but is not limited to this.

[0094] Frequency domain resource types:

[0095] 1. First frequency domain resources

[0096] In SBFD symbols, frequency domain resources in the carrier used solely for uplink transmission, such as physical resource blocks (PRBs) and / or subcarriers, are referred to as UL subbands (uplink subbands), or uplink SBFD subbands, or SBFD uplink subbands, or uplink RB sets (i.e., RB sets used for uplink), or uplink SBFD RB sets, or SBFD uplink RB sets, for example, configured by third indication information used to configure (cell-specific) first and / or third frequency domain resources. For example:

[0097] The uplink subband can be located on one side of the carrier or in the middle of the carrier.

[0098] The maximum value of UL subbands used for SBFD operation in an SBFD symbol within a TDD carrier is 1.

[0099] 2. Second frequency domain resources

[0100] In SBFD symbols and / or non-SBFD symbols, frequency domain resources available for uplink transmission in a UL BWP include, for example, PRBs and / or subcarriers; referred to as UL usable PRBs / RBs.

[0101] The definition of the second frequency domain resource differs between SBFD and non-SBFD symbols. For example, in SBFD symbols, the second frequency domain resource includes PRBs and / or subcarriers in the uplink BWP that belong to the (cell-specific) first frequency domain resource, or the PRBs and / or subcarriers in the intersection of the uplink BWP and the (cell-specific) first frequency domain resource, or the PRBs and / or subcarriers in the uplink BWP that overlap with the (cell-specific) first frequency domain resource. In non-SBFD symbols, the second frequency domain resource includes the PRBs and / or subcarriers in the uplink BWP. The SCS of the uplink BWP (including the included PRBs and / or subcarriers) may be the same as or different from the SCS of the (cell-specific) first frequency domain resource (including the included PRBs and / or subcarriers).

[0102] For example, the UL BWP can be an initial UL BWP or another UL BWP.

[0103] In some embodiments, UL BWP refers to active UL BWP, for example, when a terminal device transmits an uplink signal in the second frequency domain resource of an active UL BWP, but is not limited thereto.

[0104] Figures 3 to 4D are schematic diagrams of frequency domain resource types according to embodiments of this application. The frequency domain resource types of this embodiment will be described below with reference to the accompanying drawings.

[0105] (1) Alt.1: Define UL usable PRBs / RBs only for SBFD symbols

[0106] For example, as shown in Figures 3, 4A, and 4B, corresponding to SBFD symbols, UL usable PRBs include the intersection of (cell-specific) UL subbands and UL BWPs, such as the shaded areas corresponding to SBFD symbols in the figures. No UL usable PRBs are defined for non-SBFD symbols.

[0107] (2) Alt.2: Define UL usable PRBs / RBs for SBFD symbols and non-SBFD symbols (e.g., Full-DL and / or Full-Flexible / UL symbols).

[0108] For example, as shown in Figure 4C, for the SBFD symbol, the UL usable PRBs / RBs of the SBFD symbol include the intersection of the (cell-specific) UL subband and the UL BWP; for the Full-Flexible / UL symbol, the UL usable PRBs are the PRBs within the UL BWP; for the full-DL symbol, UL usable PRBs are not defined.

[0109] For example, as shown in Figure 4D, the SBFD symbol and the Full-Flexible / UL symbol are the same as in Figure 4C. For the non-SBFD symbol, UL usable PRBs are the PRBs in the UL BWP.

[0110] 3. Third frequency domain resources

[0111] In SBFD symbols, frequency domain resources in the carrier used only for downlink transmission, such as physical resource blocks (PRBs) and / or subcarriers, are referred to as DL subband (downlink subband), or downlink SBFD subband, or SBFD downlink subband, or downlink RB set (i.e., RB set used for uplink), or downlink SBFD RB set, or SBFD downlink RB set, for example configured by the fourth indication information, such as:

[0112] The downlink subband can be located on one side of the carrier or in the middle of the carrier.

[0113] The maximum value of UL subbands used for SBFD operation in an SBFD symbol within a TDD carrier is 1.

[0114] The fourth instruction message is included in the same or different RRC IE or message fields or messages as the third instruction message.

[0115] 4. Fourth frequency domain resources

[0116] In SBFD symbols and / or non-SBFD symbols, frequency domain resources available for downlink transmission in a DL BWP, such as PRBs and / or subcarriers, are referred to as DL usable PRBs / RBs of a DL BWP. The definition of the second frequency domain resources differs for SBFD symbols and non-SBFD symbols, as described above.

[0117] (1) Alt.1: Define DL usable PRBs / RBs only for SBFD symbols

[0118] Option 1:

[0119] For example, corresponding to SBFD symbols, DL usable PRBs include the intersection between (cell-specific) DL subband(s) and DL BWP;

[0120] Option 2:

[0121] For example, for SBFD symbols, DL usable PRBs are explicitly configured within the DL BWP of the SBFD symbol.

[0122] (2) Alt.2: Define UL usable PRBs / RBs for SBFD symbols and Full-Flexible / UL symbols respectively, or define UL usable PRBs / RBs for SBFD symbols and non-SBFD symbols respectively.

[0123] For example, for SBFD symbols, use either the first or second case in (1) Alt.1; for Full-Flexible / DL symbols or for non-SBFD symbols:

[0124] DL usable PRBs are PRBs in the DL BWP (DL usable PRBs are PRBs in the DL BWP).

[0125] The following describes the types of terminal devices (UEs) in the embodiments of this application.

[0126] The terminal device in this application embodiment includes a first terminal device (first UE) and a second terminal device (second UE); wherein,

[0127] First UE: For example, referred to as SBFD-aware UE, a UE with capabilities related to SBFD operation, including one or more of the following: (1) being able to know the SBFD configuration, such as the configuration of SBFD time-domain resources (e.g., SBFD symbols) and frequency-domain resources (e.g., UL subband / UL usable RBs, DL subbands / DL usable RBs); (2) being able to transmit uplink signals on SBFD symbols or DL ​​SBFD symbols.

[0128] Secondary UEs include, for example, legacy UEs or non-SBFD aware UEs, which are UEs that do not have the capability related to SBFD operation.

[0129] Various embodiments of the present application will now be described with reference to the accompanying drawings. These embodiments are merely exemplary and are not intended to limit the scope of the present application.

[0130] It should be noted that, in the features of the following embodiments, in order to avoid excessive length, the features / schemes are placed in parentheses. However, the features or schemes in parentheses, such as "(for the 4-step random access procedure)", "(cell-specific)", etc., are optional. They can be used as a limitation on the feature, or they can not be used as a limitation on the feature (equivalent to deleting the feature). Due to space constraints, this will not be repeated in the following embodiments.

[0131] First aspect of the embodiments

[0132] This application provides a random access method, which will be described from the perspective of the terminal device.

[0133] Figure 5 is a flowchart of a random access method according to an embodiment of this application. As shown in Figure 5, the method includes:

[0134] 501, In a cell, a random access preamble is sent at the first valid RO and / or the second valid RO;

[0135] Wherein, the first effective RO is located within the flexible time domain resources and / or the uplink time domain resources, and the second effective RO is located within the downlink time domain resources that overlap with the first time domain resources and / or the flexible time domain resources that overlap with the first time domain resources;

[0136] Alternatively, the first effective RO is located in a flexible time domain resource and / or uplink time domain resource that does not overlap with the first time domain resource, and the second effective RO is located in the first time domain resource.

[0137] It is worth noting that Figure 5 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 5 above.

[0138] In some embodiments, the terminal device may be a first terminal device (first UE) or a second terminal device (second UE), as described above, and will not be repeated here.

[0139] In some embodiments, sending a random access preamble can also be referred to as sending a PRACH.

[0140] In some embodiments, the terminal device sends a random access preamble to the first valid RO and / or second valid RO of the activated UL BWP, which is the initial UL BWP or other UL BWP.

[0141] In some embodiments, the first effective RO is (fully) located within flexible time-domain resources and / or uplink time-domain resources (including or excluding cases spanning two types of time-domain resources), and the second effective RO is (fully and / or partially and / or at least partially) located within downlink time-domain resources overlapping with the first time-domain resources (or, in other words, the second effective RO overlaps with DL SBFD symbols (fully and / or partially and / or at least partially)) and / or flexible time-domain resources overlapping with the first time-domain resources, or

[0142] The first valid RO (fully and / or partially and / or at least partially) is located in a flexible time domain resource and / or uplink time domain resource that does not overlap with the first time domain resource, and the second valid RO (fully and / or partially and / or at least partially) is located in the first time domain resource.

[0143] In some embodiments, the first valid resource is wholly and / or partially and / or at least partially located in a flexible time domain resource (Full-Flexible symbol) and / or uplink time domain resource (UL) that does not overlap with the first time domain resource, and the second valid RO is wholly and / or partially and / or at least partially located in the first time domain resource.

[0144] In some embodiments, the second effective RO does not overlap with the first effective RO.

[0145] In some embodiments, when the terminal device is a first UE, the first UE has the ability to transmit uplink signals in a first time domain resource (such as an SBFD symbol) or in a downlink time domain resource (DL SBFD symbol) overlapping with the first time domain resource and / or in a flexible time domain resource overlapping with the first time domain resource.

[0146] In some embodiments, the method may further include (not shown in the figures):

[0147] Receive first indication information for indicating a first terminal device, the first indication information including information for configuring RO. For example, the first indication information is for the cell, that is, receive (cell-specific) first indication information for indicating a first terminal device, but not limited thereto.

[0148] In some embodiments, the first indication information is dedicated to the first terminal device, and / or the feature or feature combination or device type corresponding to the first indication information includes only the first terminal device or includes both the first terminal device and the second terminal device.

[0149] In some embodiments, if the RO configured by the second indication information includes a second valid RO, the terminal device does not expect to be provided with the aforementioned first indication information. For example, the second indication information is directly included in the rach-ConfigCommon of BWP-UplinkCommon (in SIB1), but is not limited thereto.

[0150] In some embodiments, the RO configured by the first indication information includes a first RO and / or a second RO, wherein the first RO is located within flexible time domain resources and / or uplink time domain resources, and the second RO (fully and / or partially and / or at least partially) is located within downlink time domain resources overlapping with the first time domain resources and / or flexible time domain resources overlapping with the first time domain resources, or,

[0151] The first RO (fully and / or partially and / or at least partially) is located in a flexible time domain resource and / or uplink time domain resource that does not overlap with the first time domain resource, and the second RO (fully and / or partially and / or at least partially) is located in the first time domain resource.

[0152] In some embodiments, the second RO does not overlap with the first RO.

[0153] In some embodiments, the RO configured by the first indication information includes a first valid RO and / or a second valid RO. For example, it may include only the first valid RO, or only the second valid RO, or both the first and second valid ROs.

[0154] In some embodiments, the effective RO in the first RO is the first effective RO; the effective RO in the second RO is the second effective RO.

[0155] In some embodiments, the RO configured by the first indication information includes only the second valid RO, and the terminal device sends a random access preamble (PRACH) only on the second valid RO; or, when the terminal device is provided with information indicating that the valid RO includes the first valid RO, the valid RO includes both the first and second valid ROs, or the valid RO includes only the first valid RO.

[0156] In some embodiments, when the RO configured by the first indication information includes a first valid RO and a second valid RO, in the same random access process, the terminal device sends a random access preamble only in the first valid RO or only in the second valid RO; or, in the same random access process, the terminal device sends a random access preamble in the first valid RO and / or the second valid RO.

[0157] In some embodiments, the first indication information can be used to configure random access parameters and / or to provide RACH configuration. For example, the first indication information is used to configure cell-specific random access parameters (for a 4-step random access procedure) and / or to provide cell-specific RACH configuration (for a 4-step random access procedure); or, to configure feature or feature combination-specific random access parameters (for a 4-step random access procedure) and / or to provide feature or feature combination-specific RACH configuration (for a 4-step random access procedure); or, to configure cell-specific random access parameters (for a first UE) and / or to provide (cell-specific) RACH configuration (for a first UE) (for a 4-step random access procedure).

[0158] It should be noted that the above examples are merely specific examples, but this application is not limited to the above examples, and can also configure corresponding parameters and / or provide corresponding RACH configurations according to actual conditions.

[0159] In some embodiments, the first indication information is included in the BWP configuration information, such as in an IE (Internet Information Service) for configuring common parameters of the uplink BWP (UL BWP), such as BWP-UplinkCommon, which provides random access parameters that can be applied to random access performed on the UL BWP. The UL BWP can be an initial UL BWP or another configured UL BWP. For an initial UL BWP for a cell, its BWP-UplinkCommon is included in a System Information Block (SIB), such as SIB1 or other SIBs different from SIB1, such as the uplink common configuration information (UplinkConfigCommonSIB) in the SIB serving cell common configuration information (ServingCellConfigCommonSIB) included in SIB1 and / or included in dedicated RRC signaling (such as the serving cell common configuration information (UplinkConfigCommon) in the serving cell common configuration information (ServingCellConfigCommon)n of the cell; for other UL BWPs of the cell, their BWP-UplinkCommon is included in dedicated RRC signaling (such as BWP-Uplink (ServingCellConfig)), but not limited to this, and will not be listed here.

[0160] In some embodiments, the first indication information may be directly included in the BWP-UplinkCommon or included in additionalRACH-ConfigList-r17 in the BWP-UplinkCommon.

[0161] In some embodiments, the first indication information may be rach-ConfigCommon or rach-ConfigCommon-17 in additionalRACH-ConfigList-r17, but this is only an example and the application is not limited thereto. rach-ConfigCommon is used to configure cell-specific random access parameters (for the 4-step random access procedure), while rach-ConfigCommon-17 in additionalRACH-ConfigList-r17 is used to configure feature- or feature combination-specific random access parameters (for the 4-step random access procedure).

[0162] In some embodiments, for the same uplink BWP (UL BWP), its BWP configuration information may include one or more first indication information, such as only including rach-ConfigCommon (used to configure cell-specific random access parameters), or including rach-ConfigCommon and rach-ConfigCommon-17, or including rach-ConfigCommon and rach-ConfigCommon-19, and various other combinations, which will not be elaborated here.

[0163] In some embodiments, random access parameters are configured independently for different UL BWPs. For example, the first indication information corresponding to different UL BWPs is independent of each other or different UL BWPs correspond to different first indication information.

[0164] In some embodiments, the first indication information may be referred to as RACH configuration, and one first indication information corresponds to one RACH configuration.

[0165] In some embodiments, the first indication information includes information for configuring ROs (or PRACH resources, PRACH transmission occasions, RACH occasions, ROs, etc.), for example, the information includes at least one of the following, but is not limited thereto, the information including:

[0166] Information indicating the random access type;

[0167] Instruct PRACH to configure the index;

[0168] Information indicating the number of ROs in the frequency domain or the number of ROs in an FDM (Frequency Division Multiplexing) over a time instance;

[0169] Information indicating the offset of the lowest RO (starting RB) in the frequency domain relative to the corresponding physical resource block (PRB) (reference RB).

[0170] The following examples illustrate the above information.

[0171] [Revised according to Detailed Rules 26, November 2025] Table 1-1

[0172] As shown in Table 1-1, RACH-ConfigGeneric is for Type-1 random access (or 4-step random access type), for example, rach-ConfigCommon, rach-ConfigCommonIAB-r1 and rach-ConfigCommon-17 can each include RACH-ConfigGeneric.

[0173] As shown in Table 1-1, `prach-ConfigurationIndex` or `prach-ConfigurationIndex-19` indicates the PRACH configuration index in the first and second tables. The first table is for TDD (unparired spectrum), and the second table is for FDD (parired spectrum) or SUL (supplementary uplink). It indicates whether the PRACH configuration index in the first or second table is defined and / or configured / indicated.

[0174] The PRACH configuration index provides information such as the random access preamble format, the frame and / or subframe and / or time slot (such as the PRACH time slot) where the RO is located, the start symbol of the RO in the PRACH time slot, and the number of ROs.

[0175] In some embodiments, prach-ConfigurationIndex or prach-ConfigurationIndex-19 may indicate that the PRACH configuration index is configured and / or defined and / or indicated, as illustrated below.

[0176] Example 1, the configured

[0177] The first UE may be provided with information indicating that prach-ConfigurationIndex and / or prach-ConfigurationIndex-19 indicate the PRACH configuration index from the first table or the second table, which is included in, but not limited to, the corresponding first indication information.

[0178] Example 2, the definition

[0179] In rach-ConfigCommon, it indicates the PRACH configuration index of the first table;

[0180] In the first indication information for the first UE, it indicates the PRACH configuration index of the second table;

[0181] prach-ConfigurationIndex-19 indicates the PRACH configuration index of the second table.

[0182] Example 3, Combination (of defined and configured elements)

[0183] For example, in a first indication message, when a first UE is provided with information indicating that its prach-ConfigurationIndex indicates the PRACH configuration index from a second table, the prach-ConfigurationIndex in the first indication message indicates the PRACH configuration index from the second table; otherwise, the PRACH configuration index is indicated from the first table.

[0184] msg1-FDM indicates / represents the number of ROs in the frequency domain, or the number of FDMed ROs within a time interval. PRACH frequency domain resources n RA ∈{0,1,…,M-1}, where M equals the higher-layer parameter msg1-FDM or msgA-RO-FDM (if configured), in ascending order of the initial uplink bandwidth portion during initial access (PRACH frequency resourcesn). RA ∈{0,1,…,M-1},where M equals the higher-layer parameter msg1-FDM or msgA-RO-FDM if configured, are numbered in increasing order within the initial uplink bandwidth part during initial access). The FDMed RO is continuous in the frequency domain.

[0185] msg1-FrequencyStart indicates / indicates ① the offset of the lowest RO in the frequency domain relative to the lowest PRB (e.g., PRB 0 in the corresponding UL BWP) (as referred to as the first offset offset1), and / or ② the offset of the lowest RO in the frequency domain relative to the lowest PRB (e.g., PRB 0 in the corresponding UL BWP) in the UL usable PRBs (as referred to as the second offset offset2).

[0186] Figures 7A to 7G are schematic diagrams of information configuration according to an embodiment of this application. The resource configuration described above will be explained below with reference to Figures 7A to 7G.

[0187] Case 1: For RO located at any symbol, msg1-FrequencyStart has the same meaning.

[0188] (1)msg1-FrequencyStart indicates / indicates ① the offset (offset1) of the lowest RO in the frequency domain relative to the lowest PRB (such as PRB 0) in the corresponding UL BWP;

[0189] As shown in Figure 7A, for an RO located at any position, such as a symbol located at DL, F (i.e., flexible), UL, a symbol across DL and F, a symbol across F and UL, etc., the offset of the lowest RO in the frequency domain relative to the lowest PRB (in the corresponding UL BWP (i.e., the UL BWP where the RO is located) is offset1, such as Msg1-Frequencystart indicating / indicating offset1.

[0190] (2) msg1-FrequencyStart indicates / indicates the offset (offset2) of the lowest RO in the frequency domain relative to the lowest PRB (such as PRB 0) in the UL usable PRBs (corresponding UL BWP);

[0191] As shown in Figure 7B, for an RO located in an SBFD symbol, such as an RO located in any position such as a symbol in DL, F, UL, a symbol across DL and F, or a symbol across F and UL, the lowest RO in the frequency domain is offset by the lowest PRB in the UL usable PRBs (in the corresponding UL BWP (i.e., the UL BWP where the RO is located) as offset2, as indicated by Msg1-Frequencystart.

[0192] Case 2: The meaning of msg1-FrequencyStart differs depending on the symbol of the RO.

[0193] (1) For RO located in DL SBFD symbol, it is represented by ②; for other RO, it is represented by ①, as illustrated below.

[0194] Example 2-1, as shown in Figure 7C, for ROs where all resources are located within the DL SBFD symbol, msg1-FrequencyStart represents ②; for ROs located in other positions, msg1-FrequencyStart represents ①.

[0195] Example 2-2, as shown in Figure 7D, for a RO where at least part of the resource is located within the DL SBFD symbol, msg1-FrequencyStart represents ②; for other ROs, msg1-FrequencyStart represents ①.

[0196] Example 2-3, as shown in the figure, for a RO where at least some resources are located (or at least partially located) within the DL SBFD symbol and are not located (or not located at all or have no resources located) within the Full-DL symbol, msg1-FrequencyStart represents ②; for other ROs, msg1-FrequencyStart represents ①.

[0197] (2) For RO located in DL symbol, it means ②; for other RO, it means ①, as illustrated below.

[0198] Example 2-4, as shown in Figure 7F, for ROs where all resources are within the DL symbol, msg1-FrequencyStart represents ②; for other ROs, it represents ①.

[0199] Example 2-5, as shown in Figure 7G, for a RO where at least some resources are located within the DL symbol, msg1-FrequencyStart represents ②; for other ROs, it represents ①.

[0200] Furthermore, as shown in Figures 7A-7G, the number of ROs in the frequency domain is 2, i.e., msg1-FDM = 2, but it is not limited to this. As shown, offset 2 and offset 1 include the same number of PRBs as offset 1, but it is not limited to this. The above explanation uses the indication information msg1-FrequencyStart as an example, but it is not limited to this. The above are specific examples of embodiments of this application, but are not limited to this.

[0201] Case 3: msg1-FrequencyStart does not target ROs located on partial symbols.

[0202] For example, for an RO located in a DL symbol and / or a DL SBFD symbol, the position of the lowest RO in the frequency domain is predefined. For example, the offset of the lowest PRB in the UL usable PRBs of the lowest RO in the frequency domain (in the corresponding UL BWP (i.e., the UL BWP where the RO is located)) is predefined. For example, the offset is 0, that is, the lowest RO in the frequency domain starts from the lowest PRB in the UL usable PRBs.

[0203] In some embodiments, the examples described in Figures 7A to 7G above may be applicable to different situations. For example, situations 2 or 3 above may only apply when all SBFD symbols are configured within downlink symbols (or all SBFD symbols are configured / indicated as downlink by tdd-UL-DL-ConfigurationCommon) and / or the configured ROs do not include ROs within SBFD symbols located within flexible symbols. For example, when all SBFD symbols are configured within downlink symbols, the method in situation 2 or 3 may be used; otherwise, the method in situation 1 may be used, but this is not a limitation.

[0204] In some embodiments, the RO configured by msg1-FrequencyStart and msg1-FDM (located in the Flexible SBFD) should be within the corresponding UL usable PRBs (of the corresponding UL BWP), or the UE expects the RO configured by msg1-FrequencyStart and msg1-FDM (located in the Flexible SBFD) to be within the corresponding UL usable PRBs (of the corresponding UL BWP).

[0205] In some embodiments, the first indication information may further include information for indicating the applicable random access features and / or UE type. For example, this information may include information for indicating / specifying a series of preamble partitions, such as featureCombinationPreamblesList-r17, where each preamble partition is associated with a feature or feature combination, but is not limited thereto. For example, the featureCombinationPreamblesList-r17 may include one or more FeatureCombinationPreambles-r17.

[0206] In some embodiments, when the terminal device is not provided with public uplink / downlink configuration information, the first valid RO does not precede the SSB in its PRACH time slot and begins at least a first time interval after the last SSB; and / or,

[0207] When the terminal device is provided with public uplink and downlink configuration information, the first valid RO is within the uplink time domain resources; or, the first valid RO is not before the SSB in its PRACH time slot, and begins after the first time interval after the last downlink time domain resources and after the second time interval after the last SSB.

[0208] In some embodiments, the first effective RO:

[0209] Within flexible time-domain resources and / or uplink time-domain resources that do not overlap with first-time-domain resources; and / or,

[0210] Not overlapping with downlink time domain resources, and / or

[0211] It begins after the sixteenth time interval following (its) last downlink time-domain resource, and / or

[0212] It does not overlap with SSB.

[0213] Not before the SSB in its PRACH time slot, and / or

[0214] It begins after the seventeenth time interval following the last SSB (which precedes it), and / or

[0215] Not overlapping with resources in the first time domain, and / or

[0216] Beginning after the eighteenth time interval following the last first time domain resource (where the values ​​of the first and second time intervals are the same or different), and / or

[0217] Not overlapping with the third RO, and / or

[0218] In the frequency domain, it is within the first frequency domain resource (uplink available resource) or the (cell-specific) second frequency domain resource (uplink subband). As can be seen from the above embodiments, the first effective RO is an RO that has / satisfies at least one of the above conditions. The above conditions are only specific examples of this application. The embodiments of this application are not limited to the above conditions and may include any other conditions according to the actual situation, which will not be listed here.

[0219] In some embodiments, the second effective RO:

[0220] (Completely) within (the second frequency domain resources (uplink available resources) determined based on (cell-specific) first frequency domain resources) or (cell-specific) first frequency domain resources (uplink subband); and / or,

[0221] Not overlapping with SSB; and / or,

[0222] Not before the SSB in its PRACH time slot; and / or,

[0223] It begins at least three time intervals (which are the same as or different from the values ​​of the first and second time intervals mentioned above) after the last SSB (which precedes it); and / or,

[0224] It ends before at least the fourth time interval of the first SSB (which is the same as or different from the value of the first and second time intervals mentioned above); and / or,

[0225] (Completely) within the downlink time-domain resources (DL SBFD symbols) overlapping with the first time-domain resources; and / or,

[0226] Not overlapping with downlink time-domain resources (Full-DL symbols) that do not overlap with first-time-domain resources; and / or,

[0227] It begins at least five time intervals after the last downlink time-domain resource (Full-DL symbol) that does not overlap with the first time-domain resource; and / or,

[0228] It ends at least six time intervals before the first downlink time-domain resource (Full-DL symbol) that does not overlap with the first time-domain resource; and / or,

[0229] It does not overlap with flexible time-domain resources (flexible SBFD symbols) that overlap with first-time-domain resources; and / or,

[0230] It ends at least seven time intervals before the first flexible time-domain resource (Flexible SBFD symbol) that overlaps with the first time-domain resource, and / or,

[0231] It does not overlap with Flexible temporal resources (Flexible notation); and / or,

[0232] It ends at least eight time intervals before the first flexible time-domain resource (Flexible symbol) (after which), and / or,

[0233] Not overlapping with uplink time domain resources (UL symbol) or (equivalent to uplink time domain resources that do not overlap with first time domain resources (Full-UL symbol); and / or,

[0234] It ends at least nine time intervals before the first uplink time-domain resource (UL symbol) (following it), and / or,

[0235] It does not overlap with fully-flexible time-domain resources that do not overlap with first-time-domain resources; and / or,

[0236] It ends at least tenth time interval before the first flexible time-domain resource (Full-flexible symbol) that does not overlap with the first time-domain resource, and / or,

[0237] It does not overlap with second-time-domain resources (non-SBFD symbols); and / or,

[0238] Beginning at least after the eleventh time interval following (the) last second time-domain resource (non-SBFD symbol); and / or,

[0239] It ends at least twelfth time interval before the first second time-domain resource (non-SBFD symbol) (following it); and / or,

[0240] Multiple overlaps between flexible time-domain resources (Flexible SBFD symbols) that do not overlap with first time-domain resources, flexible time-domain resources (Full-Flexible symbols) that do not overlap with first time-domain resources, and flexible time-domain resources (Flexible symbols) and uplink time-domain resources (UL symbols); and / or,

[0241] It does not overlap with the third RO; and / or

[0242] It does not overlap with the thirteenth time interval between the first and second time domain resources.

[0243] As can be seen from the above embodiments, the second effective RO is an RO that has / satisfies at least one of the above conditions. The above conditions are only specific examples of this application. The embodiments of this application are not limited to the above conditions and may include any other conditions according to the actual situation, which will not be listed here.

[0244] In some embodiments, the third RO corresponds to another first indication information (i.e., configured by another first indication information) and / or the third RO and the RO configured by the first indication information corresponding to the second valid RO adopt the same or different random access preamble format and random access subcarrier spacing (PRACH SCS), and / or the third RO is a valid RO and / or associated with an SSB.

[0245] In some embodiments, the values ​​of different time intervals among the first to twelfth time intervals and the sixteenth to eighteenth time intervals may be the same or different.

[0246] In some embodiments, the terminal device determines a first valid RO and / or a second valid RO corresponding to the first indication information (or, determines a valid RO among the first ROs, i.e., a valid RO among the first and / or second ROs, i.e., a second valid RO), and / or, the ROs configured in the first indication information include the first valid RO and / or the second valid RO. Wherein, the terminal device determines the first valid RO and / or the second valid RO under preset conditions, and / or the ROs configured in the first indication information under preset conditions include the first valid RO and / or the second valid RO. For example, when the preset conditions are met (first case), the terminal device determines the first valid RO and / or the second valid RO, and / or the ROs configured in the first indication information include the first valid RO and / or the second valid RO.

[0247] In some embodiments, the preset conditions may include at least one of the following conditions:

[0248] The cell supports SBFD; and / or

[0249] The terminal device is provided with information indicating that the cell supports SBFD; and / or

[0250] The cell only allows access to the first terminal device; and / or

[0251] The terminal device is provided with information indicating that the cell only allows access from the first terminal device; and / or

[0252] The cell is configured with (cell-specific) first time domain resources and / or is configured with (cell-specific) first time domain resources in the downlink time domain; and / or

[0253] The terminal device is provided with information indicating (cell-specific) first time-domain resources of the cell; and / or

[0254] The cell is configured with (cell-specific) second frequency domain resources (uplink available resources) and / or (cell-specific) first frequency domain resources (uplink subband); and / or

[0255] The terminal device is provided with information indicating (cell-specific) second frequency domain resources (uplink available resources) and / or (cell-specific) first frequency domain resources (uplink subband);

[0256] The corresponding UL BWP (of the first indication information) includes second frequency domain resources (uplink available resources) determined based on (cell-specific) first frequency domain resources (uplink subband); and / or

[0257] The terminal device is provided with the common uplink and downlink configuration information of the cell; and / or

[0258] The cell is configured with downlink time domain resources by public uplink / downlink configuration information; and / or

[0259] The terminal device is the first terminal device; and / or

[0260] The terminal device supports random access using downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or

[0261] The cell allows random access using ROs located in downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or

[0262] The terminal device is provided with information indicating that the cell allows random access using downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or

[0263] The terminal device is provided with information indicating that the terminal device is permitted to use ROs located in downlink time domain resources and / or in downlink time domain resources overlapping with the first time domain resources and / or in the first time domain resources for random access; and / or

[0264] The terminal device is provided with information indicating that the RO configured in the first indication information includes and / or excludes a first valid RO and / or a second valid RO; and / or

[0265] The terminal device is provided with information for indicating whether to enable and / or disable the first valid RO and / or the second valid RO (corresponding to the first indication information); and / or

[0266] The terminal device is provided with information to instruct the terminal device to determine (corresponding to the first indication information) and / or use a first effective RO and / or a second effective RO; and / or

[0267] The terminal device is provided with information to indicate (corresponding to the first indication information) whether a specific RO is valid and / or invalid.

[0268] In some embodiments, the above-mentioned preset conditions may be indicated / configured / defined, but are not limited thereto.

[0269] As can be seen from the above embodiments, when the above preset conditions are met (such as in the first case), the terminal device determines that the RO configured by the first instruction information includes the first valid RO and / or the second valid RO. The above preset conditions can be at least one of the conditions listed above, that is, any combination, but not limited to the above conditions. The above are only specific examples of the embodiments of this application, but the embodiments of this application are not limited to this, and can also include any other conditions according to the actual situation, which will not be listed here one by one.

[0270] In some embodiments, for a first RO (among the ROs configured by the first indication information), in the first case described above and / or the second case described below, the first RO is valid (a valid first RO is a first valid RO), the second case including:

[0271] Within flexible time-domain resources and / or uplink time-domain resources that do not overlap with first-time-domain resources; and / or,

[0272] Not overlapping with downlink time domain resources, and / or

[0273] It begins after the sixteenth time interval following (its) last downlink time-domain resource, and / or

[0274] Not overlapping with SSB, and / or

[0275] Not before the SSB in its PRACH time slot, and / or

[0276] It begins after the seventeenth time interval following the last SSB (which precedes it), and / or

[0277] Not overlapping with resources in the first time domain, and / or

[0278] Beginning after the eighteenth time interval following the last first time domain resource (where the values ​​of the first and second time intervals are the same or different), and / or

[0279] Not overlapping with the third RO, and / or

[0280] In the frequency domain, it is within the second frequency domain resources (uplink available resources) or (cell-specific) first frequency domain resources (uplink subband).

[0281] In some embodiments, the third RO is as described above, and will not be repeated here.

[0282] As can be seen from the above embodiments, in the first and / or second cases, the terminal device determines that the first RO is valid. The second case is as described above, but is not limited to the conditions listed above. The above are only specific examples of the embodiments of this application, but the embodiments of this application are not limited to this. Any other conditions may be included according to the actual situation, which will not be listed here.

[0283] In some embodiments, for the first RO (of the ROs configured with the first indication information):

[0284] When the terminal device is not provided with public uplink / downlink configuration information, if the first RO is not before the SSB in the PRACH time slot where the first RO is located, and the first RO starts at least after a first time interval after the last SSB, then the first RO is valid; and / or,

[0285] When the terminal device is provided with public uplink and downlink configuration information, the first RO is in the uplink time domain resources; or, the first RO is not before the SSB in the PRACH time slot where the first RO is located, and the first RO starts after the first time interval after the last downlink time domain resource and after the second time interval after the last SSB, then the first RO is valid.

[0286] For example, the first effective RO, or the effective RO within the first RO, can be determined using the following method, where the first time interval and the second time interval = N. gap symbols:

[0287] As can be seen from the above embodiments, under different circumstances, i.e. when public uplink and downlink configuration information is provided and not provided, the first RO is determined to be valid under certain conditions. These conditions are not limited to these and may include any other conditions depending on the actual situation, which will not be listed here.

[0288] In the above embodiments, using the above method, only ROs located within the flexible symbols and / or uplink symbols may be valid ROs. When determining validity, it is not necessary to consider the time-frequency domain resource types related to SBFD (e.g., UL subband, UL usable RBs, SBFD symbols, non-SBFD symbols). For example, for the case where the UE is provided with tdd-UL-DL-ConfigurationCommon, Figure 9 is a resource configuration diagram of an embodiment of this application. As shown in Figure 9, let BWP SCS = Preamble SCS = SSB SCS = 15 / 30kHz. In Figure 9, among the ROs located within the flexible symbols and / or uplink symbols, the white ROs are valid ROs (the first valid RO), and the gray ROs do not satisfy the above conditions in their positional relationship with the SSB / DL symbols, therefore they are not valid ROs.

[0289] In some embodiments, for a second RO (among the ROs configured by the first indication information), in the first case described above and / or the third case described below, the second RO is valid (the valid second RO is the second valid RO), the third case including:

[0290] The second RO is (completely) within either the second frequency domain resource (uplink available resource) determined based on the (cell-specific) first frequency domain resource, or the (cell-specific) first frequency domain resource (uplink subband); and / or,

[0291] Not overlapping with SSB; and / or,

[0292] Not before the SSB in its PRACH time slot; and / or,

[0293] It begins at least three time intervals (which are the same as or different from the values ​​of the first and second time intervals mentioned above) after the last SSB (which precedes it); and / or,

[0294] It ends before at least the fourth time interval of the first SSB (which is the same as or different from the value of the first and second time intervals mentioned above); and / or,

[0295] (Completely) within the downlink time-domain resources (DL SBFD symbols) overlapping with the first time-domain resources; and / or,

[0296] Not overlapping with downlink time-domain resources (Full-DL symbols) that do not overlap with first-time-domain resources; and / or,

[0297] It begins at least five time intervals after the last downlink time-domain resource (Full-DL symbol) that does not overlap with the first time-domain resource; and / or,

[0298] It ends at least six time intervals before the first downlink time-domain resource (Full-DL symbol) that does not overlap with the first time-domain resource; and / or,

[0299] It does not overlap with flexible time-domain resources (flexible SBFD symbols) that overlap with first-time-domain resources; and / or,

[0300] It ends at least seven time intervals before the first flexible time-domain resource (Flexible SBFD symbol) that overlaps with the first time-domain resource, and / or,

[0301] It does not overlap with Flexible temporal resources (Flexible notation); and / or,

[0302] It ends at least eight time intervals before the first flexible time-domain resource (Flexible symbol) (after which), and / or,

[0303] It does not overlap with uplink time domain resources (UL symbols) or (uplink time domain resources that do not overlap with first time domain resources (Full-UL symbols); and / or,

[0304] It ends at least nine time intervals before the first uplink time-domain resource (UL symbol) (following it), and / or,

[0305] It does not overlap with fully-flexible time-domain resources that do not overlap with first-time-domain resources; and / or,

[0306] It ends at least tenth time interval before the first flexible time-domain resource (Full-flexible symbol) that does not overlap with the first time-domain resource, and / or,

[0307] It does not overlap with second-time-domain resources (non-SBFD symbols); and / or,

[0308] Beginning at least after the eleventh time interval following (the) last second time-domain resource (non-SBFD symbol); and / or,

[0309] It ends at least twelfth time interval before the first second time-domain resource (non-SBFD symbol) (following it); and / or,

[0310] Multiple overlaps between flexible time-domain resources (Flexible SBFD symbols) that do not overlap with first time-domain resources, flexible time-domain resources (Full-Flexible symbols) that do not overlap with first time-domain resources, and flexible time-domain resources (Flexible symbols) and uplink time-domain resources (UL symbols); and / or,

[0311] Not overlapping with the third RO, and / or

[0312] It does not overlap with the thirteenth time interval between the first and second time domain resources.

[0313] In some embodiments, the third RO is as described above, and will not be repeated here.

[0314] As can be seen from the above embodiments, in the first and / or third cases, the terminal device determines that the second RO is valid. The third case is as described above, but is not limited to the conditions listed above. The above are only specific examples of the embodiments of this application, but the embodiments of this application are not limited to this. Any other conditions may be included according to the actual situation, which will not be listed here.

[0315] Figures 8A to 8F are schematic diagrams of determining a valid RO according to an embodiment of this application. The following examples, in conjunction with Figures 8A to 8F, illustrate the method for determining the validity of a second RO. In the following examples, the above-mentioned case 1 (refer to Figure 7) (ROs located at any symbol configured for the same first indication information, and ROs with the same index in the frequency domain have the same frequency domain position) are used as examples. However, this determination method can also be applied to the above-mentioned case 2 (refer to Figure 7), which will not be listed here.

[0316] Example 1: When the terminal device is provided with information to indicate enabling (corresponding to the first indication information) the second valid RO (corresponding to the first case), an RO located in DL SBFD symbols is valid (otherwise invalid) under the following conditions (corresponding to the second case):

[0317] (1) (Completely) within DL SBFD symbols;

[0318] (2) (Completely) within UL usable RBs (or UL subband).

[0319] As shown in Figure 8A, the second valid RO includes the valid ROs among the ROs located in the DL SBFD symbols determined according to the method described in Example 1.

[0320] Example 2: When the terminal device is provided with information to indicate enabling (corresponding to the first indication information) the second valid RO (corresponding to the first case), an RO located in DL SBFD symbols is valid (otherwise invalid) under the following conditions (corresponding to the second case):

[0321] (1) (Completely) within DL SBFD symbols;

[0322] (2) (Completely) within UL usable RBs (or UL subband);

[0323] (3) It does not overlap with SSB.

[0324] As shown in Figure 8B, the second valid RO includes the valid ROs among the ROs located in the DL SBFD symbols determined according to the method described in Example 2.

[0325] Example 3: When the terminal device is provided with information to indicate enabling (corresponding to the first indication information) the second valid RO (corresponding to the first case), an RO located in DL-SBFD symbols is valid (otherwise invalid) in the following cases:

[0326] (1) (Completely) within DL SBFD symbols, or the RO part is in DL SBFD symbols and the other part is in Flexible SBFD symbols;

[0327] (2) (Completely) within UL usable RBs (or UL subband).

[0328] As shown in Figure 8C, the second valid RO includes the valid ROs among the ROs located in the DL SBFD symbols determined according to the method described in Example 3.

[0329] Example 4: When the terminal device is provided with information to indicate enabling (corresponding to the first indication information) the second valid RO (corresponding to the first case), an RO located in DL-SBFD symbols is valid (otherwise invalid) under the following conditions (corresponding to the second case):

[0330] (1) (Completely) within DL SBFD symbols, or the RO part is in DL SBFD symbols and the other part is in Flexible SBFD symbols;

[0331] (2) (Completely) within UL usable RBs (or UL subband);

[0332] (3) It does not overlap with SSB.

[0333] As shown in Figure 8D, the second valid RO includes the valid ROs among the ROs located in the DL SBFD symbols determined according to the method described in Example 4.

[0334] Example 5: When the terminal device is provided with information to indicate enabling (corresponding to the first indication information) the second valid RO (corresponding to the first case), an RO located in DL SBFD symbols is valid (otherwise invalid) under the following conditions (corresponding to the second case):

[0335] (1) It does not overlap with Full-DL symbols;

[0336] (2) (Completely) within UL usable RBs (or UL subband).

[0337] As shown in Figure 8E, the second valid RO includes the valid ROs among the ROs located in the DL SBFD symbols determined according to the method described in Example 5.

[0338] Example 6: When the terminal device is provided with information to indicate enabling (corresponding to the first indication information) the second valid RO (corresponding to the first case), an RO located in DL SBFD symbols is valid (otherwise invalid) under the following conditions (corresponding to the second case):

[0339] (1) It does not overlap with Full-DL symbols;

[0340] (2) (Completely) within UL usable RBs (or UL subband);

[0341] (3) It does not overlap with SSB (e.g., SS / PBCH blocks indicated by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst in ServingCellConfigCommon).

[0342] As shown in Figure 8F, the second valid RO includes the valid ROs among the ROs located in the DL SBFD symbols determined according to the method described in Example 6.

[0343] Examples 1 to 6 may also exclude the first case described therein, and this application is not limited thereto.

[0344] As can be seen from the above embodiments, the second RO is effective in the first and / or third cases described above. The items included in the first and third cases are not limited to these, and may include any other items depending on the actual situation, which will not be listed here one by one.

[0345] In some embodiments, the first cases corresponding to the first (valid) RO and the second (valid) RO may be the same or different, or the first case may be defined for only one of them, for example, the first case may be defined only for the first (valid) RO, or only for the second (valid) RO. For example, by default (i.e., the second (valid) RO is not limited to the first case), the RO configured for the first indication information of the first terminal device includes the second valid RO. When the terminal device is provided with information indicating that the RO configured for the first indication information does not include the first valid RO (the first case for the first (valid) RO), then it does not include the first valid RO.

[0346] In some embodiments, the first RO is invalid in the case opposite to the first case (fourth case) and / or in the case opposite to the second case (fifth case); the second RO is invalid in the case opposite to the first case (fourth case) and / or in the case opposite to the third case (sixth case).

[0347] For example, the fourth case is as follows:

[0348] The cell does not support SBFD; and / or

[0349] The terminal device was not provided with information indicating that the cell supports SBFD; and / or

[0350] The cell allows access for a second terminal device; and / or

[0351] The terminal device was not provided with information indicating that the cell only allows access to the first terminal device; and / or

[0352] The cell is not configured with (cell-specific) first time domain resources and / or is configured with (cell-specific) downlink time domain resources; and / or

[0353] The terminal device was not provided with information indicating (cell-specific) first time-domain resources of the cell; and / or

[0354] The cell is not configured with (cell-specific) second frequency domain resources (uplink available resources) and / or (cell-specific) first frequency domain resources (uplink subband); and / or

[0355] The terminal device was not provided with information to indicate (cell-specific) second frequency domain resources (uplink available resources) and / or (cell-specific) first frequency domain resources (uplink subband);

[0356] The corresponding UL BWP (of the first indication information) does not include the second frequency domain resources (uplink available resources) determined based on the (cell-specific) first frequency domain resources (uplink subband); and / or

[0357] The terminal device was not provided with the common uplink and downlink configuration information of the cell; and / or

[0358] The cell was not configured with downlink time domain resources by public uplink / downlink configuration information; and / or

[0359] The terminal device is not the first terminal device; and / or

[0360] The terminal device does not support random access using ROs located in downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or

[0361] The cell does not allow random access using ROs located in downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or

[0362] The terminal device was not provided with information indicating that the cell allowed random access using downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or

[0363] The terminal device was not provided with information indicating that it was permitted to use ROs located in downlink time domain resources and / or in downlink time domain resources overlapping with the first time domain resources and / or in the first time domain resources for random access; and / or

[0364] The terminal device was not provided with information indicating that the RO configured in the first indication information included and / or did not include the first valid RO and / or the second valid RO; and / or

[0365] The terminal device was not provided with information to indicate enabling and / or disabling the first valid RO and / or the second valid RO (corresponding to the first indication information); and / or

[0366] The terminal device was not provided with information to instruct the terminal device to determine (corresponding to the first indication information) and / or use the first valid RO and / or the second valid RO; and / or

[0367] The terminal device was not provided with information to indicate whether a specific RO (corresponding to the first indication information) was valid and / or invalid.

[0368] For example, the fifth case is as follows:

[0369] Not within flexible time domain resources and / or uplink time domain resources that do not overlap with first time domain resources; and / or,

[0370] Overlapping with downlink time domain resources, and / or

[0371] It does not begin after the first time interval following the last downlink time-domain resource (that precedes it), and / or

[0372] Overlapping with SSB, and / or

[0373] Before the SSB in its PRACH time slot, and / or

[0374] It does not begin after the second time interval following the last SSB (and / or)

[0375] Overlapping with resources in the first time domain, and / or

[0376] Not starting after the X3 time interval following the last first time domain resource (where the values ​​of the first and second time intervals are the same or different), and / or

[0377] Overlapping with the third RO, and / or

[0378] In the frequency domain, it is not within the second frequency domain resources (uplink available resources) or (cell-specific) first frequency domain resources (uplink subband).

[0379] For example, the sixth case is as follows:

[0380] Not (completely) within (the second frequency domain resources (uplink available resources) determined based on (cell-specific) second frequency domain resources) or (cell-specific) first frequency domain resources (uplink subband); and / or,

[0381] Overlapping with SSB; and / or

[0382] Before the SSB in its PRACH time slot; and / or

[0383] It begins within the third time interval (which may be the same as or different from the values ​​of the first and second time intervals mentioned above) after the last SSB (preceding it); and / or

[0384] It ends within the fourth time interval (which is the same as or different from the values ​​of the first and second time intervals mentioned above) before the first SSB (after which it ends); and / or

[0385] Not (completely) within the downlink time domain resources (DL SBFD symbols) overlapping with the first time domain resources; and / or

[0386] Overlapping with downlink time-domain resources (Full-DL symbols) that do not overlap with first-time-domain resources; and / or

[0387] It begins within the fifth time interval following (the last) downlink time-domain resource (Full-DL symbol) that does not overlap with the first time-domain resource; and / or

[0388] It ends within the sixth time interval of the first downlink time-domain resource (Full-DL symbol) that does not overlap with the first time-domain resource; and / or

[0389] Overlapping with flexible time-domain resources (flexible SBFD symbols) that overlap with first-time-domain resources; and / or

[0390] It does not end before at least the seventh time interval preceding (before) the first flexible time-domain resource (Flexible SBFD symbol) that overlaps with the first time-domain resource, and / or

[0391] Overlapping with flexible temporal resources (Flexible notation); and / or

[0392] It ends within the eighth time interval (before) the first flexible time-domain resource (Flexible symbol), and / or,

[0393] Overlapping with uplink time domain resources (UL symbols) or (uplink time domain resources that do not overlap with the first time domain resource (Full-UL symbols); and / or,

[0394] Ends within the ninth time interval (before) the first uplink time-domain resource (UL symbol) (following it), and / or,

[0395] Overlapping with flexible time-domain resources (Full-flexible symbols) that do not overlap with first-time-domain resources; and / or,

[0396] It ends within the tenth time interval (before) the first flexible time-domain resource (Full-flexible symbol) that does not overlap with the first time-domain resource, and / or,

[0397] Overlapping with second time-domain resources (non-SBFD symbols); and / or,

[0398] It begins within the eleventh time interval following (the) last second time-domain resource (non-SBFD symbol); and / or,

[0399] It ends within the twelfth time interval (before) the first second time-domain resource (non-SBFD symbol); and / or,

[0400] Simultaneously, it overlaps with multiple flexible time-domain resources (Flexible SBFD symbols) that overlap with the first time-domain resource, and flexible time-domain resources (Full-Flexible symbols) that do not overlap with the first time-domain resource, and flexible time-domain resources (Flexible symbols) and uplink time-domain resources (UL symbols); and / or,

[0401] Overlapping with the third RO; and / or

[0402] It overlaps with the thirteenth time interval between the first and second time domain resources.

[0403] The third RO is as described above and will not be repeated here.

[0404] As can be seen from the above embodiments, the items included in any of the first to sixth situations are not limited to these, and may include any other items according to the actual situation, which will not be listed one by one here.

[0405] In some embodiments, the SSB includes: an SS / PBCH block indicated by SSB location information (ssb-PositionsInBurst) in SIB1 or Serving Cell Config Common Configuration Information (ServingCellConfigCommon) (the candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon); and / or,

[0406] (When the terminal device is not provided with a downlink or joint TCI state list (dl-OrJointTCI-StateList),) the SS / PBCH block indicated by SSB position information (ssb-PositionsInBurst) in the SMTC Additional PCI information (SSB-MTCAdditionalPCI) associated with the physical cell ID (where the physical cell ID has an active TCI state for PDCCH or PDSCH); and / or

[0407] (Configuration) SS / PBCH block for L1 beam measurement and / or reporting; and / or,

[0408] (Configure) SS / PBCH block for in-frequency RRM measurements; and / or,

[0409] (Configure) SS / PBCH block for inter-frequency RRM measurements.

[0410] In some embodiments, the method may further include (not shown in the figures): receiving relevant information, which includes at least one of the following:

[0411] Receive information indicating that the cell supports SBFD; and / or

[0412] Receive information for indicating (cell-specific) first time-domain resources of the cell; and / or

[0413] Receive information indicating a first frequency domain resource and / or a second frequency domain resource; and / or

[0414] Receive (for the cell) common uplink and downlink configuration information; and / or

[0415] Receive information indicating that the cell allows random access using ROs located in downlink time domain resources and / or in downlink time domain resources overlapping with the first time domain resources and / or flexible time domain resources overlapping with the first time domain resources; and / or

[0416] Receive information indicating that the terminal device is permitted to perform random access using ROs located in downlink time domain resources and / or in downlink time domain resources overlapping with the first time domain resources and / or in flexible time domain resources overlapping with the first time domain resources; and / or

[0417] Receive information indicating that a valid RO (corresponding to the first indication information) includes a second valid RO; and / or

[0418] Receive information for instructing the enabling of the second valid RO (corresponding to the first instruction information); and / or

[0419] Receive information for instructing the terminal device to determine (corresponding to the first indication information) a second valid RO; and / or

[0420] Receive information indicating that a specific RO (corresponding to the first indication information) is valid and / or invalid; and / or

[0421] Receive information indicating whether PRACH transmission is permitted and / or not permitted on the SSB symbol, and / or,

[0422] Receive information indicating whether PRACH is allowed and / or not allowed across the first and second time domain resources.

[0423] In some embodiments, the information used to indicate the validity and / or invalidity of a specific RO (corresponding to the first indication information) includes a sixth indication information and / or a seventh indication information; for example, the sixth indication information (directly and / or indirectly) is used to indicate that a (first / second) RO that meets specific conditions (such as one or more of the conditions listed in the first and / or third cases) may be valid. The seventh indication information is used to indicate that a (first and / or second) RO that meets specific conditions (such as one or more of the conditions listed in the fifth and / or sixth cases) is invalid.

[0424] In some embodiments, whether an RO that satisfies the specific conditions corresponding to the sixth indication information is valid also depends on other conditions, such as other conditions listed in the first and / or second cases, and / or the first and / or third cases, or other conditions beyond these, and the embodiments of this application are not limited thereto.

[0425] For example, the sixth indication information is used to indicate that a (second) RO (can) be valid across SBFD and non-SBFD symbols. When the terminal device is provided with the sixth indication information, a (second) RO across SBFD and non-SBFD symbols is valid if it is completely within UL usable PRBs and does not overlap with SSBs. When the UE is not provided with the sixth indication information, the (second) RO across SBFD and non-SBFD symbols is invalid.

[0426] For example, the sixth indication information is used to indicate that a (second) RO overlapping with an SSB may be valid. For instance, when the UE is provided with the sixth indication information, if a (second) RO is completely within a UL usable PRB, the RO is valid. When the UE is not provided with the sixth indication information, if a (second) RO is completely within a UL usable PRB and does not overlap with an SSB, the RO is valid.

[0427] For example, the sixth indication information is used to indicate that PRACH transmission is permitted within an SSB symbol. For instance, when the UE is provided with the sixth indication information, the RO is valid if a (second) RO is (completely) within a UL usable PRB. When the UE is not provided with the sixth indication information, the RO is valid if the (second) RO is (completely) within a UL usable PRB and does not overlap with an SSB.

[0428] For example, the seventh indication information is used to indicate that a (second) RO across (DL)SBFD and non-SBFD symbols is invalid. When the UE is provided with the seventh indication information, the (second) RO across (DL)SBFD and non-SBFD symbols is invalid. When the UE is not provided with the seventh indication information, a (second) RO across (DL)SBFD and non-SBFD symbols is valid if it is (entirely) within UL usable PRBs and does not overlap with SSBs.

[0429] For example, the seventh indication information is used to indicate that a (second) RO overlapping with an SSB is invalid. When the UE is provided with the seventh indication information, the (second) RO overlapping with an SSB is invalid. When the UE is not provided with the seventh indication information, if a (second) RO overlapping with an SSB is (completely) within a UL usable PRB, the (second) RO is valid.

[0430] In this embodiment, the method may further include: (based on the information) determining (the second valid RO corresponding to the first indication information).

[0431] As can be seen from the above embodiments, the terminal device can receive the above information and make judgments on the validity of RO based on the above information. However, the received information is not limited to this and may include other information according to the actual situation, which will not be listed here.

[0432] In some embodiments, the method further includes (not shown in the figures):

[0433] Receive first information for indicating the available preamble corresponding to a valid RO (or a configured RO) and / or second information for indicating the available preamble corresponding to a first valid RO (or the first RO) and / or third information for indicating the available preamble corresponding to a second valid RO (or the second RO).

[0434] In some embodiments, when the terminal device is only provided with the first information, the available preamble corresponding to the first valid RO and the second valid RO is the same; and / or, when the terminal device is provided with the second information and / or the third information, the available preamble corresponding to the first valid RO and the second valid RO is different.

[0435] In some embodiments, the availability of the first valid RO and the second valid RO being the same or different includes the number and / or sequence of the available preamble being the same or different.

[0436] In some embodiments, the available random access preambles on a RO include one or more, with different random access preambles associated with the same or different SSBs.

[0437] In some embodiments, the first information, the second information, and the third information include information for configuring the number of random access preambles and / or information for configuring the number of random access preambles associated with an SSB (on an RO) and / or information for configuring the initial random access preamble.

[0438] For example, the first information includes: first information for configuring the number of random access preambles R, such as totalNumberOfRA-Preambles and / or first information for configuring the number of ROs N associated with an SSB, such as ssb-perRACH-OccasionAndCB-PreamblesPerSSB, which together implicitly indicate that the number of random access preambles associated with an SSB on an RO = R / N.

[0439] The second information includes: second information for configuring the starting random access preamble, startPreambleForThisPartition, and / or second information numberOfPreamblesPerSSB-ForThisPartition for configuring the number S of random access preambles associated with an SSB; for example, the terminal device maps the SSB to the available random access preambles configured by the second information according to the method described in Option 2 below.

[0440] The third piece of information differs from the first and second pieces of information. The differences include: the information domain corresponding to the third piece of information is different from that of the first and second pieces of information.

[0441] In some embodiments, the first RO and the first effective RO can be interchanged.

[0442] In some embodiments, the second RO and the second effective RO can be interchanged.

[0443] The following describes how terminal devices map SSBs to ROS and / or random access preambles.

[0444] In some embodiments, the terminal device obtains the number (N) of SSBs associated with a RO and / or the random access preamble (R / S / T) associated with an SSB. For example, the terminal device maps SSBs to ROs based on these parameters. For example, when N<1, one SSB or SSB index is associated with 1 / N ROs, that is, 1 / N consecutive ROs are associated with the same SSB. When N>1 or N=1, N SSBs or SSB indexes are associated with one RO.

[0445] For example, for the first effective RO

[0446] Option 1:

[0447] ((For mapping SSB indexes to first PRACH occasions,)(For Type-1 random access procedure,)a UE is provided a number N of SS / PBCH block indexes associated with one(first)PRACH occasion and a number R of contention based preambles per SS / PBCH block index per(first)valid PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.)

[0448] (For mapping SSB indices to the first RO,) (For Type-1 random access procedures,) the UE is provided with the number N of associated SSB indices associated with a (first) valid RO by ssb-perRACH-OccasionAndCB-PreamblesPerSSB, and the number R of contention-based random access preambles associated with each (first) valid RO by an SSB index.)

[0449] Option 2:

[0450] ((For mapping SSB indexes to first PRACH occasions,)(For a random access procedure associated with a feature combination indicated by FeatureCombinationPreambles,)a UE is provided a number N of SS / PBCH block indexes associated with one(first)PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB and a number S of contention based preambles per SS / PBCH block index per(first)valid PRACH occasion by startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition.)

[0451] (For mapping SSB indices to the first PRACH timing, (for random access procedures associated with feature combinations indicated by FeatureCombinationPreambles) ssb-perRACH-OccasionAndCB-PreamblesPerSSB provides the UE with the number N of associated SSB indices associated with a (first) valid RO, and startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition provide the UE with the number S of contention-based random access preambles associated with an SSB index in each (first) valid RO.)

[0452] For example, for the second valid RO, in addition to Option 1 or 2 above, Option 3 can also be used, as follows:

[0453] Option 1:

[0454] (For mapping SSB indexes to second PRACH occasions,)(For Type-1 random access procedure,)a UE is provided a number N of SS / PBCH block indexes associated with one(second)PRACH occasion and a number R of contention based preambles per SS / PBCH block index per(second)valid PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0455] Option 2:

[0456] (For mapping SSB indexes to second PRACH occasions,)(For a random access procedure associated with a feature combination indicated by FeatureCombinationPreambles,)a UE is provided a number N of SS / PBCH block indexes associated with one(second)PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB and a number S of contention based preambles per SS / PBCH block index per(second)valid PRACH occasion by startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition.

[0457] Option 3:

[0458] (For mapping SSB indexes to second PRACH occasions,)(For a random access procedure associated with a feature combination indicated by FeatureCombinationPreambles,)a UE is provided a number N of SS / PBCH block indexes associated with one(second)PRACH occasion by information different from ssb-perRACH-OccasionAndCB-PreamblesPerSSB and a number S of contention based preambles per SS / PBCH block index per(second)valid PRACH occasion by information different from ssb-perRACH-OccasionAndCB-PreamblesPerSSB, startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition.

[0459] (For mapping SSB indices to the second PRACH timing,) (For random access procedures associated with feature merging indicated by FeatureCombinationPreambles) the information ssb-perRACH-OccasionAndCB-PreamblesPerSSB provides the UE with the number N of SSB indices associated with one (second) valid RO, and the information ssb-perRACH-OccasionAndCB-PreamblesPerSSB,startPreambleForThisPartition, and numberOfPreamblesPerSSB-ForThisPartition provides the UE with the number T of contention-based random access preambles associated with one SSB index in each (first) valid RO.)

[0460] In some embodiments, the method further includes:

[0461] (Respectively) (in the first period) map SSB (or SSB index) to the first effective RO and / or (in the second period) map SSB to the second effective RO; and / or

[0462] (In the third cycle) SSB (or SSB index) is mapped to the first effective RO and the second effective RO.

[0463] In some embodiments, for the cases where SSB (or SSB index) is mapped to the first valid RO (in the first period) and / or mapped to the second valid RO (in the second period):

[0464] In some embodiments, the first period includes a first mapping cycle and / or a first association cycle and / or a first association pattern cycle, and the second period includes a second mapping cycle and / or a second association cycle and / or a second association pattern cycle.

[0465] In some embodiments, the first mapping cycle and / or the first association cycle and / or the first association pattern cycle are determined based on the first valid RO included in the PRACH configuration cycle, or in other words, the first mapping cycle and / or the first association cycle and / or the first association pattern cycle correspond to the first valid RO.

[0466] For example, the first mapping cycle includes... The first (valid) ROs are mapped from the first to the last SSB (index) in the SS / PBCH block (indexes). Specifically, when N<1, each SSB index is mapped to 1 / N consecutive first (valid) ROs. When N>1 or N=1, every N consecutive SSBs or SSB indexes are mapped to one first (valid) RO.

[0467] For example, the first associated period and / or the first associated pattern period are defined as follows:

[0468] (To map SSB indexes to first(valid)PRACH occasions,)An(first)association period,starting from frame 0,for mapping SS / PBCH block indexes to(first)PRACH occasions is the smallest value in the set determined by the PRACH configuration period(according Table 8.1-1)such that SS / PBCH block indexes are mapped at least once to the(first(valid))PRACH occasions within the(first)association period,where a UE obtains from the value of ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.If after an integer number of SS / PBCH block indexes to(first(valid))PRACH occasions mapping cycles within the(first)association period there is a set of(first(valid))PRACH occasions or PRACH preambles that are not mapped to SS / PBCH block indexes,no SS / PBCH block indexes are mapped to the set of(first(valid))PRACH occasions or PRACH preambles.An(first)association pattern period includes one or more(first)association periods and is determined so that a pattern between(first(valid))PRACH occasions and SS / PBCH block indexes repeats at most every 160msec.(first(valid))PRACH occasions not associated with SS / PBCH block indexes after an integer number of (first) association periods, if any, are not used for PRACH transmissions.

[0469] (In order to map the SSB index to the first (valid) RRACH timing,) starting from frame 0, a (first) association period for mapping the SS / PBCH block index to the (first) PRACH timing is a set determined by the PRACH configuration period (according to Table 8.1-1) (e.g., if PRACH configuration period = 10, then this set includes {1, 2, 4, 8, 16} PRACH configuration periods) that makes Each SS / PBCH block index is mapped at least once to the minimum value of the (first) effective PRACH timing within the (first) associated period, wherein the UE obtains the ssb-PositionsInBurst value from SIB1 or ServingCellConfigCommon. (For example, = The number of SSB indices whose corresponding bit is 1 as indicated by the ssb-PositionsInBurst indicator). In this (first) association cycle, if an integer number of SS / PBCH block indices are indexed to (the mapping cycle of the first (valid) PRACH timing) and there are unmapped to If a (first (valid)) PRACH timing or PRACH preamble set is defined for an SS / PBCH block index, then no SS / PBCH block index is mapped to that (first) PRACH timing or PRACH preamble set. A (first) associated pattern period comprises one or more (first) associated periods, such that the pattern between a (first (valid)) PRACH timing and an SS / PBCH block index repeats at most every 160 milliseconds (that is, the (first) associated pattern period is at most 160 ms). (Within a (first) associated pattern period), (first (valid)) PRACH timings (if any) not associated with an SS / PBCH block index after an integer number of (first) associated periods are not used for PRACH transmission.)

[0470] Table 8.1-1:Mapping between PRACH configuration period and SS / PBCH block to PRACH occasion association period

[0471] In some embodiments, SSB indexes are mapped to the first valid RO in, for example, in the following order:

[0472] (To map SSB indexes to first(valid)PRACH occasions,)SS / PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to(first)valid PRACH occasions in the following order.

[0473] -First,in increasing order of preamble indexes within a single(first (valid))PRACH occasion

[0474] -Second,in increasing order of frequency resource indexes for frequency multiplexed(first(valid))PRACH occasions

[0475] -Third,in increasing order of time resource indexes for time multiplexed(first (valid))PRACH occasions within a PRACH slot

[0476] -Fourth,in increasing order of indexes for PRACH slots(containing first (valid)PRACH occasions)

[0477] In order to map SSB indexes to the first valid RO index, (the SSB indexes provided by ssb-PositionsInBurst in SIB1 or the SSB indexes in ServingCellConfigCommon) are mapped to that first valid RO:

[0478] Ascending order of random access preamble within a (first (valid)) RO;

[0479] Frequency reuse (first (valid)) RO frequency resource index ascending order;

[0480] Ascending order of time resource indexes for time multiplexing (first (valid)) RO within a PRACH time slot;

[0481] PRACH time-series index (including the first (valid) RO) in ascending order.

[0482] The first valid RO and its leading edge of an SSB index mapping are determined, for example, as follows:

[0483] To map SSB indexes to(first(valid))PRACH occasions,)(For Type-1 random access procedure,)if N<1,one SS / PBCH block index is mapped to 1 / N consecutive (first)valid PRACH occasions and R contention based preambles with consecutive indexes associated with the SS / PBCH block index per(first)valid PRACH occasion start from preamble index 0.If N≥1,R contention based preambles with consecutive indexes associated with SS / PBCH block index n,0≤n≤N-1,per(first)valid PRACH occasion start from preamble index where is provided by totalNumberOfRA-Preambles(for Type-1 random access procedure), and is an integer multiple of N.

[0484] (For Type-1 (i.e., 4-step RA type) random access procedures,) if N < 1, then an SSB index is mapped to 1 / N consecutive (first) valid ROs, and for each (first) valid RO, the R contention-based random access preambles with consecutive indices associated with that SSB start from random access preamble index 0. If N ≥ 1, then for each (first) valid RO, the R contention-based random access preambles with consecutive indices associated with SSB index n (i.e., the nth index, 0 ≤ n ≤ N-1) start from random access preamble index 0. At the beginning, among them, Provided by totalNumberOfRA-Preambles (for Type-1 random access procedure), and is an integer multiple of N.

[0485] In some embodiments, the second mapping cycle and / or the second association cycle and / or the second association pattern cycle are determined based on the second valid RO included in the PRACH configuration cycle, or in other words, the second mapping cycle and / or the second association cycle and / or the second association pattern cycle correspond to the second valid RO.

[0486] For example, the second mapping cycle includes... The first to the last SSB (index) in the SS / PBCH block (indexes) are mapped to the second (valid) ROs. When N<1, each SSB index is mapped to 1 / N consecutive second (valid) ROs. When N>1 or N=1, every N consecutive SSBs or SSB indexes are mapped to one second (valid) RO.

[0487] For example, the definitions of the second associated period and / or the second associated pattern period are as follows:

[0488] (To map SSB indexes to second(valid)PRACH occasions,)An(second)association period,starting from frame 0,for mapping SS / PBCH block indexes to(second)PRACH occasions is the smallest value in the set determined by the PRACH configuration period(according Table 8.1-1)such that SS / PBCH block indexes are mapped at least once to the(second(valid))PRACH occasions within the(second)association period,where a UE obtains from the value of ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.If after an integer number of SS / PBCH block indexes to (second(valid))PRACH occasions mapping cycles within the(second)association period there is a set of(second(valid))PRACH occasions or PRACH preambles that are not mapped to SS / PBCH block indexes,no SS / PBCH block indexes are mapped to the set of(second(valid))PRACH occasions or PRACH preambles.An(second)association pattern period includes one or more(second)association periods and is determined so that a pattern between(second(valid))PRACH occasions and SS / PBCH block indexes repeats at most every 160msec.(second(valid))PRACH occasions not associated with SS / PBCH block indexes after an integer number of(second)association periods,if any,are not used for PRACH transmissions.

[0489] (In order to map the SSB index to the second (valid) RRACH timing,) starting from frame 0, a (second) association period for mapping the SS / PBCH block index to the (second) PRACH timing is a set determined by the PRACH configuration period (according to Table 8.1-1) (e.g., if PRACH configuration period = 10, then this set includes {1, 2, 4, 8, 16} PRACH configuration periods) that makes Each SS / PBCH block index is mapped at least once to the minimum value of the (second) effective PRACH timing within the (second) associated period, wherein the UE obtains the value from the ssb-PositionsInBurst value in SIB1 or ServingCellConfigCommon. (For example, = The number of SSB indices whose corresponding bit is 1 as indicated by the ssb-PositionsInBurst indicator). Within this (second) association period, if an integer number of SS / PBCH block indices are indexed to (the second (valid)) PRACH timing mapping period after which there are unmapped... If a (second (valid)) PRACH timing or PRACH preamble set is defined for an SS / PBCH block index, then no SS / PBCH block index is mapped to that (second) PRACH timing or PRACH preamble set. The (second) associated pattern period comprises one or more (second) associated periods, such that the pattern between the (first (valid)) PRACH timing and the SS / PBCH block index repeats at most every 160 milliseconds (that is, the (second) associated pattern period is at most 160 ms). (Within the (second) associated pattern period), (second (valid)) PRACH timings (if any) not associated with an SS / PBCH block index after an integer number of (second) associated periods are not used for PRACH transmission.

[0490] In some embodiments, SSB indexes are mapped to a second valid RO in, for example, in the following order:

[0491] (To map SSB indexes to second(valid)PRACH occasions,)SS / PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to(second)valid PRACH occasions in the following order.

[0492] -First,in increasing order of preamble indexes within a single(second (valid))PRACH occasion

[0493] -Second,in increasing order of frequency resource indexes for frequency multiplexed(second(valid))PRACH occasions

[0494] -Third,in increasing order of time resource indexes for time multiplexed (second(valid))PRACH occasions within a PRACH slot

[0495] -Fourth,in increasing order of indexes for PRACH slots(containing second(valid)PRACH occasions)

[0496] In order to map SSB indexes to the first valid RO index, (the SSB indexes provided by ssb-PositionsInBurst in SIB1 or the SSB indexes in ServingCellConfigCommon) are mapped to the second valid RO:

[0497] Ascending order of random access preamble within a (second (valid)) RO;

[0498] Ascending order of frequency resource index for frequency reuse (second (valid)) RO;

[0499] Ascending order of time resource indexes for time multiplexing (second (valid) RO) within a PRACH time slot; ascending order of PRACH time sequence indexes (including second (valid) RO).

[0500] The first valid RO and its leading edge of an SSB index mapping are determined, for example, as follows:

[0501] (To map SSB indexes to second PRACH occasions,)(For Type-1 random access procedure,) if N<1, one SS / PBCH block index is mapped to 1 / N consecutive (second)valid PRACH occasions and R contention based preambles with consecutive indexes associated with the SS / PBCH block index per(second)valid PRACH occasion start from preamble index 0.If N≥1,R contention based preambles with consecutive indexes associated with SS / PBCH block index n,0≤n≤N-1,per(second)valid PRACH occasion start from preamble index where The total number of RA-Preambles (for Type-1 random access procedure) is provided by the total number of RA-Preambles, and is an integer multiple of N. (For Type-1 (i.e., 4-step RA type) random access procedures,) if N < 1, then an SSB index is mapped to 1 / N consecutive (second) valid ROs, and for each (second) valid RO, the R contention-based random access preambles with consecutive indices associated with that SSB start from random access preamble index 0. If N ≥ 1, then for each (second) valid RO, the R contention-based random access preambles with consecutive indices associated with SSB index n (i.e., the nth index, 0 ≤ n ≤ N-1) start from random access preamble index 0. At the beginning, among them, Provided by totalNumberOfRA-Preambles (for Type-1 random access procedure), and is an integer multiple of N.

[0502] The following describes the case of joint mapping, that is, mapping SSB (or SSB index) to the first effective RO and the second effective RO (in the third cycle).

[0503] In some embodiments, the third period includes a third mapping cycle and / or a third associated cycle and / or a third associated pattern cycle.

[0504] In some embodiments, the third mapping cycle and / or the third association cycle and / or the third association pattern cycle are determined based on the first effective RO and the second effective RO included in the PRACH configuration cycle, or in other words, the third mapping cycle and / or the third association cycle and / or the third association pattern cycle correspond to the first effective RO and the second effective RO.

[0505] For example, the third mapping cycle includes... The first (valid) ROs and / or second valid ROs are mapped from the first to the last SSB (index) in the SS / PBCH block (indexes). Specifically, when N<1, each SSB index is mapped to 1 / N consecutive first (valid) ROs and / or second valid ROs, respectively. When N>1 or N=1, every N consecutive SSBs or SSB indexes are mapped to one first (valid) RO or one second valid RO, respectively.

[0506] For example, in a third association pattern cycle, including a first effective RO and a second effective RO, the cycle of the third association pattern is defined as follows:

[0507] An association period,starting from frame 0,for mapping SS / PBCH block indexes to PRACH occasions is the smallest value in the set determined by the PRACH configuration period according Table 8.1-1such that SS / PBCH block indexes are mapped at least once to the PRACH occasions within the association period,where a UE obtains from the value of ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon.If after an integer number of SS / PBCH block indexes to PRACH occasions mapping cycles within the association period there is a set of PRACH occasions or PRACH preambles that are not mapped to SS / PBCH block indexes, no SS / PBCH block indexes are mapped to the set of PRACH occasions or PRACH preambles. An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS / PBCH block indexes repeats at most every 160msec. PRACH occasions not associated with SS / PBCH block indexes after an integer number of association periods, if any, are not used for PRACH transmissions.

[0508] In some embodiments, for example, map the SSB indexes to the first valid RO and / or the second valid RO in the following order:

[0509] 对于类型1随机接入过程,如果N<1,则一个SS / PBCH块索引被映射到1 / N个连续的有效PRACH时机,并且每个有效PRACH时机与该SS / PBCH块索引相关联的具有连续索引的R个基于竞争的前导码从前导码索引0开始。如果N≥1,则每个有效PRACH时机与SS / PBCH块索引n(0≤n≤N-1)相关联的具有连续索引的R个基于竞争的前导码从前导码索引 其中 is provided by totalNumberOfRA-Preambles for Type-1 random access procedure,and is an integer multiple of N.

[0510] SS / PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to valid PRACH occasions in the following order.

[0511] -First,in increasing order of preamble indexes within a single PRACH occasion

[0512] -Second,in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions

[0513] -Third,in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot

[0514] -Fourth,in increasing order of indexes for PRACH slots

[0515] The number N of SSBs associated with a RO and the number R / S of preambles associated with an SSB in the combined mapping are adopted in the following manner:

[0516] Option 1:For Type-1 random access procedure,a UE is provided a number N of SS / PBCH block indexes associated with one PRACH occasion and a number R of contention based preambles per SS / PBCH block index per valid PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0517] Option 2:(For a random access procedure associated with a feature combination indicated by FeatureCombinationPreambles,)a UE is provided a number N of SS / PBCH block indexes associated with one PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB and a number S of contention based preambles per SS / PBCH block index per valid PRACH occasion by startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition.

[0518] Figure 10 is a schematic diagram of mapping SSB (index) to RO, where N = 1 is assumed. If we assume that all white ROs are the first valid ROs in the PRACH cycle (the second valid ROs are not shown), the cycles shown are the first mapping cycle, the first associated cycle, and the first associated pattern cycle. If we assume that all white ROs are the second valid ROs in the PRACH cycle (the first valid ROs are not shown), the cycles shown are the second mapping cycle, the second associated cycle, and the second associated pattern cycle. If we assume that the white ROs are the first and / or second valid ROs in the PRACH cycle (i.e., all valid ROs in the PRACH cycle), the cycles shown are the third mapping cycle, the third associated cycle, and the third associated pattern cycle.

[0519] In some embodiments, the random access preamble may be referred to as a random access preamble code, a random access preamble sequence, a preamble, or a PRACH preamble.

[0520] This application provides a method for a terminal device to perform random access, which enables the terminal device to send a random access preamble to the network device using flexible time domain resources and / or uplink time domain resources and / or downlink time domain resources overlapping with the first time domain resources, or using flexible time domain resources and / or uplink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or flexible resources overlapping with the first time domain resources. In other words, it supports the use of the resources mentioned above to send uplink transmissions for random access, thereby increasing the coverage and capacity of random access and reducing latency.

[0521] The second aspect of the implementation plan [first confirm the method part, then supplement it later]

[0522] This application provides a random access device. This device may be, for example, a terminal device, or one or more components or parts configured within a terminal device; details identical to those in the first aspect of the embodiment will not be repeated.

[0523] Figure 11 is a schematic diagram of a random access device according to an embodiment of this application. Since the principle of the random access device in solving the problem is the same as the method of the first aspect embodiment, its specific implementation can refer to the first aspect embodiment, and the contents that are the same will not be repeated.

[0524] As shown in Figure 11, the random access device 1100 includes:

[0525] The first transmitting unit 1101 is used to transmit a random access preamble (PRACH) from a first valid RO or a second valid RO; the first valid RO is within flexible time domain resources and / or uplink time domain resources, the second valid RO is in downlink time domain resources and / or flexible time domain resources that overlap with the first time domain resources, or the first valid RO is located in flexible time domain resources and / or uplink time domain resources that do not overlap with the first time domain resources, and the second valid RO is located in the first time domain resources.

[0526] It is worth noting that Figure 11 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 11 above.

[0527] In some embodiments, the implementation of the first transmitting unit 1101 may refer to 501 of the first aspect, and the repeated parts will not be described again.

[0528] In addition, the first sending unit 1101 can also be used to send other messages to the network device. For example, it can send messages related to the random access procedure to the network side.

[0529] In some embodiments, the locations of the first effective RO and the second effective RO (the conditions to be met) are as described in the embodiments of the first aspect, and will not be repeated here.

[0530] In some embodiments, the terminal device is a first terminal device, and the GIA first terminal device has the ability to transmit uplink signals in a first time domain resource or in a downlink time domain resource that overlaps with the first time domain resource.

[0531] In some embodiments, the method further includes a first receiving unit 1102: configured to receive (for the cell) first indication information for instructing a first terminal device, the first indication information including information for configuring RO.

[0532] In some embodiments, the first indication information is dedicated to a first terminal device, and / or the feature or feature combination or device type corresponding to the first indication information includes only the first terminal device or includes both the first terminal device and a second terminal device. In some embodiments, the RO configured by the first indication information includes the first valid RO and / or the second valid RO (including only the first valid RO, only the second valid RO, or both the first valid RO and the second valid RO).

[0533] In some embodiments, the RO configured by the first indication information includes a first RO and / or a second RO, wherein the first RO is located within flexible time domain resources and / or uplink time domain resources, and the second RO (fully and / or partially and / or at least partially) is located within downlink time domain resources and / or flexible time domain resources overlapping with the first time domain resources; or, the first RO (fully and / or partially and / or at least partially) is located within flexible time domain resources and / or uplink time domain resources that do not overlap with the first time domain resources, and the second RO (fully and / or partially and / or at least partially) is located within the first time domain resources.

[0534] In some embodiments, the second RO does not overlap with the first RO. In some embodiments, the first indication information is as described in the embodiments of the first aspect, the contents of which are incorporated herein by reference and will not be repeated here.

[0535] In some embodiments, the apparatus 1100 further includes a first processing unit (not shown in the figure), which is configured to determine (based on relevant information / preset conditions) a first valid RO and / or a second valid RO corresponding to the first indication information, and / or to determine that the RO configured by the first indication information includes the first valid RO and / or the second valid RO. The relevant information / preset conditions and the determination method are as described in the embodiments of the first aspect, the contents of which are incorporated herein by reference and will not be repeated here.

[0536] In some embodiments, the apparatus 1100 further includes a second processing unit (not shown) for determining that the second RO is valid. The determination method is as described in the embodiments of the first aspect, the contents of which are incorporated herein by reference and will not be repeated here.

[0537] In some embodiments, the apparatus 1100 further includes a third processing unit (not shown) for determining that the first RO is valid. The determination method is as described in the embodiments of the first aspect, the contents of which are incorporated herein by reference and will not be repeated here.

[0538] In some implementations, the device 1100 further includes a second receiving unit (not shown in the figure) for receiving relevant information as described in the embodiments of the first aspect, the contents of which are incorporated herein by reference and will not be repeated here.

[0539] In some embodiments, the apparatus 1100 further includes a fourth processing unit (not shown) for determining the first effective RO and / or the second effective RO based on the relevant information.

[0540] In some embodiments, when the RO configured by the first indication information includes a first valid RO and a second valid RO, in the same random access process, the sending unit 1101 sends a random access preamble only in the first valid RO or only in the second valid RO; or, in the same random access process, the sending unit 1201 sends a random access preamble in the first valid RO and / or the second valid RO.

[0541] In some embodiments, the apparatus 1100 further includes a third receiving unit (not shown in the figure), which is configured to receive first information for indicating the available preamble corresponding to a valid RO and / or second information for indicating the available preamble corresponding to a first valid RO and / or third information for indicating the available preamble corresponding to a second valid RO.

[0542] In some embodiments, the first, second, and third information are as described in the embodiments of the first aspect, the contents of which are incorporated herein and will not be repeated here.

[0543] In some embodiments, when the terminal device is only provided with the second information, the available preamble corresponding to the first effective RO and the second effective RO is the same; and / or,

[0544] When the terminal device is provided with the second information and / or the third information, the available preambles corresponding to the first valid RO and the second valid RO are different.

[0545] In some embodiments, the apparatus 1100 further includes a fifth processing unit (not shown in the figures), which maps SSBs (or SSB indexes) to the first valid RO (in a first cycle) and / or maps SSBs to the second valid RO (in a second cycle), or maps SSBs (or SSB indexes) to both the first and second valid ROs (in the first cycle). The specific mapping methods are as described in the embodiments of the first aspect, and their contents are incorporated herein by reference and will not be repeated here.

[0546] Furthermore, for simplicity, Figure 11 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used based on the above description. The various components or modules in the above embodiments can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0547] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0548] Third aspect of the embodiments

[0549] This application provides a random access method, which will be described from the perspective of the network device. The content that is the same as that in the first aspect of the embodiment will not be repeated.

[0550] Figure 12 is a schematic diagram of a random access method according to an embodiment of this application. As shown in Figure 12, the method includes:

[0551] 1201, receive the random access preamble in the first valid RO or the second valid RO;

[0552] Wherein, the first effective RO is within flexible time domain resources and / or uplink time domain resources, the second effective RO is in downlink time domain resources and / or flexible time domain resources that overlap with the first time domain resources, or the first effective RO is located in flexible time domain resources and / or uplink time domain resources that do not overlap with the first time domain resources, and the second effective RO is located in the first time domain resources.

[0553] It is worth noting that Figure 12 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 12 above.

[0554] In some embodiments, the method may further include: receiving a random access preamble sent by a first terminal device at a first valid RO and / or a second valid RO; and / or receiving a random access preamble sent by a second terminal device at the first valid RO.

[0555] In some embodiments, the method further includes: sending (to the terminal device) first indication information for configuring random access parameters, wherein the RO configured by the first indication information includes the first valid RO and / or the second valid RO, and the second valid RO is not used by the second terminal device to send a random access preamble.

[0556] In some embodiments, the first instruction information is as described in the embodiments of the first aspect, the contents of which are incorporated herein and will not be repeated here.

[0557] In some embodiments, the method may further include: sending relevant information (to the terminal device) for determining a first valid RO and / or a second valid RO, so that the terminal device determines (the first indication information) the first valid RO and / or the second valid RO based on the relevant information, and / or determines that the valid RO (corresponding to the first indication information) includes the first valid RO and / or the second valid RO.

[0558] In some embodiments, this relevant information is as described in the embodiments of the first aspect, the contents of which are incorporated herein by reference and will not be repeated here.

[0559] In some embodiments, the method may further include: (to the terminal device) sending first information for indicating an available random access preamble corresponding to a valid RO and / or second information for indicating an available preamble corresponding to a first valid RO and / or third information for indicating an available preamble corresponding to a second valid RO.

[0560] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0561] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0562] Fourth aspect of the embodiment

[0563] This application provides a random access device. This device may be, for example, a network device, or one or more components or parts configured within a network device; details identical to those in the third aspect of the embodiment will not be repeated.

[0564] Figure 13 is a schematic diagram of a random access device according to an embodiment of this application. Since the principle of the random access device in solving the problem is the same as the method of the embodiment of the third aspect, its specific implementation can refer to the embodiment of the third aspect, and the contents that are the same will not be repeated.

[0565] As shown in Figure 13, the random access device 1300 of this application embodiment includes:

[0566] The fourth receiving unit 1301 is used to receive a random access preamble in the first valid RO or the second valid RO.

[0567] Wherein, the first effective RO is within flexible time domain resources and / or uplink time domain resources, the second effective RO is in downlink time domain resources and / or flexible time domain resources that overlap with the first time domain resources, or the first effective RO is located in flexible time domain resources and / or uplink time domain resources that do not overlap with the first time domain resources, and the second effective RO is located in the first time domain resources.

[0568] It is worth noting that Figure 13 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 13 above.

[0569] In some embodiments, the apparatus 1300 may further include a fifth receiving unit (not shown in the figure), which is configured to: receive a random access preamble sent by a first terminal device at a first valid RO and / or a second valid RO; and / or receive a random access preamble sent by a second terminal device at a first valid RO.

[0570] In some embodiments, the apparatus 1300 further includes a second transmitting unit 1302, which is used to transmit (to the terminal device) first indication information for configuring random access parameters. The RO configured by the first indication information includes the first valid RO and / or the second valid RO. The second valid RO is not used by the second terminal device to transmit a random access preamble.

[0571] In some embodiments, the first instruction information is as described in the embodiments of the first aspect, the contents of which are incorporated herein and will not be repeated here.

[0572] In some embodiments, the apparatus 1300 may further include a third transmitting unit (not shown in the figure), which is configured to transmit relevant information for determining a first valid RO and / or a second valid RO (to the terminal device), so that the terminal device determines the first valid RO and / or the second valid RO (corresponding to the first indication information) based on the relevant information, and / or determines that the valid RO (corresponding to the first indication information) includes the first valid RO and / or the second valid RO.

[0573] In some embodiments, this relevant information is as described in the embodiments of the first aspect, the contents of which are incorporated herein by reference and will not be repeated here.

[0574] In some embodiments, the apparatus 1300 may further include a fourth transmitting unit (not shown in the figure), which is used to transmit (to the terminal device) first information for indicating the available preamble corresponding to a valid RO and / or second information for indicating the available preamble corresponding to a first valid RO and / or third information for indicating the available preamble corresponding to a second valid RO.

[0575] In some embodiments, the first information, the second information, and the third information are as described in the embodiments of the first aspect, the contents of which are incorporated herein and will not be repeated here.

[0576] In the embodiments of this application, it should be noted that the features or schemes in parentheses, such as "(to the terminal device)", "(corresponding to the first instruction information)", etc., are optional and can be used as a limitation on the feature or not as a limitation on the feature (equivalent to deleting the feature). Due to space limitations, this will not be elaborated here.

[0577] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The random access device 1300 of this application embodiment may also include other components or modules, and for details of these components or modules, please refer to related technologies.

[0578] Furthermore, for simplicity, Figure 13 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0579] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0580] Fifth aspect of the embodiment

[0581] This application also provides a communication system, which can be referred to FIG1. ​​The contents that are the same as those in the embodiments of the first to fourth aspects will not be repeated.

[0582] In some embodiments, the communication system 100 may include at least: a network device 101 and / or a terminal device 102, wherein the network device 101 includes the random access device 1300 in the embodiments of the fourth aspect, and the terminal device 102 includes the random access device 1100 in the embodiments of the second aspect, which will not be described in detail here.

[0583] This application also provides a terminal device, but the application is not limited thereto and may also include other devices.

[0584] Figure 14 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 14, the terminal device 1400 may include a processor 1410 and a memory 1420; the memory 1420 stores data and programs and is coupled to the processor 1410. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0585] For example, processor 1410 may be configured to execute a program to implement the method described in the embodiments of the first aspect.

[0586] As shown in Figure 14, the terminal device 1400 may further include: a communication module 1430, an input device 1440, a display 1450, and a power supply 1460. The functions of these components are similar to those in the prior art and will not be described again here. It is worth noting that the terminal device 1400 does not necessarily include all the components shown in Figure 14; these components are not essential. Furthermore, the terminal device 1400 may also include components not shown in Figure 14, which can be referred to in the prior art.

[0587] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0588] Figure 15 is a schematic diagram of the network device configuration according to an embodiment of this application. As shown in Figure 15, the network device 1500 may include: a processor 1510 (e.g., a central processing unit CPU) and a memory 1520; the memory 1520 is coupled to the processor 1510. The memory 1520 can store various data; in addition, it also stores an information processing program 1530, and executes the program 1530 under the control of the processor 1510.

[0589] For example, processor 1510 may be configured to execute a program to implement the method described in the embodiments of the third aspect.

[0590] In addition, as shown in Figure 15, network device 1500 may also include: transceiver 1540 and antenna 1550, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 1500 does not necessarily include all the components shown in Figure 15; in addition, network device 1500 may also include components not shown in Figure 15, which can be referred to in the prior art.

[0591] Figure 16 is a schematic diagram of a random access procedure according to an embodiment of this application, using a 4-step CBRA as an example. As shown in Figure 16, the method includes:

[0592] 1601, the UE sends a Random Access Preamble (Msg1) to the gNB from the first valid RO or the second valid RO;

[0593] Wherein, the first effective RO (completely) is located within the flexible time domain resource and / or the uplink time domain resource (including or excluding cases spanning two types of time domain resources), and the second effective RO (completely or at least partially) is located in the downlink time domain resource that overlaps with the first time domain resource;

[0594] 1602, The network device sends a Random Access Response (RAR) (Msg2) message to the terminal device;

[0595] 1603, the UE sends a connection request message (Schedule Transmission) (Msg3) on the acquired uplink resources;

[0596] 1604, the network device sends a contention resolution message (Msg4) to the UE that has successfully accessed the network.

[0597] In some embodiments, prior to step 1601, the method may further include: determining a first effective RO or a second effective RO. The determination and selection of the first effective RO or the second effective RO, as well as other operations, can be specifically implemented with reference to the embodiments of the first aspect, and the details that are the same will not be repeated.

[0598] In some embodiments, other operations may also be included, the specific implementation of which can be referred to the embodiments of the first aspect, and the contents that are the same will not be repeated.

[0599] In some embodiments, 1602 to 1604 are similar to the prior art, and will not be described in detail here.

[0600] This application also provides a computer-readable program, wherein when the program is executed in a random access device or network device, the program causes the computer to perform the method described in the third aspect of the embodiments in the random access device or network device.

[0601] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to perform the methods described in the embodiments of the third aspect in a random access or network device.

[0602] This application also provides a computer-readable program, wherein when the program is executed in a signal random access device or terminal device, the program causes the computer to perform the method described in the first aspect of the embodiment in the random access device or terminal device.

[0603] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to perform the method described in the embodiments of the first aspect in a random access device or terminal device.

[0604] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. Logic components include, for example, field-programmable logic devices (FPGAs), microprocessors, and processors used in computers. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, and flash memory.

[0605] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

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

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

[0608] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

Claims

1. A random access device for a terminal device, comprising: The first transmitting unit transmits a random access preamble in a cell at the first valid RO and / or the second valid RO; Wherein, the first effective RO is located within flexible time-domain resources and / or uplink time-domain resources, and the second effective RO is located within downlink time-domain resources overlapping with the first time-domain resources and / or flexible time-domain resources overlapping with the first time-domain resources, or The first valid RO is located in a flexible time domain resource and / or uplink time domain resource that does not overlap with the first time domain resource, and the second valid RO is located in the first time domain resource.

2. The apparatus according to claim 1, wherein, The terminal device is a first terminal device, which has the ability to transmit uplink signals in the first time domain resources and / or downlink time domain resources that overlap with the first time domain resources.

3. The apparatus according to claim 1, wherein, The device further includes: The first receiving unit receives first instruction information for indicating a first terminal device, the first instruction information including information for configuring RO.

4. The apparatus according to claim 3, wherein, The first indication information is dedicated to the first terminal device, and / or the feature or feature combination or device type corresponding to the first indication information includes only the first terminal device or includes both the first terminal device and the second terminal device.

5. The apparatus according to claim 3, wherein, The RO configured by the first indication information includes the first valid RO and / or the second valid RO.

6. The apparatus according to claim 1, wherein, The first valid RO is within flexible time-domain resources and / or uplink time-domain resources that do not overlap with the first time-domain resource; and / or, Not overlapping with downlink time domain resources; and / or Starts after the sixteenth time interval following the last downlink time domain resource; and / or Not overlapping with SSB; and / or Not before the SSB in its PRACH time slot; and / or It begins after the seventeenth time interval following the last SSB; and / or Not overlapping with first-time domain resources; and / or Starts after the eighteenth time interval following the last first-time domain resource; and / or and / or does not overlap with the third RO; and / or In the frequency domain, it is within the first or second frequency domain resources.

7. The apparatus according to claim 1, wherein, The second valid RO is within the first frequency domain resource or the second frequency domain resource; and / or Not overlapping with SSB; and / or Not before the SSB in its PRACH time slot; and / or It begins at least three time intervals after the last SSB; and / or End before at least the fourth time interval of the first SSB; and / or Within the downlink time domain resources that overlap with the first time domain resources; and / or Not overlapping with downlink time domain resources that do not overlap with first time domain resources; and / or It begins at least five time intervals after the last downlink time domain resource that does not overlap with the first time domain resource; and / or Ends at least before the sixth time interval of the first downlink time domain resource that does not overlap with the first time domain resource; and / or It does not overlap with flexible time-domain resources that overlap with first-time-domain resources; and / or Ends at least before the seventh time interval of the first flexible time-domain resource that overlaps with the first time-domain resource, and / or Not overlapping with flexible time-domain resources; and / or End before at least the eighth time interval of the first flexible time-domain resource, and / or Not overlapping with or intersecting with upstream time domain resources; and / or Ends at least before the ninth time interval of the first uplink time domain resource, and / or It does not overlap with flexible time-domain resources that do not overlap with first-time-domain resources; and / or Ends at least before the tenth time interval of the first flexible time-domain resource that does not overlap with the first time-domain resource, and / or Within the first time domain resource; and / or not overlapping with the second time domain resource; and / or Begins at least after the eleventh time interval of the last second time domain resource; and / or End before at least the twelfth time interval of the first second time domain resource; and / or Flexible time-domain resources that do not overlap with first time-domain resources and flexible time-domain resources that do not overlap with first time-domain resources, and multiple overlaps between flexible time-domain resources and uplink time-domain resources; and / or It does not overlap with the third RO.

8. The apparatus according to claim 3, wherein, The cell supports SBFD; and / or The terminal device is provided with information indicating that the cell supports SBFD; and / or The cell only allows the first terminal device to access it; and / or The terminal device is provided with information to indicate that the cell only allows the first terminal device to access; and / or The cell is configured with first time domain resources and / or is configured with first time domain resources in downlink time domain resources; and / or The terminal device is provided with information for indicating the first time-domain resources of the cell; and / or The cell is configured with second frequency domain resources and / or first frequency domain resources; and / or The terminal device is provided with information for indicating the second frequency domain resources and / or the first frequency domain resources; The corresponding UL BWP includes second frequency domain resources determined based on the first frequency domain resources; and / or The terminal device is provided with the common uplink and downlink configuration information of the cell; and / or The cell is configured with downlink time domain resources by public uplink / downlink configuration information; and / or The terminal device is the first terminal device; and / or The terminal device supports random access using downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or The cell allows random access using ROs located in downlink time domain resources and / or downlink time domain resources overlapping with the first time domain resources and / or ROs located in the first time domain resources; and / or The terminal device is provided with information to indicate that the cell allows random access using downlink time domain resources and / or downlink time domain resources that overlap with the first time domain resources and / or ROs located in the first time domain resources; and / or The terminal device is provided with information indicating that the terminal device is permitted to use ROs located in downlink time domain resources and / or in downlink time domain resources overlapping with the first time domain resources and / or in the first time domain resources for random access; and / or The terminal device is provided with information indicating that the RO configured in the first indication information includes and / or excludes a first valid RO and / or a second valid RO; and / or The terminal device is provided with information to indicate enabling and / or de-enabling the first effective RO and / or the second effective RO; and / or The terminal device is provided with information to instruct the terminal device to determine and / or use a first effective RO and / or a second effective RO; and / or The terminal device is provided with information to indicate whether a specific RO is valid and / or invalid.

9. The apparatus according to claim 8, wherein, The device includes a first processing unit, configured to determine a first valid RO and / or a second valid RO corresponding to the first indication information; and / or The RO configured by the first indication information includes a first valid RO and / or a second valid RO.

10. The apparatus according to claim 3, wherein, The RO configured in the first indication information includes a first RO and / or a second RO, wherein the first RO is located within flexible time domain resources and / or uplink time domain resources, and the second RO is located within downlink time domain resources overlapping with the first time domain resources and / or flexible time domain resources overlapping with the first time domain resources; or The first RO is located in a flexible time domain resource and / or uplink time domain resource that does not overlap with the first time domain resource, and the second RO (fully and / or partially and / or at least partially) is located in the first time domain resource.

11. The apparatus according to claim 10, wherein, If the second RO is within the second frequency domain resource or the first frequency domain resource; and / or Not overlapping with SSB; and / or Not before the SSB in its PRACH time slot; and / or It begins at least three time intervals after the last SSB; and / or End before at least the fourth time interval of the first SSB; and / or Within the downlink time domain resources that overlap with the first time domain resources; and / or Not overlapping with downlink time domain resources that do not overlap with first time domain resources; and / or It begins at least five time intervals after the last downlink time domain resource that does not overlap with the first time domain resource; and / or Ends at least before the sixth time interval of the first downlink time domain resource that does not overlap with the first time domain resource; and / or It does not overlap with flexible time-domain resources that overlap with first-time-domain resources; and / or Ends at least before the seventh time interval of the first flexible time-domain resource that overlaps with the first time-domain resource, and / or Not overlapping with flexible time-domain resources; and / or End before at least the eighth time interval of the first flexible time-domain resource; and / or Not overlapping with uplink time domain resources; and / or Ends at least before the ninth time interval of the first uplink time domain resource; and / or It does not overlap with flexible time-domain resources that do not overlap with first-time-domain resources; and / or Ends at least before the tenth time interval of the first flexible time-domain resource that does not overlap with the first time-domain resource; and / or Within the first time domain resource; and / or not overlapping with the second time domain resource; and / or Begins at least after the eleventh time interval of the last second time domain resource; and / or End before at least the twelfth time interval of the first second time domain resource; and / or Flexible time-domain resources that do not overlap with first time-domain resources and flexible time-domain resources that do not overlap with first time-domain resources, and multiple overlaps between flexible time-domain resources and uplink time-domain resources; and / or If it does not overlap with the third RO, then the second RO is effective.

12. The apparatus according to claim 3, wherein, The device further includes a second receiving unit, which is used for: Receive information indicating that the cell supports SBFD; and / or Receive information for indicating the first time-domain resources of the cell; and / or Receive information indicating a first frequency domain resource and / or a second frequency domain resource; and / or Receive public uplink and downlink configuration information; and / or Receive information indicating that the cell allows random access using ROs located in downlink time domain resources and / or located in downlink time domain resources overlapping with the first time domain resources; and / or Receive information indicating that the terminal device is permitted to use ROs located in downlink time domain resources and / or in downlink time domain resources overlapping with the first time domain resources for random access; and / or Receive information indicating that the RO configured by the first indication information includes and / or excludes a first valid RO and / or a second valid RO; and / or Receive information indicating to enable and / or de-enable the first valid RO and / or the second valid RO; and / or Receive information for instructing the terminal device to determine and / or use a first valid RO and / or a second valid RO; and / or Receive information indicating whether a specific RO is valid and / or invalid; and / or Receive information indicating whether PRACH transmission is permitted and / or not permitted on the SSB symbol; and / or Receive information indicating whether PRACH is allowed and / or not allowed across the first and second time domain resources.

13. The apparatus according to claim 12, wherein, The device further includes a fourth processing unit, which is used for: Based on the information, determine the first effective RO and / or the second effective RO (corresponding to the first indication information).

14. The apparatus according to claim 1, wherein, If the first RO is within flexible time-domain resources and / or uplink time-domain resources that do not overlap with the first time-domain resources; and / or Not overlapping with downlink time domain resources; and / or It begins after the sixteenth time interval following (its) last downlink time-domain resource; and / or Not overlapping with SSB; and / or Not before the SSB in its PRACH time slot; and / or It begins after the seventeenth time interval following the last SSB (preceding it); and / or Not overlapping with first-time domain resources; and / or Beginning after the eighteenth time interval following the last first time domain resource (where the values ​​of the first and second time intervals are the same or different); and / or and / or does not overlap with the third RO; and / or If the first RO is within the first frequency domain resource (uplink available resource) or the (cell-specific) second frequency domain resource (uplink subband), then the first RO is valid.

15. The apparatus according to claim 3, wherein, When the RO configured by the first indication information includes a first valid RO and a second valid RO; or During the same random access process, the terminal device sends a random access preamble only in the first valid RO or only in the second valid RO; or During the same random access process, the terminal device sends a random access preamble to the first valid RO and / or the second valid RO.

16. The apparatus according to claim 1, wherein, The device further includes a third receiving unit, which is used for: Receive first information for indicating the available preamble corresponding to a valid RO and / or second information for indicating the available preamble corresponding to a first valid RO and / or third information for indicating the available preamble corresponding to a second valid RO.

17. The apparatus according to claim 1, wherein, The device further includes a fifth processing unit, which is used for: Mapping SSBs to the first valid RO and / or mapping SSBs to the second valid RO; or Map SSBs to the first valid RO and the second valid RO.

18. A random access device, applied to a network device, comprising: Receive random access preamble in the first valid RO and / or the second valid RO; The first valid RO is located within flexible time domain resources and / or uplink time domain resources, and the second valid RO is located within downlink time domain resources overlapping with the first time domain resources and / or flexible time domain resources overlapping with the first time domain resources.

19. The apparatus according to claim 18, wherein, The device further includes a fourth receiving unit, which is used for: Receives a random access preamble sent by the first terminal device at the first valid RO and / or the second valid RO; and / or The first valid RO receives the random access preamble sent by the second terminal device.

20. The apparatus according to claim 18, wherein, The device further includes a second transmitting unit, which is used for: Send first indication information for configuring random access parameters, wherein the RO configured by the first indication information includes the first valid RO and / or the second valid RO, and the second valid RO is not used by the second terminal device to send a random access preamble.

Images